Re: [Wrapper-user] JVM exited unexpectedly

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

Paul Casanova wrote:

>Thank you so much for your swift response - much appreciated.  I have been
>on my clients asking them to give you a donation for your excellent work -
>I trust that they have responded.  Unfortunately due to privacy I can't
>identify my client.
>  
>
Thanks I am glad you appreciate what goes into developing and supporting 
the Wrapper.
So far, there have not been any contributors who did not wish to have 
their names listed
on the sponsors page.  So you can take a look yourself.
http://wrapper.tanukisoftware.org/doc/english/sponsors.html

I actually get about an order of magnitude more emails announcing 
upcoming donations than
actual donations.  The complements are appreciated.  But I wouldn't mind 
retiring from the
day job either :-)  I do consulting work myself and usually find that 
users have a hard time
understanding what the Wrapper is or does for them, let alone trying to 
convince them to
make donations.   If you wish to contribute, which I hope you do.  Then 
it is usually
necessary to include it as a software cost when billing your customers, 
or at least keep it
in mind when coming up with the total quote.  Depending on the donation 
size vs the
project size, it is usually not all that significant to the total cost 
of the project, however if
it is "significant" then I am sure I would be happy to hear about it. :-)

>Currently we are using wrapper version 3.03 - what is required to upgrade?
>Can we just replace the wrapper.dll, wrapper.jar and wrapper.exe files?
>  
>
Yes, to upgrade, copying those 3 files is all that is required.  Read 
over the release notes
to make sure there is nothing else you need to do.  The wrapper.conf 
file will work as is
but there are some additional properties that may let you do things that 
you could not do
before.   One example is removing the wrapper.port property.   The 
Wrapper will now
automatically allocate a port to use for its communications socket.  
Before you had to
manually choose non-conflicting ports if you wanted to run multiple 
copies of the
Wrapper without getting any warning messages.

If you are using the batch files that come with the Wrapper, you should 
also upgrade them
as well.

>Also - news just in: I've found a file "hs_err_pid1176.log" in the bin
>directory generated one second before the wrapper logged the unexpected
>exit.  Could this point to the problem?
>  
>
Great.  that shows you what is crashing in your application.  The next 
step is to go and
do a search of the Java bug database.

Doing a search of "NativeFontWrapper.drawStringIntDiscreteRaster" 
however, all I see are
a couple old bugs involving True Type fonts on Solaris systems.  You may 
want to compare
a few crash logs and make sure that the JVM is always crashing at the 
same point.   Then
submit a bug to Sun.

They usually take a while to get back to you.  Understandable with the 
number of bugs they
get.   The first thing they will ask you to do is try to duplicate it 
with the newest version of
the JVM.  The newest 1.3.1 JDK may be fine, but they may ask for 
1.4.2.   It looks like
you are using 1.3.1_09-b03, you might want to try 1.3.1_09 which appears 
to be the
newest right now.

Have you reproduced this on more than one machine?  I have seen problems 
where some
JVM files get corrupted after the Windows system crashes.  Not sure who 
to blame when
that happens.  (But blaming MS is more fun, besides they are the one 
who's OS crashes)
Long shot, but one possibility.   Uninstalling and then reinstalling the 
JDK fixes this when
it has happened (about 4 times so far)

>It's long, but the contents are below.  Sorry, I wasn't sure of the
>protocol for including output (attachment etc), so I hope I haven't
>offended anyone by sending a large email.
>  
>
That file is pretty small, so no problem.  Anything over 100k or so, I 
usually ask people to
send a message minus the file to the list, and then a mail with the 
attachment directly to me.

Cheers,
Leif