Skip to Content

Inbound proxy scenario, the messages are getting stuck in ECC t-code smq2

Hi Experts,

Soap to XI scenario.

Here we are using XI receiver so that we can push messages to ECC.

The RFC destination which we're using in receiver channel will give status code 500 when we do test connection.

Messages are getting delivered from PI and reaching ECC successfully but as soon as we receive them it'll be stuck in queue(SMQ2). Then once release them they're changing in success status.

One more thing to add, when we keep external break point for the code written in ECC it will not trigger through that breakpoint.

We can only see messages in SXMB_MONI(ECC) which is in scheduled status.

Please help me to resolve this error.

Here if I execute it'll change the message status to success from scheduled status.

Regards,

Vidhya Nizamkar

capture.png (9.5 kB)
capture1.png (10.5 kB)
capture2.png (9.4 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Dec 10, 2016 at 01:57 AM

    Hello Vidhya,

    1. In tx. SXMS_QREG or SXMB_ADM > Manage Queues, check that corresponding Integration Engine queues are registered - if not, register them.
    2. Cross-check in tx. SMQR, that respective queues (XB*) are registered at qRFC Inbound Scheduler (by observing them in a list of registered queue names).

    Regards,

    Vadim

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 09, 2016 at 10:26 AM

    Check there are any locks in SM12 and/or check for any dumps in ST22 which give you hint about the behavior

    - Nikhil Bose

    Add comment
    10|10000 characters needed characters exceeded