Well, I finally had some time to delve into the source code. I searched the
source code for JbossAS, Jboss-Messaging, and Jboss-Remoting. I did not find
the root cause (EXACTLY), but I did find a solution.
POSSIBLE ROOT CAUSE:
>From searching inside the source code, I see that almost all of
PeterJ:
Yes, I think you are correct. I guess I will dive into the source code next
week. Fun. Fun.
Thanks again for all your effort.
Rich
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154790#4154790
Reply to the post :
http://www.jboss.com/index.html?
PeterJ:
Navigated to the jmx-console on test and qa. All of the properties were the
same in both. The properties that contained server names all had the correct
server names. No localhost or 127.0.0.1 were found.
Perhaps re-stating my issue will help...
I run the same script on test and qa
PeterJ:
1. If I ping the servers, I get their correct IP addresses.
2. Tried adding -Djava.rmi.server.hostname. Unfortunately, same results.
Clients receive a serverLocatorURI of 127.0.0.1.
3. Yes, I do know that -b and jboss.bind.address are supposed to be the same.
Unfortunately I coul
The 8080 message is the same in both places:
[Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
Host File for Test (balin.flpi.com OR 10.77.0.60):
127.0.0.1 localhost.localdomain localhost balin balin.flpi.com
#10.78.0.60 balin balin.flpi.com
10.78.0.65
I have installed jboss-4.2.2.GA with jboss-messaging-1.4.0.SP3 on a test server
and a qa server. Both servers run the same version of Linux (Red Hat
Enterprise Linux WS release 3 (Taroon Update 9)). Both are also running the
same version of Java (IBM J9SE VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 L
