Re: [Wrapper-user] Re: Unable to bind port ?

[Grant \(ProtectionNET\) <gr...@pr...>]

Thanks - that was it... not having the local (lo) interface up and plumbe=
d
was the reason.

I'm not happy about having to have a port open (even on a local interface=
) -
would it be much work to change the code (both Linux and Java) to watch a
file rather than a TCP port ? I'm thinking of making changes to Wrapper t=
o
support such a mode so that it doesn't need networking started before it =
can
run Java apps.

Basically I would get the Java Wrapper service manager to write a specifi=
ed
tmp file to a location. The Wrapper native code would then look for the
presense of the file and then delete it. Then Java Wrapper service would
then immediately re-create the file again. If the Java runtime crashes, t=
hen
the Wrapper native code would launch the JVM again.

Would this work ? Any other things I need to consider ?

Grant

----- Original Message -----=20
From: "EXT-Smith, Eric M" <eri...@bo...>
To: <wra...@li...>
Sent: Friday, December 05, 2003 1:09 AM
Subject: [Wrapper-user] Re: Unable to bind port ?


> (Sorry if this is sent incorrectly.  I haven't quite got the hand of
Outlook)
>
> I am using the wrapper on 4 separate *-nix versions (HP-UX, Red Hat,
Mandrake, Debian) and 3 separate Windows versions (NT,2K,XP).  Barring so=
me
minor issues on the HP-UX with library locations and OS versions, and som=
e
issues with environment variable loading on the Windows Boxes (download
latest code from cvs), this is the only other problem I have experienced.
>
> I ran into this problem the first time I tried launching some processes
under Red Hat Linux.
>
> When I ran some test code using Red Hat Linux (7.3, 8.0) and the Sun JD=
K
(1.4.0 & 1.4.1)  I experienced problems getting ServerSocket to bind
properly.  Since Linux has by default the lo adapter as well as your norm=
al
network adapter, the bind process was getting confused about which IP
address to use (127.0.0.1 or x.x.x.x).  I discovered this when I turned o=
ff
lo (ifdown lo) and tried running my test code again and everything
succeeded.
>
> I corrected the problem by updating my Linux system to include all
patches, and downloading the latest 1.4.1 jdk (1.4.1_05).
>
> *** NOTE ***
> I have only experienced this problem on my Red Hat Linux systems.
Mandrake and Debian Linux behaved as I expected.
>
> Eric
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM=
's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admi=
n.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=CCk
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user