Posted: Fri Apr 04, 2008 10:03 am Post subject: SocketTimeoutException
Shaman
Joined: 22 Oct 2003 Posts: 742 Location: Austin, Texas, USA
We are getting a SocketTimeoutException on a WAS 5.1 server. Presumably (if I am reading the error correctly), the MDB wants a socket it can't find. Am I interpreting the error correctly? Is there is anything I should look at on the MQ server?
WebServicesFault
faultCode: Server.generalException
faultString: java.net.SocketTimeoutException: Read timed out
faultActor: null
faultDetail:
java.net.SocketTimeoutException: Read timed out
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:161)
at com.ibm.ws.webservices.engine.transport.http.HTTP11Sender.invoke(HTTP 11Sender.java:330)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:87)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:214)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:255)
at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:702)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:628)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:450)
at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:672)
at us.tx.state.hhsc.services.api.eligDet.EligibilityDeterminationBindingStub.determineEligibility(EligibilityDeterminationBindingStub.java:376)
at us.tx.state.hhsc.services.api.eligDet.EligibilityDeterminationTypeProxy.determineEligibility(EligibilityDeterminationTypeProxy.java:64)
at us.tx.state.hhsc.integration.PXListenerBean.getEligibilityServiceData(PXListenerBean.java:352)
at us.tx.state.hhsc.integration.PXListenerBean.onMessage(PXListenerBean.java:138)
at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:211)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:56)
at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:200)
at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:178)
at com.ibm.mq.jms.MQSession.run(MQSession.java:1043)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:924)
at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:752)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:527)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:494)
at sun.reflect.GeneratedMethodAccessor60.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:91)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:375)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:937)
I'm not a WAS or JMS guru, so go easy if this is a silly question. Thanks.
I think that means the HTTP service being invoked didn't return an HTTP Reply in time. _________________ I am *not* the model of the modern major general.
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