The answer turns out to be a RedHat environment variable. You need to set
something like this or JNDI will not respond to remote requests.
JAVA_OPTS=-Djava.rmi.server.hostname=192.26.123.93
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3907322#3907322
Re
Hello. I have a small example application which writes a text message to a
queue. Works great when JBoss and application are working through localhost,
fails when application and JBoss reside on different machines.
I do have JBoss RMI clients working in the same scenario, I know enough to
pro
I test w/Fedora 3 and Solaris 9 hosts. The hosts all have the same version of
JBoss (3.2.6) and the same JVM (1.4.2_06). Clustering works in my scenario.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862466#3862466
Reply to the post :
http://www.jboss.org
Hello, all. If your using Fedora3 and JBoss 3.2.6 you might have noticed this
problem when running the "all" configuration.
| 18:13:39,873 INFO [HANamingService] Listening on /0.0.0.0:1100
| 18:13:39,882 WARN [HANamingService] Failed to start AutomaticDiscovery
| java.net.SocketExceptio
