On Tue, 19 Sep 2000, Greg Pierce wrote:
> Okay here is the deal. We upgraded to the BETA-PROD and moved all of our
> beans over to the new version and after a couple of flips and such got it
> all working again. But here is the interesting thing. If you change the
> jndi.properties file to point to your machines IP address, jBoss seems to
> ignore it. You have to change the jboss.properties file's naming.provider in
> order for it to work or the remote clients get the old 'localhost' problem.
> After changing the java.rmi.server.hostname to the proper machines IP
> address everything is happy but then begs the question.. what does the
> provider URL in the jndi.properties file in the conf directory really do?
The host name in jndi.properties is where JNDI will go for initial
lookups. If that is wrong, you will get "no object found" JNDI
errors. Once you have found something through JNDI, that something
controls all subsequent communication. The settings in jboss.properties
control where the jBoss classes will look for subsequent
communication. So if those settings are wrong, you will successfully get
an object from JNDI, but then it will be unable to communicate any further
with the server. This is most commonly a "localhost" error, since the
default configuration declares "localhost" to be the server name in
jboss.properties.
Reportedly, you can fix jboss.properties by commenting out the
java.rmi.server.hostname, or by correcting the java.rmi.server.hostname
and uncommenting java.rmi.server.useLocalHostName. It's not clear to me
why this isn't shipped with the java.rmi.server.hostname line commented
out, which should make remote client work with only the jndi.properties
change.
Aaron
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
