although i've had some trouble adding log4j to my jboss classpath. when i
do, something nasty happens and i get the following stack... should i just
build against this log4j lib, but then not put in my jboss classpath when
running?
log4j:ERROR Could not instantiate class
[org.jboss.logging.log4j.ConsoleAppender
].
java.lang.ClassNotFoundException: org.jboss.logging.log4j.ConsoleAppender
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at
org.apache.log4j.helpers.OptionConverter.instantiateByClassName(Optio
nConverter.java:301)
at
org.apache.log4j.helpers.OptionConverter.instantiateByKey(OptionConve
rter.java:116)
at
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigura
tor.java:612)
at
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigura
tor.java:595)
at
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyC
onfigurator.java:502)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:410)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:309)
at
org.apache.log4j.PropertyWatchdog.doOnChange(PropertyConfigurator.jav
a:665)
at
org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.
java:80)
at
org.apache.log4j.helpers.FileWatchdog.<init>(FileWatchdog.java:49)
at
org.apache.log4j.PropertyWatchdog.<init>(PropertyConfigurator.java:65
7)
at
org.apache.log4j.PropertyConfigurator.configureAndWatch(PropertyConfi
gurator.java:373)
at org.jboss.logging.Log4jService.start(Log4jService.java:122)
at org.jboss.logging.Log4jService.preRegister(Log4jService.java:189)
at
com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServer
Impl.java:2245)
at
com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.ja
va:513)
at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
at org.jboss.Main.<init>(Main.java:182)
at org.jboss.Main$1.run(Main.java:116)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.Main.main(Main.java:112)
log4j:ERROR Could not instantiate appender named "Console".
log4j:ERROR Could not instantiate class
[org.jboss.logging.log4j.JBossCategory$J
BossCategoryFactory].
java.lang.ClassNotFoundException:
org.jboss.logging.log4j.JBossCategory$JBossCat
egoryFactory
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at
org.apache.log4j.helpers.OptionConverter.instantiateByClassName(Optio
nConverter.java:301)
at
org.apache.log4j.PropertyConfigurator.configureCategoryFactory(Proper
tyConfigurator.java:459)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:411)
at
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurato
r.java:309)
at
org.apache.log4j.PropertyWatchdog.doOnChange(PropertyConfigurator.jav
a:665)
at
org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.
java:80)
at
org.apache.log4j.helpers.FileWatchdog.<init>(FileWatchdog.java:49)
at
org.apache.log4j.PropertyWatchdog.<init>(PropertyConfigurator.java:65
7)
at
org.apache.log4j.PropertyConfigurator.configureAndWatch(PropertyConfi
gurator.java:373)
at org.jboss.logging.Log4jService.start(Log4jService.java:122)
at org.jboss.logging.Log4jService.preRegister(Log4jService.java:189)
at
com.sun.management.jmx.MBeanServerImpl.preRegisterInvoker(MBeanServer
Impl.java:2245)
at
com.sun.management.jmx.MBeanServerImpl.createMBean(MBeanServerImpl.ja
va:513)
at javax.management.loading.MLet.getMBeansFromURL(MLet.java:523)
at javax.management.loading.MLet.getMBeansFromURL(MLet.java:369)
at org.jboss.Main.<init>(Main.java:182)
at org.jboss.Main$1.run(Main.java:116)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.Main.main(Main.java:112)
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Scott M
Stark
Sent: Saturday, January 19, 2002 3:23 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Logging
Use log4j. The Logger is just a wrapper on top of log4j that adds support
for a custom TRACE priority used to allow for high frequency messages
inside of the server.
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
From: "Jozsa Kristof" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, January 19, 2002 11:14 AM
Subject: [JBoss-user] Logging
> Hi,
>
> got quickshot question here - what's the most preferred way to use logging
> from my own beans? I don't need anything funky, just something smarter
then
> System.out.println..
>
> I've did a lil' search, and found org.jboss.logging.Logger. Shall I use
it's
> log() or debug() function, or is that anything better/newer/etc?
>
> Thanks,
> Christopher
> --
> .Digital.Yearning.for.Networked.Assassination.and.Xenocide
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
