-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Milestone
Description
Hey guys,
Not sure if this is caused by our software or the wrapper. We experience that when we close the java services with the wrapper, that occasionally the java instance isn't killed properly. Then, when we start up the service again, the error message "java.net.BindException: Address already in use" pops up. We know that this means that there is still a java instance running at the port, and we know how to kill it manually. What we would like to know if it is possible to prevent this from happening at all. Why is this happening? Could it be caused by the wrapper?
Help would be really appreciated!
Best regards,
Niek
Metadata
Metadata
Assignees
Labels
No labels