[Wrapper-user] Fwd: Issue with i2p-0.8.2 which uses the taniuk 3.1.1 embedded within during startup

[Wendell M. <mac...@gm...>]

After registering...

---------- Forwarded message ----------
From: Wendell MacKenzie <mac...@gm...>
Date: Sat, Jan 8, 2011 at 4:30 PM
Subject: Issue with i2p-0.8.2 which uses the taniuk 3.1.1 embedded within
during startup
To: wra...@li...


HI:

   I've recently upgraded my OpenSUSE 11.3 laptop to version 2.6.37-31.1
which is the most recent stable version of their kernel.

   I use the i2p software router previously with no problems.  Since the
kernel change, the i2p router will not startup properly.
It appears to launch the i2p jvm, then attempts to ping it (regardless if I
set the wrapper.ping.timeout or interval to 0) and
ultimately kills it and restarts it (5 times).  It works normal under prior
kernel versions.

   As the attached debug.log shows, its exhibiting the same behaviour with
the newer version of the wrapper (3.5.7).  I can start
the i2p router without the wrapper using the provided runplain.sh, however,
it doesn't provide any of the failover capability.
One not of difference under the 2.6.37 startup is that the launch of the i2p
router using runplain.sh is that is slower to start up
which may account for why the wrapper is having problems pinging it.

   If there is something I can set/try to resolve it I'd sure like to stick
with 2.6.37 as its a much better desktop kernel.

thx.
W. MacKenzie




-- 
this message was NOT sent from an iPad