| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| 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
|
hi all,
first of all, let me give an high level view of my environment.
WMB 8.0.0.4 running on windows 2008 R2 server standard
broker name = BRKESB01A
Several message flows running in a single execution group
Every message flows is recording events to record & replay infrastructure (a datacapture store inserts the events to an oracle database)
There is a particular message flow with a weird behaviour: gen.FilenetWS.
This is a web service implemented with soap nodes:
Soap input --> compute ---> http request --> compute --> soap reply
http request is configured with 120 seconds timeout
soap input is configured with a higher value (1800)
From monitoring info (record and replay) i can see the following usage
MSGFLOW_NAME|EVENT_TIMESTAMP|LOCAL_TRANSACTION_ID|EVENT_TYPE|NODE_NAME|HAS_BITSTREAM|HAS_EXCEPTION|HAS_USERDATA
gen.FileNetWS|2014-10-22 15:27:20.577|e58d6079-b002-4754-86e6-f236693cbd5f-1|SOAP Input.TransactionEnd|SOAP Input|N|N|N|
gen.FileNetWS|2014-10-22 15:27:20.481|e58d6079-b002-4754-86e6-f236693cbd5f-1|SOAP Reply.InTerminal|SOAP Reply|Y|N|N|
gen.FileNetWS|2014-10-22 15:27:20.480|e58d6079-b002-4754-86e6-f236693cbd5f-1|SOAP Input.HTTP TimeoutTerminal|SOAP Input|N|N|N|
gen.FileNetWS|2014-10-22 15:27:20.462|e58d6079-b002-4754-86e6-f236693cbd5f-1|SOAP Input.TransactionStart.FileNetws|SOAP Input|Y|N|N|
The XML received by the service in "soapinput.transaction start" is the following
| 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: |
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
|
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 |
|
| Back to top |
|
 |
| 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. |
|
| Back to top |
|
|
| 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 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
