[JBoss-user] logging issues
Hi folks, I hope someone has solved this riddle already ... I am trying to make use of a 3rd party library that uses LOG4J in the context of JBoss. Unfortunately, this library subclasses the LoggerFactory. The result is that after the first call to this 3rd party API, JBoss stops logging completely. I have already tried scoped classloading for this specific app, but to no avail. Any hints or suggestions are highly appreciated! Thanks, Steve --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] logging issues
Hi folks, I hope someone has solved this riddle already ... I am trying to make use of a 3rd party library that uses LOG4J in the context of JBoss. Unfortunately, this library subclasses the LoggerFactory. The result is that after the first call to this 3rd party API, JBoss stops logging completely. I have already tried scoped classloading for this specific app, but to no avail. Any hints or suggestions are highly appreciated! Thanks, Steve --- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf ___ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging through JBoss from an external source
The org.jboss.logging.Log4jSocketServer MBean, which is not configured
by default,
can be used as the target of org.apache.log4j.net.SocketAppender to
collect output
from mulitple sources in a central location. The Log4jSocketServer uses
a thread
per client that does a MDC.put("host",
clientSocket.getInetAddress().getHostName())
so that output can be distiguished.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, December 23, 2003 7:59 AM
To: [EMAIL PROTECTED]
Subject: [JBoss-user] Logging through JBoss from an external source
I would like to consolidate the logs from several processes, so that I
have only a single log file. (Let's ignore archiving, etc. for now.)
Being relatively new to JBoss, EJBs, etc., I'm looking for advice as to
the best way to do this. Right now, I'm considering having a logging
session bean that the external processes will call when they want to
log. This session bean will then use log4j.
Are there better ways? I noticed that there is a Log4jService MBean.
I
know almost nothing about MBeans. Is there a way I can access that to
do logging, or is that exclusively for "management" operations of some
sort?
Thanks in advance,
Keith
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for
IBM's Free Linux Tutorials. Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging through JBoss from an external source
I would like to consolidate the logs from several processes, so that I have only a single log file. (Let's ignore archiving, etc. for now.) Being relatively new to JBoss, EJBs, etc., I'm looking for advice as to the best way to do this. Right now, I'm considering having a logging session bean that the external processes will call when they want to log. This session bean will then use log4j. Are there better ways? I noticed that there is a Log4jService MBean. I know almost nothing about MBeans. Is there a way I can access that to do logging, or is that exclusively for "management" operations of some sort? Thanks in advance, Keith --- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging EJB calls
Enable the TRACE level on the org.jboss.ejb.plugins.LogInterceptor category in the log4j.xml configuration: -- Scott Stark Chief Technology Officer JBoss Group, LLC Alban Soupper wrote: Hi all, I would like to trace the calls to my EJBs, so I can observe the life (and death) of my EJBs. How can I configure JBoss 3.0.x (and Log4j ?) to print this kind of informations. Thanks by advance. Alban. --- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging EJB calls
I reckon the easiest way is to write an interceptor that logs the call and plug it into your container's interceptor chain. Another option (which I use) is to add logging statements to your EJB's constructor/finalizer/activate/passivate/load/store routines. I maintain a class wide (static) counter which I increase in the constructor and decrease in the finalizer so that I know how many instances JBoss keeps floating around... ++Jos.nl On Tue, Oct 21, 2003 at 12:11:54PM +0200 it came to pass that Alban Soupper wrote: > Hi all, > I would like to trace the calls to my EJBs, so I can observe the life (and > death) of my EJBs. > How can I configure JBoss 3.0.x (and Log4j ?) to print this kind of > informations. > > Thanks by advance. > Alban. > > > *** > > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager to [EMAIL PROTECTED] > > *** > > > > --- > This SF.net email is sponsored by OSDN developer relations > Here's your chance to show off your extensive product knowledge > We want to know what you know. Tell us and you have a chance to win $100 > http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user -- La vida no es la que uno vivió, sino la que recuerda y cómo la recuerda para contarla... ~ Gabriel García Márquez --- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging EJB calls
Hi all, I would like to trace the calls to my EJBs, so I can observe the life (and death) of my EJBs. How can I configure JBoss 3.0.x (and Log4j ?) to print this kind of informations. Thanks by advance. Alban. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager to [EMAIL PROTECTED] *** --- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] logging to specific files using log4j.xml
You have to associate the appender with a category. Try reading the log4j manual
to see how one uses appenders:
http://jakarta.apache.org/log4j/docs/documentation.html
Matthew Hixson wrote:
In server/default/conf/log4j.xml I have the following:
In my class I'm getting a logger and logging a test message like so:
Logger _systemLogger = Logger.getLogger("system");
_systemLogger.debug("Hey, is this thing on?");
The strange thing is that the message does not appear in
/usr/local/jboss/server/default/log/debug.log, and in fact no such file
ever gets created. Instead I see:
2003-09-04 00:56:27,291 DEBUG [system] Hey, is this thing on?
in server/default/log/server.log. That file is mentioned in two of the
appenders that are commented out. I don't know why my messages are
going to that file instead of the one that I have told the appender to use.
Another thing that would be very nice would be the ability to send
everything that met the "system" appender's threshold to both the
logfile and the console. I don't want to have to change the "CONSOLE"
appender's threshold to DEBUG because then I get a ton of messages from
JBoss' internals and this really slows things down.
Attached is my entire log4j.xml.
Thanks in advance,
-M@
--
Scott Stark
Chief Technology Officer
JBoss Group, LLC
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] logging to specific files using log4j.xml
In server/default/conf/log4j.xml I have the following:
In my class I'm getting a logger and logging a test message like so:
Logger _systemLogger = Logger.getLogger("system");
_systemLogger.debug("Hey, is this thing on?");
The strange thing is that the message does not appear in
/usr/local/jboss/server/default/log/debug.log, and in fact no such file
ever gets created. Instead I see:
2003-09-04 00:56:27,291 DEBUG [system] Hey, is this thing on?
in server/default/log/server.log. That file is mentioned in two of the
appenders that are commented out. I don't know why my messages are
going to that file instead of the one that I have told the appender to
use.
Another thing that would be very nice would be the ability to send
everything that met the "system" appender's threshold to both the
logfile and the console. I don't want to have to change the "CONSOLE"
appender's threshold to DEBUG because then I get a ton of messages from
JBoss' internals and this really slows things down.
Attached is my entire log4j.xml.
Thanks in advance,
-M@
log4j.xml
Description: Binary data
Re: [JBoss-user] logging sometimes works, sometimes doesn't
I cannot give you an answer to your question, but I can tell you what I do
to get a logger from within my EJB:
//The logger instance
private transient final Category log =
Category.getInstance(getClass().getName());
from now on, you can use log.info(String msg) or the other methods
associated with the log4j logger.
Hope it will help,
Marco
- Original Message -
From: "Matthew Hixson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 29, 2003 9:07 PM
Subject: [JBoss-user] logging sometimes works, sometimes doesn't
> I am doing some debugging and would like to see all logging messages
> written to the console. In the class of interest I am gaining a
> reference to the logger like so:
>
> private static Logger _systemLogger = Logger.getLogger("CONSOLE");
>
> Sometimes I see messages like:
>
> [CONSOLE] :
>
> but more often than not I don't see them. I haven't been able to
> figure out what it is that makes them show up. Usually when I see them
> its just after restarting JBoss. Anyone know why the messages would
> sometimes appear and other times not?
>This seems like the classic problem of writing to stdout instead of
> stderr in C and learning that your debug messages don't always get
> flushed to the screen when you'd expect them to.
>How can I make certain that my logging info makes it out to the
> console?
>
> JBoss 3.2.1, MacOS X 10.2.6, Java 1.4.1.
>
>Thanks,
> -M@
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] logging sometimes works, sometimes doesn't
I am doing some debugging and would like to see all logging messages
written to the console. In the class of interest I am gaining a
reference to the logger like so:
private static Logger _systemLogger = Logger.getLogger("CONSOLE");
Sometimes I see messages like:
[CONSOLE] :
but more often than not I don't see them. I haven't been able to
figure out what it is that makes them show up. Usually when I see them
its just after restarting JBoss. Anyone know why the messages would
sometimes appear and other times not?
This seems like the classic problem of writing to stdout instead of
stderr in C and learning that your debug messages don't always get
flushed to the screen when you'd expect them to.
How can I make certain that my logging info makes it out to the
console?
JBoss 3.2.1, MacOS X 10.2.6, Java 1.4.1.
Thanks,
-M@
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging question
On Thu, Mar 20, 2003 at 10:54:36PM -0500, David Corbin wrote: > If I have multiple .WARs (often with common classes), is there anyway to > either > 1) detect which .WAR is logging and control logging based on that via > log4j settings > or > 2) or include information about the .WAR in each log line. You could do something like this: Package both WARs in an EAR. Included in the EAR is a jar component that wraps Log4J. It defines methods like: static void logMessage(String message, Class reporter, LogLevel severity); Each WAR contains a local Logger that extends the Logger implemented at the EAR level. It defines methods like: static void logMessage(String message, LogLevel severity); When the Logger subclasses call the superclass, they pass their own class as the reporter. This allows you to filter. Ya it's dirty, but it'll work. -c -- 11:25pm up 150 days, 15:16, 3 users, load average: 4.99, 4.83, 4.53 --- This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging question
If I have multiple .WARs (often with common classes), is there anyway to either 1) detect which .WAR is logging and control logging based on that via log4j settings or 2) or include information about the .WAR in each log line. Thanks. David --- This SF.net email is sponsored by: Tablet PC. Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging to JMS Topic
I'm trying to setup logging to a JMS appender.
>From my log4j.xml:
In jbossmq-destinations-service.xml:
jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager
The jmx-console shows what appears to be a healthy, started jboss.mq.destination MBEAN.
I copied Scott's DurableTopicRecvClient from chap06 of JBOSS_305 examples and
basically changed only the following line:
topic = (Topic) iniCtx.lookup("topic/logFactor5Topic");
Running the client generates:
Begin DurableTopicRecvClient, now=1047596943192
Begin recvSync
[DEBUG,SpyConnectionFactoryObjectFactory] Extracting SpyConnectionFactory from
reference
[DEBUG,SpyConnectionFactoryObjectFactory] The GenericConnectionFactory is:
GenericConnectionFactory:[EMAIL
PROTECTED],connectionProperties={OIL_TCPNODELAY_KEY=yes, PingPeriod=6,
OIL_PORT_KEY=8090, ClientILService=org.jboss.mq.il.oil.OILClientILService,
OIL_ADDRESS_KEY=10.2.65.88}]
[DEBUG,Connection] Setting the clockDaemon's thread factory
[DEBUG,GenericConnectionFactory] Handing out ClientIL:
org.jboss.mq.il.oil.OILClientILService
[DEBUG,OILClientILService] Waiting for the server to connect to me on port 1785
[DEBUG,SpyDestinationObjectFactory] SpyDestinationObjectFactory->getObjectInstance()
Timed out waiting for msg
[DEBUG,SpySession] Session closing.
[DEBUG,SpyMessageConsumer] Message consumer closing.
[DEBUG,Connection] Connection:
removeSession(dest=TOPIC.logFactor5Topic.DurableSubscriberExample.chap6-ex1dtps)
[DEBUG,OILClientILService] Closing receiver connections on port: 1785
End DurableTopicRecvClient
While it was running, I dropped a few jars in and out of the deploy directory to
generate some console logging in the hopes that I would see the same logging in the
DurableTopicRecvClient.
It's not clear to me that log messages are actually making it to the topic. I do have
an empty TOPIC.logFactor5Topic.DurableSubscriberExample.chap6-ex1dtps folder under
db/jbossmq/file.
Any hints are appreciated
thanks,
Marty La Jeunesse
---
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging DBPool-size usage
The "close connections for you and warn loudly" in 3.2RC2 and all cvs versions will probably work better than logging for this. david jencks On 2003.02.27 18:27 MailMan wrote: > The main reason for this trace, is because we just gone public with a > e-shop and we have seen some strange db-wanings (unable to obtain > database-connections) - so besides from investigating this error, we just > want to be really really sure that all connections are closed. > So for debugging purposes this is a nice feature - just let the server > run for at while, and if there are to many unused connections, it is > pretty simple to back-track the log and find the error. > > - René > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of David Jencks > Sent: 28. februar 2003 00:16 > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Logging DBPool-size usage > > > Did you try setting the org.jboss.resource.connectionmanager log level to > TRACE? > > I think you will get what you want and more. > > Why do you want this? If it seems like a generally useful feature it > might > be a good idea to have an additional category for loggin just this info > without any other fluff. However, all current cvs versions loudly warn > you > if you do not close a connection, and soon if not already the jsr-77 > stuff > will let you get pool statistics. > > > david jencks > > On 2003.02.27 17:37 René Nygaard wrote: > > Hello all > > > > Jboss3.0.6 (soon 3.2x) > > We have in a previous JBoss (2x i think) been able to log all usage of > > the database pool-sizes, eg. when a connection is made and after > > disconnecting. > > But now we need this info again, and cant find the switch to enable > this > > information! > > Where can we enable this info ? > > > > thanks in advance > > --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging DBPool-size usage
The main reason for this trace, is because we just gone public with a e-shop and we have seen some strange db-wanings (unable to obtain database-connections) - so besides from investigating this error, we just want to be really really sure that all connections are closed. So for debugging purposes this is a nice feature - just let the server run for at while, and if there are to many unused connections, it is pretty simple to back-track the log and find the error. - René -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Jencks Sent: 28. februar 2003 00:16 To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Logging DBPool-size usage Did you try setting the org.jboss.resource.connectionmanager log level to TRACE? I think you will get what you want and more. Why do you want this? If it seems like a generally useful feature it might be a good idea to have an additional category for loggin just this info without any other fluff. However, all current cvs versions loudly warn you if you do not close a connection, and soon if not already the jsr-77 stuff will let you get pool statistics. david jencks On 2003.02.27 17:37 René Nygaard wrote: > Hello all > > Jboss3.0.6 (soon 3.2x) > We have in a previous JBoss (2x i think) been able to log all usage of > the database pool-sizes, eg. when a connection is made and after > disconnecting. > But now we need this info again, and cant find the switch to enable this > information! > Where can we enable this info ? > > thanks in advance +,~wzf¢+,¦ì¢·o$áyyézW(ëhç¤ æ¯zxm¶ÿ¶§Ê&þÇÉ,ºÇ«¨¥x%ËI,ºÇ«+-²Ê.Ç¢¸ ëa¶Úlÿùb²Û,¢êÜyú+éÞ·ùb²Û?+-wèþ6è²Ë¬z
Re: [JBoss-user] Logging DBPool-size usage
Did you try setting the org.jboss.resource.connectionmanager log level to TRACE? I think you will get what you want and more. Why do you want this? If it seems like a generally useful feature it might be a good idea to have an additional category for loggin just this info without any other fluff. However, all current cvs versions loudly warn you if you do not close a connection, and soon if not already the jsr-77 stuff will let you get pool statistics. david jencks On 2003.02.27 17:37 René Nygaard wrote: > Hello all > > Jboss3.0.6 (soon 3.2x) > We have in a previous JBoss (2x i think) been able to log all usage of > the database pool-sizes, eg. when a connection is made and after > disconnecting. > But now we need this info again, and cant find the switch to enable this > information! > Where can we enable this info ? > > thanks in advance > - René > NygaardÿÓ+,ÿùÞµéX¬²'²Þu¼ÿN§gg¥r¶ zH^j÷§þmÿÿÿ¶§ÿ÷(û ÿÿÿÉ,þë ®f¢)à+-$,ÿû¬zÿåËlþÊ.Ç¢¸ þwÛiÿÿÿ+-ÿû(º· ~àÿùÞ·ùb²Û?+-wèþ6è²ÿî --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging DBPool-size usage
Hello all Jboss3.0.6 (soon 3.2x) We have in a previous JBoss (2x i think) been able to log all usage of the database pool-sizes, eg. when a connection is made and after disconnecting. But now we need this info again, and cant find the switch to enable this information! Where can we enable this info ? thanks in advance - René NygaardN¬±ùÞµéX¬²'²Þu¼)äç¤Yé\¢g¢½éá¶ÚþØbH zG(û $,²ë ®f¢)à+-$,²ë ®X¬¶Ë(º· ~àzwÛi³ÿåËl²«qç讧zßåËlþX¬¶)ߣøÛ¢Ë.±ê
RE: [JBoss-user] Logging threshold...
Thanks, I actually tried that earlier, but it didn't work. From what I gather it was because I was invoking the reconfigure method that didn't take a parameter. As soon as I used the one which took a String parameter and I filled in the URL, everything worked. -Eric On Thu, 2003-02-06 at 13:17, Sebastian Hauer wrote: > Hi Eric, > > Change your servers log4j.xml file, go to the jmx-console, click on the > jboss.system:service=Logging,type=Log4jService Mbean link and invoke the > reconfigure() method. > > Sebastian > > > -Original Message- > > From: Eric Klimas [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, February 06, 2003 11:52 AM > > To: [EMAIL PROTECTED] > > Subject: [JBoss-user] Logging threshold... > > > > > > Hi all, > > > > I'm running Jboss3.0.4 Tomcat 4.1.12, and was wondering if > > there was some way to change the logging threshold of the > > server without having to restart jboss or redeploy my app > > (i.e. via the jmx-console). Probably a simple answer for > > somebody, but I can't seem to find it > > > --- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld http://www.vasoftware.com > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user -- Eric Klimas <[EMAIL PROTECTED]> --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging threshold...
Hi Eric, Change your servers log4j.xml file, go to the jmx-console, click on the jboss.system:service=Logging,type=Log4jService Mbean link and invoke the reconfigure() method. Sebastian > -Original Message- > From: Eric Klimas [mailto:[EMAIL PROTECTED]] > Sent: Thursday, February 06, 2003 11:52 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-user] Logging threshold... > > > Hi all, > > I'm running Jboss3.0.4 Tomcat 4.1.12, and was wondering if > there was some way to change the logging threshold of the > server without having to restart jboss or redeploy my app > (i.e. via the jmx-console). Probably a simple answer for > somebody, but I can't seem to find it --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging threshold...
Hi all, I'm running Jboss3.0.4 Tomcat 4.1.12, and was wondering if there was some way to change the logging threshold of the server without having to restart jboss or redeploy my app (i.e. via the jmx-console). Probably a simple answer for somebody, but I can't seem to find it Thanks, Eric -- Eric Klimas <[EMAIL PROTECTED]> --- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] logging in a clustered environment
Try send log to syslog ( in UNIX environment ) by using SyslogAppender. For security reasons is good sending log to another computer ( maybe over firewall ). When server is compromited, cracker cannot remove logs. I don't know if it's possible make similar on WIndow$. I don't use it. cheers vlk BTW. In Linux ( Red Hat ) is disabled remote logging. You need add options "-r" and "-l" to /etc/sysconfig/syslog. > -Original Message- > From: Sacha Labourey [mailto:[EMAIL PROTECTED]] > Sent: 19. novembra 2002 17:19 > To: [EMAIL PROTECTED] > Subject: RE: [JBoss-user] logging in a clustered environment > > > This is a log4j configuration issue (you should check all > available log4j > plugins). I personnaly prefer one log per server for small > clusters but you > may want a unified log for your own (application-level) > logging information. > > Cheers, > > > Sacha > > > -Message d'origine- > > De : [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]De la part de Emerson > > Cargnin - SICREDI Serviços > > Envoyé : mardi, 19 novembre 2002 17:16 > > À : [EMAIL PROTECTED] > > Objet : [JBoss-user] logging in a clustered environment > > > > > > How do I make a unique log in a clustered environment, is > this used by > > someone? Or a log per node is a better approache? > > -- > > > > | Emerson Cargnin | > > | Analista de Sistemas Sr. | > > | Tel : (051) 3358-4959| > > | SICREDI Serviços | > > | Porto Alegre - Brasil| > > |xx| > > > > > > > > --- > > This sf.net email is sponsored by: To learn the basics of securing > > your web site with SSL, click here to get a FREE TRIAL of a Thawte > > Server Certificate: http://www.gothawte.com/rd524.html > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > > > --- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > --- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] logging in a clustered environment
How do I make a unique log in a clustered environment, is this used by someone? Or a log per node is a better approache? -- | Emerson Cargnin | | Analista de Sistemas Sr. | | Tel : (051) 3358-4959| | SICREDI Serviços | | Porto Alegre - Brasil| |xx| --- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] logging in a clustered environment
This is a log4j configuration issue (you should check all available log4j plugins). I personnaly prefer one log per server for small clusters but you may want a unified log for your own (application-level) logging information. Cheers, Sacha > -Message d'origine- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]De la part de Emerson > Cargnin - SICREDI Serviços > Envoyé : mardi, 19 novembre 2002 17:16 > À : [EMAIL PROTECTED] > Objet : [JBoss-user] logging in a clustered environment > > > How do I make a unique log in a clustered environment, is this used by > someone? Or a log per node is a better approache? > -- > > | Emerson Cargnin | > | Analista de Sistemas Sr. | > | Tel : (051) 3358-4959| > | SICREDI Serviços | > | Porto Alegre - Brasil| > |xx| > > > > --- > This sf.net email is sponsored by: To learn the basics of securing > your web site with SSL, click here to get a FREE TRIAL of a Thawte > Server Certificate: http://www.gothawte.com/rd524.html > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > --- This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging problem
> I am using Struts framework --> JBoss 3.0 (Stateless Session Beans) --> > Castor JDO. > > How can I separate the Castor logging from JBoss logging and have a > separate file for the output ? change the log4j.xml file int he conf dir of the server config you are using. Essentially this is a log4j issue - what you want to do is configure it so some "categories" go to one appender (file) and some go to another. I've attached my log4j.xml file which hopefully will giv eyou a start on this. cheesr dim http://jakarta.apache.org/log4j/"; debug="false">
[JBoss-user] Logging problem
Hi, I am using Struts framework --> JBoss 3.0 (Stateless Session Beans) --> Castor JDO. How can I separate the Castor logging from JBoss logging and have a separate file for the output ? Thanks in advance. Regards, Arijit --- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with Jboss 3.0
Ahh, thanks! On Thu, 2002-07-25 at 02:10, Alex Loubyansky wrote: > Hello Ryan, > > JBoss uses log4j for logging. All you need is to have a Category > variable in your class and configure logging if neccessary in > log4j.xml. > > alex > > Thursday, July 25, 2002, 9:47:33 AM, you wrote: > > RM> Is there a best practice for having my application output to the jboss > RM> logs? I haven't been able to find an docs or archived list threads on > RM> printing to the jboss logs in 3.0. > > RM> -ryan > > -- > Best regards, > Alex Loubyansky > -- Humans are the unfortunate result of a local maximum in the fitness landscape. www.ryanmarsh.com --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with Jboss 3.0
Hello Ryan, JBoss uses log4j for logging. All you need is to have a Category variable in your class and configure logging if neccessary in log4j.xml. alex Thursday, July 25, 2002, 9:47:33 AM, you wrote: RM> Is there a best practice for having my application output to the jboss RM> logs? I haven't been able to find an docs or archived list threads on RM> printing to the jboss logs in 3.0. RM> -ryan -- Best regards, Alex Loubyansky --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging with Jboss 3.0
Is there a best practice for having my application output to the jboss logs? I haven't been able to find an docs or archived list threads on printing to the jboss logs in 3.0. -ryan -- Humans are the unfortunate result of a local maximum in the fitness landscape. www.ryanmarsh.com --- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging problem
I have been reading the forums, but haven seen an error quite like I am having with Log4j and JBoss/Jetty 3.0.0 I started using log4j with the standard log4j initialization servlet from their sample code, well I got and error that the display was looping and it would just lock up. After a little reading I realized that jboss has there own PropertyConfigurator that is being used by the server so I figured I would just not configure my app and use yours for the time being. That worked fine except now I get this error after the server sits for a while and I am assuming trys to passivate: 14:03:22,617 ERROR [Log4jService$ThrowableListenerLoggingAdapter] unhandled throwable java.rmi.ServerException: Could not passivate; nested exception is: java.rmi.MarshalException: Invalid remote object I gather that this is because I am using JBoss's configuration for logging, but I really do need to know how to deploy with either the servlet or some other way. It seems like a few people have had this problem, but I haven't seen any clear responses on what they have done to solve it. Thanks, Bryan __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
Hello!
Thanks everyone, now logging works as desired!
Dimitri
On Mon, 8 Jul 2002 12:27:09 +0100, you wrote:
>On Mon, Jul 08, 2002 at 12:42:30AM +0200, Dimitri PISSARENKO wrote:
>
>
>
>> does not work in my case (although logger.isDebugEnabled() returns
>> true).
>>
>> Does someone know, how one can get the reference to the Logger from
>> wihin an EJB?
>
>I found that I needed to drop the Console appenders "Threshold" to
>DEBUG. You'll also need to limit the "org.jboss" category to "INFO" if
>you do this, but that should be a case of editing the log4j.xml file
>in the server/${server.name}/conf directory. I also added a category
>for my own classes.
>
>The log4j.xml that ships with JBoss is well commented, so you
>shouldn't find anything too frightening.
>
>Cheers,
>
>Simon
---
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
On Mon, Jul 08, 2002 at 12:42:30AM +0200, Dimitri PISSARENKO wrote:
> does not work in my case (although logger.isDebugEnabled() returns
> true).
>
> Does someone know, how one can get the reference to the Logger from
> wihin an EJB?
I found that I needed to drop the Console appenders "Threshold" to
DEBUG. You'll also need to limit the "org.jboss" category to "INFO" if
you do this, but that should be a case of editing the log4j.xml file
in the server/${server.name}/conf directory. I also added a category
for my own classes.
The log4j.xml that ships with JBoss is well commented, so you
shouldn't find anything too frightening.
Cheers,
Simon
--
"The idea of a karaoke version of ``My Way'' that lasts for 3750
minutes is just too frightening to consider."
Programming Ruby, the Pragmatic Programmers
---
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
Thanks for pointing that out - I do indeed have a downlevel version of log4j
source code. However, the JBoss source is NOT using
org.apache.log4j.Logger, which as you point out extends Category. Instead
the source is using org.jboss.logging.Logger, which does not extend
Category, but instead wraps it.
- Original Message -
From: "Andreas Kuckartz" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 08, 2002 12:41 AM
Subject: Re: [JBoss-user] Logging from within EJBs
> > How can JBoss deprecate an interface in a separate package?
>
> Category has been deprecated by the log4j project:
>
> "This class has been deprecated and replaced by the Logger subclass. It
will
> be kept around to preserve backward compatibility until mid 2003.
>
> Logger is a subclass of Category, i.e. it extends Category. In other
words,
> a logger is a category. Thus, all operations that can be performed on a
> category can be performed on a logger. Whenever log4j is asked to produce
a
> Category object, it will instead produce a Logger object. However, methods
> that previously accepted category objects still continue to accept
category
> objects.
>
> For example, the following are all legal and will work as expected.
>
>// Deprecated form:
>Category cat = Category.getInstance("foo.bar")
>
>// Preferred form for retrieving loggers:
>Logger logger = Logger.getLogger("foo.bar")
>
> The first form is deprecated and should be avoided.
>
> There is absolutely no need for new client code to use or refer to the
> Category class. Whenever possible, please avoid referring to it or using
> it."
>
> http://jakarta.apache.org/log4j/docs/api/index.html
>
> Andreas
>
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Oh, it's good to be a geek.
> http://thinkgeek.com/sf
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
---
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
> How can JBoss deprecate an interface in a separate package?
Category has been deprecated by the log4j project:
"This class has been deprecated and replaced by the Logger subclass. It will
be kept around to preserve backward compatibility until mid 2003.
Logger is a subclass of Category, i.e. it extends Category. In other words,
a logger is a category. Thus, all operations that can be performed on a
category can be performed on a logger. Whenever log4j is asked to produce a
Category object, it will instead produce a Logger object. However, methods
that previously accepted category objects still continue to accept category
objects.
For example, the following are all legal and will work as expected.
// Deprecated form:
Category cat = Category.getInstance("foo.bar")
// Preferred form for retrieving loggers:
Logger logger = Logger.getLogger("foo.bar")
The first form is deprecated and should be avoided.
There is absolutely no need for new client code to use or refer to the
Category class. Whenever possible, please avoid referring to it or using
it."
http://jakarta.apache.org/log4j/docs/api/index.html
Andreas
---
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
How can JBoss deprecate an interface in a separate package? I see what you
are referring to - jboss-all\common\src\main\org\jboss\logging\Logger.java
wraps Category so it can introduce Trace level logging. I wasn't aware of
this - thanks for pointing it out. I don't necessarily agree with it (since
Log4j is a standalone package, I think it would be better to stay compatible
with it.) We are, of course, free to continue to use the Category
interface.
- Original Message -
From: "Stephen Coy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 07, 2002 10:29 PM
Subject: Re: [JBoss-user] Logging from within EJBs
> He *is* using log4j. Your suggestion below is a "deprecated" interface.
>
> I suspect that he is not looking in the right place for the debug
> messages.
>
> Debug messages only appear in the log/server.log file, not on the
> console.
>
> This works for us btw.
>
>
> On Monday, July 8, 2002, at 11:34 AM, Guy Rouillier wrote:
>
> > Use log4j, e.g.,
> >
> >private final Category log =
> > Category.getInstance(getClass().getName());
> >
> > - Original Message -
> > From: "Dimitri PISSARENKO" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Sunday, July 07, 2002 6:42 PM
> > Subject: [JBoss-user] Logging from within EJBs
> >
> >
> > Hello!
> >
> > I want some of the events in the life of my EJBs to be logged at debug
> > level. The usual way to get an instance of Logger
> >
> > class ProjectBean ...
> > {
> > ...
> > private Logger logger = Logger.getLogger(ProjectBean.class);
> > }
> >
> > and invokation of
> >
> > if (logger.isDebugEnabled())
> > {
> > logger.debug("...")
> > }
> >
> > does not work in my case (although logger.isDebugEnabled() returns
> > true).
> >
> > Does someone know, how one can get the reference to the Logger from
> > wihin an EJB?
> >
> > Thanks
> >
> > Dimitri Pissarenko
> >
> >
> > ---
> > This sf.net email is sponsored by:ThinkGeek
> > We have stuff for geeks like you.
> > http://thinkgeek.com/sf
> > ___
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
> >
> >
> >
> >
> >
> >
> > ---
> > This sf.net email is sponsored by:ThinkGeek
> > We have stuff for geeks like you.
> > http://thinkgeek.com/sf
> > ___
> > JBoss-user mailing list
> > [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> We have stuff for geeks like you.
> http://thinkgeek.com/sf
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
---
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
He *is* using log4j. Your suggestion below is a "deprecated" interface.
I suspect that he is not looking in the right place for the debug
messages.
Debug messages only appear in the log/server.log file, not on the
console.
This works for us btw.
On Monday, July 8, 2002, at 11:34 AM, Guy Rouillier wrote:
> Use log4j, e.g.,
>
>private final Category log =
> Category.getInstance(getClass().getName());
>
> - Original Message -
> From: "Dimitri PISSARENKO" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, July 07, 2002 6:42 PM
> Subject: [JBoss-user] Logging from within EJBs
>
>
> Hello!
>
> I want some of the events in the life of my EJBs to be logged at debug
> level. The usual way to get an instance of Logger
>
> class ProjectBean ...
> {
> ...
> private Logger logger = Logger.getLogger(ProjectBean.class);
> }
>
> and invokation of
>
> if (logger.isDebugEnabled())
> {
> logger.debug("...")
> }
>
> does not work in my case (although logger.isDebugEnabled() returns
> true).
>
> Does someone know, how one can get the reference to the Logger from
> wihin an EJB?
>
> Thanks
>
> Dimitri Pissarenko
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> We have stuff for geeks like you.
> http://thinkgeek.com/sf
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
>
>
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> We have stuff for geeks like you.
> http://thinkgeek.com/sf
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging from within EJBs
Use log4j, e.g.,
private final Category log = Category.getInstance(getClass().getName());
- Original Message -
From: "Dimitri PISSARENKO" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, July 07, 2002 6:42 PM
Subject: [JBoss-user] Logging from within EJBs
Hello!
I want some of the events in the life of my EJBs to be logged at debug
level. The usual way to get an instance of Logger
class ProjectBean ...
{
...
private Logger logger = Logger.getLogger(ProjectBean.class);
}
and invokation of
if (logger.isDebugEnabled())
{
logger.debug("...")
}
does not work in my case (although logger.isDebugEnabled() returns
true).
Does someone know, how one can get the reference to the Logger from
wihin an EJB?
Thanks
Dimitri Pissarenko
---
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
---
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging from within EJBs
Hello!
I want some of the events in the life of my EJBs to be logged at debug
level. The usual way to get an instance of Logger
class ProjectBean ...
{
...
private Logger logger = Logger.getLogger(ProjectBean.class);
}
and invokation of
if (logger.isDebugEnabled())
{
logger.debug("...")
}
does not work in my case (although logger.isDebugEnabled() returns
true).
Does someone know, how one can get the reference to the Logger from
wihin an EJB?
Thanks
Dimitri Pissarenko
---
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging mbean to a separate log
I have made a MBean that logs normally with log4j. The problem is that it logs so much that I want the output to a separate file, and not in the main logfile. I have managed to have the output in a separate file using a new appender, and a with to that logger, but I can't find an easy way to exclude the output to the main log (root category). It outputs the logging from the mbean to both server.log and mylog.log. Have anyone a clue of how to do this? I can't find a comprehensive doc on log4j, not in the for-pay-doc on log4j either. Thanks Marius K Boostcom signature.asc Description: This is a digitally signed message part
[JBoss-user] Logging JDBC Connections
We have upgraded JBoss version from 2.4.3 to the 2.4.4 version. In JBoss 2.4.3 we could log the number of JDBC connection (opened/used/max) setting to true one of the attributes of the connection in jboss.jcml file true What should we do to obtain the same information in the upgraded version 2.4.4. TIA ___ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] logging of server side conatiner exceptions
I believe stuff sent via System.out winds up being redirected to the logs as DEBUG level messages. Peter Levart wrote: > Hello! > > I noticed that in the recent CVS version of JBoss 3.0 the exceptions thrown > by the container don't get logged to the CONSOLE or FILE any more. Since the > stack trace is lost on the client side (with jdk 1.3 at least), it is hard to > diagnose them. Is there any way to enable logging or display of those > exceptions. Also I noticed, that anything that is printed via System.out is > lost too... > > > Peter > > ___ > 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] logging of server side conatiner exceptions
Hello! I noticed that in the recent CVS version of JBoss 3.0 the exceptions thrown by the container don't get logged to the CONSOLE or FILE any more. Since the stack trace is lost on the client side (with jdk 1.3 at least), it is hard to diagnose them. Is there any way to enable logging or display of those exceptions. Also I noticed, that anything that is printed via System.out is lost too... Peter ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] logging and admininstration
I'm not sure.
I've been thinking about writing a PropertyService
for setting properties. This would allow them to be configured
in jboss.jcml and also allow them to be changed at runtime through
the JMX interface.
But it is about priority 145 on my to-do list :-)
Note: This won't work for all properties. I think some
are only checked by the JVM at start-up.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] logging and admininstration
>Date: Tue, 19 Feb 2002 07:10:47 -0500
>
>thanks. if i move to 2.4.4 though, what is the proper solution for setting
>system properties -D?
>
>-Original Message-
>From: Adrian Brock [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, February 19, 2002 5:20 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: RE: [JBoss-user] logging and admininstration
>
>
>You can create a classpath extension for a directory
>in jboss.conf.
>Just put a '/' on the end of the url and don't put
>any jars or zips in the directory.
>
>Regards,
>Adrian
>
> >From: "Eric Kaplan" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >CC: <[EMAIL PROTECTED]>
> >Subject: RE: [JBoss-user] logging and admininstration
> >Date: Mon, 18 Feb 2002 22:15:32 -0500
> >
> >couple more questions wrt 3 below. we're using jboss 2.4.1, which seems
>to
> >use jboss.properties, but i think you're saying that the latest version
>of
> >jboss no longer uses it? also, in development we have a classes
>directory
> >which contains the heierarchy of all our class files, so there is no jar
>to
> >copy to lib/ext. what should we do in this case?
> >
> >thanks
> >
> >eric
> >
> >
> >
> >-Original Message-
> >From: Adrian Brock [mailto:[EMAIL PROTECTED]]
> >Sent: Monday, February 18, 2002 1:43 PM
> >To: [EMAIL PROTECTED]
> >Cc: [EMAIL PROTECTED]
> >Subject: Re: [JBoss-user] logging and admininstration
> >
> >
> >Here's some short answers.
> >
> >1) Stop on error
> >JBoss is designed to host many services concurrently.
> >There is no mechanism to say one is critical and end the server.
> >
> >JBoss3.0 introduces the ideas of dependencies.
> >If the database doesn't come up, neither will services that
> >use it, instead they wait. When you fix the database config,
> >restart the database service and all the dependencies start as well.
> >There is no need to end the server.
> >You can do a similar thing on 2.4.4, but you have to manually
> >work out the dependencies, i.e. which services need to be restarted.
> >
> >2) Log4j
> >The best way to do logging for a bean (at the moment)
> >private static final Category log = Category.newInstance(MyClass.class);
> >
> >If you want to separate the logging from JBoss, change
> >log4.properties to have something like
> >
> >log4j.com.acme=INFO, MyAppender
> >log4j.additivity.com.acme=false
> >log4j.appender.MyAppender={etc.}
> >
> >Assuming all your beans are in the package com.acme
> >
> >If you want to customize log4j, put your customisations in a jar,
> >and add the jar to the Log4jService "archives" attribute in jboss.conf
> >Be careful, make sure your customisations don't conflict with
> >jboss's own.
> >
> >3) run.bat
> >Don't put anything in the classpath of run.bat, especially not
> >something that uses Class.forName() to load classes.
> >Put your jars in jboss/lib/ext
> >There used to be a jboss.properties for system properties. It was
> >removed, I don't know why? I guess it was used as a dumping ground
> >by developers when they should have been using jboss.jcml for
> >configuration.
> >
> >Regards,
> >Adrian
> >
> >
> > >From: "Eric Kaplan" <[EMAIL PROTECTED]>
> > >To: <[EMAIL PROTECTED]>
> > >Subject: [JBoss-user] logging and admininstration
> > >Date: Mon, 18 Feb 2002 12:25:27 -0500
> > >
> > >Three questions:
> > >
> > >1. Typically, we bring up the application server and eyeball the output
> >for
> > >obvious errors, which are one of three typically:
> > > - Cannot bind to the required port, usually because a jboss instance
> > >is already running
> > > - Cannot create one or more db pools, usually because the database
> > >is down
> > > - One or more errors deploying the beans, including verifier
> > >
RE: [JBoss-user] logging and admininstration
log4.jar is in lib/ext, not lib4j-core.ext. perhaps this is the time to upgrade to 2.4.4. thanks for your help eric -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 19, 2002 6:02 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-user] logging and admininstration Hi, I can imagine your frustration. I can't see any bug fixes since 2.4.1 except for RMI-IIOP checking in the verifier and license changes from GPL to LGPL. This certainly works in 2.4.4, sorry I've never used 2.4.1 Maybe the fix isn't in an obvious place? Do you have log4j.jar in lib/ext? Don't put it in the classpath, it can't see the rest of the system from there, hence the other errors you report. Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] logging and admininstration >Date: Mon, 18 Feb 2002 21:58:46 -0500 > >Adrian > >I'm not sure what I need to do still. I added the simple log4j code you >suggested to one of my beans, and when i started jboss, without putting >log4j.jars in the startup classpath, I get... > >[Verifier] java.lang.NoClassDefFoundError: org/apache/log4j/Category >[Verifier] at >com.abp.ejb.ybpreloadprocessor.YBPreloadProcessorBean. >(YBPreloadProcessorBean.java:46) >[Verifier] at java.lang.Class.newInstance0(Native Method) >[Verifier] at java.lang.Class.newInstance(Unknown Source) >[Verifier] at >org.jboss.verifier.strategy.AbstractVerifier.hasDefaultConstr >uctor(AbstractVerifier.java:356) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.verifySessionBean(E >JBVerifier11.java:630) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.checkSession(EJBVer >ifier11.java:93) >[Verifier] at >org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:134) > >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:4 >67) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >69) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >04) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.j >ava:494) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeploy >er.java:468) >[Verifier] at >org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:20 >8) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379) >[Verifier] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217) >[Verifier] at >org.jboss.ejb.AutoDeployer.startService(AutoDeployer.java:353 >) >[Verifier] at >org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport. >java:107) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.configuration.ConfigurationService$ServiceProxy.inv >oke(ConfigurationService.java:836) >[Verifier] at $Proxy0.start(Unknown Source) >[Verifier] at >org.jboss.util.ServiceControl.start(ServiceControl.java:81) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.Main.(Main.java:210) >[Verifier] at org.jboss.Main$1.run(Main.java:116) >[Verifier] at java.security.AccessController.doPrivileged(Native >Method) >[Verifier] at org.jboss.Main.main(Main.java:112) >[Container factory] Deploying YBPreloadProcessorEJB >[Bean Cache] Cache policy scheduler started > > >If I then explicitly put log4j.jar, I get a different error... > >JBOSS_CLASSPATH=c:\armanta-abp\build\classes;c:\armanta\lib\log4j.jar;c:\ar m >anta >\build\lib\ext\jakarta-regexp-1.2.jar;c:\armanta\build\lib\ext\classes12.zi p >;c:\ &g
RE: [JBoss-user] logging and admininstration
Hi, I can imagine your frustration. I can't see any bug fixes since 2.4.1 except for RMI-IIOP checking in the verifier and license changes from GPL to LGPL. This certainly works in 2.4.4, sorry I've never used 2.4.1 Maybe the fix isn't in an obvious place? Do you have log4j.jar in lib/ext? Don't put it in the classpath, it can't see the rest of the system from there, hence the other errors you report. Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] logging and admininstration >Date: Mon, 18 Feb 2002 21:58:46 -0500 > >Adrian > >I'm not sure what I need to do still. I added the simple log4j code you >suggested to one of my beans, and when i started jboss, without putting >log4j.jars in the startup classpath, I get... > >[Verifier] java.lang.NoClassDefFoundError: org/apache/log4j/Category >[Verifier] at >com.abp.ejb.ybpreloadprocessor.YBPreloadProcessorBean. >(YBPreloadProcessorBean.java:46) >[Verifier] at java.lang.Class.newInstance0(Native Method) >[Verifier] at java.lang.Class.newInstance(Unknown Source) >[Verifier] at >org.jboss.verifier.strategy.AbstractVerifier.hasDefaultConstr >uctor(AbstractVerifier.java:356) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.verifySessionBean(E >JBVerifier11.java:630) >[Verifier] at >org.jboss.verifier.strategy.EJBVerifier11.checkSession(EJBVer >ifier11.java:93) >[Verifier] at >org.jboss.verifier.BeanVerifier.verify(BeanVerifier.java:134) > >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:4 >67) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >69) >[Verifier] at >org.jboss.ejb.ContainerFactory.deploy(ContainerFactory.java:3 >04) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startModules(J2eeDeployer.j >ava:494) >[Verifier] at >org.jboss.deployment.J2eeDeployer.startApplication(J2eeDeploy >er.java:468) >[Verifier] at >org.jboss.deployment.J2eeDeployer.deploy(J2eeDeployer.java:20 >8) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.ejb.AutoDeployer.deploy(AutoDeployer.java:379) >[Verifier] at org.jboss.ejb.AutoDeployer.run(AutoDeployer.java:217) >[Verifier] at >org.jboss.ejb.AutoDeployer.startService(AutoDeployer.java:353 >) >[Verifier] at >org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport. >java:107) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at >org.jboss.configuration.ConfigurationService$ServiceProxy.inv >oke(ConfigurationService.java:836) >[Verifier] at $Proxy0.start(Unknown Source) >[Verifier] at >org.jboss.util.ServiceControl.start(ServiceControl.java:81) >[Verifier] at java.lang.reflect.Method.invoke(Native Method) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1628) >[Verifier] at >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl >.java:1523) >[Verifier] at org.jboss.Main.(Main.java:210) >[Verifier] at org.jboss.Main$1.run(Main.java:116) >[Verifier] at java.security.AccessController.doPrivileged(Native >Method) >[Verifier] at org.jboss.Main.main(Main.java:112) >[Container factory] Deploying YBPreloadProcessorEJB >[Bean Cache] Cache policy scheduler started > > >If I then explicitly put log4j.jar, I get a different error... > >JBOSS_CLASSPATH=c:\armanta-abp\build\classes;c:\armanta\lib\log4j.jar;c:\arm >anta >\build\lib\ext\jakarta-regexp-1.2.jar;c:\armanta\build\lib\ext\classes12.zip >;c:\ >armanta\build\classes;c:\armanta\build\lib\help.jar;run.jar;../lib/crimson.j >ar >jboss.home = C:\armanta-3rdparty\JBoss-2.4.1_Jetty-3.1.RC9-1\jboss >Using JAAS LoginConfig: >file:/C:/armanta-3rdparty/JBoss-2.4.1_Jetty-3.1.RC9-1/jb >oss/conf/default/auth.conf >Using configuration "default" >log4j:ERROR Could not
RE: [JBoss-user] logging and admininstration
You can create a classpath extension for a directory
in jboss.conf.
Just put a '/' on the end of the url and don't put
any jars or zips in the directory.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>CC: <[EMAIL PROTECTED]>
>Subject: RE: [JBoss-user] logging and admininstration
>Date: Mon, 18 Feb 2002 22:15:32 -0500
>
>couple more questions wrt 3 below. we're using jboss 2.4.1, which seems to
>use jboss.properties, but i think you're saying that the latest version of
>jboss no longer uses it? also, in development we have a classes directory
>which contains the heierarchy of all our class files, so there is no jar to
>copy to lib/ext. what should we do in this case?
>
>thanks
>
>eric
>
>
>
>-Original Message-
>From: Adrian Brock [mailto:[EMAIL PROTECTED]]
>Sent: Monday, February 18, 2002 1:43 PM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: Re: [JBoss-user] logging and admininstration
>
>
>Here's some short answers.
>
>1) Stop on error
>JBoss is designed to host many services concurrently.
>There is no mechanism to say one is critical and end the server.
>
>JBoss3.0 introduces the ideas of dependencies.
>If the database doesn't come up, neither will services that
>use it, instead they wait. When you fix the database config,
>restart the database service and all the dependencies start as well.
>There is no need to end the server.
>You can do a similar thing on 2.4.4, but you have to manually
>work out the dependencies, i.e. which services need to be restarted.
>
>2) Log4j
>The best way to do logging for a bean (at the moment)
>private static final Category log = Category.newInstance(MyClass.class);
>
>If you want to separate the logging from JBoss, change
>log4.properties to have something like
>
>log4j.com.acme=INFO, MyAppender
>log4j.additivity.com.acme=false
>log4j.appender.MyAppender={etc.}
>
>Assuming all your beans are in the package com.acme
>
>If you want to customize log4j, put your customisations in a jar,
>and add the jar to the Log4jService "archives" attribute in jboss.conf
>Be careful, make sure your customisations don't conflict with
>jboss's own.
>
>3) run.bat
>Don't put anything in the classpath of run.bat, especially not
>something that uses Class.forName() to load classes.
>Put your jars in jboss/lib/ext
>There used to be a jboss.properties for system properties. It was
>removed, I don't know why? I guess it was used as a dumping ground
>by developers when they should have been using jboss.jcml for
>configuration.
>
>Regards,
>Adrian
>
>
> >From: "Eric Kaplan" <[EMAIL PROTECTED]>
> >To: <[EMAIL PROTECTED]>
> >Subject: [JBoss-user] logging and admininstration
> >Date: Mon, 18 Feb 2002 12:25:27 -0500
> >
> >Three questions:
> >
> >1. Typically, we bring up the application server and eyeball the output
>for
> >obvious errors, which are one of three typically:
> > - Cannot bind to the required port, usually because a jboss instance
> >is already running
> > - Cannot create one or more db pools, usually because the database
> >is down
> > - One or more errors deploying the beans, including verifier
> >problems.
> >If we see an error, we fix it and restart. However, in production, we
>want
> >to automatically bring up the server, detect problems, and exit with an
> >error code. Is there a straightforward way of doing this?
> >
> >2. Logging with log4j. Log4j on its own is easy. However, I'm still
> >frustrated getting my beans to log using log4j with jboss. Scanning the
> >forum, it seems there are a LOT of people having the same problem. We
>are
> >probably all doing the same thing wrong, but it's not clear exactly what
> >the
> >remedy is. Can someone please tell me? I would think I could get the
> >latest log4j and log4-core jars, put them in the classpath, and roll, but
> >this is not the case. Please let me know what I need to do?
> >
> >3. We have a couple of system properties (-D flag) as well as classpath
> >extensions to make when running jboss. We currently have hacked run.bat,
> >but I don't think this is a great solution. What is the sanctioned way
>in
> >jboss for dealing with this?
> >
> >Thanks
> >
> >Eric Kaplan
> >Armanta, Inc.
> >55 Madison Ave.
> >Morristown, NJ 07960
> >Phone: (973) 326-9600
> >
> ><< winmail.dat >>
>
>
>_
>Chat with friends online, try MSN Messenger: http://messenger.msn.com
>
>
_
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] logging and admininstration
> > 2) Log4j > > The best way to do logging for a bean (at the moment) > > private static final Category log = Category.newInstance(MyClass.class); > > > >The following accomplishes the same thing, and can be cut and pasted from >one source to the next. > >private static final Category log = >Category.getInstance(getClass().getName()); Blind leading the Blind :-) Of course, it is getInstance() not newInstance() But you cannot use getClass() from a static context, you need an object for that :-( The reason for static is to avoid serialization problems. And the ejb spec requires all static attributes to be final. > > > 3) run.bat > > Don't put anything in the classpath of run.bat, especially not > > something that uses Class.forName() to load classes. > > Put your jars in jboss/lib/ext > >I would disagree with this. I prefer to keep the JBoss directories >"virgin", and add whatever I need extra to an external directory. I then >modify run.sh to put my extra jars on JBoss's classpath. You can probably >accomplish the same thing with classpath extensions. By doing this, >upgrading from one version of JBoss to the next is easier. I try to follow >this same philosophy with other packages (e.g., Tomcat.) > The lib/myext is better. In the future the JBoss3 branch will keep track of which deployments use each jar for automatic dependency checking. This could also lead to hot-deploying util jars that use a JBoss classloader. If you load from the classpath in run.sh, it can't do this :-( > > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user Regards, Adrian _ Send and receive Hotmail on your mobile device: http://mobile.msn.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] logging and admininstration
[Guy Rouillier] > > 2) Log4j > > The best way to do logging for a bean (at the moment) > > private static final Category log = Category.newInstance(MyClass.class); > > > > The following accomplishes the same thing, and can be cut and pasted from > one source to the next. > >private static final Category log = > Category.getInstance(getClass().getName()); AFAIK this will never work since you're calling the non-static method java.lang.Object's getClass() from a static context. Specifically: *** jmm@bp6:/tmp> javac foo.java foo.java:4: non-static method getClass() cannot be referenced from a static context private static final Category log = Category.getInstance(getClass().getName()); ^ 1 error *** Now you *could* drop the static part and then it'd work, but all instances of the class would have their own copies of the same reference returned from Category.getInstance, which seems wasteful. Alternatives? -- James Manning <[EMAIL PROTECTED]> GPG Key fingerprint = B913 2FBD 14A9 CE18 B2B7 9C8E A0BF B026 EEBB F6E4 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] logging and admininstration
> 2) Log4j > The best way to do logging for a bean (at the moment) > private static final Category log = Category.newInstance(MyClass.class); > The following accomplishes the same thing, and can be cut and pasted from one source to the next. private static final Category log = Category.getInstance(getClass().getName()); > 3) run.bat > Don't put anything in the classpath of run.bat, especially not > something that uses Class.forName() to load classes. > Put your jars in jboss/lib/ext I would disagree with this. I prefer to keep the JBoss directories "virgin", and add whatever I need extra to an external directory. I then modify run.sh to put my extra jars on JBoss's classpath. You can probably accomplish the same thing with classpath extensions. By doing this, upgrading from one version of JBoss to the next is easier. I try to follow this same philosophy with other packages (e.g., Tomcat.) ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] logging and admininstration
couple more questions wrt 3 below. we're using jboss 2.4.1, which seems to
use jboss.properties, but i think you're saying that the latest version of
jboss no longer uses it? also, in development we have a classes directory
which contains the heierarchy of all our class files, so there is no jar to
copy to lib/ext. what should we do in this case?
thanks
eric
-Original Message-
From: Adrian Brock [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 1:43 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] logging and admininstration
Here's some short answers.
1) Stop on error
JBoss is designed to host many services concurrently.
There is no mechanism to say one is critical and end the server.
JBoss3.0 introduces the ideas of dependencies.
If the database doesn't come up, neither will services that
use it, instead they wait. When you fix the database config,
restart the database service and all the dependencies start as well.
There is no need to end the server.
You can do a similar thing on 2.4.4, but you have to manually
work out the dependencies, i.e. which services need to be restarted.
2) Log4j
The best way to do logging for a bean (at the moment)
private static final Category log = Category.newInstance(MyClass.class);
If you want to separate the logging from JBoss, change
log4.properties to have something like
log4j.com.acme=INFO, MyAppender
log4j.additivity.com.acme=false
log4j.appender.MyAppender={etc.}
Assuming all your beans are in the package com.acme
If you want to customize log4j, put your customisations in a jar,
and add the jar to the Log4jService "archives" attribute in jboss.conf
Be careful, make sure your customisations don't conflict with
jboss's own.
3) run.bat
Don't put anything in the classpath of run.bat, especially not
something that uses Class.forName() to load classes.
Put your jars in jboss/lib/ext
There used to be a jboss.properties for system properties. It was
removed, I don't know why? I guess it was used as a dumping ground
by developers when they should have been using jboss.jcml for
configuration.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: [JBoss-user] logging and admininstration
>Date: Mon, 18 Feb 2002 12:25:27 -0500
>
>Three questions:
>
>1. Typically, we bring up the application server and eyeball the output for
>obvious errors, which are one of three typically:
> - Cannot bind to the required port, usually because a jboss instance
>is already running
> - Cannot create one or more db pools, usually because the database
>is down
> - One or more errors deploying the beans, including verifier
>problems.
>If we see an error, we fix it and restart. However, in production, we want
>to automatically bring up the server, detect problems, and exit with an
>error code. Is there a straightforward way of doing this?
>
>2. Logging with log4j. Log4j on its own is easy. However, I'm still
>frustrated getting my beans to log using log4j with jboss. Scanning the
>forum, it seems there are a LOT of people having the same problem. We are
>probably all doing the same thing wrong, but it's not clear exactly what
>the
>remedy is. Can someone please tell me? I would think I could get the
>latest log4j and log4-core jars, put them in the classpath, and roll, but
>this is not the case. Please let me know what I need to do?
>
>3. We have a couple of system properties (-D flag) as well as classpath
>extensions to make when running jboss. We currently have hacked run.bat,
>but I don't think this is a great solution. What is the sanctioned way in
>jboss for dealing with this?
>
>Thanks
>
>Eric Kaplan
>Armanta, Inc.
>55 Madison Ave.
>Morristown, NJ 07960
>Phone: (973) 326-9600
>
><< winmail.dat >>
_
Chat with friends online, try MSN Messenger: http://messenger.msn.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] logging and admininstration
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.(FileWatchdog.java:49) at org.apache.log4j.PropertyWatchdog.(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.(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.(FileWatchdog.java:49) at org.apache.log4j.PropertyWatchdog.(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.(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) JBoss 2.4.1 Started in 0m:10s I'm very frustrated to say the least. This should not be that difficult, please tell me I doing something extremely basic wrong. As for the system properties, what's the answer? I can put the jars where you said, but I still need to set a system property. Where's the best place for this? Thanks Eric -Original Message- From: Adrian Brock [mailto:[EMAIL PROTECTED]] Sent: Monday, February 18, 2002 1:43 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [JBoss-user] logging and admininstration Here's some short answers. 1) Stop on error JBoss is designed to host many services concurrently. There is no mechanism to say one is critical and end the server. JBoss3.0 introduces the ideas of dependencies. If the database doesn't come up, neither will services that use it, instead they wait. When you fix the database config, restart the database service and all the dependencies start as well. There is no need to end the server. You can do a similar thing on 2.4.4, but you have to manually work out the dependencies, i.e. which services need to be restarted. 2) Log4j The best way to do logging for a bean (at the moment) private static final Category log = Category.newInstance(MyClass.class); If you want to separate the logging from JB
Re: [JBoss-user] logging and admininstration
Here's some short answers.
1) Stop on error
JBoss is designed to host many services concurrently.
There is no mechanism to say one is critical and end the server.
JBoss3.0 introduces the ideas of dependencies.
If the database doesn't come up, neither will services that
use it, instead they wait. When you fix the database config,
restart the database service and all the dependencies start as well.
There is no need to end the server.
You can do a similar thing on 2.4.4, but you have to manually
work out the dependencies, i.e. which services need to be restarted.
2) Log4j
The best way to do logging for a bean (at the moment)
private static final Category log = Category.newInstance(MyClass.class);
If you want to separate the logging from JBoss, change
log4.properties to have something like
log4j.com.acme=INFO, MyAppender
log4j.additivity.com.acme=false
log4j.appender.MyAppender={etc.}
Assuming all your beans are in the package com.acme
If you want to customize log4j, put your customisations in a jar,
and add the jar to the Log4jService "archives" attribute in jboss.conf
Be careful, make sure your customisations don't conflict with
jboss's own.
3) run.bat
Don't put anything in the classpath of run.bat, especially not
something that uses Class.forName() to load classes.
Put your jars in jboss/lib/ext
There used to be a jboss.properties for system properties. It was
removed, I don't know why? I guess it was used as a dumping ground
by developers when they should have been using jboss.jcml for
configuration.
Regards,
Adrian
>From: "Eric Kaplan" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Subject: [JBoss-user] logging and admininstration
>Date: Mon, 18 Feb 2002 12:25:27 -0500
>
>Three questions:
>
>1. Typically, we bring up the application server and eyeball the output for
>obvious errors, which are one of three typically:
> - Cannot bind to the required port, usually because a jboss instance
>is already running
> - Cannot create one or more db pools, usually because the database
>is down
> - One or more errors deploying the beans, including verifier
>problems.
>If we see an error, we fix it and restart. However, in production, we want
>to automatically bring up the server, detect problems, and exit with an
>error code. Is there a straightforward way of doing this?
>
>2. Logging with log4j. Log4j on its own is easy. However, I'm still
>frustrated getting my beans to log using log4j with jboss. Scanning the
>forum, it seems there are a LOT of people having the same problem. We are
>probably all doing the same thing wrong, but it's not clear exactly what
>the
>remedy is. Can someone please tell me? I would think I could get the
>latest log4j and log4-core jars, put them in the classpath, and roll, but
>this is not the case. Please let me know what I need to do?
>
>3. We have a couple of system properties (-D flag) as well as classpath
>extensions to make when running jboss. We currently have hacked run.bat,
>but I don't think this is a great solution. What is the sanctioned way in
>jboss for dealing with this?
>
>Thanks
>
>Eric Kaplan
>Armanta, Inc.
>55 Madison Ave.
>Morristown, NJ 07960
>Phone: (973) 326-9600
>
><< winmail.dat >>
_
Chat with friends online, try MSN Messenger: http://messenger.msn.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] logging and admininstration
Three questions: 1. Typically, we bring up the application server and eyeball the output for obvious errors, which are one of three typically: - Cannot bind to the required port, usually because a jboss instance is already running - Cannot create one or more db pools, usually because the database is down - One or more errors deploying the beans, including verifier problems. If we see an error, we fix it and restart. However, in production, we want to automatically bring up the server, detect problems, and exit with an error code. Is there a straightforward way of doing this? 2. Logging with log4j. Log4j on its own is easy. However, I'm still frustrated getting my beans to log using log4j with jboss. Scanning the forum, it seems there are a LOT of people having the same problem. We are probably all doing the same thing wrong, but it's not clear exactly what the remedy is. Can someone please tell me? I would think I could get the latest log4j and log4-core jars, put them in the classpath, and roll, but this is not the case. Please let me know what I need to do? 3. We have a couple of system properties (-D flag) as well as classpath extensions to make when running jboss. We currently have hacked run.bat, but I don't think this is a great solution. What is the sanctioned way in jboss for dealing with this? Thanks Eric Kaplan Armanta, Inc. 55 Madison Ave. Morristown, NJ 07960 Phone: (973) 326-9600 winmail.dat Description: application/ms-tnef
RE: [JBoss-user] Logging with JBoss ...
This is the first request I've heard for it, but I have anticipated this myself. I'll look into it during the LoggerRepository changes, it is likely we will need to support both in the same server VM. >From what I've seen of JDK1.4beta it doesn't provide the LoggerRepository technology of log4j. So there is no way to separate JBoss and application configurations. It does support Java2 security so it is possible to stop rogue applications reconfiguring the logging. But everyting has to share, a bit like how it is with JBoss now. It also only works on JDK1.4. So any support would have to be provided as an optional patch. Regards, Adrian >From: [EMAIL PROTECTED] >To: [EMAIL PROTECTED], [EMAIL PROTECTED] >Subject: RE: [JBoss-user] Logging with JBoss ... >Date: Tue, 22 Jan 2002 16:47:43 -0200 > >What about the new java.util.logging.* APIs? We're using them and they look >just like log4j. Have you heard of any plans JBOSS logging infrastructure >moving to these APIs in the future? > >Rodrigo > > >-Original Message- >From: Peter Sojan [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, January 22, 2002 4:09 PM >To: [EMAIL PROTECTED] >Subject: Re: [JBoss-user] Logging with JBoss ... > > > >Thanks for your prompt answer! > >On Tue, Jan 22, 2002 at 05:51:29PM +, Adrian Brock wrote: > > You are going to hit problems here. > >I already hit some ;-) Instead of tilting windmills I really should use >the internal JBoss logging infrastructure. I hope there's a way to >configure >logging priority to "debug" for my beans without getting flooded with JBoss >debug messages at the same time. > > > > > Nearly the same thing - will provide automatic upgrade to log4j 1.2 > > where Category has been deprecated. > > import org.jboss.logging.Logger; > > private static final Logger log = Logger.getLogger(myName); > > But it is not portable to other servers. > > >not really a viable solution. > > > I am currently investigating the new > > log4j LoggerRepositories for JBoss3 that will solve this problem. > >I´m looking forward to it! > >Thx >Peter > > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with JBoss ...
On Tue, Jan 22, 2002 at 06:31:22PM +, Adrian Brock wrote: > To selectively turn on debug for your classes add something like > the following to $JBOSS_HOME/conf//log4j.properties > > log4j.category.your.package.name=DEBUG > or > log4j.category.your.package.name.OneClass=DEBUG > > I assume you are using class names for your categories. > > You will need > log4j.category.org.jboss=INFO > to stop all of JBoss's debugging messages. > > Also DEBUG messages do not go to the Console. > They go to $JBOSS_HOME/log/server.log > > But you can change this on the line > log4j.appender.Console.Threshold=INFO > replace INFO with DEBUG > Everything works now! Thank you for your support Adrian! Maybe this should go into the faqs, if it isn't there already (Forums are down again, so I couldn't look into it) so long Peter ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging with JBoss ...
Title: RE: [JBoss-user] Logging with JBoss ... What about the new java.util.logging.* APIs? We're using them and they look just like log4j. Have you heard of any plans JBOSS logging infrastructure moving to these APIs in the future? Rodrigo -Original Message- From: Peter Sojan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 22, 2002 4:09 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] Logging with JBoss ... Thanks for your prompt answer! On Tue, Jan 22, 2002 at 05:51:29PM +, Adrian Brock wrote: > You are going to hit problems here. I already hit some ;-) Instead of tilting windmills I really should use the internal JBoss logging infrastructure. I hope there's a way to configure logging priority to "debug" for my beans without getting flooded with JBoss debug messages at the same time. > > Nearly the same thing - will provide automatic upgrade to log4j 1.2 > where Category has been deprecated. > import org.jboss.logging.Logger; > private static final Logger log = Logger.getLogger(myName); > But it is not portable to other servers. > not really a viable solution. > I am currently investigating the new > log4j LoggerRepositories for JBoss3 that will solve this problem. I´m looking forward to it! Thx Peter ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with JBoss ...
To selectively turn on debug for your classes add something like the following to $JBOSS_HOME/conf//log4j.properties log4j.category.your.package.name=DEBUG or log4j.category.your.package.name.OneClass=DEBUG I assume you are using class names for your categories. You will need log4j.category.org.jboss=INFO to stop all of JBoss's debugging messages. Also DEBUG messages do not go to the Console. They go to $JBOSS_HOME/log/server.log But you can change this on the line log4j.appender.Console.Threshold=INFO replace INFO with DEBUG Regards, Adrian >From: Peter Sojan <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: [JBoss-user] Logging with JBoss ... >Date: Tue, 22 Jan 2002 19:09:28 +0100 > > >Thanks for your prompt answer! > >On Tue, Jan 22, 2002 at 05:51:29PM +, Adrian Brock wrote: > > You are going to hit problems here. > >I already hit some ;-) Instead of tilting windmills I really should use >the internal JBoss logging infrastructure. I hope there's a way to >configure >logging priority to "debug" for my beans without getting flooded with JBoss >debug messages at the same time. > > > > > Nearly the same thing - will provide automatic upgrade to log4j 1.2 > > where Category has been deprecated. > > import org.jboss.logging.Logger; > > private static final Logger log = Logger.getLogger(myName); > > But it is not portable to other servers. > > >not really a viable solution. > > > I am currently investigating the new > > log4j LoggerRepositories for JBoss3 that will solve this problem. > >I´m looking forward to it! > >Thx >Peter > > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with JBoss ...
Thanks for your prompt answer! On Tue, Jan 22, 2002 at 05:51:29PM +, Adrian Brock wrote: > You are going to hit problems here. I already hit some ;-) Instead of tilting windmills I really should use the internal JBoss logging infrastructure. I hope there's a way to configure logging priority to "debug" for my beans without getting flooded with JBoss debug messages at the same time. > > Nearly the same thing - will provide automatic upgrade to log4j 1.2 > where Category has been deprecated. > import org.jboss.logging.Logger; > private static final Logger log = Logger.getLogger(myName); > But it is not portable to other servers. > not really a viable solution. > I am currently investigating the new > log4j LoggerRepositories for JBoss3 that will solve this problem. I´m looking forward to it! Thx Peter ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging with JBoss ...
You are going to hit problems here. There is a log4j.jar in lib/ext so this should be available to any beans you deploy. It is not available to classes added in run.sh/run.bat. NOTE: for ejbs do import org.apache.log4j.Category; private static final Category log = Category.newInstance(myName); because Category is not serializable and any static attributes must be final according to the spec. Nearly the same thing - will provide automatic upgrade to log4j 1.2 where Category has been deprecated. import org.jboss.logging.Logger; private static final Logger log = Logger.getLogger(myName); But it is not portable to other servers. You can configure log4j from your beans, but it is sharing configuration with JBoss. You will break the JBoss configuration. I am currently investigating the new log4j LoggerRepositories for JBoss3 that will solve this problem. But this is not yet done, and it may not get into JBoss3.0 because it requires log4j 1.2. It has no firm date for a final release (it is currently an alpha). The configuration of log4j will be somewhere in your deployment descriptor(s) or you could do it programatically, makes no difference, you will have your own logging universe. IMHO it is not the application's job to configure logging. This should be the responsibility of the deployer with help from the server. Regards, Adrian >From: Peter Sojan <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: [JBoss-user] Logging with JBoss ... >Date: Tue, 22 Jan 2002 18:13:35 +0100 > > >Ok! I´m done. I have no glue where so search for more information. >I dont know how to do logging with Log4j in JBoss. > >Following questions: >- where do I have to put my OWN log4j jars in the ejb-jar file !? >- how will JBoss classloader find them !? >- how can I configure a boot-strap class which gets fired up on > every deployment (I need this to configure log4j properly) > >please help me out !! > >Thx >Peter > > >___ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user _ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging with JBoss ...
Ok! I´m done. I have no glue where so search for more information. I dont know how to do logging with Log4j in JBoss. Following questions: - where do I have to put my OWN log4j jars in the ejb-jar file !? - how will JBoss classloader find them !? - how can I configure a boot-strap class which gets fired up on every deployment (I need this to configure log4j properly) please help me out !! Thx Peter ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging
) [Default] [Default] at java.lang.reflect.Method.invoke(Native Method) [Default] [Default] at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor. invoke(StatelessSessionContainer.java:543) [Default] [Default] at org.jboss.ejb.plugins.TxInterceptorBMT.invoke(TxInterceptorBM T.java:276) [Default] [Default] at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.inv oke(StatelessSessionInstanceInterceptor.java:87) [Default] [Default] at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInte rceptor.java:128) [Default] [Default] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.ja va:195) [Default] [Default] at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessi onContainer.java:286) [Default] [Default] at org.jboss.ejb.plugins.jrmp.server.JRMPContainerInvoker.invoke (JRMPContainerInvoker.java:393) [Default] [Default] at java.lang.reflect.Method.invoke(Native Method) [Default] [Default] at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) [Default] [Default] at sun.rmi.transport.Transport$1.run(Unknown Source) [Default] [Default] at java.security.AccessController.doPrivileged(Native Method) [Default] [Default] at sun.rmi.transport.Transport.serviceCall(Unknown Source) [Default] [Default] at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Sou rce) [Default] [Default] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unkn own Source) [Default] [Default] at java.lang.Thread.run(Unknown Source) [Default] The exception is NoClassDefFoundError. I'm far from being -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Adrian Brock Sent: Saturday, January 19, 2002 9:21 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Logging Hi Eric, We have not hacked log4j. The Log4jService extends log4j using mechansims exposed in its api. But for these to work, log4j must be able to see classes in jboss.jar. It cannot do this if you put log4j in the system classloader, the parent of the jboss classloader. A parent classloader cannot load classes from a child classloader. Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] Logging >Date: Sat, 19 Jan 2002 20:10:49 -0500 > >is the implication that jboss depends upon a "hacked" version of log4j that >references jboss code?... > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]On Behalf Of Adrian Brock >Sent: Saturday, January 19, 2002 7:20 PM >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: RE: [JBoss-user] Logging > > >Hi, > >Don't add it to the classpath in run.bat/run.sh, it is already in lib/ext >If you put it in the classpath org.jboss.logging can "see" >org.apache.log4j but the reverse is not true, hence your error. > >Your bean should be able to see the log4j.jar in lib/ext > >Regards, >Adrian > > > >From: "Eric Kaplan" <[EMAIL PROTECTED]> > >To: "Scott M Stark" <[EMAIL PROTECTED]>, > ><[EMAIL PROTECTED]> > >Subject: RE: [JBoss-user] Logging > >Date: Sat, 19 Jan 2002 18:08:10 -0500 > > > >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) > &g
RE: [JBoss-user] Logging
Hi Eric, We have not hacked log4j. The Log4jService extends log4j using mechansims exposed in its api. But for these to work, log4j must be able to see classes in jboss.jar. It cannot do this if you put log4j in the system classloader, the parent of the jboss classloader. A parent classloader cannot load classes from a child classloader. Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >CC: <[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] Logging >Date: Sat, 19 Jan 2002 20:10:49 -0500 > >is the implication that jboss depends upon a "hacked" version of log4j that >references jboss code?... > >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED]]On Behalf Of Adrian Brock >Sent: Saturday, January 19, 2002 7:20 PM >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED] >Subject: RE: [JBoss-user] Logging > > >Hi, > >Don't add it to the classpath in run.bat/run.sh, it is already in lib/ext >If you put it in the classpath org.jboss.logging can "see" >org.apache.log4j but the reverse is not true, hence your error. > >Your bean should be able to see the log4j.jar in lib/ext > >Regards, >Adrian > > > >From: "Eric Kaplan" <[EMAIL PROTECTED]> > >To: "Scott M Stark" <[EMAIL PROTECTED]>, > ><[EMAIL PROTECTED]> > >Subject: RE: [JBoss-user] Logging > >Date: Sat, 19 Jan 2002 18:08:10 -0500 > > > >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.(FileWatchdog.java:49) > > at > >org.apache.log4j.PropertyWatchdog.(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.(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 instantia
RE: [JBoss-user] Logging
is the implication that jboss depends upon a "hacked" version of log4j that references jboss code?... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Adrian Brock Sent: Saturday, January 19, 2002 7:20 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: RE: [JBoss-user] Logging Hi, Don't add it to the classpath in run.bat/run.sh, it is already in lib/ext If you put it in the classpath org.jboss.logging can "see" org.apache.log4j but the reverse is not true, hence your error. Your bean should be able to see the log4j.jar in lib/ext Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: "Scott M Stark" <[EMAIL PROTECTED]>, ><[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] Logging >Date: Sat, 19 Jan 2002 18:08:10 -0500 > >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.(FileWatchdog.java:49) > at >org.apache.log4j.PropertyWatchdog.(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.(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.PropertyConfig
RE: [JBoss-user] Logging
Hi, Don't add it to the classpath in run.bat/run.sh, it is already in lib/ext If you put it in the classpath org.jboss.logging can "see" org.apache.log4j but the reverse is not true, hence your error. Your bean should be able to see the log4j.jar in lib/ext Regards, Adrian >From: "Eric Kaplan" <[EMAIL PROTECTED]> >To: "Scott M Stark" <[EMAIL PROTECTED]>, ><[EMAIL PROTECTED]> >Subject: RE: [JBoss-user] Logging >Date: Sat, 19 Jan 2002 18:08:10 -0500 > >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.(FileWatchdog.java:49) > at >org.apache.log4j.PropertyWatchdog.(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.(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(PropertyConfigurato
Re: [JBoss-user] Logging
Scott, Becareful where you put log4j.jar...I accidently put it in my JAVA_HOME/lib/ext and was getting the same Exception as you. I took it out, and no more problems. Steve Knight - Original Message - From: "Eric Kaplan" <[EMAIL PROTECTED]> To: "Scott M Stark" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Saturday, January 19, 2002 6:08 PM Subject: RE: [JBoss-user] Logging > 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.(FileWatchdog.java:49) > at > org.apache.log4j.PropertyWatchdog.(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.(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.a
RE: [JBoss-user] Logging
d(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. Scott Stark Chief Technology Officer JBoss Group, LLC - 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
Re: [JBoss-user] Logging
log4j is the standard logging mechanism. - Original Message - From: "Jozsa Kristof" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, January 19, 2002 2:14 PM 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
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. Scott Stark Chief Technology Officer JBoss Group, LLC - 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] 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
Re: [JBoss-user] Logging different categories to different files
O ok got it, RTFE You have to declare categories as: log4j.category.NameOfTheCategory Cheers, Vladimir On 2001.07.07 20:30 Vladimir Blagojevic wrote: > Hey there, > > How do you log different categories to different files? Couldn't find it > log4j doco so I am guessing here. > > I tried declaring the following in log4j.properties: > > log4j.NameOfTheCategory= DEBUG, NameOfTheCategoryFileLog > > > log4j.appender.NameOfTheCategoryFileLog=org.apache.log4j.FileAppender > log4j.appender.NameOfTheCategoryFileLog.File=../log/somefile.log > > ..blah blah.. > > .all other options for that appender > > > And nothings get logged into those files :( > > Know why? > > Thanks, > Vladimir > > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging different categories to different files
Hey there, How do you log different categories to different files? Couldn't find it log4j doco so I am guessing here. I tried declaring the following in log4j.properties: log4j.NameOfTheCategory= DEBUG, NameOfTheCategoryFileLog log4j.appender.NameOfTheCategoryFileLog=org.apache.log4j.FileAppender log4j.appender.NameOfTheCategoryFileLog.File=../log/somefile.log ..blah blah.. .all other options for that appender And nothings get logged into those files :( Know why? Thanks, Vladimir ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging in J2EE/EJB world
** Logging in J2EE/EJB world * Overview The needs and scenarios in a distributed computing environment are very different from desktop computing. Server programs must be available 24 x 7 and you can not assume your server is monitored by human all the time. So, server programs need logging: log errors and log events. The development environment is different as well. When you develop a desktop program you use a debugger to set break points. When something is wrong, you can simply restart your program. Unfortunately, this is not the case for server programs. In the first phase of development, you can run both server and client on your desktop machine and fix all bugs you can find. In the real world the situation is much more complex when many clients concurrently access your server. Things get even more complicated when your server load balances and failovers. It is impossible to set break points when the server is in production. The only thing you can do is tracing log message. * Features we need for logging Logging facilities should be dynamically configurable. Un-wanted log messages should be easily filtered out: they are too noisy and there is always a performance penalty associated with logging. Logging messages should be persistent. When they are persistent, they are the resource for tracing. So a source code level tracing is a natural companion of logging. Logging must be centralized. In a distributed environment (clustering) the your server can dynamically move EJBs and other components from one physical machine to another due to load balancing and failover. If logging messages stay on local machine, log messages will be all over those machines and it would be very difficult to analysis these messages. Logging must be chronological. When your server is concurrently accessed by many clients, there are time dependency issues. Logging must be easy to use. If it is too complicated, it will be error prone. Logging part of the program will not be tested as thoroughly as the main part. When something happens and you want see log messages, it is the worst time to find out that you have a bug in logging or you did not configured logging system correctly. Alert facilities must be companions of logging. If some thing happens, you need administrator's attention. There only one practical persistent solution: use database to store logging messages. There are some implementation and operation issues too. For example, your log database should not be a part of your transaction. If some thing happens, the log message should not be ROLLBACKed. Just like log message printed on your screen, you can not take them back. So the connection between log system and log database must be a dedicated one. In a clustering environment, there are many physical machines and many servers. Your logging attributes (configuration information) must be stored in a central place, for example, the log database. Logging system must fetch logging attributes from the log database. There is a performance penalty to pay. But the penalty may not be severe for you application. On the other hand, if your system is stable, you should be able to download log attributes from the log database to the local machine and use attributes from local machine instead. This will give you a performance boost. Log method call should provide caller's class name, method name, time stamp and other information. If you hard code this information, your program would be very difficult to maintain. So you need a tool to rectify these information before you deploy your EJBs or other components. * Rejected options EJB specification prohibits file IO. So logging on files are not acceptable, although many server leave a back door for you. There are some other issues as well. Asynchronized JMS as the mechanism is not the best choice. It can not guarantee log messages be chronological. Suppose you have machine A which logs message "first". Later machine B logs message "second". JMS guarantees delivery, but does not guarantee timing. You may see the message "second" before "first". You can get around of this problem by fetching a unique id from a central place each time a log method is called. But the extra remote access would be expensive. Another work-a-round is use time stamp as log id in a synchronized time network system. But the resolution of time stamp may not be good enough (usually at millisecond level) and may not be unique if you have many physical machines. You will get more performance overhead by using JMS than direct database access. On the surface, you call JMS based log method and it returns immediately, so your main program goes faster. But the part of JMS on your local machine will compete computing resources (both memory and CPU) with your main program. * SuperLogging is designed to resolve above issues SuperLogging of Super is designed to resolve above issues. You can get it from http://www.acelet.com.
[JBoss-user] Logging in J2EE/EJB world
** Logging in J2EE/EJB world * Overview The needs and scenarios in a distributed computing environment are very different from desktop computing. Server programs must be available 24 x 7 and you can not assume your server is monitored by human all the time. So, server programs need logging: log errors and log events. The development environment is different as well. When you develop a desktop program you use a debugger to set break points. When something is wrong, you can simply restart your program. Unfortunately, this is not the case for server programs. In the first phase of development, you can run both server and client on your desktop machine and fix all bugs you can find. In the real world the situation is much more complex when many clients concurrently access your server. Things get even more complicated when your server load balances and failovers. It is impossible to set break points when the server is in production. The only thing you can do is tracing log message. * Features we need for logging Logging facilities should be dynamically configurable. Un-wanted log messages should be easily filtered out: they are too noisy and there is always a performance penalty associated with logging. Logging messages should be persistent. When they are persistent, they are the resource for tracing. So a source code level tracing is a natural companion of logging. Logging must be centralized. In a distributed environment (clustering) the your server can dynamically move EJBs and other components from one physical machine to another due to load balancing and failover. If logging messages stay on local machine, log messages will be all over those machines and it would be very difficult to analysis these messages. Logging must be chronological. When your server is concurrently accessed by many clients, there are time dependency issues. Logging must be easy to use. If it is too complicated, it will be error prone. Logging part of the program will not be tested as thoroughly as the main part. When something happens and you want see log messages, it is the worst time to find out that you have a bug in logging or you did not configured logging system correctly. Alert facilities must be companions of logging. If some thing happens, you need administrator's attention. There only one practical persistent solution: use database to store logging messages. There are some implementation and operation issues too. For example, your log database should not be a part of your transaction. If some thing happens, the log message should not be ROLLBACKed. Just like log message printed on your screen, you can not take them back. So the connection between log system and log database must be a dedicated one. In a clustering environment, there are many physical machines and many servers. Your logging attributes (configuration information) must be stored in a central place, for example, the log database. Logging system must fetch logging attributes from the log database. There is a performance penalty to pay. But the penalty may not be severe for you application. On the other hand, if your system is stable, you should be able to download log attributes from the log database to the local machine and use attributes from local machine instead. This will give you a performance boost. Log method call should provide caller's class name, method name, time stamp and other information. If you hard code this information, your program would be very difficult to maintain. So you need a tool to rectify these information before you deploy your EJBs or other components. * Rejected options EJB specification prohibits file IO. So logging on files are not acceptable, although many server leave a back door for you. There are some other issues as well. Asynchronized JMS as the mechanism is not the best choice. It can not guarantee log messages be chronological. Suppose you have machine A which logs message "first". Later machine B logs message "second". JMS guarantees delivery, but does not guarantee timing. You may see the message "second" before "first". You can get around of this problem by fetching a unique id from a central place each time a log method is called. But the extra remote access would be expensive. Another work-a-round is use time stamp as log id in a synchronized time network system. But the resolution of time stamp may not be good enough (usually at millisecond level) and may not be unique if you have many physical machines. You will get more performance overhead by using JMS than direct database access. On the surface, you call JMS based log method and it returns immediately, so your main program goes faster. But the part of JMS on your local machine will compete computing resources (both memory and CPU) with your main program. * SuperLogging is designed to resolve above issues SuperLogging of Super is designed to resolve above issues. You can get it from http://www.acelet.com.
Re: [JBoss-user] logging question
SuperLogging of Super from www.acelet.com will give your more that that. It is free for jBoss users. --- fractals <[EMAIL PROTECTED]> wrote: > Hi, > > Is it possible to get logging information "on demand" ? That is: I would > like to get logging information and than maybe reboot my system (or allow it > to crash), and then get a conduit to my app server (JBoss) again to get more > info, and so on... > > I guess this must be a very obvious request, but I couldn't find info on > this in the docs :-( > > Regards, > > Candide Kemmler > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] logging question
Hi, Is it possible to get logging information "on demand" ? That is: I would like to get logging information and than maybe reboot my system (or allow it to crash), and then get a conduit to my app server (JBoss) again to get more info, and so on... I guess this must be a very obvious request, but I couldn't find info on this in the docs :-( Regards, Candide Kemmler ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging with embedded Tomcat
I'm running JBoss-2.2.1 with embedded Tomcat 3.2.1 in a Windows 2000 environment and I'm having problems with logging. Logging of the JBoss activity works just fine until the first invocation of a Tomcat web app is made. After the first few messages appear in the (jboss) server.log file, that file basically remains unchanged. The (tomcat) servlet.log file continues to work fine. I have tried two configurations in the jboss.conf file: 1) the console logging & file logging option and 2) the Log4j option. Both apparently behave the same way. Help appreciated, Robin Hillyard == Robin Hillyard TruExchange, Inc. 781-457-1311 [EMAIL PROTECTED] http://www.truexchange.com ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging
Check out the log4j documentation at Jakarta
http://jakarta.apache.org/log4j/docs/documentation.html
Vinay
- Original Message -
From: "Ralf Purnhagen" <[EMAIL PROTECTED]>
To: "jBoss" <[EMAIL PROTECTED]>
Sent: Friday, May 11, 2001 9:39 AM
Subject: [JBoss-user] Logging
> Hi!
>
> I want to change the format of the Logfile. Where can i find some
> information about the format strings (default is [{2}] {4})?
>
> Thank you,
> Ralf
>
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging
Hi!
I want to change the format of the Logfile. Where can i find some
information about the format strings (default is [{2}] {4})?
Thank you,
Ralf
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging
Try SuperLogging. It is free for jBoss users. Try SuperLogging of Super from http://www.acelet.com. It is free for open source (Jonas, jboss and j2ee-ri). Evaluation edition is free for other servers. SuperLogging is a full-featured logging tool: * It is a centralized logging, guaranteed tobe chronolotical. It supports distributed computing and works well in any clustering environment. all log messages are recorded in one central place regardless which EJB runs on which server. * It is platform neutral and EJB vendor neutral. * All log statements used in the source code do not need be removed for production releases. Log messages can be dynamically filter out and the performance penalty will be minimum. * An open source wrapper com.acelet.opensource.logging.Alog is provided for preventing vendor lock in. Source code of EJBs is not required for any modification if another logging packages is chosen. In that case, the only modification needed is this wrapper, which is just a few lines of code. * It is fully dynamically configurable by a Swing tool. The configurable attributes include the following: * Choice of configuration scope: Global Dynamic, Global Static and Singleton. * Choice of mode: Quiet, Verbose and Conditional. * Class registration: log messages will be printed out for registered classes only. * Log level: lower level log requests will be filtered out. * It provides Tracing facilities which show both log messages and source code with marked line in question. * It provides built-in email alert method and alert interval control. * It provides email methods which allow sending email by a simple method call. --- Bojan Smojver <[EMAIL PROTECTED]> wrote: > A really simple and probably a really stupid question too: how do you > make the System.out and System.err be redirected to server.log or any > other file? All the System.out.println calls from within EJB's go > nowhere for me... > > Config: > - RH Linux 7 > - Sun JDK 1.3.0_02 > - JBoss 2.2.1 > > Thanks, > Bojan > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/ ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging
Thanks Scott. Just compared my configuration files with the distribution and they are almost identical (except for a few unimportant details). The logging actually works exactly as you explained. The problem had nothing to do with logging, but with the fact that my EJB died way before it got the chance to do the logging. Sorry... Programming late at night is not the brightest of ideas :-( Bojan Scott M Stark wrote: > > This is the default behavior for logging. All System.out.println statements > for me show up both on the console and the server.log file. Have you > changed the logging configuration from the default? > > - Original Message - > From: "Bojan Smojver" <[EMAIL PROTECTED]> > To: "JBoss User" <[EMAIL PROTECTED]> > Sent: Friday, May 04, 2001 6:24 AM > Subject: [JBoss-user] Logging > > > A really simple and probably a really stupid question too: how do you > > make the System.out and System.err be redirected to server.log or any > > other file? All the System.out.println calls from within EJB's go > > nowhere for me... > > > > Config: > > - RH Linux 7 > > - Sun JDK 1.3.0_02 > > - JBoss 2.2.1 > > > > Thanks, > > Bojan > > > > ___ > > JBoss-user mailing list > > [EMAIL PROTECTED] > > http://lists.sourceforge.net/lists/listinfo/jboss-user > > > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] Logging
Probably you can redirect them explicitly:
OutputStream out = new FileOutputStream("my.log")
System.setOut(out);
System.setErr(out);
But that will override the System.out and System.err for all classes loaded
by this.getClass().getClassLoader() classloader... probably you should use
the Log4j stuff (I didn't try it yet, but I've read it's in the JBoss
distribution)...
> -Original Message-
> From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 4. Mai 2001 15:24
> To: JBoss User
> Subject: [JBoss-user] Logging
>
>
> A really simple and probably a really stupid question too: how do you
> make the System.out and System.err be redirected to server.log or any
> other file? All the System.out.println calls from within EJB's go
> nowhere for me...
>
> Config:
> - RH Linux 7
> - Sun JDK 1.3.0_02
> - JBoss 2.2.1
>
> Thanks,
> Bojan
>
> ___
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Logging
This is the default behavior for logging. All System.out.println statements for me show up both on the console and the server.log file. Have you changed the logging configuration from the default? - Original Message - From: "Bojan Smojver" <[EMAIL PROTECTED]> To: "JBoss User" <[EMAIL PROTECTED]> Sent: Friday, May 04, 2001 6:24 AM Subject: [JBoss-user] Logging > A really simple and probably a really stupid question too: how do you > make the System.out and System.err be redirected to server.log or any > other file? All the System.out.println calls from within EJB's go > nowhere for me... > > Config: > - RH Linux 7 > - Sun JDK 1.3.0_02 > - JBoss 2.2.1 > > Thanks, > Bojan > > ___ > JBoss-user mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/jboss-user > ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
[JBoss-user] Logging
A really simple and probably a really stupid question too: how do you make the System.out and System.err be redirected to server.log or any other file? All the System.out.println calls from within EJB's go nowhere for me... Config: - RH Linux 7 - Sun JDK 1.3.0_02 - JBoss 2.2.1 Thanks, Bojan ___ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
