Abhishek Upadhyay wrote:Can you paste a more of exception.
I dont kno about JBoss, but check:
IS Queue Name bind to the JNDI name you are providing.
Also, you might need other jars like
dhbcore.jar, fscontext.jar(or depending on Intial Context), jndi.jar, and providerutil.jar
Above jars are needed when sending message form a java program, which is not running in app. server.
vk jain wrote:Can you please share the deployment descriptor you are using to deploy receiver.
Abhishek Upadhyay wrote:
dhbcore.jar, fscontext.jar(or depending on Intial Context), jndi.jar, and providerutil.jar
Above jars are needed when sending message form a java program, which is not running in app. server.
Abhishek Upadhyay wrote:
Also, you might need other jars like
dhbcore.jar, fscontext.jar(or depending on Intial Context), jndi.jar, and providerutil.jar
Above jars are needed when sending message form a java program, which is not running in app. server.
A. S. Georgie wrote:
------------ NamingException ------------
javax.naming.NoInitialContextException: Need to specify class name in environmen
t or system property, or as an applet parameter, or in an application resource f
ile: java.naming.factory.initial
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
java.naming.provider.url=localhost:1099
Vishwanath Krishnamurthi wrote:
javax.naming.NoInitialContextException: Need to specify class name in environmen
t or system property, or as an applet parameter, or in an application resource f
ile: java.naming.factory.initial[/color]
Quick! Before anybody notices! Cover it up with this tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|