Skip to main content
georget37352040
Inspiring
September 27, 2022
Answered

Web service issue on Coldfusion org.apache.axis2.AxisFault: Stream closed

  • September 27, 2022
  • 1 reply
  • 958 views

Our webservice is thorwing out this error.

We are running Cold Fusion 2021 Update 4 on Windows 2019

 

The most recent thing we changed was the TLS 1.2 lock down.

I reverted all the TLS registry changes but it didnt fix anything.

I am not 100% its even related.

The only other thing that happened between last time it worked, was regular windows updates.

NO code changes to the web service or site code.

org.apache.axis2.AxisFault: Stream closed
	at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:531)
	at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:375)
	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 ws.internal.WsInternalInstallsCfcStub.getCurrentVersions(WsInternalInstallsCfcStub.java:192)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at coldfusion.xml.rpc.Axis2ServiceProxy.getResult(Axis2ServicePr... ''

 

 

AXIS2.XML file on coldfusion is running version 1.7.0

 

it has these parrameters

 

   <transportSender name="local"
                     class="org.apache.axis2.transport.local.LocalTransportSender"/>
    <transportSender name="http"
                     class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding">chunked</parameter>

        <!-- If following is set to 'true', optional action part of the Content-Type will not be added to the SOAP 1.2 messages -->
        <!--  <parameter name="OmitSOAP12Action">true</parameter>  -->
    </transportSender>

    <transportSender name="https"
                     class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
        <parameter name="PROTOCOL">HTTP/1.1</parameter>
        <parameter name="Transfer-Encoding">chunked</parameter>
    </transportSender>

 

 

    This topic has been closed for replies.
    Correct answer georget37352040

    We found out that the WS worked when placed in /Webservice folder of the site, but not /WS locations.

    That wold indicate its some sort of prermission, but we could not figure it out. Gave it all possible permissions.

    It could be aconflict with the code there.

     

    We could not figure it out, so we reworked the WS code to run differently

    1 reply

    BKBK
    Community Expert
    Community Expert
    September 28, 2022

    It might be that the web service is unable to read the response coming in. Perhaps the response is in an unexpected format, character-set or file extension?

    georget37352040
    georget37352040AuthorCorrect answer
    Inspiring
    October 5, 2022

    We found out that the WS worked when placed in /Webservice folder of the site, but not /WS locations.

    That wold indicate its some sort of prermission, but we could not figure it out. Gave it all possible permissions.

    It could be aconflict with the code there.

     

    We could not figure it out, so we reworked the WS code to run differently

    BKBK
    Community Expert
    Community Expert
    October 5, 2022

    Thanks for the update. Glad to hear that.