#97 NT Service fails to grab a port

[svemt]

We use three java programs, each having it's own
wrapper. Usually this works fine on both Windows and
Linux, but at least two times we have seen problems on
Windows 2003 where an explicit setting of wrapper.port
solved the probIem.

The scenario is:
-The first service grabs port 32000 and starts nicely
-The second service tries to grab port 32001 but fails
-The problem was solved by explicitly setting
wrapper.port=32001

In one case the computer owner claims that it worked
without explicitly setting the wrapper.port, but stopped
working after installing the following Microsoft patches:
896727, 899591, 899588, 899587 and 893756
(But he has installed the patches on another computer
without problems, so...?)

Here is a short log of the problem, a debug log is
attached:
Error message in logs :
INFO | jvm 5 | 2005/08/15 08:28:47 | at
org.tanukisoftware.wrapper.WrapperManager.run
(WrapperManager.java:2693)
INFO | jvm 5 | 2005/08/15 08:28:47 | at
java.lang.Thread.run(Thread.java:534)
ERROR | wrapper | 2005/08/15 08:28:48 | Startup failed:
Timed out waiting for a signal from the JVM.
ERROR | wrapper | 2005/08/15 08:28:48 | JVM did not
exit on request, terminated
FATAL | wrapper | 2005/08/15 08:28:49 | There were 5
failed launches in a row, each lasting less than 300
seconds. Giving up.
FATAL | wrapper | 2005/08/15 08:28:49 | There may be
a configuration problem: please check the logs.
STATUS | wrapper | 2005/08/15 08:28:49 | <-- Wrapper
Stopped

[svemt]

Debug log when the problem occurs