JMS Sender ADAPTER SAP PI

[Former Member]

When we Receive a Message via JMS we get alwayls following Error. This is caused bacause we always receive the Same JMS Message ID. Can this been solved ?

4/6/09 3:55:57 PM 11b01762-4722-4847-0d15-e83197359d6d A duplicate JMS message was received. It was was received earlier and processed with XI message ID 11b01762-4722-4847-0d15-e83197359d6d. It will be ignored and discarded from the JMS queue. 4/6/09 3:55:57 PM ba725a6b-d826-47d6-17cf-b72b957a51aa Added dynamic header: DCJMSMessageID to XI message ba725a6b-d826-47d6-17cf-b72b957a51aa which corresponds to JMS property: JMSMessageID that has the value "TESTMOBILE" in JMS message "TESTMOBILE"

4/6/09 3:55:57 PM ba725a6b-d826-47d6-17cf-b72b957a51aa Added dynamic header: DCJMSCorreleationID to XI message ba725a6b-d826-47d6-17cf-b72b957a51aa which corresponds to JMS property: JMSCorrelationID that has the value ID:433030303030303030303132353837383100000000000000 in JMS message "TESTMOBILE"

4/6/09 3:55:57 PM ba725a6b-d826-47d6-17cf-b72b957a51aa XI message ID corresponding to JMS message with ID "TESTMOBILE" will be created as a new GUID with value ba725a6b-d826-47d6-17cf-b72b957a51aa

4/6/09 3:52:56 PM 11b01762-4722-4847-0d15-e83197359d6d Channel successfully processed message: 11b01762-4722-4847-0d15-e83197359d6d

4/6/09 3:52:55 PM 11b01762-4722-4847-0d15-e83197359d6d Added dynamic header: DCJMSCorreleationID to XI message 11b01762-4722-4847-0d15-e83197359d6d which corresponds to JMS property: JMSCorrelationID that has the value ID:433030303030303030303132353837373900000000000000 in JMS message "TESTMOBILE"

[rosh]

Hi Filip,

if you have DB access you could go to "XI_AF_SVC_ID_MAP" and delete the line according to the PI/JMS message id. This is a very enterprisey solution that I highly recommend

The id-maps also have an individual expiration date, so you could just wait (I don't know when the JMS-Messages expire).

Alternatively you should stop the message in the sender-system and generate a new JMS message.

Regards

[Former Member]

Hi

is it normal behavior that the messages are not stored in PI , but removed from the MQ ?

We use alse the parameter Time Period For Duplicate checks, we use 1 second, but this is not working. The records are still in table "XI_AF_SVC_ID_MAP".

When we remove the entry in thsi table manually the message is processed.

Thxs

[rosh]

Hello,

the problem is in the message ID's. I guess your sender channel is set to "Exactly Once" - that means when a message is already processed it cannot be processed once more.

Whether the messages should be rejected rather than deleted is arguable, but you're not going to change that :(. (Have you tried synchronous messaging? Maybe the ID is not checked there)

However the root cause is of course the JMS sender generating different messages with the same ID. You might want to change that.