Mail Session JNDI Lookup fails on 5.0.25
I've been using 4.1.x and 5.0.x for quite some time with the sample application. This application does a JNDI lookup of a mail session. This session is configured in my app's context with the following: Resource name=mail/Session auth=Container type=javax.mail.Session/ ResourceParams name=mail/Session parameter namemail.smtp.host/name valuelocalhost/value /parameter /ResourceParams My code has worked flawlessly on all Tomcat 4.1.x and Tomcat 5.0.x releases (even 5.0.24), but it doesn't work on 5.0.25. Here's my code: session = (Session) new InitialContext().lookup(java:comp/env/ + Constants.JNDI_MAIL); Where Constants.JNDI_MAIL is: public static final String JNDI_MAIL = mail/Session; I noticed that I didn't have a resource-ref in my web.xml for this resource, but adding it didn't fix the problem. Any idea what changed in 5.0.25? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mail Session JNDI Lookup fails on 5.0.25
Hi, Hmm. I wasn't aware of anything in the naming/JNDI area that changed in 5.0.25 that could cause this. Yet I can reproduce your problem, so it's clearly not specific to you. You get a javax.naming.NamingException: Cannot create resource instance exception, right? Digging a bit deeper, I see nothing related to this in the 5.0.25 changelog, and none of the files under org.apache.naming have changed in the last two months. So we need to dig deeper still ;( Yoav Shapira Millennium Research Informatics -Original Message- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 2:39 PM To: Tomcat Users List Subject: Mail Session JNDI Lookup fails on 5.0.25 I've been using 4.1.x and 5.0.x for quite some time with the sample application. This application does a JNDI lookup of a mail session. This session is configured in my app's context with the following: Resource name=mail/Session auth=Container type=javax.mail.Session/ ResourceParams name=mail/Session parameter namemail.smtp.host/name valuelocalhost/value /parameter /ResourceParams My code has worked flawlessly on all Tomcat 4.1.x and Tomcat 5.0.x releases (even 5.0.24), but it doesn't work on 5.0.25. Here's my code: session = (Session) new InitialContext().lookup(java:comp/env/ + Constants.JNDI_MAIL); Where Constants.JNDI_MAIL is: public static final String JNDI_MAIL = mail/Session; I noticed that I didn't have a resource-ref in my web.xml for this resource, but adding it didn't fix the problem. Any idea what changed in 5.0.25? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Mail Session JNDI Lookup fails on 5.0.25
Hi, After adding some debugging statement to the code (on a local build of 5.0.26 that has no relevant changes): getting mail session factory. factory class name = org.apache.naming.factory.MailSessionFactory java.lang.ClassNotFoundException: org.apache.naming.factory.MailSessionFactory at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClas sLoader.java:854) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClas sLoader.java:721) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at org.apache.naming.factory.ResourceFactory.getObjectInstance(ResourceF actory.java:125) And further, jar tvf $CATALINA_HOME/common/lib/naming-factory.jar shows org.apache.naming.factory.MailSessionFactory is indeed missing. The same command on tomcat 5.0.24's common/lib shows the class present. I have a vague theory on why this happened. Regardless, this is a good catch on your part. I've opened a bugzilla item for it (http://nagoya.apache.org/bugzilla/show_bug.cgi?id=29255), and noted in the item that a quick workaround until the next build is available is to copy the naming-factory.jar from 5.0.24 to the common/lib directory. Yoav Shapira Millennium Research Informatics -Original Message- From: Matt Raible [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 2:39 PM To: Tomcat Users List Subject: Mail Session JNDI Lookup fails on 5.0.25 I've been using 4.1.x and 5.0.x for quite some time with the sample application. This application does a JNDI lookup of a mail session. This session is configured in my app's context with the following: Resource name=mail/Session auth=Container type=javax.mail.Session/ ResourceParams name=mail/Session parameter namemail.smtp.host/name valuelocalhost/value /parameter /ResourceParams My code has worked flawlessly on all Tomcat 4.1.x and Tomcat 5.0.x releases (even 5.0.24), but it doesn't work on 5.0.25. Here's my code: session = (Session) new InitialContext().lookup(java:comp/env/ + Constants.JNDI_MAIL); Where Constants.JNDI_MAIL is: public static final String JNDI_MAIL = mail/Session; I noticed that I didn't have a resource-ref in my web.xml for this resource, but adding it didn't fix the problem. Any idea what changed in 5.0.25? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
