ugh I doubt it.
- Original Message -
From: "Tim Taylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 16, 2001 6:38 AM
Subject: RE: [JBoss-user] NamingService initialization problems--ConnectionException
> Yes. That file is there and it sets n
7;m running it on Solaris and Linux with zero
problems.
> -Original Message-
> From: Scott M Stark [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, May 16, 2001 5:49 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-user] NamingService initialization
> problems--ConnectionExce
aylor" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 15, 2001 10:40 AM
Subject: RE: [JBoss-user] NamingService initialization
problems--ConnectionException
> Scott, thanks for the reply. I get an NPE when I delete the
jndi.properties
> f
Scott, thanks for the reply. I get an NPE when I delete the jndi.properties
file.
Here's the code for org.jboss.naming.NamingService.initService() in JBoss
2.2.1. Without the jndi.properties file, the System.getProperties... line
gets an NPE. With the jndi.properties file in place, the Context
The problem is the warning msg displayed at the start
of the server startup regarding the jndi.properties
file. You have a jndi.properties file in your classpath
that most likely contains a provider url which puts
the naming service in client mode and so fails to connect
to the non-existant server
