[
https://issues.apache.org/jira/browse/AXIS2-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce G Stewart updated AXIS2-4642:
-----------------------------------
Description:
AxisService.getWSDL() sends the response body for a ..service?wsdl query, then
calls .flush() and .close() for its output stream. Upon return,
ListingAgent.processListService() calls .flush() and .close() again for the
same stream.
The second close() interferes with the next request on the intermediate ajp
connector socket.
I don't know whether calling close() twice should be harmless but, in this
case, it is not.
[edit: Actually, the 2nd close() is harmelss. It's the flush() coming after the
1st close() that seems to be the problem.]
was:
AxisService.getWSDL() sends the response body for a ..service?wsdl query, then
calls .flush() and .close() for its output stream. Upon return,
ListingAgent.processListService() calls .flush() and .close() again for the
same stream.
The second close() interferes with the next request on the intermediate ajp
connector socket.
I don't know whether calling close() twice should be harmless but, in this
case, it is not.
> ?wsdl query calls out.close() twice, confusing at least some Tomcat connectors
> ------------------------------------------------------------------------------
>
> Key: AXIS2-4642
> URL: https://issues.apache.org/jira/browse/AXIS2-4642
> Project: Axis2
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.5.1
> Environment: Axis2.war deployed in Tomcat 6.0.24, using ajp to jk
> isapi_redirect to IIS on Windows Server 2008.
> Reporter: Bruce G Stewart
> Priority: Minor
>
> AxisService.getWSDL() sends the response body for a ..service?wsdl query,
> then calls .flush() and .close() for its output stream. Upon return,
> ListingAgent.processListService() calls .flush() and .close() again for the
> same stream.
> The second close() interferes with the next request on the intermediate ajp
> connector socket.
> I don't know whether calling close() twice should be harmless but, in this
> case, it is not.
> [edit: Actually, the 2nd close() is harmelss. It's the flush() coming after
> the 1st close() that seems to be the problem.]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
