Howdy,
Make sure your initial context factory implementation is in WEB-INF/lib,
and that you construct an initial context with the environment parameter
(hashtable), not just new InitialContext(). In that environment,
specify the factory class name and server JNDI URL. When you don't,
you're
Thank you for the response.
I am constructing the initial context factory as you suggest - using the hastable.
Both this and the provider URL are specified in the log4j file for the
JMSQueueAppender.
ht.put(Context.INITIAL_CONTEXT_FACTORY, initialContextFactory);
Subject: RE: JMSQueueAppender and Tomcat 4.1
Thank you for the response.
I am constructing the initial context factory as you suggest - using
the
hastable. Both this and the provider URL are specified in the log4j
file
for the JMSQueueAppender.
ht.put(Context.INITIAL_CONTEXT_FACTORY
with log4j?
Yoav Shapira
Millennium ChemInformatics
-Original Message-
From: Sabitha [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 18, 2003 9:50 AM
To: Log4J Users List
Subject: RE: JMSQueueAppender and Tomcat 4.1
Thank you for the response.
I am constructing the initial context
, December 18, 2003 11:17 AM
To: Log4J Users List
Subject: RE: JMSQueueAppender and Tomcat 4.1
Yes.. this class is in the websphere.jar file and I have included it -
along with log4j-1.2.8.jar - in my WEB-INF/lib directory.
Sabitha
Shapira, Yoav [EMAIL PROTECTED] wrote:
Howdy,
And the class
Subject: RE: JMSQueueAppender and Tomcat 4.1
Yes.. this class is in the websphere.jar file and I have included it -
along with log4j-1.2.8.jar - in my WEB-INF/lib directory.
Sabitha
Shapira, Yoav wrote:
Howdy,
And the class with the initial context factory implementation
(com.ibm...) is in your WEB
