Skip to Content
author's profile photo Former Member
Former Member

SMQ2 Error in ECC : ThISend: bad tm type / connection closed (no data)

Hi Guru's,

I am working on scenario FTP ---> PI ---> Proxy.

Messages are processed successfully from PI and when i checked in ECC sxmb_moni they are in schedule status(Green flag).

In SMQ2 of ECC i found messages got struck in que's with below error message :

ThISend: bad tm type / connection closed (no data).

I tried to unlock the que's but its not working.

When i tried to check the proxy in SPROXY with same xml data, its updating properly.

But i am getting the message : "Successful with empty result - commit may be required in ECC 6".

So , Any one suggest why the messages struck up in the ECC que.

Thanks in advance for your time and quick help.

Regards

Suresh

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Posted on Sep 13, 2012 at 11:52 AM

    Hi Suresh,

    Did you see in st22 is there any dump By PI remote user. if yes then check for that also. and is there any batch job is trigger by proxy check for that also.

    Regards

    Gagan

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Sep 13, 2012 at 12:10 PM

    Hi Suresh,

    Check if your Integration Engine configuration in SXMB_ADM if the path prefix is /sap/xi/engine?type=entry

    Regards,

    Naveen.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 13, 2012 at 01:10 PM

    Hi Suresh,

    Could be an issue with the Proxy code. "During background processing, the system attempted to send a screen to a user." This could be the reason why SPROXY test is working as it is not background processing.

    Can you please have the ABAP team check the code.


    Regards,
    Sathya

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi,

      Yep, this is what I think it is too...You need to catch all exceptions appropriately in the Abap code. Test proxy with the incoming payload through SPROXY on ECC & take it through the debugger. You'll pick it up that way.

      Regards, Trevor

  • author's profile photo Former Member
    Former Member
    Posted on Jun 29, 2016 at 06:52 AM

    Hello All,

    I am having the same issue and for me some of the messages are getting processes and some are getting in error with " thisend: bad tm type / connection closed no data :".

    Thanks,

    Avakash

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.