IP number change prevents JBoss from running correctly

[lightfinger]

We are in the process of moving a number of machines into a new DMZ. This change requires us to change the IP number of the machines in question to allow the correct broadcast/propagation.

Last weekend, I attempted to do this with the production server that houses JBoss. When I changed the IP number, and changed the cables out, JBoss would not run on the machine any longer.

After clearing the work and temp directories, and trying multiple times, our users were getting ancy, so I plugged in the old cable and put in the old IP...and JBoss came up fine.

Any suggestions as to why JBoss would be doing this? We're running 4.04GA on a single deployment. The server itself is running Fedora Core 5 (upgrade to 7 will take place after the server move). We only have about 7 apps running on the server at this time, though we have major ones in development.

Thanks!

David West
Programmer/Analyst
Douglas-Omaha Technology Commission
[e-mail]

[peterj]

Are you binding the app server to a specific address (i.e., staring it using the -b option?)

[lightfinger]

Not that I can determine. I'm running with the following:

JAVA_OPTS="-server -Xms256m -Xmx1536m -XX:MaxPermSize=256m -Dsun.rmi.dgc.clie
nt.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
fi

[peterj]

Next question - what do you mean by "JBoss would not run on the machine any longer"?

[lightfinger]

Jboss would start on the server reboot, but would soon shut down with no logs or other notice as to why it suddenly stopped. A 'ps aux' would show the java was no longer processing.

The curious part is by changing IPs back, it has remained up and stable. That's why I am associating it with the IP change causing the issue.

[peterj]

I suggest you try starting it from the command line - then you can see the console output and any errors that might have appeared. I am rather surprised, though, that neither the server/xxx/log/boot.log or server.log contains any error indication.