I don't know why a IP address change should change the jboss behaviour
Do you start the JBoss with -b ip-address => than it is clear that the JBoss can not start , change the start command with the correct IP.
If you have still problems attech the boot.log file.
Thanks for your quick advise!
As I recall, we didn't start JBoss with any ip-address. Let me locate the start parameter we use in the Windows service, and also attach the boot.log
My Jboss windows service is started using the following: "C:\Program Files\jboss-5.1.0.GA\bin\jbosssvc.exe" -r JBAS50SVC
And here's the extract from the BOOT.LOG on the exeception part (sorry, the whole BOOT.log is over 2MB)
Some more information to share, I just performed a keyword search for 'ERROR' in the BOOT.LOG, and located the errors below:
Appreciate if any one has any further clue?
09:48:32,682 ERROR [Http11Protocol] Error initializing endpoint
java.net.BindException: Address already in use: JVM_Bind /0.0.0.0:80
could you please edit your posts and remove the logfile it will make the thread unreadable.
Attach it as file in this case a 2MB boot.log is no problem if you compress it.
The file dialog is visible if you edit the comment.
By default the JBoss 5.1 bind against 127.0.0.1
What if you start the JBoss from cmd for testing?
As you mentioned the IP address of the system was changed, so I think there is a mismatch of IP address and bind address.
Sorry, I overlooked the attachment function.
GOOD NEWS! Problem solved.
It turns out to be the MS SQL Reporting Services which was recently installed occupied the port 80. After I stop the SQL reporting servivces, and start JBOSS again, everything resumes.
That good for you
But that look like that there are additional changes you not know (or mentionend) in the same time as the IP address changed.
Yes, it didn't come to my mind that this SQL reporting service installed by another team member few days back. And I was focused on the latest change on the IP.
Anyway, good to know this platform for JBoss knowledge sharing.