6:22 a.m.
Hallo,
Hope I use the right list.
I'm creating a connection to JBoss AS as part of JBASM-3. See below for
code and exception. I can workaround it by setting
"org.jboss.logging.Logger.pluginClass" to "logging.JDK14LoggerPlugin".
But as server manager could be running in any environment I guess
blindly setting this system property is not desirable.
Any other ways I can fix that? Actually the code works but the exception
is visible to the user.
Code like:
ctx=new InitialContext(properties);
MBeanServerConnection connection = (MBeanServerConnection)
ctx.lookup("jmx/rmi/RMIAdaptor");
connection.invoke("jboss.system/type/Server", "shutdown",null,null);
*outputs* an exception:
[server:stop] Shutting down server: profileservice
[server:stop] java.lang.NoClassDefFoundError: org/apache/log4j/Priority
[server:stop] at java.lang.Class.getDeclaredConstructors0(Native Method)
[server:stop] at
java.lang.Class.privateGetDeclaredConstructors(Class.java:235
7)
[server:stop] at java.lang.Class.getConstructor0(Class.java:2671)
[server:stop] at java.lang.Class.newInstance0(Class.java:321)
[server:stop] at java.lang.Class.newInstance(Class.java:303)
[server:stop] at
org.jboss.logging.Logger.getDelegatePlugin(Logger.java:312)
[server:stop] at org.jboss.logging.Logger.<init>(Logger.java:78)
[server:stop] at org.jboss.logging.Logger.getLogger(Logger.java:291)
[server:stop] at
org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:
162)
[server:stop] at
org.jnp.interfaces.NamingContextFactory.getInitialContext(Nam
ingContextFactory.java:55)
...
Thanks much,
Aleksandar
6:51 a.m.
On Wed, 2008-10-08 at 14:22 +0300, Aleksandar Kostadinov wrote:
Hallo,
Hope I use the right list.
Not really unless this turns out to be a jboss development problem
instead of your mistake.
*outputs* an exception:
[server:stop] Shutting down server: profileservice
[server:stop] java.lang.NoClassDefFoundError: org/apache/log4j/Priority
[server:stop] at java.lang.Class.getDeclaredConstructors0(Native Method)
[server:stop] at
java.lang.Class.privateGetDeclaredConstructors(Class.java:235
7)
[server:stop] at java.lang.Class.getConstructor0(Class.java:2671)
[server:stop] at java.lang.Class.newInstance0(Class.java:321)
[server:stop] at java.lang.Class.newInstance(Class.java:303)
[server:stop] at
org.jboss.logging.Logger.getDelegatePlugin(Logger.java:312)
[server:stop] at org.jboss.logging.Logger.<init>(Logger.java:78)
[server:stop] at org.jboss.logging.Logger.getLogger(Logger.java:291)
[server:stop] at
org.jnp.interfaces.NamingContext.<clinit>(NamingContext.java:
162)
[server:stop] at
org.jnp.interfaces.NamingContextFactory.getInitialContext(Nam
ingContextFactory.java:55)
Your classpath is wrong. You have
jboss-logging-log4j.jar in the classpath
but not log4j.jar
FIXES:
* Remove jboss-logging-log4j.jar from the classpath
which will then use the "NullLogger"
* add log4j.jar to the classpath
9 a.m.
Adrian Brock wrote, On 10/08/2008 02:51 PM (EEST):
On Wed, 2008-10-08 at 14:22 +0300, Aleksandar Kostadinov wrote:
> Hallo,
>
> Hope I use the right list.
Not really unless this turns out to be a jboss development problem
instead of your mistake.
Yep, that's right.
<...>
FIXES:
* Remove jboss-logging-log4j.jar from the classpath
which will then use the "NullLogger"
That seems more like a workaround rather than fix. But I actually have
log4j *somehow* in my classpath.
See, I have the server:stop task defined in ant with classpath including
all files in "client" directory. It contains log4j.jar. To get a server
connection, I have to put the classloader created by ant as the thread's
context classloader. To me it seems that log4j classes are not
requested from the thread's context classloader. And I think these should.
Anyways, I'll try to exclude jboss-logging-log4j.jar from the classpath
and see what happens. It will be rather ugly in testsuite/build.xml though.
* add log4j.jar to the classpath
Adding log4j.jar as an additional dependency is not desirable as long as
I'm not logging anything anyways. I mean in the pom.xml of the project.
I'll leave it with the system property solution there. Though I wonder
whether jboss-logging-log4j.jar should be a dependency of
jmx-invoker-adaptor-client and jboss-as-server-client...
Thanks much for the answer,
Aleksandar
8:21 a.m.
Adrian Brock wrote, On 10/08/2008 02:51 PM (EEST):
> FIXES:
>
> * Remove jboss-logging-log4j.jar from the classpath
> which will then use the "NullLogger"
I removed that but still see the same issue. I eventually removed the
jar itself and excluded jbossall-client.jar. To check I'm really not
having it somewhere
Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
Thread.currentThread().getContextClassLoader().loadClass("org.jboss.logging.log4j.Log4jLoggerPlugin");
It throws
java.lang.ClassNotFoundException: org.jboss.logging.log4j.Log4jLoggerPlugin
My only guess is that it is searching for the jboss-logging-log4j.jar in
some predefined locations and happens to find and load it under the
hood. Anyways I filed https://jira.jboss.org/jira/browse/JBLOGGING-7
Any help to workaround that issue will be appreciated!
8:16 a.m.
<explitive-deleted/>
Are you a software developer or a clueless user?
If you raise a bug report explain how to reproduce the problem.
Bug reports are not there so you can delegate investigation
of your broken usage to other developers.
We're not going to play "20 questions" to try to understand
what the real problem is.
Don't "guess". Show what the problem really is.
"My only guess is that it is searching for the jboss-logging-log4j.jar
in some predefined locations and happens to find and load it under the
hood."
There is no such "discovery" mechanism, The jboss Logger class
in init()
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/common/common-logging-spi/trun...
Tries
* the system property
* the log4j plugin class
* null logger
all by looking at the TCL.
Create a reproducable testcase BEFORE you re-open the bug report.
My **GUESS** is that by the time you've reproduced the problem
with simpler code you'll understand what you are doing wrong.
One of your more recent posts suggested it was an ant classloader
problem (which is known to have issues). The usual fix is to
"fork" the process so it uses the real JRE classloader
in a seperate jvm or some other workaround.
http://ant.apache.org/faq.html#delegating-classloader
P.S. Issues with writing ant tasks or its classloading implementation
are not really a subject for the jboss-dev list or jboss bug reports.
On Tue, 2008-10-14 at 16:21 +0300, Aleksandar Kostadinov wrote:
> Adrian Brock wrote, On 10/08/2008 02:51 PM (EEST):
>> FIXES:
>>
>> * Remove jboss-logging-log4j.jar from the classpath
>> which will then use the "NullLogger"
I removed that but still see the same issue. I eventually removed the
jar itself and excluded jbossall-client.jar. To check I'm really not
having it somewhere
Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
Thread.currentThread().getContextClassLoader().loadClass("org.jboss.logging.log4j.Log4jLoggerPlugin");
It throws
java.lang.ClassNotFoundException: org.jboss.logging.log4j.Log4jLoggerPlugin
My only guess is that it is searching for the jboss-logging-log4j.jar in
some predefined locations and happens to find and load it under the
hood. Anyways I filed https://jira.jboss.org/jira/browse/JBLOGGING-7
Any help to workaround that issue will be appreciated!
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
9:58 a.m.
Aleksandar Kostadinov wrote:
> Adrian Brock wrote, On 10/08/2008 02:51 PM (EEST):
>> FIXES:
>>
>> * Remove jboss-logging-log4j.jar from the classpath
>> which will then use the "NullLogger"
I removed that but still see the same issue. I eventually removed the
jar itself and excluded jbossall-client.jar. To check I'm really not
having it somewhere
Thread.currentThread().setContextClassLoader(this.getClass().getClassLoader());
Thread.currentThread().getContextClassLoader().loadClass("org.jboss.logging.log4j.Log4jLoggerPlugin");
It throws
java.lang.ClassNotFoundException: org.jboss.logging.log4j.Log4jLoggerPlugin
My only guess is that it is searching for the jboss-logging-log4j.jar in
some predefined locations and happens to find and load it under the
hood. Anyways I filed https://jira.jboss.org/jira/browse/JBLOGGING-7
Any help to workaround that issue will be appreciated!
Sigh. Did you even bother reading Adrian's reply? This is a list for
developers of jboss to talk about the development of jboss. It's not for
support. If you actually find a bug, and you want to talk about how
*you* plan to fix it, then this is the place to talk about it.
Otherwise, you are posting to the wrong place.
--
Jason T. Greene
JBoss, a division of Red Hat
5934
days inactive
5941
days old
jboss-development@lists.jboss.org
5 comments
3 participants
participants (3)
-
Adrian Brock -
Aleksandar Kostadinov -
Jason T. Greene