Hi,
I suppose you are using a 3.0 snapshot or milestone.
Whatever the version you are using, the wrapper is the same and i have no idea what the cause of the error can be. In a future, we will implement the wrapper with another maven plugin (but there's no guarantee the problem will disappear). You could also envisage to use linux on production env if this suits your policies.
Tks,
- Eric

On 29/03/2011 03:16, USHAKOV, Sergey wrote:
Hi All,

I have come across occasional cases when James fails to start as Windows
service just for no visible reason.
The log complains as being unable to send the start command to the JVM...
A subsequent attempt to start the service typically succeeds.

This does not bother me too much now when just getting things set up, but
may be an issue in production mode...

Any ideas?

Regards,
Sergey


E:\>java -version
java version "1.6.0_23"
Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
Java HotSpot(TM) Client VM (build 19.0-b09, mixed mode, sharing)

...
STATUS | wrapper  | 2011/03/29 03:39:22 | <-- Wrapper Stopped
STATUS | wrapper  | 2011/03/29 03:49:18 | --> Wrapper Started as Service
STATUS | wrapper  | 2011/03/29 03:49:18 | Launching a JVM...
INFO   | jvm 1    | 2011/03/29 03:49:19 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2011/03/29 03:49:19 |   Copyright 1999-2006 Tanuki
Software, Inc.  All Rights Reserved.
INFO   | jvm 1    | 2011/03/29 03:49:19 |
ERROR | wrapper | 2011/03/29 03:49:19 | Unable to send the start command
to the JVM.
ERROR  | wrapper  | 2011/03/29 03:49:19 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2011/03/29 03:49:24 | Launching a JVM...
INFO   | jvm 2    | 2011/03/29 03:49:25 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO   | jvm 2    | 2011/03/29 03:49:25 |   Copyright 1999-2006 Tanuki
Software, Inc.  All Rights Reserved.
INFO   | jvm 2    | 2011/03/29 03:49:25 |
ERROR | wrapper | 2011/03/29 03:49:25 | Unable to send the start command
to the JVM.
ERROR  | wrapper  | 2011/03/29 03:49:25 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2011/03/29 03:49:30 | Launching a JVM...
INFO   | jvm 3    | 2011/03/29 03:49:31 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO   | jvm 3    | 2011/03/29 03:49:31 |   Copyright 1999-2006 Tanuki
Software, Inc.  All Rights Reserved.
INFO   | jvm 3    | 2011/03/29 03:49:31 |
ERROR | wrapper | 2011/03/29 03:49:31 | Unable to send the start command
to the JVM.
ERROR  | wrapper  | 2011/03/29 03:49:31 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2011/03/29 03:49:36 | Launching a JVM...
INFO   | jvm 4    | 2011/03/29 03:49:37 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO   | jvm 4    | 2011/03/29 03:49:37 |   Copyright 1999-2006 Tanuki
Software, Inc.  All Rights Reserved.
INFO   | jvm 4    | 2011/03/29 03:49:37 |
ERROR | wrapper | 2011/03/29 03:49:37 | Unable to send the start command
to the JVM.
ERROR  | wrapper  | 2011/03/29 03:49:37 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2011/03/29 03:49:42 | Launching a JVM...
INFO   | jvm 5    | 2011/03/29 03:49:43 | Wrapper (Version 3.2.3)
http://wrapper.tanukisoftware.org
INFO   | jvm 5    | 2011/03/29 03:49:43 |   Copyright 1999-2006 Tanuki
Software, Inc.  All Rights Reserved.
INFO   | jvm 5    | 2011/03/29 03:49:43 |
ERROR | wrapper | 2011/03/29 03:49:43 | Unable to send the start command
to the JVM.
ERROR  | wrapper  | 2011/03/29 03:49:43 | JVM did not exit on request,
terminated
FATAL | wrapper | 2011/03/29 03:49:44 | There were 5 failed launches in a
row, each lasting less than 300 seconds.  Giving up.
FATAL  | wrapper  | 2011/03/29 03:49:44 |   There may be a configuration
problem: please check the logs.
STATUS | wrapper  | 2011/03/29 03:49:44 | <-- Wrapper Stopped


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to