You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Sahan Gamage (JIRA)" <ji...@apache.org> on 2006/01/31 14:03:32 UTC

[jira] Created: (AXIS2C-48) Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()

Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()
--------------------------------------------------------------------------------------------------------------

         Key: AXIS2C-48
         URL: http://issues.apache.org/jira/browse/AXIS2C-48
     Project: Axis2-C
        Type: Bug
  Components: transport/http  
    Reporter: Sahan Gamage
     Fix For: Current (Nightly)


Inside the axis2_http_transport_utils_create_soap_msg() function xml_reader, om_stax_builder and a soap_builder is created to get the soap_envelope from the http response (using the input stream). But once the soap_envelope is created the builders and the reader cannot be freed at the end of the function (before return) due to the deferred buiding mechanism. We need to find a way to free these.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Closed: (AXIS2C-48) Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()

Posted by "Sahan Gamage (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2C-48?page=all ]
     
Sahan Gamage closed AXIS2C-48:
------------------------------

    Fix Version: Current (Nightly)
     Resolution: Fixed

since the soap_builder, om_stax_builder and the xml_reader is tightly bound to the created soap envelope and they are linked together, we can easily free them when freeing the soap envelope. i.e. inside axis2_soap_envelope_free() function. This is done by nandika and hence the problem is solved by now.

> Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()
> --------------------------------------------------------------------------------------------------------------
>
>          Key: AXIS2C-48
>          URL: http://issues.apache.org/jira/browse/AXIS2C-48
>      Project: Axis2-C
>         Type: Bug
>   Components: transport/http
>     Versions: M0.3
>     Reporter: Sahan Gamage
>      Fix For: Current (Nightly)

>
> Inside the axis2_http_transport_utils_create_soap_msg() function xml_reader, om_stax_builder and a soap_builder is created to get the soap_envelope from the http response (using the input stream). But once the soap_envelope is created the builders and the reader cannot be freed at the end of the function (before return) due to the deferred buiding mechanism. We need to find a way to free these.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (AXIS2C-48) Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()

Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2C-48?page=all ]

Samisa Abeysinghe updated AXIS2C-48:
------------------------------------

    Fix Version: M1.0
                     (was: Current (Nightly))
        Version: M0.3

> Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()
> --------------------------------------------------------------------------------------------------------------
>
>          Key: AXIS2C-48
>          URL: http://issues.apache.org/jira/browse/AXIS2C-48
>      Project: Axis2-C
>         Type: Bug
>   Components: transport/http
>     Versions: M0.3
>     Reporter: Sahan Gamage
>      Fix For: M1.0

>
> Inside the axis2_http_transport_utils_create_soap_msg() function xml_reader, om_stax_builder and a soap_builder is created to get the soap_envelope from the http response (using the input stream). But once the soap_envelope is created the builders and the reader cannot be freed at the end of the function (before return) due to the deferred buiding mechanism. We need to find a way to free these.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[jira] Updated: (AXIS2C-48) Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()

Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2C-48?page=all ]

Samisa Abeysinghe updated AXIS2C-48:
------------------------------------

    Fix Version:     (was: M0.4)

> Free the xml_reader, om_stax_builder, soap_builder created inside axis2_http_transport_utils_create_soap_msg()
> --------------------------------------------------------------------------------------------------------------
>
>          Key: AXIS2C-48
>          URL: http://issues.apache.org/jira/browse/AXIS2C-48
>      Project: Axis2-C
>         Type: Bug
>   Components: transport/http
>     Versions: M0.3
>     Reporter: Sahan Gamage

>
> Inside the axis2_http_transport_utils_create_soap_msg() function xml_reader, om_stax_builder and a soap_builder is created to get the soap_envelope from the http response (using the input stream). But once the soap_envelope is created the builders and the reader cannot be freed at the end of the function (before return) due to the deferred buiding mechanism. We need to find a way to free these.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira