MQSeries.net :: View topic - Process not getting killed in case of Web Service time out

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Process not getting killed in case of Web Service time out

Process not getting killed in case of Web Service time out

« View previous topic :: View next topic »

Author

Message

nimisha.parihar

Posted: Tue Jan 04, 2011 1:55 am Post subject: Process not getting killed in case of Web Service time out

Apprentice

Joined: 03 Nov 2010
Posts: 41

HI,

We have developed a web service using HTTP nodes and specified a time out of 180 seconds.

When a Time Out is happening the process for Web Service is not getting killed. I have to explicitly give "kill -9 <<process_id>>" command to kill so that i can hit back the web service.

If i dont kill the process explicitly i am unable to get my second request serviced from the Web Service.

smdavies99

Posted: Tue Jan 04, 2011 2:32 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Is your Service sending a reply back with the correct error code? There is a proper HTML reply code for a timeout. Use something like HTTPWatch to see that you are getting.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

nimisha.parihar

Posted: Tue Jan 04, 2011 3:08 am Post subject:

Apprentice

Joined: 03 Nov 2010
Posts: 41

Yes we are getting HTTP Gateway Timout 504

smdavies99

Posted: Tue Jan 04, 2011 4:56 am Post subject:

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

What process are you explicity killing? I hope it is not the Execution Group (aka DataFlowEngine)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.

nimisha.parihar

Posted: Wed Jan 05, 2011 2:58 am Post subject:

Apprentice

Joined: 03 Nov 2010
Posts: 41

it indeed was the DataFlowEngine process.......

The execution group has onle one Message Flow deployed and thats for this Web Service.

When we did - ps -eaf | grep <<message_flow_name>>we got just that process.

After killing it everything worked fine again...

harish_td

Posted: Wed Jan 05, 2011 7:52 pm Post subject:

Master

Joined: 13 Feb 2006
Posts: 236

nimisha.parihar wrote:

After killing it everything worked fine again...

I bet, this cannot be done in production.

My guess is that there is something wrong that happens before/in the SOAPReply Node. This causes the message to be rolled back to the previous terminal's catch node. The best way to debug this is to take a user trace and see exactly why the Message Flow gets into a non-responsive state.

You can also try and increase the number of Additional Instances that are deployed to this Execution Group. This will only tell the Message Broker to spawn another thread for processing the request and not solve your underlying problem

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Process not getting killed in case of Web Service time out

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP