MQSeries.net :: View topic - Strange Timeout in SOAP Input node

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 » Strange Timeout in SOAP Input node

Strange Timeout in SOAP Input node

« View previous topic :: View next topic »

Author

Message

ruimadaleno

Posted: Tue Oct 28, 2014 7:53 am Post subject: Strange Timeout in SOAP Input node

Master

Joined: 08 May 2014
Posts: 274

Code:

<SOAP_Domain_Msg xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Context operation="" operationType="UNKNOWN" portType="FileNetWS" portTypeNamespace="http://www.contact admin.pt/FilenetWS_V2" port="FileNetWSHttpPort" service="FileNetWSHttpService" fileName="FileNetWS.wsdl">
   <SOAP_Version>1.1</SOAP_Version>
   <Namespace xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/>
   <_XmlDeclaration Version="1.0" Encoding="UTF-8"/>
</Context>
<Header/>
<Body>
   <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Server</faultcode>
      <faultstring>A timeout occurred during processing</faultstring>
      <faultactor>/FileNetWS_V2</faultactor>
      <detail>
         <text>Timeout. The Broker BRKESB01A did not provide a response within the specified time interval (30 seconds). The message reached the main flow, but timed out during processing. It was then given to the the timeout flow for processing.</text>
      </detail>
   </SOAP-ENV:Fault>
</Body>
</SOAP_Domain_Msg>

http headers for this request:

Code:

10.42.48.129 is the ip address of server running IBM BPM product.

this is were things get weird

The service was called with a soap fault ?
the service response was the following XML:

Code:

POST http://asesbvs1.csanet.int:7800/FileNetWS_V2 HTTP/1.1
Content-Type: text/xml; charset=UTF-8
SOAPAction: "http://www.contact admin.pt/FilenetWS_V2/GetDocContent"
User-Agent: Axis2
Host: asesbvs1.csanet.int:7800
Transfer-Encoding: chunked
X-Remote-Addr: 10.42.48.129
X-Remote-Host: 10.42.48.129
X-Server-Name: asesbvs1.csanet.int
X-Server-Port: 7800

<SOAP_Domain_Msg xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><Context operation="" operationType="UNKNOWN" portType="FileNetWS" portTypeNamespace="http://www.contact admin.pt/FilenetWS_V2" port="FileNetWSHttpPort" service="FileNetWSHttpService" fileName="FileNetWS.wsdl"><SOAP_Version>1.1</SOAP_Version><Namespace xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"/><_XmlDeclaration Version="1.0" Encoding="UTF-8"/></Context><Header/><Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode><faultstring>A timeout occurred during processing</faultstring><faultactor>/FileNetWS_V2</faultactor><detail><text>Timeout. The Broker BRKESB01A did not provide a response within the specified time interval (30 seconds). The message reached the main flow, but timed out during processing. It was then given to the the timeout flow for processing.</text></detail></SOAP-ENV:Fault></Body></SOAP_Domain_Msg>

The service output is a fault message, and looking at the text fault it looks like a timeout...but ... the processing time took about a second (see column 2 of the table above).

There is no 30 second timeout configured in service (all timetout equal or above 120 seconds).

confused

can you shed some ligth in this issue ?
_________________
Best regards

Rui Madaleno

Vitor

Posted: Tue Oct 28, 2014 7:59 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

a) Run a user trace to capture additional information

b) Confirm the FileNet service isn't mixing up the HTTP sessions so it's sending a 30 second timeout message to the last connection that was made, not the request that timed out.
_________________
Honesty is the best policy.
Insanity is the best defence.

ruimadaleno

Posted: Tue Oct 28, 2014 9:20 am Post subject:

Master

Joined: 08 May 2014
Posts: 274

more info in this issue:

Service gen.filenetWS configured with "additional instances=3" , "pool associated with message flow". So there are 4 threads handling requests.

Supose all 4 threads are busy , handling request, and a fitfth request arrives.

This fifth request must wait until one thread is free to handle it.

how much time does this fifth request waits for a free thread ? is this configurable ? maybe 30 seconds and this is why i receive the xml payload above ?
_________________
Best regards

Rui Madaleno

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange Timeout in SOAP Input node

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