axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Charith Dhanushka Wickramarachchi (Commented) (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5203) JAX-WS Message Receiver Adds a new URL class loader to TCCL per each request.
Date Tue, 29 Nov 2011 12:17:40 GMT


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. 

> JAX-WS Message Receiver Adds a new URL class loader to TCCL per each request.
> -----------------------------------------------------------------------------
>                 Key: AXIS2-5203
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message