Unable to connect remotely

[markvl]

I am unable to connect to JBoss from a remote client. I am also unable to connect locally (on the server) using its external IP. The only way I can connect is using 127.0.0.1.

I have disabled the firewall and SELinux and rebooted the server.

JBoss version is 4.2.0GA. Server OS is CentOS5.

I have tested by running as root is case there was some permissions issue.

I have tested both ports 8080 and 80.

I am testing by telnet to the IP and port.

Interestingly, I started up Apache on port 80 and I can access it remotely, so this leads me to the conclusion that it is a JBoss issue and not a problem with the setup of the server.

Anyone got any ideas what the problem might be?

Thanks
Mark

[genman]

What's the value of jboss.bind.address (system property?)

[markvl]

Thankyou.

I had not set jboss.bind.address. It works now.

Strange though. I don't recall setting this before with earlier versions of JBoss.

For anyone else encountering this problem, read about the -b parameter on http://www.jboss.org/wiki/Wiki.jsp?page=JBossRunParameters

[peterj]

Did you read the readme.html file? The first bullet under section "Configuration Issues"?

(So far the forums have been averaging 2-3 queries a week on this exact same issue.)

[markvl]

Yes I read it, but obviously not carefuly enough.

[avihaimar]

Hey,

i have the same problem.
i cant connect to Jboss 4.2 from remote computer .

Can you please explain how you did it?


Thank you

[jaikiran]

Hmm.... this question seems to have created a record of sorts as far as the FAQs are concerned. Have a look at
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=111140 for the solution

[jaikiran]

There's even a FAQ about this at the wiki:

http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss42FAQ

Maybe someone will add this FAQ as a Sticky in this Installation, Configuration & Deployment forum (if that will help bring down the number of times this question is being asked)

[peterj]

Considering that this issue is addressed in a FAQ on the wiki, and is documented in the readme file, and there are dozens of individual posts on this topic in this and several of the other forums, I doubt very seriously that even a Sticky would help. That is why I don't answer the question any more, but rather refer to poster to the readme. At least I point them to the exact text, but a few more weeks of this I and won't even do that.

[avihaimar]

If you will try to google this problem you will not find a solution.

By the way can i expose my server to group of servers?

thank you

[markvl]

I had googled for it and searched the forums, but had not chosen the right search terms.

I think it would be good for such a major change to be highlighted in bold at the start of the readme.html.

[jaikiran]

"PeterJ" wrote:
Considering that this issue is addressed in a FAQ on the wiki, and is documented in the readme file, and there are dozens of individual posts on this topic in this and several of the other forums, I doubt very seriously that even a Sticky would help.

True, i have to agree with that.

[markvl]

I read the Sticky topic at the top of this forum before starting this topic.

A Sticky would definitely have helped me.

[brintoul]

I see no discussion of how to solve this in the case where JBoss is being set up to run as a service in Windows. What's the best way? Currently I've renamed "run.bat" to "runService.bat" and made a "run.bat" with contents simply being: "runService.bat -b 0.0.0.0". Is there a better way?

Thanks.

[peterj]

It is difficult to give directions on how to set this up for a Windows service without knowing which tool you are using the establish and run the service. I have worked with three such tools and each one works differently. Having said this, I know that I have helped various people set this up using JavaService. I don't recall if I helped anyone who uses Java Service Wrapper.

Based on the phrasing of your question, I assume that you are using JBoss Native. In this case, I recommend making copies of service.bat and editing them. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=118307. The instructions there are for running alternate configurations (the -c option), but you can just as easily append the -b option to the invoke of the run.bat.