• Post Reply Bookmark Topic Watch Topic
  • New Topic

Hi there  RSS feed

 
James Callaghan
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm trying to run a stand-alone client from the command prompt that accesses an ELB that I've created but I'm getting a NoInitialContextException on java.naming.factory.initial.
I've checked my CLASSPATH and I seem to have all of the relevant jar files there (j2ee.jar, ldapbp.jar, providerutil.jar, jaas.jar and ldap.jar ar all there). Now I'm just stumped. I thought that the java.naming properties were set in the j2ee.jar?
Cheers for any help.
Jimbo
 
Renat Zubairov
Greenhorn
Posts: 29
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually, during init of InitialContext object it trying to find address and
port where to connect in order to recieve access JNDI server.
You can see description here:
http://java.sun.com/j2se/1.4.1/docs/api/javax/naming/InitialContext.html
Usually you have to set up two properties (java -D<prop_name>=<prop_value> .....)
java.naming.provider.url - URL of the server like tcp://localhost:3035
java.naming.factory.initial - Class name of JNDI factory like org.exolab.jms.jndi.InitialContextFactory
Br
Renat
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!