cancel
Showing results for 
Search instead for 
Did you mean: 

Message struck at inbound que in server proxy

former_member859847
Active Contributor
0 Kudos

Sub :Message struck in SMQ2 with status text"ThiSend:bad tm type" .

HI,

I executed inbound proxy form PI 7.0, the message was struck in the inbound queue of ECC 6.0,

with status text "ThiSend:bad tm type /connection closed (no data)".

when i test the same message from 'SPROXY' t.code, inbound proxy class was working fine.

I came to know the message scheduled due to function

module sxms_async_exec

and raising an exception as ThiSend:bad tm type/

connection closed (no data)

please provide the details like when this function

module throw an exception as connection closed(no data).

inside inbound proxy,

could you please suggest us, what should be avoided inside the proxy

method.

warm regards

mahesh.

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Mahesh,

We are facing same kind of problem, but in our case same message is failing some times that is because it carries huge data.

If you have fixed your problem, can you help me out

Regards

Chaitanya Naru

former_member859847
Active Contributor
0 Kudos

Hi Chaitanya,

previouly, i have the same problem.

At that time, we are using 'submit' command inside proxy method i.e i ABAP program.

because of that, the message was struck in the inbound que.

'submit' is not suggestable inside proxy method.

so, pls check your ABAP Program.

warm regards

mahesh.

Former Member
0 Kudos

Hi Mahesh,

We are using Idoc's, so in our case the problem is some where else,if there is some thing else if you want to add please... it would be of great help.

Any ways thanks for the reply..

Regards

Naru

Former Member
0 Kudos

Mahesh,

We have the similar issue or the same issue.

Some messages are going fine and for some messages we have this issue.

Please let us know if you have fixed this.

reg

Former Member
0 Kudos

hi mahesh,

The function module sxms_async_exec will call the integration engine pipeline and processess the message

so check the path prefix i.e:/sap/xi/engine?type=entry

regards

kummari

Edited by: kummari on Aug 11, 2008 8:06 AM

former_member859847
Active Contributor
0 Kudos

Hi,

Thanks for the reply.

my connection type is 'H" with path prefix as

/sap/xi/engine?type = entry only.

why remaing all inbound interfaces are working fine.

only this interface struck in the inbound queue

saying status test as 'cooonection closed(no data).

same interface working fine from 'sproxy' t.code.

could you please check it and let any other solution .

Former Member
0 Kudos

hi

check connection of the rfc dest ...

execute the t.code SLDCHECK in the R/3 system

regards

kummari

former_member859847
Active Contributor
0 Kudos

Hi,

I already check the rfcdest and sld check.

pls note that, all inbound itefaces with server proxy

working fine.

only this interface not working fine end to end

i.e from xi->ecc.

saying status test in smq2 as 'connection closed(no data).

for your information, inside server proxy i use the submit command to call another report program.

could you pls sugget me, it will create any problem.

warm regards.

mahesh.

Former Member
0 Kudos

hi mahesh,

is your R/3 system based on WEBAS 6.20 or WEBAS 6.40

regards

kummari

former_member859847
Active Contributor
0 Kudos

Hi,

Pls chek it below.

ECC 6.0 SAP_BASIS 700 SP11

XI 7.0 SP14

Former Member
0 Kudos

Hi Mahesh,

I feel there should not be any problem even if you are using "SUBMIT" but make sure that you have all authorization to access the programs or FM you have used in your server proxy code.

Thanks

Sudharshan