Re: [Wrapper-user] Wrapper not recognising socket exception

[Leif M. <le...@ta...>]

Richard,
Sorry for the delay.  Glad you have gotten it working.

Please let us know if you have any other issues.

Cheers,
Leif

On Mon, Mar 9, 2009 at 6:59 PM, Richard Wilson
<ri...@mi...> wrote:
> Apologies, I can see now this is covered under bug ref 1594073 and fixed in 3.3.0.
>
> --- ri...@mi... wrote:
>
> From: "Richard Wilson" <ri...@mi...>
> To: <wra...@li...>
> Subject: Wrapper not recognising socket exception
> Date: Wed, 4 Mar 2009 06:58:47 -0800
>
> Hi,
>
> I have a problem where the wrapper is failing to start correctly because it cannot open the JVM communications socket on port 31000. With debug on, the log contains:
>
>>>>
>
> Launching a JVM...
> Starting the Mule Server...
> WrapperManager class initialized by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@1855af5
> Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
>  Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
>
> Wrapper Manager: JVM #1
> Running a 32-bit JVM.
> Wrapper Manager: Registering shutdown hook
> Wrapper Manager: Using wrapper
> Load native library.  One or more attempts may fail if platform specific libraries do not exist.
> Loaded native library: libwrapper-solaris-sparc-32.so
> Calling native initialization method.
> Inside native WrapperManager initialization method
> Java Version   : 1.5.0_06-b05 Java HotSpot(TM) Server VM
> Java VM Vendor : Sun Microsystems Inc.
>
> Control event monitor thread started.
> Startup runner thread started.
> WrapperManager.start(org.mule.module.boot.MuleServerWrapper@1256ea2, args["console0"]) called by thread: main
> Communications runner thread started.
> Open socket to wrapper...Wrapper-Connection
> java.net.SocketException: Address already in use
> Open socket to wrapper...Wrapper-Connection
> java.net.SocketException: Address already in use
> Open socket to wrapper...Wrapper-Connection
> java.net.SocketException: Address already in use
> …
>
> <<<
>
> I guess it is trying to open a socket on port 31000 but failing. However, it is not recognising the exception correctly in order to try the next available port number. Instead, I believe it is trying the same port number indefinitely.
>
> The problem seems to be the logic inside WrapperManager.openSocket(), which looks for either a BindException or an exception with "errno: 48" in the message. In this case there is neither.
>
> I am running the wrapper version 3.2.3 as part of a Mule 2.1.2 installation on a Fujitsu/Sparc/Solaris server.
> Uname –a returns: SunOS xxxxxxx 5.10 Generic_125100-10 sun4us sparc FJSV,GPUZC-M
>
> regards
> Richard.