-
1. Re: ConnectionFactory lookup
joelvogt Sep 23, 2002 4:35 AM (in response to cfg123)not sure. What context are you using? Is this in jboss or an external client?
-
2. Re: ConnectionFactory lookup
cfg123 Sep 23, 2002 5:25 AM (in response to cfg123)sorry, this is the context used in my program....
System.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
System.setProperty("java.naming.provider.url", "192.90.1.19:1099");
Context context = new InitialContext();
QueueConnectionFactory queueFactory =(QueueConnectionFactory)context.lookup(factoryJNDI); -
3. Re: ConnectionFactory lookup
cfg123 Sep 23, 2002 5:26 AM (in response to cfg123)sorry, this is the context used in my program....
System.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
System.setProperty("java.naming.provider.url", "192.90.1.19:1099");
Context context = new InitialContext();
QueueConnectionFactory queueFactory =(QueueConnectionFactory)context.lookup(factoryJNDI); -
4. Re: ConnectionFactory lookup
cfg123 Sep 23, 2002 5:39 AM (in response to cfg123)Sorry, the context i used here is just a normal context in jboss. The program is like this:
System.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
System.setProperty("java.naming.provider.url", "192.90.1.19:1099");
Context context = new InitialContext();
QueueConnectionFactory queueFactory =(QueueConnectionFactory)context.lookup("ConnectionFactory"); -
5. Re: ConnectionFactory lookup
radazz Oct 21, 2002 5:48 AM (in response to cfg123)Hi!
I have the same problem under jboss 2.4.8 and above.
But under 2.4.4 external client works..
R. -
6. Re: ConnectionFactory lookup
joelvogt Oct 21, 2002 7:20 AM (in response to cfg123)try this
props.put("java.naming.rmi.security.manager", "yes");
props.put(Context.URL_PKG_PREFIXES, "org.jboss.naming"); -
7. Re: ConnectionFactory lookup
sordes Oct 29, 2002 10:55 PM (in response to cfg123)We had the exact same problem not so long ago on one of my programmer's pc. It was fix by removing some conflicting jars from our classpath. Internally it was producing a marchaling error and for some reason the generated stub didn't complain about it and simply returned null.
Hope this will fix your problem as it did for us!