Of course, I had it set to
1. other machine's hostname
2. IP address
3. the above with the port number.
Then I tried the same thing on the same machine where JBoss is running and
used localhost there, to no avail.
On Sun, 25 Feb 2001, Steve Salkin wrote:
> >
> > I've tried something similar to this, e.g. putting jndi.properties on the
> > classpath (actually into META-INF of the WAR being deployed). That took
> > care of exceptions JNDI was throwing because it could not find the
> > provider. But now it just hangs trying to create InitialContext. Any
> > ideas?
> >
> >
> > On Mon, 26 Feb 2001, Lionel Siau wrote:
> >
> > > Hi,
> > >
> > > try this on the 'client' code. Self explanatory. I think it can be placed at
> > > the command line too.
> > >
> > > There are a couple similar looking mails on this.
> > >
> > > Lionel
> > >
> > > System.setProperty("java.naming.factory.initial",
> > > "org.jnp.interfaces.NamingContextFactory");
> > > System.setProperty("java.naming.provider.url",
> > > "localhost:1099");
>
> In an earlier mail, you said that your setup is to have tomcat and jboss on
>different machines. Not to insult your intelligence but is it possible that
> you have the naming provider url set to localhost just as Lionel's code snippet?
>
> S-
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> List Help?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
