[nalbion]

Until I upgraded from JBoss 4.0.5 to 4.2.0 and MyEclipse 5.1 to 5.5 I was able to deploy my web app to local host, and then browse to it at 127.0.0.1:8080 or 192.168.1.1:8080 or myRealAddress:8080. Now, all that works is 127.0.0.1:8080.

I’m not sure if it’s a JBoss problem or a myEclipse problem, but surely it should be something I can set using myEclipse?

[Riyad Kalla]

This is likely a JBoss setting somewhere. MYEclipse doesn’t set any of this information, it simply runs the main class of the app server and connects the debugger to it.

[nalbion]

I’ve discovered that (probably right from the start) the problem has been with my workspace
(C:\Documents and Settings\nick\workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings).

If I open a new workspace, I’m able to set the Application Server properties using the MyEclipse GUI, but if I open the old workspace the Application Servers menu won’t open. To acheive my objective, I could edit the file “com.genuitec.eclipse.easie.jboss4.prefs” and add/set the line “SERVER_STARTUP_ARG=-c default -b 0.0.0.0”.

I haven’t had a chance to test this yet, but I’m pretty confident I’m on the right track. Obviously, I’d much prefer to be able to use the MyEclipse GUI to make these changes rather than go hunting for the text files.

[Steve Prior]

I was just chasing this last night.

The behavior of JBoss changed with version 4.2.0 to only accept connections from localhost by default for security reasons. The -b option overrides this and allows you to specify the bind to address. So the correct way to work around this is to go to the JBoss config screen in MyEclipse and set the optional program arguments to -b <address>. Why you can’t get to that option with your old workspace would be a MyEclipse issue.

[Riyad Kalla]

sprior,
Thank you for the followup… I wasn’t even aware of this change in JBoss 4.2.0

[Author]

Posts