You must be logged in to do that (read scm)
[JIRA] Work started: (GF_CORBA_V3_MIRROR-2) Bug in JDKBridge caching affects GFv3
- From: "kcavanaugh (JIRA)" <jira-no-reply@kenai.com>
- To: issues@gf-corba-v3-mirror.kenai.com
- Subject: [JIRA] Work started: (GF_CORBA_V3_MIRROR-2) Bug in JDKBridge caching affects GFv3
- Date: Wed, 4 Nov 2009 18:50:27 +0000 (GMT+00:00)
[
http://kenai.com/jira/browse/GF_CORBA_V3_MIRROR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on GF_CORBA_V3_MIRROR-2 started by kcavanaugh.
> 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
>
> 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.
--
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
|
[JIRA] Work started: (GF_CORBA_V3_MIRROR-2) Bug in JDKBridge caching affects GFv3 |
kcavanaugh (JIRA) | 11/04/2009 |





