on 11-24-2011 5:18 PM
I have PI 7.0 connecting to WMQ 6.0 using JMS adapter.
The scenario in technical terms is a IDoc to JMS scenario. For one of the message flows, PI delivered an empty message to the MQ queue.
Having checked the audit logs and the MessagingSystem etc, there were no clues why this happened.
In the Message monitoring, on the content tab , in the drop down, i could only see the SOAP envelope. The message content wasnt available in the drop down at all.
Any clues why this may have happened?
There is no content conversion and we are delivering XML to the queues.
hi,
In the Message monitoring, on the content tab , in the drop down, i could only see the SOAP envelope. The message content wasnt available in the drop down at all.
Ok, but here you see the message received by your JMS, so the interest is limited. You need to compare your source message (idoc) to your target message (JMS). here's how to check.
Go to SXMB_MONI, select your message and then "detail" button.
In the left tree, open the FIRST level called "Inbound Message (CENTRAL)". And under this level check your Payload (should be your Idoc sent by ECC).
Then, in the same left tree, go to a level before "Call adapter", for instance in "XML validation Outbound Channel Request". Under this level, check your Payload (that should the XML sent to your JMS). Note: do not go in "response" level, because there is certainly no payload.
What do you have ? does your target payload is empty ? (certainly yes)
if yes, that's mean it's your mapping that something is wrong. Certainly a bad context management, due to a missing "SpliByValue" or something like that. And you certainly have one target message with the content of two idoc segment, whereas this one is empty.
To know which mapping link is bad, in SXMB_MONI, download the source message (so under level "Inbound Message (CENTRAL)", and test it i your Message Mapping.
regards.
mickael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
ah. so not a mapping issue... unfortunately.
1. maybe you have a too lowest trace level to see the payload content, or someone plays with authorizaiton and you cannot see the payload of a JMS, or with JMS it's not possible to see the payload (check with help on JMS adapter).
2. another possibilty could be CPA cache problem; because if issue is not in mapping, it is just after, so in adapter.
Mickael
Edited by: Mickael Huchet on Nov 24, 2011 6:14 PM
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.