Scott, After manually install the jmxtools jar to the local repository, I try to hot deploy the packaged war to the Tomcat instance. The problem is still not solved.
Here is the "NEW" log message, the bold part appears only after I upgraded to log4j-1.2.15: INFO: Undeploying context [/cas] log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. Oct 24, 2007 4:27:40 PM org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive cas.war log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester). log4j:WARN Please initialize the log4j system properly. Harry scott_battaglia wrote: > > Harry, > > Does it go away with the Log4j upgrade? If so, I'll upgrade the Log4j > before putting out 3.1.1 (which I'm behind schedule on due to some other > priorities). > > -Scott > > On 10/23/07, Harry Ng <[EMAIL PROTECTED]> wrote: >> >> >> Hi, >> >> I can reproduce the case when I hot deploy the new war file to Tomcat. >> And >> yes, even the Null Pointer is thrown, it will not affect Authentication >> Handler. >> >> I'm not familiar with the EH Cache stuff, but it causes me problem on hot >> deploy. After I turned on the service managment module with the use of >> Hibernate, on every time I hot deploy, Tomcat is unable to clean the >> acegi-security-1.0.4.jar file. As far as what I search, this EH Cache is >> used as a core program for Hibernate through spring-dao, and spring-dao >> is >> made included within the acegi dependency. >> >> I may have made the problem quite complicated, and please correct me if I >> am >> wrong. >> >> Harry >> >> >> scott_battaglia wrote: >> > >> > There should be no issues with updating to Log4j 1.2.15 (we should >> > probably >> > upgrade the stock CAS release if its not included...off to JIRA I go). >> > >> > However, that NullPointerException should be happening in a different >> > thread >> > that does not affect how the Authentication Handler is connecting to >> LDAP. >> > >> > -Scott >> > >> > On 10/23/07, Andrew R Feller <[EMAIL PROTECTED]> wrote: >> >> >> >> Tarik, >> >> >> >> >> >> >> >> What version of CAS are you running? What version of log4j is it >> using? >> >> After doing some snooping, it appears that there was a bug in >> >> log4j-1.2.14on Tomcat and EH Cache shutdown where they were doing >> things >> >> poorly/badly. >> >> A fix was made in the log4j-1.2.15 release that should address this >> >> problem. ( >> >> >> http://www.nabble.com/DO-NOT-REPLY--Bug-40212---New%3A----NullPointerException-in-getLogger-when-called-from-ShutdownHook-t2073202.html#a5708242 >> ) >> >> >> >> >> >> >> >> >> >> Scott: This is just my cursory investigation as I cannot reproduce >> this >> >> issue personally. Are there any issues with updating to log4j-1.2.15? >> >> >> >> >> >> >> >> Hope this helps, >> >> >> >> >> >> >> >> Andrew R Feller, Analyst >> >> >> >> Subversion Administrator >> >> >> >> University Information Systems >> >> >> >> Louisiana State University >> >> >> >> [EMAIL PROTECTED] >> >> >> >> (office) 225.578.3737 >> >> ------------------------------ >> >> >> >> *From:* [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] >> ] >> >> *On >> >> Behalf Of *Tarik Arrad >> >> *Sent:* Tuesday, October 23, 2007 5:39 AM >> >> *To:* Yale CAS mailing list >> >> *Subject:* Re: The CAS Java Client on the website should be updated to >> >> 3.1.0 >> >> >> >> >> >> >> >> I'm trying to deploy CAS with LDAP (OpenLDAP), after authentication i >> >> have >> >> this log messages : >> >> >> >> 2007-10-23 10:19:25,770 INFO [ >> >> org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting ContextPath >> for >> >> cookies to: /cas> >> >> 2007-10-23 10:19:30,920 INFO [ >> >> org.jasig.cas.authentication.AuthenticationManagerImpl] - >> >> <AuthenticationHandler: >> >> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler failed to >> >> authenticate the user which provided the following credentials: Driss> >> >> Exception in thread "Store ticketCache Expiry Thread" >> >> java.lang.NullPointerException >> >> at org.apache.log4j.LogManager.getLogger(LogManager.java:188) >> >> at org.apache.log4j.Logger.getLogger(Logger.java :104) >> >> at org.apache.commons.logging.impl.Log4JLogger.getLogger( >> >> Log4JLogger.java:283) >> >> at org.apache.commons.logging.impl.Log4JLogger.isDebugEnabled( >> >> Log4JLogger.java:293) >> >> at net.sf.ehcache.store.DiskStore.expiryThreadMain (DiskStore.java >> >> :834) >> >> at net.sf.ehcache.store.DiskStore.access$700(DiskStore.java:59) >> >> at net.sf.ehcache.store.DiskStore$ExpiryThread.run(DiskStore.java >> >> :1008) >> >> 2007-10-23 10:20:44,687 INFO [ >> >> org.jasig.cas.web.flow.AuthenticationViaFormAction ] - >> <FormObjectClass >> >> not set. Using default class of >> >> org.jasig.cas.authentication.principal.UsernamePasswordCredentials >> with >> >> formObjectName credentials and validator >> >> org.jasig.cas.validation.UsernamePasswordCredentialsValidator .> >> >> 2007-10-23 10:20:47,878 INFO [ >> >> org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting ContextPath >> for >> >> cookies to: /cas> >> >> 2007-10-23 10:20:53,176 INFO [ >> >> org.jasig.cas.authentication.AuthenticationManagerImpl ] - >> >> <AuthenticationHandler: >> >> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler failed to >> >> authenticate the user which provided the following credentials: Tarik> >> >> 2007-10-23 10:20:59,737 INFO [ >> >> org.jasig.cas.authentication.AuthenticationManagerImpl ] - >> >> <AuthenticationHandler: >> >> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler failed to >> >> authenticate the user which provided the following credentials: >> Manager> >> >> 2007-10-23 10:21:03,940 INFO [ >> >> org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner ] - >> >> <Starting cleaning of expired tickets from ticket registry at [Tue Oct >> 23 >> >> 10:21:03 WET 2007]> >> >> 2007-10-23 10:21:03,940 INFO [ >> >> org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - >> <0 >> >> found to be removed. Removing now.> >> >> 2007-10-23 10:21:03,940 INFO [ >> >> org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - >> >> <Finished cleaning of expired tickets from ticket registry at [Tue Oct >> 23 >> >> 10:21:03 WET 2007]> >> >> 2007-10-23 10:23:45,405 INFO [ >> >> org.jasig.cas.authentication.AuthenticationManagerImpl] - >> >> <AuthenticationHandler: >> >> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler failed to >> >> authenticate the user which provided the following credentials: Tarik> >> >> Exception in thread "Store ticketCache Expiry Thread" >> >> java.lang.NullPointerException >> >> at org.apache.log4j.LogManager.getLogger(LogManager.java:188) >> >> at org.apache.log4j.Logger.getLogger(Logger.java :104) >> >> at org.apache.commons.logging.impl.Log4JLogger.getLogger( >> >> Log4JLogger.java:283) >> >> at org.apache.commons.logging.impl.Log4JLogger.isDebugEnabled( >> >> Log4JLogger.java:293) >> >> at net.sf.ehcache.store.DiskStore.expiryThreadMain (DiskStore.java >> >> :834) >> >> at net.sf.ehcache.store.DiskStore.access$700(DiskStore.java:59) >> >> at net.sf.ehcache.store.DiskStore$ExpiryThread.run(DiskStore.java >> >> :1008) >> >> 2007-10-23 10:23:59,140 INFO [ >> >> org.jasig.cas.web.flow.AuthenticationViaFormAction ] - >> <FormObjectClass >> >> not set. Using default class of >> >> org.jasig.cas.authentication.principal.UsernamePasswordCredentials >> with >> >> formObjectName credentials and validator >> >> org.jasig.cas.validation.UsernamePasswordCredentialsValidator .> >> >> 2007-10-23 10:24:02,829 INFO [ >> >> org.jasig.cas.web.flow.InitialFlowSetupAction] - <Setting ContextPath >> for >> >> cookies to: /cas> >> >> 2007-10-23 10:24:12,016 INFO [ >> >> org.jasig.cas.authentication.AuthenticationManagerImpl ] - >> >> <AuthenticationHandler: >> >> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler failed to >> >> authenticate the user which provided the following credentials: >> Manager> >> >> 2007-10-23 10:24:17,246 INFO [ >> >> org.jasig.cas.authentication.AuthenticationManagerImpl ] - >> >> <AuthenticationHandler: >> >> org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler failed to >> >> authenticate the user which provided the following credentials: Tarik> >> >> 2007-10-23 10:24:18,374 INFO [ >> >> org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner ] - >> >> <Starting cleaning of expired tickets from ticket registry at [Tue Oct >> 23 >> >> 10:24:18 WET 2007]> >> >> 2007-10-23 10:24:18,374 INFO [ >> >> org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - >> <0 >> >> found to be removed. Removing now.> >> >> 2007-10-23 10:24:18,374 INFO [ >> >> org.jasig.cas.ticket.registry.support.DefaultTicketRegistryCleaner] - >> >> <Finished cleaning of expired tickets from ticket registry at [Tue Oct >> 23 >> >> 10:24:18 WET 2007]> >> >> >> >> Help Plz >> >> Tarik Arrad >> >> >> >> _______________________________________________ >> >> Yale CAS mailing list >> >> [email protected] >> >> http://tp.its.yale.edu/mailman/listinfo/cas >> >> >> >> >> > >> > >> > -- >> > -Scott Battaglia >> > >> > LinkedIn: http://www.linkedin.com/in/scottbattaglia >> > >> > _______________________________________________ >> > Yale CAS mailing list >> > [email protected] >> > http://tp.its.yale.edu/mailman/listinfo/cas >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/CAS-proxy-mode-tf4670705.html#a13366048 >> Sent from the CAS Users mailing list archive at Nabble.com. >> >> _______________________________________________ >> Yale CAS mailing list >> [email protected] >> http://tp.its.yale.edu/mailman/listinfo/cas >> > > > > -- > -Scott Battaglia > > LinkedIn: http://www.linkedin.com/in/scottbattaglia > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > > -- View this message in context: http://www.nabble.com/CAS-proxy-mode-tf4670705.html#a13381310 Sent from the CAS Users mailing list archive at Nabble.com. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
