axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (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 09:07:40 GMT


Andreas Veithen commented on AXIS2-5203:

Basically, your analysis is limited to the fact that JAXWSMessageReceiver creates a _new_
class loader for every request (and therefore your logical conclusion is to cache that class
loader), while I would go a step further and say that  the very fact that it creates a class
loader and the way it creates it are problematic. If I get the time tonight I will try to
construct an argument that clearly shows that the original code which creates this class loader
is incorrect.
> 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