Subhendu,

What version of Log4J are you using, and what is the exact error message?

Mark


On Wed, 16 Mar 2005 21:06:24 +0530, subhendu mahanta
<[EMAIL PROTECTED]> wrote:
> 
> We are working with Sun Application Server 2004Q2. and want to use JMSAppender
> I have used a properties file logger.properties like this:
> ############################################################################
> log4j.rootCategory=, JMSAppender
> 
> log4j.appender.JMSAppender=org.apache.log4j.net.JMSAppender
> 
> log4j.appender.JMSAppender.InitialContextFactoryName=com.sun.jndi.cosnaming.CNCtxFactory
> 
> log4j.appender.JMSAppender.ProviderURL=iiop://10.5.2.226:3700
> 
> log4j.appender.JMSAppender.TopicConnectionFactoryBindingName=jms/ConnFactory
> 
> log4j.appender.JMSAppender.TopicBindingName=jms/TestTopic
> 
> #log4j.appender.JMSAppender.UserName=system
> 
> #log4j.appender.JMSAppender.password=security
> 
> log4j.appender.JMSAppender.layout=org.apache.log4j.PatternLayout
> 
> log4j.appender.JMSAppender.layout.ConversionPattern=(%C:%M:%L) - %m%n
> 
> ##############################################################################
> 
> I have used PropertyConfigurator.configure("logger.properties") inside the 
> init method of a servlet iside a war file deployed in the server.There are 
> some MDBs which will use this.
> 
> However this does not work as the JMSAppender cannot look-up the connection 
> factory though that connection-factory does exist in the server.I have tried 
> this also without success:
> 
> log4j.appender.JMSAppender.TopicConnectionFactoryBindingName=java:comp/env/jms/ConnFactory
> 
> Let me clarify this does work with RollingFileAppender if I make necessary 
> changes in the properties file.
> 
> Thanks in advance
> 
> Subhendu
> 
> If you can give me some suggestion I will very much appreciate that.
> 
> Regards
> 
> Subhendu
> 
> *********************************************************
> Disclaimer:
> 
> The contents of this E-mail (including the contents of the enclosure(s) or 
> attachment(s) if any) are privileged and confidential material of MBT and 
> should not be disclosed to, used by or copied in any manner by anyone other 
> than the intended addressee(s).   In case you are not the desired addressee, 
> you should delete this message and/or re-direct it to the sender.  The views 
> expressed in this E-mail message (including the enclosure(s) or attachment(s) 
> if any) are those of the individual sender, except where the sender 
> expressly, and with authority, states them to be the views of MBT.
> 
> This e-mail message including attachment/(s), if any, is believed to be free 
> of any virus.  However, it is the responsibility of the recipient to ensure 
> that it is virus free and MBT is not responsible for any loss or damage 
> arising in any way from its use
> 
> *********************************************************
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to