| Author |
Message
|
| mdilovski |
 Posted: Tue Aug 30, 2022 10:54 pm Post subject: IBM ACE 12 MRM Message Set Issue |
 |
|
Newbie
Joined: 30 Aug 2022
Posts: 4
|
Hello Everyone,
I hope you are doing well!
We are using IBM App Connect v12.0.2.0 on premise on Windows. We are experiencing a strange issue with a particular message set. It is parsing without a problem on most of the Integration Servers, but on others it is not able to parse successfully. The message set is MRM. Here are the things that we have tried and we were not able to resolve the issue:
1. Deploy the application to another Integration Server in the same node.
2. Delete the application and deploy it again.
3. Create a new Integration Server on the same Integration Node and deploy the application to it.
4. Deploy the application to another Integration Server on a different node.
5. Create a new Integration Server on another node and deploy the application to it.
6. Increase the max heap memory of the integration server and make it double.
7. Create a new integration node and new integration server on it.
8. Create a new project from scratch.
Is there some kind of a hidden cache or any setting that could cause this strange behavior.
Have a great day! |
|
| Back to top |
|
 |
| timber |
| Posted: Wed Aug 31, 2022 7:26 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
| Please quote the full text of the parsing errors. |
|
| Back to top |
|
|
| mdilovski |
| Posted: Wed Aug 31, 2022 8:05 am Post subject: |
|
|
Newbie
Joined: 30 Aug 2022
Posts: 4
|
Unfortunately there is no Parsing error, otherwise it would be easier to be resolved. Here is a screenshot in debug mode:
ibb.co/VtQ5dcs
*Sorry for not being able to set the image correctly, but I need to have more posts in order to add URLs |
|
| Back to top |
|
|
| timber |
| Posted: Thu Sep 01, 2022 2:27 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
I am not going to click on your URL - that is a security risk. Please describe the problem.
You said:
| Quote: |
| It is parsing without a problem on most of the Integration Servers, but on others it is not able to parse successfully. |
If it does not parse successfully then there are 2 possibilities:
a) there was a parsing error, and it will be reported somewhere.
b) there was no parsing error, but the message tree created by the MRM parser was not correct.
Which is it? |
|
| Back to top |
|
|
| mdilovski |
| Posted: Thu Sep 01, 2022 7:47 pm Post subject: |
|
|
Newbie
Joined: 30 Aug 2022
Posts: 4
|
| The problem is that there is no parsing error, but the message tree created by the MRM parser was not correct. The same MRM message set is parsing without a problem on another Integration Server, but when I deploy this application to other Integration Server again it is not able to parse it. Usually this was working and stopped working without introducing any new changes to the message set. |
|
| Back to top |
|
|
| timber |
| Posted: Fri Sep 02, 2022 1:30 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
There are no hidden caches or other features. I cannot comment on the causes without knowing a lot more about the problem.
You need to supply all of the following information without using screenshots please:
- the input message (with any confidential content changed)
- the correct message tree
- the incorrect message tree |
|
| Back to top |
|
|
| mdilovski |
| Posted: Sun Sep 04, 2022 7:26 pm Post subject: |
|
|
Newbie
Joined: 30 Aug 2022
Posts: 4
|
| We were able to resolve the issue. The problem was that the MRM Message Set usually was having a <CR> as group terminator, but in the message there was also a <LF>. After modifying the payload and removing this unnecessary LF, the issue was resolved. |
|
| Back to top |
|
|
|
|
