[
https://issues.apache.org/jira/browse/AXIS2-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159214#comment-13159214
]
Charith Dhanushka Wickramarachchi commented on AXIS2-5203:
----------------------------------------------------------
Hi Amila ,
I tried this scenario with normal Axis2 services with and without parameter
<parameter name="ServiceTCCL">composite</parameter> And in both cases this
issue does not exist for them. I can see TCCL remains same for all requests.
thanks,
Charith
> JAX-WS Message Receiver Adds a new URL class loader to TCCL per each request.
> -----------------------------------------------------------------------------
>
> Key: AXIS2-5203
> URL: https://issues.apache.org/jira/browse/AXIS2-5203
> Project: Axis2
> Issue Type: Improvement
> Components: jaxws
> Environment: any
> Reporter: Charith Dhanushka Wickramarachchi
> Priority: Critical
> Attachments: AXIS2-5203.diff
>
>
> In Current JAX-WS Message Receiver its adds a new URL class Loader instance
> as TCCL for each request. This becomes a major performance hit as it cause to
> create XMLOutputFactory at Axiom level for each response from the server.
> And also this may cause OOM situation since at AXIOM level it cache the
> XMLOutput factories per class Loader by default. So in this case the Hash map
> entries that's used for this cache will get accumulated.
> thanks,
> Charith
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
