Re: [JBoss-user] Converting to 3.2.1 - javax.naming.NameNotFoundException:comp not bound
Scott M Stark wrote: The significance of the ordering of the java.naming.factory.url.pkgs is that this defines the order of packages from which url context factories are found, which includes the java: context. This must be the org.jboss.naming.java.javaURLContextFactory to select the server local java: context. Scott, sorry, one more time if I may. I switched from using this in 2.4.3: java.naming.factory.url.pkgs=org.jnp.interfaces to using this (from testsuite) in 3.2.1: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces The second one is working, as I reported in my last message. Are you saying that instead of the second one, I should instead be using: java.naming.factory.url.pkgs=org.jboss.naming.java.javaURLContextFactory What is the difference between this last one and the second one? As always, thanks for your time. -- Guy Rouillier --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Converting to 3.2.1 - javax.naming.NameNotFoundException:comp not bound
Use: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces -- Scott Stark Chief Technology Officer JBoss Group, LLC Guy Rouillier wrote: Scott M Stark wrote: The significance of the ordering of the java.naming.factory.url.pkgs is that this defines the order of packages from which url context factories are found, which includes the java: context. This must be the org.jboss.naming.java.javaURLContextFactory to select the server local java: context. Scott, sorry, one more time if I may. I switched from using this in 2.4.3: java.naming.factory.url.pkgs=org.jnp.interfaces to using this (from testsuite) in 3.2.1: java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces The second one is working, as I reported in my last message. Are you saying that instead of the second one, I should instead be using: java.naming.factory.url.pkgs=org.jboss.naming.java.javaURLContextFactory What is the difference between this last one and the second one? As always, thanks for your time. --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Converting to 3.2.1 - javax.naming.NameNotFoundException:comp not bound
I would say you have a jndi.properties file in one of the jars that is interfering with the java:comp context setup. -- Scott Stark Chief Technology Officer JBoss Group, LLC Guy Rouillier wrote: I've initiated the process of converting our 2.4.3 systems to 3.2.1, using JDK 1.3.1 on Win2k SP2. The first one I tried is a simple EJB that uses a single Oracle database. To try this quickly, I put classes12.jar and a standard jar of ours (containing exception classes) into server/servername/lib. Here is the -ds.xml file for it: = datasources local-tx-datasource jndi-nameordermanagementDB/jndi-name connection-urljdbc:oracle:thin:@servername.company.com:1521:sidname/connection-url driver-classoracle.jdbc.driver.OracleDriver/driver-class user-nameuserid/user-name passwordpassword/password exception-sorter-class-nameorg.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter/exception-sorter-class-name /local-tx-datasource /datasources Using jmx-console, I can see that this datasource is successfully started. When I deploy an EJB that does a lookup on this datasource, I get the subject exception (partial stack at end of message). However, if I then delete the JAR file and immediately copy it back (without shutting down JBoss), this time it will be deployed successfully!??? I've verified that the EJB and the db connection work fine once the EJB is successfully deployed. This is a best case scenario. Tonight, preparing to write this message, I tried deleting and copying the JAR five times, and got the subject error each time. I had to shut down JBoss, restart it, deploy the EJB, watch it fail, delete it then deploy it a second time. Finally, I got a successful deployment. This is a binary JBoss 3.2.1 installation, not from source, and the same thing is happening to a co-worker on completely different hardware (Linux). This has me baffled - what am I doing wrong? Here is a partial stack trace: 2003-06-27 23:01:24,562 DEBUG [org.jboss.ejb.StatelessSessionContainer] Begin java:comp/env for EJB: com.masergy.ejb.OrderManagement.OrderManagement 2003-06-27 23:01:24,562 DEBUG [org.jboss.ejb.StatelessSessionContainer] TCL: [EMAIL PROTECTED] 2003-06-27 23:01:24,640 ERROR [org.jboss.ejb.StatelessSessionContainer] Starting failed javax.naming.NameNotFoundException: comp not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:495) at org.jnp.server.NamingServer.getBinding(NamingServer.java:503) at org.jnp.server.NamingServer.getObject(NamingServer.java:509) at org.jnp.server.NamingServer.lookup(NamingServer.java:282) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) at javax.naming.InitialContext.lookup(InitialContext.java:350) at org.jboss.ejb.Container.setupEnvironment(Container.java:734) at org.jboss.ejb.Container.startService(Container.java:568) --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Converting to 3.2.1 - javax.naming.NameNotFoundException:comp not bound
Scott M Stark wrote: I would say you have a jndi.properties file in one of the jars that is interfering with the java:comp context setup. Scott, thanks for the reply. I spent a half hour constructing a follow-up. Just as I was about to hit the send key, I noticed that in my jndi.properties (copied from my 2.4.3 implementation), I had java.naming.factory.url.pkgs=org.jnp.interfaces I noticed that in the testsuite jndi.properties file, it had java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces Sure enough, when I changed mine to this, the problem went away. Thanks for steering me in that direction. What is the semantic significance of putting org.jboss.naming: on the front? And any guess as to why this worked if I deployed/undeployed enough times? -- Guy Rouillier --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] Converting to 3.2.1 - javax.naming.NameNotFoundException:comp not bound
The significance of the ordering of the java.naming.factory.url.pkgs is that this defines the order of packages from which url context factories are found, which includes the java: context. This must be the org.jboss.naming.java.javaURLContextFactory to select the server local java: context. -- Scott Stark Chief Technology Officer JBoss Group, LLC Guy Rouillier wrote: Scott M Stark wrote: I would say you have a jndi.properties file in one of the jars that is interfering with the java:comp context setup. Scott, thanks for the reply. I spent a half hour constructing a follow-up. Just as I was about to hit the send key, I noticed that in my jndi.properties (copied from my 2.4.3 implementation), I had java.naming.factory.url.pkgs=org.jnp.interfaces I noticed that in the testsuite jndi.properties file, it had java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces Sure enough, when I changed mine to this, the problem went away. Thanks for steering me in that direction. What is the semantic significance of putting org.jboss.naming: on the front? And any guess as to why this worked if I deployed/undeployed enough times? --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0016ave/direct;at.asp_061203_01/01 ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
