We also ran into the same issue and is causing many headaches
prompting some team-members to insist that we get rid of Log4J. Log4J
being open-source is used by different teams/companies who have no
cooridnation between them. I hope in the future releases this problem
can be solved.
--- In
Do you have any clustering Issues with your MDB's?
--- In [EMAIL PROTECTED], Ebersole, Steven [EMAIL PROTECTED] wrote:
I do this exact same thing through JMS logging. I have a User
object which
acquires a per-instance Logger by doing : Logger.getLogger
( session. +
getUserName() ).
In
We plan to use JMS Appender in our production environment. We want to
automate the creation of Queues and JMS Servers using scripts. I have
been paritially successful at this.
I am able to create JMS Conx Factory, JMS File Store and JMS Server
using the Commandline, for e.g.
When i use the
XMLLayout as shown below:
log4j.appender.R.layout=org.apache.log4j.xml.XMLLayout
It generates the following message:
log4j:event category=plat.ivss.sloc timestamp=1029016634611
level=WARN thread=main
log4j:message![CDATA[WARN]]/log4j:message
/log4j:event
The issue i am facing
I create an MDB which monitors a queue. I write one single msg to
this queue using JMSAppender. The Container keeps on creating
instances of this MDB to service this one single message.
I tried setting the acknowledge-mode in the ejb-jar.xml,
tried setting the pool in weblogic-ejb-jar.xml to
I downloaded jakarta-log4j-1.2.1 sometime in May'02. When i use the
XMLLayout as shown below:
log4j.appender.R=org.apache.log4j.RollingFileAppender
log4j.appender.R.file=MyApp.log
log4j.appender.R.MaxFileSize=1
log4j.appender.R.layout=org.apache.log4j.xml.XMLLayout
It generates the
Fixed it, it was due to an error caused by copy-paste-code.
--- In [EMAIL PROTECTED], sanjayrajsoni [EMAIL PROTECTED] wrote:
I create an MDB which monitors a queue. I write one single msg to
this queue using JMSAppender. The Container keeps on creating
instances of this MDB to service
