cancel
Showing results for 
Search instead for 
Did you mean: 

Messages are on HOLD in runtime workbench

Former Member
0 Kudos

Hi All,

I need your help. I don't know how to solve the following problem.

We have a message (idoc xml with a standard business document header from a gs1 xml) which will be send from a logical system in XI to another logical system in xi (same system).

The mapping is from one message - to more messages. This means one message comes in and dependent from the message two different message types could be go out (only one at one time). If the mapping is to one of these interface then it is also possible that one incoming message can create two or more output messages (same message type). And with this I have the problem. If more then one message is created in this mapping then this messages stay on hold in the runtime workbench. (If only one message is created, it is working fine). The QoS is for the messages "Exactly Once In Order" - thats what I see in the runtime workbench. The QoS in the sender communication channel is "Exactly Once".

Do you have any idea?

Thanks and regards

Manuela

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Manuela !

First, check in RWB or SXMB_MONI why the message is on hold, maybe, because of the QoS=EOIO there is a previous message blocking the queue. Check all messages for that interface using the filters.

Regards,

Matias.

Former Member
0 Kudos

Hallo Matias,

thanks for your answer.

In SXMB_MONI I can not find these messages.

I can not see a previous message in the runtime workbench wich has an error. But I can not search on queue name in rw.

The problem is that it should not be "EOIO" it only should be "EO". And the commchannel is configured as "EO" but why it has then "EOIO"? Is there a different configuration if you have an interface collection (the mapping from one interface to two different interfaces) between?

Thanks and regards

Manu

Former Member
0 Kudos

Hi Manuela,

if your queue is stuck you will see in sxmb moni in the Q status column. There will be a STOP mark. Then dblclick the queue id and try to find out, what's wrong. Then process or delete the message, which has caused the error in the queu. After this will be messages processed.

Peter

Former Member
0 Kudos

Hi Manuela !

QoS is determined by the sender. Try to check the sender comm channel and make some dummy changes (e.g. modify the description) and save it and reactivate it.

Another temporary idea, open the sender channel, select QoS=EOIO, and enter some queue name. Making the scenario use a different queue will skip the blocked queue that is on HOLD right now.

Regards,

Matias.

Former Member
0 Kudos

Hi Peter,

I see no STOP marker and if I doubleclick on the queue name - the queue is empty.

But I can not restart the HOLD messages in the runtime workbench as well.

Regards

Manu

Former Member
0 Kudos

Hi,

What kind of message can you see when you go inside message in RWB? Please check if CC is active.

Best regards,

WG

Former Member
0 Kudos

Hi Matias,

I checked the sending comm channel - there is as QoS " Exactly Once".

And this I see in the trace for this message:

<SAP:Receiver>

<SAP:Party agency="" scheme="" />

<SAP:Service>EU_GBO</SAP:Service>

<SAP:Interface namespace="http://sap.com/xi/XI/System">InterfaceCollection</SAP:Interface>

- <SAP:Mapping notRequired="S">

<SAP:ObjectId>b7MX71ixNta+q25WeTTMQA==</SAP:ObjectId>

<SAP:SWCV>qHLzgJMLEdqrbvR4kTdAeQ==</SAP:SWCV>

<SAP:SP>-1</SAP:SP>

</SAP:Mapping> </SAP:Receiver>

<SAP:Interface namespace="http://sap.com/xi/XI/System">InterfaceCollection</SAP:Interface>

</SAP:Main>

- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>

But in the runtime workbench I see as QoS "Exactly Once in Order". Can I insert pictures here?

The reactivating I tried - did not help :(!

I really don't know what to do...

Thanks and regards

Manu

Former Member
0 Kudos

Have you checked the receiver determination there is quality of service?

Best regards,

Wojciech

Former Member
0 Kudos

Hii WG,

what is CC?

That is the Message Type in the rwb "Recv".

Thanks and regards

Manuela

Former Member
0 Kudos

Hi Wojciech,

I checked the receiver determination. But I could not find a QoS there. Where should it be?

Thanks and regards

Manuela

Former Member
0 Kudos

CC = Communication Channel.

The QoS is stated always in the SENDER communication channel object, depending of the type of adapter could be indicated externally when sending the data to XI.

Regards,

Matias

Former Member
0 Kudos

Hi Mathias,

thats the information in the rwb:

Attribute Value

Status Holding

Repeatable Yes

Cancelable Yes

Error Category

Error Code

Start 07.02.2008 10:46:59

End

Sender Party

Sender Service EU_GBO

Receiver Party

Receiver Service EU_GBO

Interface http://unilever.com/Xproc/ProcComm/GS1/ItmDtaNot/xi

Align_Item_Data_Notification_V2_1_ABS

Quality of Service Exactly Once in Order

Message 47aa17db-8e63-0158-0000-000091374080

Reference

Conversation ID MMFSERIALIZE0018

Version 0

Edited No

Serialization Context INBOUND_MMFSERIALIZE0018__

Direction INBOUND

Message Type Recv

Profile XI

Connection SOAP_http://sap.com/xi/XI/System

Transport HTTP

End Point http://ex1c002a:58300/MessagingSystem/receive/AFW/XI

Authorization

Sequential Number 105

Number of Retries 3

Failed 0

Retries 300000

Valid to

Persist Until 14.02.2008 10:46:59

Schedule Time 07.02.2008 10:46:59

2008-02-07 10:46:59 Success Processing child message of multi-message with message ID 47aa0c4f-ce91-0122-0000-000091374080

2008-02-07 10:46:59 Success Using connection SOAP_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.

2008-02-07 10:46:59 Success Message successfully put into the queue.

2008-02-07 10:46:59 Success The message was successfully retrieved from the receive queue.

2008-02-07 10:46:59 Success The message status set to HOLD.

MMh external I think is not possible. Because it comes from a logical system in XI and goes from a logical system to XI. But on step before it comes from a SAP system. COuld it be there?

REgards

Manuela

prateek
Active Contributor
0 Kudos

Inside Interface Mapping, remove the checkbox "Maintain Order at Runtime"

Regards,

Prateek

Former Member
0 Kudos

Hi Prateek,

yes now it is working. Super thank you very much,

But one question on dev and prod the checkbox is activated and there it is working without any problems.

Why?

Regards

Manuela

prateek
Active Contributor
0 Kudos

Ur welcome.

It was an unusual behaviour in ur box as it was working on dev n prod. Better is to be ready with the workarounds

Please close the thread.

Regards,

Prateek

Answers (0)