[jboss-dev-forums] [Design of JMX on JBoss (JBoss/JMX)] - Re: RepositoryClassLoader::repository Null
adrian@jboss.org
do-not-reply at jboss.com
Wed Dec 12 05:22:53 EST 2007
"clebert.suconic at jboss.com" wrote :
| And the test was fixed by patching this:
|
| Index: jmx/src/main/org/jboss/mx/loading/RepositoryClassLoader.java
| | ===================================================================
| | --- jmx/src/main/org/jboss/mx/loading/RepositoryClassLoader.java (revision 68148)
| | +++ jmx/src/main/org/jboss/mx/loading/RepositoryClassLoader.java (working copy)
| | @@ -620,7 +620,7 @@
| | throw new ClassNotFoundException("Class Not Found(blacklist): " + name);
| | }
| |
| | - Translator translator = repository.getTranslator();
| | + Translator translator = repository==null ? null : repository.getTranslator();
| | if (translator != null)
| | {
| | // Obtain the transformed class bytecode
| |
| |
|
| I already have an issue on the EAP project, and I will commit the change there... but I want someone to validate it (please):
|
| http://jira.jboss.com/jira/browse/JBPAPP-420
| http://jira.jboss.com/jira/browse/JBAS-5071
|
|
The correct fix is
| if (repository == null)
| throw new IllegalStateException("Use of undeployed classloader");
| Translator translator = repository.getTranslator();
|
As Scott says, the real issue is elsewhere.
It's also likely a memory leak.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4112208#4112208
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4112208
More information about the jboss-dev-forums
mailing list