org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Attempted read on closed stream. on local .NET webservice

[TheCycoONE]

To facilitate code sharing between ColdFusion and our .NET applications we have a .NET webservice running through IIS on localhost.

Occasionally, under what appears to be high or persistent load, this connection errors out, which it didn't do with ColdFusion 9.  Is there something I can change on either the service or the in ColdFusion to prevent this from coming up?

Note that the service uses basicHttpBinding (<basicHttpBinding>) .  It is listening to localhost on port 8888, and is not https.

The fault returned when invoking the web service operation is:

org.apache.axis2.AxisFault: com.ctc.wstx.exc.WstxIOException: Attempted read on closed stream.

at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:124)

at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:68)

at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)

at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)

at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)

at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)

at org.tempuri.ErmsInternalStub.textToSpeech(ErmsInternalStub.java:828)

at sun.reflect.GeneratedMethodAccessor46.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606) at coldfusion.xml.rpc.Axis... ''

[vishu_13]

TheCycoONE wrote:

@

Occasionally, under what appears to be high or persistent load, this connection errors out, which it didn't do with ColdFusion 9.

Seems like you have upgraded to CF 10 or CF11

Try tuning CF and jvm

HTH

Thanks

VJ

[TheCycoONE]

I figured this out.  I was storing the CreateObject('webservice'...) result in the application scope and using it for each page call.  In CF9 this was fine, but in 10 calling from the same object concurrently caused the problems above.  Creating a new object for each request resolves the issue.