cancel
Showing results for 
Search instead for 
Did you mean: 

Message Status as scheduled..

Former Member
0 Kudos

Hello All,

I configured scenario which use SOAP as sender and XI Adpter as receiver.

It is syncrnous call. I can see different message status...

intiatially it came as black triangle --> scheduled for outbound processing.

Now, It is showing Green flag which is just sceduled......

What is wrong and how to troubleshoot further....

Thanks,

Srini

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

See below SAP Note 1118297:

Liang

=====Note 1118297===========

Symptom

You are using the Exchange Infrastructure and you are processing asynchronous messages. These messages are scheduled in queues that are no longer processed. The inbound queue of the qRFC Monitor (transaction SMQ2), for example, contains entries with the status "Running". However, you recognize in the process overview (transaction SM50) that there is no active work process.

Other terms

QRFC, SXMS_ASYNC_EXEC, inbound, running, resource

Reason and Prerequisites

You are using the Exchange Infrastructure and you are processing asynchronous messages. These message are scheduled in the QRFC and are only processed slowly or not at all.

Solution

The asynchronous messages are scheduled in the queues.

Check the following points of your middleware.

Queue configuration:

If the QRFC Inbound Scheduler is configured, see Note

369007.qRFC: Configuration for the QIN Scheduler

Are the XI queues registered and active? In transaction SXMB_ADMIN->Administration->Manage Queues, you can register the queues for the XI runtime.

If the resources are configured for TRFC/QRFC, note the common usage of system resources. For further details, see Notes

74141 Resource management for tRFC and aRFC

527481 tRFC or qRFC calls are not processed

For the qRFC resources see Note

1051445 qRFC scheduler does not use all available

resources

For further information see Unit 3.1 of the "SAP Exchange Infrastructure Tuning Guide", which you can download from the marketplace.

In the XI configuration you can set locks for the processing of XI messages. Note that for many parallel queues there are also sufficient resources for lock objects. At least one enqueue entry is required for each queue, depending on the configuration. For further information see Notes

552289 FAQ: Lock management R/3

654328 Enqueue: System log message GE9

Queue status:

Transaction SMQ2 contains queue entries with the following status

"Running"

If the J2EE engine is downloaded in production mode with the mapping engine or recipient Adapter Framework, processing QRFC entries may not recognize this and remain in the "Running" status. A symptom can be, for example, that the RFC destination "AI_RUNTIME_JCOSERVER" is no longer registered. You can find this information in the Gateway Monitor (transaction SMGW).

Otherwise, the system may reach this status if the application server is downloaded in a controlled manner, and long-running processes can no longer terminate.

The system no longer processes any message. In transaction SMQR, you can activate the queues manually again. You can also schedule the report RSQIWKEX, which automatically restarts the queues. For further information see Notes

620633 Status RUNNING in SMQ2 with XI queues

864333 RSQOWKEX & RSQIWKEX start Running(Executed) queues

"Sysfail"

A queue entry with the status "Sysfail" can have two possible causes.

1. Further processing cannot be carried out on the process for technical reasons (for example, the program terminates with a dump or a system (mapping or recipient system cannot be reached).

2. Queue processing should be stopped, as the message cannot be processed, due to a configuration error. Processing is not permitted for the subsequent messages, as the queue sequence displays the message sequence. You can use the report RSXMB_RESTART_MESSAGES to restart the message processing again. See Note

813029 Automatic processing of failed XI messages

XI-QRFC and IDoc-TRFC processing:

Note that when you use the IDoc adapter this uses the RFC/TRFC resources, which are used together with the QRFC resources. This means an intensive usage of the TRFC can influence the performance of the XI queue message processing. When possible always use the package processing of the IDoc adapter (transport of several IDocs with an RFC call to the recipient system):

1. Package created from an IDoc XML payload with several IDocs

2. Packaging, package created with IDoc package filter

3. Package created with message packaging (queue message package)

(as of NW2004s)

For more information about acknowledgements, see also Note:

1111968 IDoc adapter: Parallel processing of acknowledgements

to reduce the number of acknowledgement queues.

Tuning Balancing parameter :

The BALANCING parameter activates the entries for the parameters B_EO_IN_PARALLEL_SENDER, B_EO_OUT_PARALLEL and B_EO_IN_PARALLEL.

They are used if the number of parallel queues is changed and the messages are distributed to the new queues. A balancing procedure is already used in the Standard System to distribute the messages equally to the queues. If the Balancing parameter is continually active, it has a negative impact on performance (as queue entries are constantly distributed between the queues and this means they cannot be processed). This can cause problems during queue processing.

Its use in the Tuning Guide is not described clearly.

Oracle database:

When using an Oracle database see Note

742950 Performance affected on Oracle DB with supplement 11

if you discover performance problems when processing queue entries. This improves the scheduling process only, and not the processing time of a queue entry.

See also Note

1020260 Delivering Oracle statistics

EO (exactly once) handling of XI-Messages when you restart QRFC entries:

The XI log guarantees the uniqueness of the transfer between the client and server. A restart does not trigger a double execution of messages. Note that a synchronization of the reorganization between client and server is guaranteed. The EO recognition is executed with the message ID. The retention time determines the amount of time this information is retained in the system for.

The individual messages are saved to the database in the system with a key from the message ID and version. This prevents a parallel execution of the same message. A queue entry can be executed in parallel using the report RSQIWKEX or by carrying out a manual start from the queue. We recommend to set the parameter LOCK_MESSAGE (default value is active "1") of the category "RUNTIME" in the XI configuration to the value '0'. More information is contained in Note

1058915 Outbound queue remains in status 'SYSFAIL'

=====End of Note 1118297===========

Answers (4)

Answers (4)

Former Member
0 Kudos

Hello guys,

Thanks a lot for your replies. I am slowly understnding these queues and how to guide is really helpful.

Thanks,

Srinivasa

Former Member
0 Kudos

Hello,

Thank you for suggestions. I thought these queues register in XI automatically.

When i send messagess, different queue are listed for differents messages.

So, I registered all. But, what is the point of having many queues. i know these are based on Priority, but how prioriy can be set.

What is the scenario where i can tell my message that go to this queue because i already defined this queue as highest priority.

this will be helpful if somebody provide more details to understand.

thanks,

Srini

Former Member
0 Kudos

HI,

Refer the below link it will give u all ur answer to ur questions

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/59e837d3-0201-0010-c096-dc186973...

/people/sap.user72/blog/2005/12/12/how-to-prioritize-messages-in-xi

thnx

chirag

Former Member
0 Kudos

Your messages might be stuck in Queues. Check in SMQ2 or SMQ1

More on queues

/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

Former Member
0 Kudos

Hi,

Have you already discovered where the message stoped?

Try going to RWB, Message Monitoring and search for your message. Check Adapter Engine log for this message, and go to audit log. Analyse the entries there, you can get some tip to discover where is the problem.

regards.

roberti

agasthuri_doss
Active Contributor
0 Kudos

Hi,

>It is showing Green flag which is just sceduled......

Check the Queues status.

Check whether the Queues got Registered.

Go to SXMB_ADM -> Manage Queues -> Register Queues

Regards

Agasthuri Doss