problems with web app and JndiContextSelector

I am having problems moving our web app over to Log4j 2.0 using JNDI lookups. I followed the configuration documentation and am not getting any errors, but nothing is being logged to my configured appenders. Weirdly, if I remove the JNDI env-entry configuration from web.xml logging seems to work, a

Re: problems with web app and JndiContextSelector

ect that demonstrates the problem. At a > minimum I would think the web.xml and log4j 2 configuration. > > Ralph > > On Jul 29, 2014, at 5:47 AM, Mike Calmus wrote: > > > I am having problems moving our web app over to Log4j 2.0 using JNDI > > lookups. I followed the

Re: problems with web app and JndiContextSelector

Scenario 1 above now works. The JNDI configuration does not work. On Fri, Aug 1, 2014 at 3:16 PM, Mike Calmus wrote: > We're using a Servlet 2.5 container and configuration. I added the > Log4jContextSelector environment variable to the container startup as well > as loading all the

Re: problems with web app and JndiContextSelector

I don't know for sure, but based upon my reading online it appears that may be a new feature for 12c which we are not yet using. On Wed, Aug 6, 2014 at 1:33 PM, Matt Sicker wrote: > Are system libraries in Weblogic loaded as OSGi bundles? > > > On 6 August 2014 11:39, M

Re: problems with web app and JndiContextSelector

w. I'll see > if I can take a look at this since we use the same version of Weblogic at > my work (thus I actually know a little bit about this application). > > > On 6 August 2014 16:31, Mike Calmus wrote: > > > I don't know for sure, but based upon my reading onli

adding log4j 2.x support to a library

We have some existing code that is used as a library by other projects. This code uses log4j 1.2. We would like to convert it to use log4j 2.x but not remove support for 1.2 so that projects that have not yet migrated can still see logging. Any thoughts on how this might be accomplished? Thanks.

ExceptionInInitializerError with JUL turned on

I'm trying to add the log4j-jul jar to our configuration. I set the "java.util.logging.manager" system property as per the documentation in the server's startup configuration. When I try to start the server I get an ExceptionInInitialerError with the following: Caused By: java.lang.IllegalStateExc

Re: ExceptionInInitializerError with JUL turned on

Version 2.4.1 of Log4j. Java 7 (u85). On Tue, Oct 20, 2015 at 2:43 PM, Ralph Goers wrote: > What version of Java and what version of Log4j? > > Ralph > > > On Oct 20, 2015, at 10:57 AM, Mike Calmus wrote: > > > > I'm trying to add the log4j-jul

log4j-jcl causing logging issues

I saw this with older version of Log4j 2 as well, but now I'm using 2.4.1 on Java 7. We are including all the log4j libraries in the Weblogic server startup classpath. Commons-logging 1.2 is included as well. All works fine using JndiRepositorySelector when log4j-jcl is not included. When that jar

Unable to lookup java:comp/env/log4j/context-name

We are moving from Weblogic (10g) to JBoss (EAP6). The server is set to use the JndiContextSelector. All the required properties are set in the web.xml. With apps that have EJBs or web services, JBoss seems to be initializing the code as it is being deployed. Because our base web service classes

Re: Unable to lookup java:comp/env/log4j/context-name

inline with its declaration. Then, a @PostConstruct method is used to instantiate the Logger. On Thu, Dec 10, 2015 at 3:09 PM, Mike Calmus wrote: > We are moving from Weblogic (10g) to JBoss (EAP6). > > The server is set to use the JndiContextSelector. All the required > properties ar

Re: Header does not end with a new line in Console appender

This is included as an improvement in Log4j2 2.6: https://issues.apache.org/jira/browse/LOG4J2-1237 > On Mar 22, 2016, at 2:30 PM, Kamal Mettananda wrote: > > Hi all > > This is my first email, so please raise if I have not correctly understood > the usage of the header attribute. > > When I

Logging stops on application redeploy

We are having issues with Log4j (many versions up to and including 2.6.2) where it works fine when an application is newly deployed and at server startup but where logging stops when an application is redeployed. We are using JBoss EAP 6. Applications are configured as Servlet 3.0 and we are using

Re: Logging stops on application redeploy

nd a configuration file. > > I wonder how redeploy could cause Log4j to become unable to find the > configuration... > > What do you see when you enable Log4j internal status logging? > https://logging.apache.org/log4j/2.x/faq.html#troubleshooting > > Remko > > Sent from

Re: Logging stops on application redeploy

We have found that the apps having this issue all seem to be using Spring-web. Apps not using Spring do not seem to be experiencing the issue. On Fri, Jul 29, 2016 at 11:21 AM, Mike Calmus wrote: > 10:44:02,263 INFO [stdout] (ServerService Thread Pool -- 88) 2016-07-29 > 10:44: