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

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

Wendell,
At the point that things are getting stuck, the Java side of the
Wrapper is attempting to open a socket across the loopback device to
the Wrapper.   It appears to be freezing at this point.  There are no
errors shown.

I am not familiar with the i2p tool.  Is it possible that it is
affecting this backend socket?

Also, I don't think it is related, but please make sure that the
"wrapper", "libwrapper.so", and "wrapper.jar" files are all from the
same version of the Wrapper.  Operation when the versions do not match
is undefined.

---
2011/01/08 15:57:00 | WrapperManager: WARNING - The Wrapper jar file
currently in use is version "3.5.7"
2011/01/08 15:57:00 | WrapperManager:           while the version of
the Wrapper which launched this JVM is
2011/01/08 15:57:00 | WrapperManager:           "3.1.1".
2011/01/08 15:57:00 | WrapperManager:           The Wrapper may appear
to work correctly but some features may
2011/01/08 15:57:00 | WrapperManager:           not function
correctly.  This configuration has not been tested
2011/01/08 15:57:00 | WrapperManager:           and is not supported.
---

Can you provide any more information about the i2p tool?

Cheers,
Leif

On Sun, Jan 9, 2011 at 5:33 AM, Wendell MacKenzie <mac...@gm...> wrote:
> 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