You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Eric Norman (JIRA)" <ax...@ws.apache.org> on 2004/12/14 20:46:58 UTC
[jira] Created: (AXIS-1722) MethodCache does not consider the classloader in the cache key
MethodCache does not consider the classloader in the cache key
--------------------------------------------------------------
Key: AXIS-1722
URL: http://nagoya.apache.org/jira/browse/AXIS-1722
Project: Axis
Type: Bug
Components: Basic Architecture
Versions: 1.2RC2
Environment: Any
Reporter: Eric Norman
Attachments: MethodCache.java
If you load a class with the same name in different classloaders, the method cache only uses the first one. This is a problem because our server loads components into their own classloaders, so if two components contain the same classname, the MethodCache will often return a Method from the wrong class, eventually causing a problem serializing and/or deserializing the SOAP message into their java objects. Suggest using the class object as the key in the HashMap instead of the classname.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AXIS-1722) MethodCache does not consider the classloader in the cache key
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXIS-1722?page=history ]
Davanum Srinivas resolved AXIS-1722:
------------------------------------
Resolution: Fixed
Applied.
thanks,
dims
> MethodCache does not consider the classloader in the cache key
> --------------------------------------------------------------
>
> Key: AXIS-1722
> URL: http://nagoya.apache.org/jira/browse/AXIS-1722
> Project: Axis
> Type: Bug
> Components: Basic Architecture
> Versions: 1.2RC2
> Environment: Any
> Reporter: Eric Norman
> Attachments: MethodCache.java
>
> If you load a class with the same name in different classloaders, the method cache only uses the first one. This is a problem because our server loads components into their own classloaders, so if two components contain the same classname, the MethodCache will often return a Method from the wrong class, eventually causing a problem serializing and/or deserializing the SOAP message into their java objects. Suggest using the class object as the key in the HashMap instead of the classname.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1722) MethodCache does not consider the classloader in the cache key
Posted by "Eric Norman (JIRA)" <ax...@ws.apache.org>.
[ http://nagoya.apache.org/jira/browse/AXIS-1722?page=history ]
Eric Norman updated AXIS-1722:
------------------------------
Attachment: MethodCache.java
Attached is the modified MethodCache object that uses the clazz object as the HashMap key to make it safe across classloaders.
> MethodCache does not consider the classloader in the cache key
> --------------------------------------------------------------
>
> Key: AXIS-1722
> URL: http://nagoya.apache.org/jira/browse/AXIS-1722
> Project: Axis
> Type: Bug
> Components: Basic Architecture
> Versions: 1.2RC2
> Environment: Any
> Reporter: Eric Norman
> Attachments: MethodCache.java
>
> If you load a class with the same name in different classloaders, the method cache only uses the first one. This is a problem because our server loads components into their own classloaders, so if two components contain the same classname, the MethodCache will often return a Method from the wrong class, eventually causing a problem serializing and/or deserializing the SOAP message into their java objects. Suggest using the class object as the key in the HashMap instead of the classname.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira