-
1. Re: Configuring the Jboss server to shutdown on Port collisiion
ptyagi_redhat.com Jun 7, 2017 1:04 PM (in response to sameerp)This is "java.net.BindException: Address already in use"; you should fix this issue and check what other process is using this port. This error typically occurs if port is already in use by another process or another jboss instance or service running on the same machine.
-
2. Re: Configuring the Jboss server to shutdown on Port collisiion
sameerp Jun 8, 2017 6:30 AM (in response to ptyagi_redhat.com)Hi Priyanka,
Thanks for your answer. Actually I was looking for some kind of configuration in Jboss itself to stop the server than manually going and fixing the issue. Currently, the Jboss doesn't stop from going ahead , but rather goes ahead with some wrong configurations due to the unavailability of the port.
I hope I was able to convey what I exactly intended to say.
Sameer.
-
3. Re: Configuring the Jboss server to shutdown on Port collisiion
sshashan Oct 24, 2017 2:37 AM (in response to sameerp)Hello Sameer,
There is no such in built feature.
Possibly you can write a shell script to check for the ports status and then internally call the Jboss startup script in it.
Thanks,
Sujay Shashank
-
4. Re: Configuring the Jboss server to shutdown on Port collisiion
sameerp Oct 24, 2017 6:39 AM (in response to sshashan)Thanks Sujay, this would work I feel. Thanks for your answer.