[JBoss JIRA] Created: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
4:29 p.m.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create
classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://jira.jboss.org/jira/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-metro-3.0.3, jbossws-native-3.0.3
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a reference
to the ClassLoader and then preventing garbage collection and leading to a leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped with
a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:37 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://jira.jboss.org/jira/browse/JBWS-2317?page=com.atlassian.jira.plug...
]
Darran Lofthouse updated JBWS-2317:
-----------------------------------
Attachment: Injector.java
Uploading modified injector.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://jira.jboss.org/jira/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:06 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://jira.jboss.org/jira/browse/JBWS-2317?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2317:
----------------------------------
Fix Version/s: jbossws-native-3.0.5
jbossws-metro-3.0.5
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://jira.jboss.org/jira/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.4, jbossws-metro-3.0.4, jbossws-native-3.0.5,
jbossws-metro-3.0.5
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:08 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://jira.jboss.org/jira/browse/JBWS-2317?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2317:
----------------------------------
Fix Version/s: (was: jbossws-native-3.0.4)
(was: jbossws-metro-3.0.4)
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://jira.jboss.org/jira/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:25 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://jira.jboss.org/jira/browse/JBWS-2317?page=com.atlassian.jira.plug...
]
Darran Lofthouse commented on JBWS-2317:
----------------------------------------
Modified file submitted to JAXB project :
https://jaxb.dev.java.net/issues/show_bug.cgi?id=564
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://jira.jboss.org/jira/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.0.5, jbossws-metro-3.0.5
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:59 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://jira.jboss.org/jira/browse/JBWS-2317?page=com.atlassian.jira.plug...
]
Alessio Soldano updated JBWS-2317:
----------------------------------
Fix Version/s: (was: jbossws-native-3.0.5)
(was: jbossws-metro-3.0.5)
Unscheduling this while waiting for Sun to review and apply the patch. I've linked
this issue to JBWS-2302 in order to check if something changed before releasing.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://jira.jboss.org/jira/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Alessio Soldano
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://issues.jboss.org/browse/JBWS-2317?page=com.atlassian.jira.plugin....
]
Richard Kettelerij commented on JBWS-2317:
------------------------------------------
Note that the underlying JAXB bug is fixed (http://java.net/jira/browse/JAXB-564, used to
be https://jaxb.dev.java.net/issues/show_bug.cgi?id=564). JBoss just needs to upgrade to
JAXB 2.1.13+. Meanwhile we're still using the "noOptimize=true" system
property.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://issues.jboss.org/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Alessio Soldano
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:43 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://issues.jboss.org/browse/JBWS-2317?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-2317:
---------------------------------------
Richard, thanks for the comment. Can you verify if the problem is gone with jbossws 3.4.x
? We're using JAXB 2.2 since 3.4.x, so assuming the jaxb fix went upstream too at
Sun/Oracle, this jira could be solved.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://issues.jboss.org/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Alessio Soldano
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:31 p.m.
New subject: [JBoss JIRA] Commented: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://issues.jboss.org/browse/JBWS-2317?page=com.atlassian.jira.plugin....
]
Richard Kettelerij commented on JBWS-2317:
------------------------------------------
Thanks for the comment Alessio. Actually we're in the process of upgrading to JBoss
5.1.0 which ships JBossWS 3.1.2 and JAXB 2.1.9 out-of-the-box. It might take awhile before
we get to 3.4+ and be able to verify the behavior.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://issues.jboss.org/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Alessio Soldano
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:33 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBWS-2317) $JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing to re-create classes.
[
https://issues.jboss.org/browse/JBWS-2317?page=com.atlassian.jira.plugin....
]
Richard Kettelerij edited comment on JBWS-2317 at 5/30/11 9:32 AM:
-------------------------------------------------------------------
Thanks for the comment Alessio. Actually we're in the process of upgrading to JBoss
5.1.0 which ships JBossWS 3.1.2 and JAXB 2.1.9 out-of-the-box. It might take a while
before we get to 3.4+ and be able to verify the behavior.
was (Author: rkettelerij):
Thanks for the comment Alessio. Actually we're in the process of upgrading to
JBoss 5.1.0 which ships JBossWS 3.1.2 and JAXB 2.1.9 out-of-the-box. It might take awhile
before we get to 3.4+ and be able to verify the behavior.
$JAXBAccessorF_ and $JAXBAccessorM_ cache loosing classes and failing
to re-create classes.
-------------------------------------------------------------------------------------------
Key: JBWS-2317
URL: https://issues.jboss.org/browse/JBWS-2317
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-metro, jbossws-native
Affects Versions: jbossws-native-3.0.3, jbossws-metro-3.0.3
Reporter: Darran Lofthouse
Assignee: Alessio Soldano
Attachments: Injector.java
The JAXB implementation contains a package of classes to optimise field and method access
by dynamically generating classes to avoid reflection, this has a start-up performance hit
but then leads to an optimised runtime.
The package is: -
'com.sun.xml.bind.v2.runtime.reflect.opt'
Within the Injector class is a HashMap to maintain a cache of these classes against the
classloader they were created for: -
private static final Map<ClassLoader,WeakReference<Injector>> injectors =
Collections.synchronizedMap(new
WeakHashMap<ClassLoader,WeakReference<Injector>>());
A WeakReference has been used to wrap the value to prevent the value retaining a
reference to the ClassLoader and then preventing garbage collection and leading to a
leak.
The problem is that nothing retains a reference to the Injector so as this is wrapped
with a WeakReference it is garbage collected.
I will attach to this case a new version of Injector.java.
The fix switches to using a Strong reference to the Injector so it is not garbage
collected.
To maintain the original requirements the Injector will no longer hold a reference to the
ClassLoader and will instead make use of the one passed in.
Within the Injector the HashMap of classes will reference the Class with a WeakReference.
If we get a WeakReference with no class it means the class was previously loaded but
garbage collected, in this case try to load the class by name from the classloader - if
this fails then redefine the class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4714
days inactive
5694
days old
jbossws-issues@lists.jboss.org
9 comments
3 participants
participants (3)
-
Alessio Soldano (JIRA) -
Darran Lofthouse (JIRA)
-
Richard Kettelerij (JIRA)