This typically means you haven¹t declared any appenders to apply to the logger for the class specified. This could be due to the lack of assigning appenders to the ³log4j.rootLogger² option or maybe issues with reading in the configuration file.
On 6/16/09 10:54 AM, "Jeison Gutierrez" <[email protected]> wrote: > One more thing ,,, when i build the package i get this warning,,,And it takes > good bit time to continue with the build process,,,do you know how to fix it > > http://pastebin.com/mb22aea1 > > > > On Tue, Jun 16, 2009 at 10:43 AM, Marvin S. Addison <[email protected]> > wrote: >>> > org.springframework.ldap.CommunicationException: simple bind failed: >>> > localhost:389; nested exception is >>> > javax.naming.CommunicationException: simple bind failed: localhost:389 >>> > [Root exception is javax.net.ssl.SSLHandshakeException: Remote host >>> > closed connection during handshake] >> >> Based on the LDAP config in your deployerConfigContext.xml, it looks >> like you're trying to talk SSL to port 389, which is likely not going to >> work. You either need to communicate with the SSL port, 636, or >> configure your LDAP context source to issue a startTLS command to >> upgrade your connection to TLS on the standard 389 port. I can provide >> configuration for that if you'd like the latter, but most folks take the >> easy route and talk to the SSL port, e.g. https://directory.vt.edu:636. >> Also, it might be helpful for us to know what LDAP software you're >> using. >> >> M -- Andrew Feller, Analyst LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
