Hello,
achieving different logging contexts is also a log4j issue and I've seen
some discussions on it on the log4j-user list. At
https://www.qos.ch/logging/sc.html you'll find something on using
RepositorySelectors to have different logging contexts in web
applications. You can find example
Yes, it is. There is only one log4j configuration available in JBoss as it is
a singleton (and thus global to the whole JVM that hosts JBoss).
This is a problem which is quite annoying, I don't know if there is a clear
solution to this
check $JBOSS_HOME/server/default/conf/log4j.xml and the
Each call to a stateless session bean could be handled by a different bean instance.
Stateless means there should be no client state maintained by the bean. You
shouldn't be keeping a database connection or statement open accross bean method
calls. If you cannot think of another way of
