Menu
▾
▴
Re: [Wrapper-user] Failed to connect to the Wrapper at port 0
|
From: Leif M. <lei...@ta...> - 2009-06-24 22:46:38
|
Marcelo, Another user reported this problem with version 3.3.0 last summer. We made some changes that were likely to affect this in 3.3.1. I never heard back from the user who reported the problem as to whether or not it was actually resolved however. Here is the issue: https://sourceforge.net/tracker/?func=detail&atid=425188&aid=1968781&group_id=39428 Could you please test this with 3.3.5 and let me know if it resolves the problem? It sounds like you are able to reproduce this. Cheers, Leif On Thu, Jun 25, 2009 at 2:29 AM, DATACOM - Marcelo<ma...@da...> wrote: > Hello, we are facing very often this kind of problem in a Windows server > but we saw this in a Solaris 64 server as well: > > STATUS | wrapper | 2009/06/24 08:23:52 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/24 08:23:52 | Java Service Wrapper Community > Edition 3.3.0 > STATUS | wrapper | 2009/06/24 08:23:52 | Copyright (C) 1999-2008 > Tanuki Software, Inc. All Rights Reserved. > STATUS | wrapper | 2009/06/24 08:23:52 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2009/06/24 08:23:52 | > STATUS | wrapper | 2009/06/24 08:23:52 | Launching a JVM... > INFO | jvm 1 | 2009/06/24 08:23:53 | WrapperManager: Initializing... > INFO | jvm 1 | 2009/06/24 08:23:55 | **** Build release: > 20090623173109 **** > ERROR | wrapper | 2009/06/24 08:35:20 | JVM appears hung: Timed out > waiting for signal from JVM. > STATUS | wrapper | 2009/06/24 08:35:25 | Launching a JVM... > INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager: Initializing... > INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager Error: Failed > to connect to the Wrapper at port 0. Cause: java.net.ConnectException: > connect: Address is invalid on local machine, or port is not valid on > remote machine > INFO | jvm 2 | 2009/06/24 08:35:26 | WrapperManager Error: Exiting > JVM... > ERROR | wrapper | 2009/06/24 08:35:26 | JVM exited while loading the > application. > STATUS | wrapper | 2009/06/24 08:35:32 | Launching a JVM... > INFO | jvm 3 | 2009/06/24 08:35:32 | WrapperManager: Initializing... > INFO | jvm 3 | 2009/06/24 08:35:58 | **** Build release: > 20090623173109 **** > INFO | wrapper | 2009/06/24 13:37:53 | User logged out. Ignored. > INFO | wrapper | 2009/06/24 13:37:53 | User logged out. Ignored. > STATUS | wrapper | 2009/06/24 13:48:17 | <-- Wrapper Stopped > STATUS | wrapper | 2009/06/24 13:59:23 | --> Wrapper Started as Service > STATUS | wrapper | 2009/06/24 13:59:23 | Java Service Wrapper Community > Edition 3.3.0 > STATUS | wrapper | 2009/06/24 13:59:23 | Copyright (C) 1999-2008 > Tanuki Software, Inc. All Rights Reserved. > STATUS | wrapper | 2009/06/24 13:59:23 | > http://wrapper.tanukisoftware.org > STATUS | wrapper | 2009/06/24 13:59:23 | > STATUS | wrapper | 2009/06/24 13:59:24 | Launching a JVM... > INFO | jvm 1 | 2009/06/24 13:59:24 | WrapperManager: Initializing... > INFO | jvm 1 | 2009/06/24 13:59:25 | **** Build release: > 20090623173109 **** > > I saw in the mailing list this problem only once and this issue died. Is > there a common fix for this ? > > Thanks in advance, > > -- > MARCELO Ribeiro |
