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

[Former Member]

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

[Former Member]

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

[Former Member]

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

[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

[naveen_chichili]

Hi Suresh,

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

Regards,

Naveen.

[gagandeep_batra]

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

[Former Member]

Hi Gangadeep,

I have checked in ST22 for user PIAPPL_XXX, i saw error DYNPRO_SEND_IN_BACKGROUND.

Error analysis

    An exception occurred that is explained in detail below.

    The exception, which is assigned to class 'CX_SY_SEND_DYNPRO_NO_RECEIVER', was

     not caught and

    therefore caused a runtime error.

    The reason for the exception is:

    During background processing, the system attempted to send a

    screen to a user.

    Current screen: "MP001400 " 2010.

And there is no batch job for this proxy.

Can you suggest , how to proceed further with abobe error.

Regards

Suresh

[gagandeep_batra]

Hi Suresh,

can you check your proxy connection from PI to ECC is working fine.

and check following link that may help you.

http://scn.sap.com/thread/1925702

Regards

Gagan

[Former Member]

Hi Gagan,

Actually its a issue with some abap code. After doing some chnages to abap code, the messages are posted into ECC by unlocking the ques from SMQ2.

But now the issue is : when ever we push the messages from PI to ECC they are struck in ECC SMQ2 with READY status. When we unlock the que, all the messages are processing successfully.

Can any one suggest , why this is happening.

Regards

Suresh

[gagandeep_batra]

hi Suresh,

did you check the status of the queue in SMQR?

and try to unregister & unregister the Queue

Regards

Gagandeep