logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ceki Gulcu <...@urbanet.ch>
Subject Re: Logging in restricted environments (EJB Container)
Date Fri, 19 Jan 2001 10:12:56 GMT


Many people have reported to have used log4j in an EJB environment. I have 
seen this recently: http://theserverside.com/home/thread.jsp?thread_id=3288

Log4j does not contain any entity or session beans. However, it allows 
logging using files (an EJB no-no but it seem to work), sockets or JMS.

Only very select components, namely the AsyncAppendner and the 
SocketAppender have underlying threads. The SocketAppedner fires a thread 
in case of connection failure and will attempt to re-establish the 
connection. I just realized that this feature cannot be turned off. I'll 
fix this for the next release.

Cheers, Ceki

At 10:51 19.01.2001 +0100, you wrote:
>i'm currently looking for a logging/tracing Toolkit that
>works well inside an J2EE Application Server.
>Due to the various restrictions a EnterpriseJavaBean has,
>i'm interested if anyone has successfully used log4j
>inside an Application Server.
>Jürgen Zeller
>sd&m AG
>Thomas-Dehler-Str. 27, D-81737 München
>Tel: +49 89 63812 709 Fax: +49 89 63812 490
>To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-dev-help@jakarta.apache.org

Freedom as in the capacity to exercise choice.

View raw message