|
Rajakumar,
Hi. It
may be that I am not sure what you are suggesting I do but here is what I did
try, to no avail.
First
off I forgot to mention that I am running the final 3.0 release of JBoss for
Linux (RH 7.2).
Under
my $JBOSS_HOME directory (/use/local/jboss in my case) I do not have an 'admin'
directory anywhere, but I did find three copies of the file
jndi.properties. They are at:
[root@host jboss]# find . -name jndi.properties
-print
./server/all/conf/jndi.properties ./server/default/conf/jndi.properties ./server/minimal/conf/jndi.properties ./catalina/lib/jndi.properties [root@host jboss]# They
are all the same.
The
first thing I did was copy of the lines you have below as the contents of the
jndi.properties file to a file of that name in the /usr/local/jboss/catalina/lib
directory. Restarting the server, which by the way has no errors in the
/usr/local/jboss/server/default/log/server.log file, and accessing via the
browser produced the same 'no context' error message.
Then I
moved that file to /usr/local/jboss/catalina/common/lib and restarted the
server. The result was the same error msg.
Finally I copied the contents of one of the three jndi.properties files
that were originally part of jboss overtop of the contents of the
jndi.properties file in the /usr/local/jboss/catalina/common/lib directory and
restarted the server. No change.
Lastly
I moved that file up to the /usr/local/jboss/catalina/lib directory and
restarted. Also no change.
BTW
the new contents of the jndi.properties file is:
[root@host lib]# cat
jndi.properties
java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces # Do NOT uncomment this line as it causes in VM calls to go over # RMI! #java.naming.provider.url=localhost [root@host lib]#
|
