Problem with HTTP adapter sending xml to websphere

[Former Member]

Hello everybody,

I have problem sending XML file through HTTP adapter on websphere application server 6.0.

I get error message: HTTP-Client Code 402 Reason ICM_HTTP_TIMEOUT.

I tried to change the icm/conn_timeout to 8000 but it didn't work.

The scenario is: file -> XI -> websphere.

The processing seems to stop on HTTP adapter with queue status - "Queue stopped"

and XML message status stops on "Scheduled for outbound processing".

Do you have any ideas or suggestions, where the problem could be?

Thanks in advance.

[Former Member · Accepted solution]

Hi,

This is the communication problem between the J2EE and ABAP stack, while trying to send the message from J2EE to ABAP (Integration Server). Trying increasing the time out as suggested below.

1. goto smicm -> goto -> paramerters -> change

look for icm/conn_timeout and increase its value

2. visual admin -> server -> services -> httpprovider ->

check property ServeletInputStreamTimeout, typically it is 6000.

I think you are just increasing the time as per point 1 only.

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Refresh the Queues and try it once again

I think there are already few messages stuck-up in queue.

Thanks

Swarup

Edited by: Swarup Sawant on Apr 17, 2008 3:40 PM

Edited by: Swarup Sawant on Apr 17, 2008 3:41 PM

[Former Member · Accepted solution]

Hi Swarup,

I did only the first changes.

I will try to do the other changes and let you know.

Thanks

[Former Member]

Hi richard

code 402 is reserved for future use

The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.

If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server's TCP stack will send a reset packet to the client, which may erase the client's unacknowledged input buffers before they can be read and interpreted by the HTTP application.

Specialy 402 is reserved for future use

here the error is due to CLIENT RECEIVED FAILED

This means message could not find the relevent service

for more details on HTTP codes you may follow these links

http://www.web-cache.com/Writings/http-status-codes.html

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

http://www.helpwithpcs.com/courses/html/html_http_status_codes.htm

Check whether you have given the right credentials. If you are very sure that you have given right credentials then your problem will be solved by restarting J2EE engine

steps to restart J2EE engine

1) run transaction SMICM

2) then in the tab administration => J2EE instance(local) =>send soft shutdown with restart

by this java engine will restart and will be up in 5-10 minutes and your problem will be solved

Thanks

sandeep sharma

PS ; if helpful kindly reward points

[Former Member]

Hi,

it seems that the problem is on side of the websphere.

The program isn't sending a response, that XI has sent something.

I will inform you about next steps soon.

And also if it is already solved.

Richard

[Former Member]

Hi,

the problem is solved now.

On websphere there was runnig some monitoring that "filtered" the data that came to it.

This is why we got errors.

We turned off the monitoring and changed the port and now it is running.

Thanks for help!

Richard

[Former Member]

hi

delete all the pending messages in the queues and register the queues again.

does the messages reach web sph ??

hw much time it is taking to process the same ?

eo or eoio ?

rgds,

Arun

[Former Member]

Hi Arun,

i deleted all the messages in queue and it did still not work.

The message reaches web sphere but it has no body.

it is eo.

It don't understand what you mean with the second question.