cancel
Showing results for 
Search instead for 
Did you mean: 

Adapter Status Error : Error in creating message ID map for JMS message:

Former Member
0 Kudos

Currently in the SAP XI 3.0 JMS Adapter, I am receiving the following error

Error in creating message ID map for JMS message:

ie. Error while processing message 'de8265f6-c864-4479-1137-9bab17b78b3b'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterException: Error in creating message ID map for JMS message: ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:103)

Although I am receivng this error, when I check the details of the message processing, all steps are successful and the message is set to status : DLVD

Audit Log for Message: de8265f6-c864-4479-1137-9bab17b78b3b

Time Stamp Status Description

09.06.2009 13:27:24 Success New JMS message with JMS message ID ID:c3e2d840d8d4d7f14040404040404040c44f8e2213630b01 received. The XI message ID for this message is de8265f6-c864-4479-1137-9bab17b78b3b

09.06.2009 13:27:24 Success JMS message converted to XI message format successfully

09.06.2009 13:27:24 Success RRB: entering RequestResponseBean

09.06.2009 13:27:24 Success RRB: suspending the transaction

09.06.2009 13:27:24 Success RRB: passing through ...

09.06.2009 13:27:24 Success RRB: leaving RequestResponseBean

09.06.2009 13:27:24 Success Transform: using Transform.Class: com.sap.aii.messaging.adapter.Conversion

09.06.2009 13:27:24 Success Transform: transforming the payload ...

09.06.2009 13:27:24 Success Transform: successfully transformed

09.06.2009 13:27:24 Success Application attempting to send an XI message synchronously using connection JMS_http://sap.com/xi/XI/System.

09.06.2009 13:27:24 Success Trying to put the message into the call queue.

09.06.2009 13:27:24 Success Message successfully put into the queue.

09.06.2009 13:27:24 Success The message was successfully retrieved from the call queue.

09.06.2009 13:27:24 Success The message status set to DLNG.

09.06.2009 13:27:25 Success The application sent the message synchronously using connection JMS_http://sap.com/xi/XI/System. Returning to application.

09.06.2009 13:27:25 Success The message was successfully transmitted to endpoint http://sapxia.swets.nl:8000/sap/xi/engine?type=entry using connection JMS_http://sap.com/xi/XI/System.

09.06.2009 13:27:25 Success The message status set to DLVD.

Not sure why this is occurring.......

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

No, not using correlation id.

I was able to resolve the issue on this queue by changing the following setting

Under the PROCESSING tab, under XI SETTINGS

Time period for Duplicate Check for EO(IO) (secs) it was set to 86400

I have changed this to 300 seconds and the adapter has now gone green.

BUT......

That said, I have the exact scenario on another sender JMS channel set to 300 seconds and it exhibits the same issue.

correlation settings:

Set XI message id to = GUID

Set Xi conversation

Former Member
0 Kudos

Set SAP XI Conversation ID = JMS Message ID

Sorry Yes, I am using correlation ID....

Receiver channel setting the JMSCorrelationID = XI Conversation ID

Former Member
0 Kudos

Ok, in this case you need to make sure that the time for messages checking EO(IO) is propper. How often do the messages come? If refering messages arrive e.g. within 60 min then setting the value to 300s should be okay.

Also you should check the option "persist messages".

Kai

Former Member
0 Kudos

Stopping and Re-Starting the channel fixed the issue.

Former Member
0 Kudos

No this is a sender channel (outbound interface)......

Former Member
0 Kudos

Okay. then the link should be:

http://help.sap.com/saphelp_nwpi711/helpdata/en/f4/2d6189f0e27a4894ad517961762db7/content.htm

Do you use correlation settings?

Former Member
0 Kudos

Hi,

I assume this is a receiver channel, right?

So you may check the settings in the channel configuration regarding:

- persistence settings (Persist / Do Not Persist JMS Messages in the JMS Provider)

- Correlation Settings (point 14-17 in the link below)

http://help.sap.com/saphelp_nwpi711/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm

Kai