• Post Reply Bookmark Topic Watch Topic
  • New Topic

java.io.IOException

 
Rajesh Krsh
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Any idea why the following exception is caused during webservice call?

WebServicesFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultString: java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
faultActor: null
faultDetail:

java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
at com.ibm.ws.webservices.engine.xmlsoap.builders.WebServicesFaultProcessor.createFault(WebServicesFaultProcessor.java:420)
at com.ibm.ws.webservices.engine.xmlsoap.SOAPFault.getFault(SOAPFault.java:500)
at com.ibm.ws.webservices.engine.SOAPPart.getFault(SOAPPart.java:1097)
at com.ibm.ws.webservices.engine.SOAPPart.getFault(SOAPPart.java:754)
at com.ibm.ws.webservices.engine.Message.getFault(Message.java:900)
at com.ibm.ws.webservices.engine.Message.ifFaultThrowSelf(Message.java:880)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:280)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:860)

WAS version is 6.1.13. Googling didn't help..

Thanks for your help in advance...

Cheers
KR
 
Bear Bibeault
Author and ninkuma
Marshal
Posts: 65516
105
IntelliJ IDE Java jQuery Mac Mac OS X
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
"Rmthy Krsh", please check your private messages for an important administrative matter.

 
Tomáš Kotrbatý
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

I have the same exception.
Also when calling web service.
WAS version is 6.1.0.21.
The problem occurs randomly.

Trying to find the solution.
Any help will be appreciated.

Thanks Tomas

Similar errorstack:

PivotHandlerW W com.ibm.ws.webservices.engine.PivotHandlerWrapper invoke WSWS3734W: Warning: Exception caught from invocation to com.ibm.ws.webservices.engine.transport.http.HTTPSender:
WebServicesFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultString: java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
faultActor: null
faultDetail:

java.io.IOException: Async IO operation failed, reason: RC: 76 A socket must be already connected.
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:192)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:832)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:229)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:336)
at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:929)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:722)
at com.ibm.ws.webservices.engine.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:161)
....
 
Chris Serra
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Bump for this. I'm facing the same problem.
 
sudheer kiran
Ranch Hand
Posts: 237
Firefox Browser MyEclipse IDE Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
mostly because of port in use.
check out where you have published server secondtime.
 
Tomáš Kotrbatý
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
sudheer kiran wrote:mostly because of port in use.
check out where you have published server secondtime.



Thanks for your response,

What do you mean "check out where you have published server secondtime" ?

Tomas
 
Tomáš Kotrbatý
Greenhorn
Posts: 9
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

IBM first supported to increase some timeouts. But it did not help.

Then IBM realized, that we send web service calls via webseal.
We switchover the WS calls without webseal and everything works OK.

So the problem was due our infrastructure.

By Tomas
 
Faisal Mohammad
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
How did you switchover the WS calls without webseal ?

Faisal
 
Tomáš Kotrbatý
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The Webseals in our infrastructure behaves like a proxy, that provides authentication and other stuff.
We bypass the communication by the direct call from the application server of my calling application (WS client) to the application server that provides the WS (WS server).
In the call we use IP instead of DNS name of the server.
We had to fulfill some our internal recommendation when not using webseals, but it works.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!