Re: [Wrapper-user] Jar works with console, throws exceptions when launched via start?

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

Stas,
See my replies in line.

On Tue, Sep 16, 2008 at 10:29 PM, Stas Oskin <sta...@gm...> wrote:
> Well, I sorted it out - it was an Enter key handler which somehow interfered
> and caused a chain reaction.

The Wrapper should be able to handle input streams from within Java.
Could you describe a little more what you are doing?  Maybe with a
code fragment?  I would like to try it out.

> I noticed a very serious issue in the wrapper - sometimes it exits/crashes
> together with the Java app, and hence can't restart it.

That would not be good.  What version of the Wrapper are you using and
what platform are you running on?  There are no crashes that I am
aware of in the newest version, but some older versions have had a
couple issues which could lead to this.

If you are able to reproduce this, could you please set the following
properties and then send me the resulting wrapper.log file up through
the crash.  It will be quite large, so please send it to me directly
rather than on list.
---
wrapper.debug=true
wrapper.state_output=true
---
That should show me exactly where the crash is happening.

> Any idea what's going on, and how the wrapper can be reliably used?

We'll get this figured out for you.

Cheers,
Leif

> 2008/9/16 Leif Mortenson <le...@ta...>
>>
>> Stas,
>> What platform and version are you running on?  I see a reference to a
>> UNIXProcess so I assume it is not Windows.
>>
>> On UNIX versions, there is really no difference in the way the Wrapper
>> launches the JVM between running in Console or Started as a daemon
>> process.  There could be differences in the environment variables
>> available to the Wrapper when it launches however.  For example, the
>> PATH, or LD_LIBRARY_PATH.   There could also be file permission issues
>> if they are not being run as the same user.
>>
>> Either way however, the Wrapper and JVM appear to be working.   Most
>> likely something in the application is failing for one of the above
>> reasons which is leading to it being in an unstable state, thus
>> causing the exceptions.
>>
>> As these appear to be JDBC driver related, I would guess that maybe a
>> native component of your driver is failing to load.  Does MySQL have a
>> native driver?  I have used the pure Java driver.   I tried Googling
>> and found your question but not much else.
>>
>> I would be happy to help out with more information.
>>
>> Cheers,
>> Leif
>>
>> On Sat, Sep 13, 2008 at 7:11 PM, Stas Oskin <sta...@gm...> wrote:
>> > Hi.
>> >
>> > I'm trying to get my app packaged in jar to work with the Java Wrapper,
>> > and
>> > have set up all correctly.When I launch the service in console mode, all
>> > works correctly.
>> >
>> > When I do the same with service mode - the service shuts down after a
>> > few
>> > seconds, and has the following errors in the log:
>> >
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 | java.sql.SQLException:
>> > java.lang.ThreadDeath
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > com.mysql.jdbc.Util.handleNewInstance(Util.java:430)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > com.mysql.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:302)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> >
>> > com.mysql.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:282)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > java.sql.DriverManager.getConnection(DriverManager.java:582)
>> > INFO   | jvm 1    | 2008/09/13 00:05:01 |       at
>> > java.sql.DriverManager.getConnection(DriverManager.java:185)
>> >
>> > (Below it my own functions exceptions - but this is a standard JDBC
>> > connector for MySQL).
>> >
>> > And this comes next (where I have function launching external process
>> > via
>> > exec function):
>> >
>> > INFO   | jvm 1    | 2008/09/13 00:05:03 | java.lang.InterruptedException
>> > INFO   | jvm 1    | 2008/09/13 00:05:03 |       at
>> > java.lang.Object.wait(Native Method)
>> > INFO   | jvm 1    | 2008/09/13 00:05:03 |       at
>> > java.lang.Object.wait(Object.java:485)
>> > INFO   | jvm 1    | 2008/09/13 00:05:03 |       at
>> > java.lang.UNIXProcess.waitFor(UNIXProcess.java:165)
>> >
>> >
>> > Any idea what different between the console and start modes, and why the
>> > basic functionality doesn't work in this mode?
>> >
>> > Regards.