"rdaly" wrote :
| In searching through the Jboss-Messaging code, I found the code that parses
the remoting-*-service.xml files. The class is
org.jboss.remoting.transport.Connector. There is a method inside that class
that parses the xml:
|
That's jboss remoting code (not jboss messaging
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?
Never mind, I was looking at the wrong log file, I found the entry and the
code. But unless someone else has this already figured out and jumps in with
the solution, it looks like the only thing left to do is debug the code to find
out what method is returning 127.0.0.1 instead of the host name.
I cannot find the log entry you posted in any of my logs. Could you post the
corresponding entry from the server.log file - that will have the full class
name (actually, log category name, but they are usually the same). This might
help pinpoint the code that has the problem (or at least let us
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
Actually, -b and -Djboss.bind.address are not exatcly the same. While they both
set jboss.bund.address, the -b option also sets java.rmi.server.hostname (under
certain conditions, which is why I had you set it sepcifically), and also sets
some jgroup-related system properties.
Try this. Go into
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
Hello,
just for sure, give it a try without using -Djboss.bind.adress... Just use -b
0.0.0.0
Also show me output of hostname command please.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154599#4154599
Reply to the post :
http://www.jboss.com/index.html?m
The hosts files look ok to me. What response do you get if you ping
qa.server.com and test.server.com remotely?
Try adding -Djava.rmi.server.hostname=qa.server.com to the run script and see
if that helps.
By the way, the -b and -Djboss.bind.address options do the same thing - they
both set the
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
Oh, and one question. When you start the server, a few lines before the
"Started in xxx seconds" log message, there will be another log message that
looks like this:
10:40:09,859 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
http-0.0.0.0-8080
Could you post that for both of your servers?
What are the contents or the /etc/hosts files?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154403#4154403
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4154403
___
jboss-us
13 matches
Mail list logo
