[JIRA] Updated: (GF_CORBA_V3_MIRROR-2) Bug in JDKBridge caching affects GFv3

["kcavanaugh (JIRA)" <jira-no-reply@kenai.com>]

     [ 
http://kenai.com/jira/browse/GF_CORBA_V3_MIRROR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kcavanaugh updated GF_CORBA_V3_MIRROR-2:
----------------------------------------

       Priority: Minor  (was: Major)
    Description: 
JDKBridge contains a cache to speed up unmarshaling of value types.
Unfortunately this cache caches classes by name, and this causes severe 
problems in 
GFv3 when an EJB is re-deployed, leading to the use of the same classname in 
different
ClassLoaders.

Temporary fix: remove the cache, but this needs to be revisited.

--------------------------------------

The temporary fix is in place, but evaluating performance impact and deciding 
whether to implement some
form of caching is still outstanding.

  was:
JDKBridge contains a cache to speed up unmarshaling of value types.
Unfortunately this cache caches classes by name, and this causes severe 
problems in 
GFv3 when an EJB is re-deployed, leading to the use of the same classname in 
different
ClassLoaders.

Temporary fix: remove the cache, but this needs to be revisited.


> Bug in JDKBridge caching affects GFv3
> -------------------------------------
>
>                 Key: GF_CORBA_V3_MIRROR-2
>                 URL: http://kenai.com/jira/browse/GF_CORBA_V3_MIRROR-2
>             Project: gf-corba-v3-mirror
>          Issue Type: Bug
>         Environment: GlassFish v3
>            Reporter: kcavanaugh
>            Assignee: kcavanaugh
>            Priority: Minor
>
> JDKBridge contains a cache to speed up unmarshaling of value types.
> Unfortunately this cache caches classes by name, and this causes severe 
> problems in 
> GFv3 when an EJB is re-deployed, leading to the use of the same classname 
> in different
> ClassLoaders.
> Temporary fix: remove the cache, but this needs to be revisited.
> --------------------------------------
> The temporary fix is in place, but evaluating performance impact and 
> deciding whether to implement some
> form of caching is still outstanding.

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