Can't remote to Jboss, -b 0.0.0.0 not working

[bombarta]

I just finished a JBoss installation today. Took it a step further and set it up as a windows service with Wrapper (fantastic tool). I was able to use localhost:8080 and 127.0.0.1:8080 on my host PC and it worked perfectly.

I tried on another PC on my network with the IP address of my host+port number and its giving me a "Internet Explorer cannot display the webpage"
error.

After reading up on security prevention in the installation and configuration guides, I came across the -b 0.0.0.0 parameter that you can add to the run.bat script. I've added it after org.jboss.Main in the executable line at the bottom of run.bat. I restarted my JBoss service and tried to remote again, and it gave the same message about not displaying the page.

What else do I need to do? On a similar J2EE with Glassfish, I can remote just fine.

[peterj]

Exactly what tool are you using to run JBossAS as a service (I do not recognize "Wrapper" as a specific tool - almost all of them have the words Wrapper or Service in them). Each tool uses different mechanisms to configure the service and how it launches the app server so how to apply the -b option depends on the tool.

[bombarta]

The tool is irrelevent, but it's called "Java Service Wrapper". Rather than running JBoss from a CMD window, it runs it as a windows or linux service depending on your platform. It's irrelevent simply because I've tried -b 0.0.0.0 from the cmd prompt as well as trying to include it in the executable line of run.bat .

run.bat -b 0.0.0.0

Now this is JBoss 4.2.3, and from my understanding, as of 4.2 the security tightened up and now locks JBoss to localhost only. Well, this does me no good. I've read that using SSH/putty you can tunnel a port remotely, however the -b 0.0.0.0 seemed simple enough. My concerns for security are minimal. The server and PC's that need to remote are on a closed network, so I'm not concerned with outside sources attempting to use the admin console, etc.

So what other info can I provide to help with my problem? I'm pretty new to JBoss, however I've been running Glassfish for some time now and do have a little knowledge about J2EE app servers.

[jaikiran]

"Bombarta" wrote:
The tool is irrelevent, but it's called "Java Service Wrapper". Rather than running JBoss from a CMD window, it runs it as a windows or linux service depending on your platform. It's irrelevent simply because I've tried -b 0.0.0.0 from the cmd prompt as well as trying to include it in the executable line of run.bat .

It is relevant, because as Peter said, each service wrapper has its own way of accepting/passing the parameters for launching the app server.

You can find more information about using Java Service Wrapper here http://wiki.jboss.org/wiki/RunJBossAsAServiceOnWindows. That wiki has an example of configuring the parameters through wrapper.conf file, which even includes the -b option.

"Bombarta" wrote:

So what other info can I provide to help with my problem?

Try out the instructions mentioned in the wiki. If it still does not work then let us know and also post the configuration file of your service wrapper.

[peterj]

Bombarta wrote:
It's irrelevent simply because I've tried -b 0.0.0.0 from the cmd prompt as well as trying to include it in the executable line of run.bat .

run.bat -b 0.0.0.0

You never come out and say it, but this statement implies that even when you use -b 0.0.0.0 to start the app server from the command line that you still cannot access the app server remotely. Is that really the case? If so, when you run from the command line, look for a a line that looks like:

2008-08-21 07:50:43,343 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080

It will be a few lines before the "Started in xxx seconds" line. The IP address mentioned here is what the port was bound to.

[bombarta]

It is relevant, because as Peter said, each service wrapper has its own way of accepting/passing the parameters for launching the app server.

I did mention that I had tried starting the server without running it through a windows service using the wrapper, which is why its irrelevent. It works no differently between manually running the CMD prompt or running the wrapper.

Thank you for the suggestions though. I will look for that line today when I get back to working with it.