|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
HTTP Timeout |
« View previous topic :: View next topic » |
Author |
Message
|
rkford11 |
Posted: Wed May 04, 2016 10:15 am Post subject: HTTP Timeout |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
When client app calls the IIB (v9.0.0.5) HTTP JSON service, getting the following timeout error, but runs fine while calling from Soap UI/Nettool utiity
2016-05-04 05:55:16.359329 3066 { TomcatNodeRegistrationUtil.getDataFromHTTP , ' : 5000 timeout: true'
2016-05-04 05:55:16.359337 3066 { WebServicesClassLoader.getInstance
2016-05-04 05:55:16.359343 3066 } WebServicesClassLoader.getInstance , 'instance=com.ibm.broker.classloading.WebServicesClassLoader@a4e20051'
2016-05-04 05:55:16.359348 3066 { TomcatInstanceManager.getWorkInProgress , ' timeout: 5000 leg: TIMEOUT'
2016-05-04 05:55:16.465572 3555 AdapterClass.handleWorkRequest TIMEOUT 'Timeout for |/app/svc/first|'
2016-05-04 05:55:16.465645 3555 { com.ibm.broker.inlinehttp.tomcatthreadpool.WorkObject@-17ef1eed.streamHasBeenUsed
2016-05-04 05:55:16.465660 3555 com.ibm.broker.inlinehttp.tomcatthreadpool.WorkObject@-17ef1eed.streamHasBeenUsed 'iOutputStream |com.ibm.broker.inlinehttp.tomcatthreadpool.InlineHTTPOutputStream@cb27c975|'
2016-05-04 05:55:16.465670 3555 InlineHTTPOutputStream.streamHasBeenUsed() 'USED: false'
2016-05-04 05:55:16.465681 3555 } com.ibm.broker.inlinehttp.tomcatthreadpool.WorkObject@-17ef1eed.streamHasBeenUsed , 'false'
2016-05-04 05:55:16.465691 3555 com.ibm.broker.inlinehttp.tomcatthreadpool.WorkObject@-17ef1eed.getOutputStream 'iOutputStream |com.ibm.broker.inlinehttp.tomcatthreadpool.InlineHTTPOutputStream@cb27c975|'
2016-05-04 05:55:16.465715 3555 InlineHTTPOutputStream.invalidate() 'invalid: false : com.ibm.broker.inlinehttp.tomcatthreadpool.InlineHTTPOutputStream@cb27c975'
2016-05-04 05:55:16.465725 3555 AdapterClass.handleWorkRequest TIMEOUT 'Fault format in registration info: SOAP 1.1'
2016-05-04 05:55:16.465733 3555 AdapterClass.handleWorkRequest TIMEOUT 'HTTPInput node timeout - content type determined by fault format.'
2016-05-04 05:55:16.465742 3555 AdapterClass.handleWorkRequest TIMEOUT 'Content Type: text/xml; charset=utf-8'
2016-05-04 05:55:16.465832 3555 AdapterClass.handleWorkRequest TIMEOUT 'used by flow : true timeout: true'
2016-05-04 05:55:16.465843 3555 AdapterClass.handleWorkRequest TIMEOUT 'Fault format: SOAP 1.1'
2016-05-04 05:55:16.466146 3555 AdapterClass.handleWorkRequest TIMEOUT file:/build/slot1/S900_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp line:175 message:3632.BIPmsgs 'sent timeout fault' , '7800', '/app/svc/first', '10'
2016-05-04 05:55:16.466146 3555 UserTrace BIP3632W: Maximum client wait time '10' reached; the broker has sent a fault message back to a client using port '7800' and URL path '/app/svc/first'.
A flow has taken too long to process a message received on port '7800' and URL path '/app/svc/first', and the broker has sent a fault message back to the originating client.
Increase the speed of the flow, or increase the maximum client wait time for the nodes using this URL.
Request doesn't even get into the actual flow, just times out. Please let me know if I am missing anything.
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 04, 2016 10:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
What have you done to troubleshoot the connection?
What have you done to troubleshoot the client request parameters?
What have you done to troubleshoot the data? _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
rkford11 |
Posted: Wed May 04, 2016 11:39 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
Have enabled the trace and captured the below log. Here are the client request parameters
POST /app/svc/first HTTP/1.1
Content-Type: application/json
Host: abc.com:7800
User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
Via: 1.1 DQCAECRHblg-,1.1 EQCABDVmHxY-,1.1 AQAAAEIwc8g-
X-Client-IP: 11.43.6.678,127.0.0.1,127.0.0.1
X-Global-Transaction-ID: 47697489
X-Archived-Client-IP: 11.43.6.678,11.43.6.678,127.0.0.1
Authorization: Negotiate KFFHHFUIGHTIIF5gYGKwYBBQUCoIIF2jCCBdagDTALBgkqhkiG9xIBAgKiggXb3EgECAgEAboIFqjCCBaagAwIBBaEDAgEOogcDBQAAAAAAo4I...........
Data is simple JSON message.
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 04, 2016 11:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
can you telnet to the http listener port from the client machine?
What is the connection timeout on the client side? _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
rkford11 |
Posted: Fri May 06, 2016 8:44 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
Yes. Same port accepts SOAP & HTTP connections.
Works for SOAP services.
Using HTTP listener as an embedded listener.
Time out on client side is 120 sec, as defined on HTTP input node.
Thanks |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 06, 2016 9:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
So the error message says
Quote: |
2016-05-04 05:55:16.466146 3555 AdapterClass.handleWorkRequest TIMEOUT file:/build/slot1/S900_P/src/DataFlowEngine/NativeTrace/ImbNativeTrace.cpp line:175 message:3632.BIPmsgs 'sent timeout fault' , '7800', '/app/svc/first', '10'
2016-05-04 05:55:16.466146 3555 UserTrace BIP3632W: Maximum client wait time '10' reached; the broker has sent a fault message back to a client using port '7800' and URL path '/app/svc/first'.
A flow has taken too long to process a message received on port '7800' and URL path '/app/svc/first', and the broker has sent a fault message back to the originating client.
Increase the speed of the flow, or increase the maximum client wait time for the nodes using this URL. |
This means that the flow downstream of the HTTP web server (the actual HTTPInput node) did not fetch the pending request from the webserver (the httplistener) before the node timed out.
So perhaps the message flow is running in a single instance and it's too busy to process new messages. (or at least the part of a message flow that starts with an HTTPInput ndoe)
Perhaps the HTTPReply node didn't get called, or didn't get called in time.
Perhaps you need more instances. Perhaps you need to optimize code. Perhaps you need to tune the threads of the http listener... _________________ chmod -R ugo-wx / |
|
Back to top |
|
 |
rkford11 |
Posted: Mon May 09, 2016 9:17 am Post subject: |
|
|
Partisan
Joined: 06 Jun 2004 Posts: 316
|
Even after increasing the instances of the flow, we are receiving the same error.
Service works fine with SOAP UI utility with out any issues. Receiving timeout when calling from Datapower.
Thanks |
|
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
|
|
|
|