Uploaded image for project: 'Spring Web Services'
  1. Spring Web Services
  2. SWS-333

Transport streams not closed in WebServiceConnection

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.5
    • Fix Version/s: 1.5.1
    • Component/s: Core
    • Labels:
      None

      Description

      Currently, in the AbstractWebServiceConnection and subclasses, the TransportOutputStream and TransportInputStream are not closed, mainly because Axis1 SAAJ and Axiom lazy-load messages.

      This is not a major issue for most transports, because the streams are closed in the end (during connection.close()), but closing the streams explicitly can't hurt.

        Activity

        tareq Tareq Abedrabbo created issue -
        arjen.poutsma Arjen Poutsma made changes -
        Field Original Value New Value
        Description  Currently, in the AbstractWebServiceConnection and subclasses, the TransportOutputStream and TransportInputStream are not closed, mainly because Axis1 SAAJ and Axiom lazy-load messages.

        This is not a major issue for most transports, because the streams are closed in the end (during connection.close()), but closing the streams explicitly can't hurt.
        Fix Version/s 1.5.1 [ 10917 ]
        arjen.poutsma Arjen Poutsma made changes -
        Resolution Fixed [ 1 ]
        Status Open [ 1 ] Resolved [ 5 ]
        arjen.poutsma Arjen Poutsma made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            arjen.poutsma Arjen Poutsma
            Reporter:
            tareq Tareq Abedrabbo
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: