cancel
Showing results for 
Search instead for 
Did you mean: 

JMS Delievery Problem

frank_schmitt3
Participant
0 Kudos

Hi,

After having deployed SP7 we have problems with the delievery of JMS

Messages in a scenario that uses the Sync/Async Bridge with Adapter

Modules.Our receiver ist xy, that offers an Request/Reply

Service with Queues, our Sender is a synchronous Web Service Client via

SOAP Adapter.

The Problem is, the JMS Messages never get delievered to the Request

Queue, so the client receives a Message expired Exception.

On the channel monitoring we see a confusing message that says that the

message was processed but ignored.

Here s the orginal message in German Language:

"XI-Message d5ed86c0-6fb9-11de-8041-00144f805f2a wurde erfolgreich als

JMS-Message mit ID d5ed86c06fb911de804100144f805f2a beim Empfänger

verarbeitet und aus diesem Grund ignoriert."

We set up a trace in receiver system and we can see the message never appears

there.

In the Audit Log of the failed request messages we see the error

message "Unable to read payload from the message object" with the SAP

Category XIServer and the SAP:Code area="MAPPING", which doesn t makes

sense to us, as the message gets transformed succesfully.

The secanrio worked before deploying the Service Pack and we didn t

change anything about the configuration.

Can you anyone give uns infos?

Thanks in advance,

Frank

View Entire Topic
Former Member
0 Kudos

Hi Frank,

can you give some more details about your scenario / systems please?

E.g. PI 7.0 or 7.1, JMS provider and version, deployed JMS libraries, ...?

Thanks,

Kai

frank_schmitt3
Participant
0 Kudos

Hi,

we are using PI 7.1 SPS7 an Tibco Enterprise Message Server 4.4.1; libraries Enterprise Message Service 4.3.0.

Thanks,

Frank

Former Member
0 Kudos

Hm - I am not very familiar with Tibco, but had also problems after SP upgrades on PI 7.0 and MQ series 6.

I can only suggest to contact Tibco and / or SAP for some support on this issue.

Ours had been solved by a OSS note which had been released.

Regads,

Kai

Former Member
0 Kudos

Hello Kai,

Could you please let us know the OSS note number through which you got this problem solved. Currently we are in the same situation.

Regards,

Vijay