wrapper-user — User issues for Wrapper. (Support questions, etc.)

Re: [Wrapper-user] JVM appears to be hung message.

[Tasso A. <ta...@rb...>]

It could be the swap. I doubt it's the wrapper. I purposely set the memory to verry low to test for leaks. Als I was running the Netbeans profile when this happened, when I removed the profiler the app ran for 10 hours no problem while stressing it...

-----Original Message-----
From: Leif Mortenson [mailto:lei...@ta...] 
Sent: Friday, August 06, 2010 12:39 AM
To: wra...@li...
Subject: Re: [Wrapper-user] JVM appears to be hung message.

Tasso,
1) The first warning you get on startup is because you are running a
64-bit JVM with a 32-bit version of the Wrapper.  Please download a
64-bit version and request a trial license to run your tests:
http://wrapper.tanukisoftware.com/doc/english/requestTrial.jsp

---
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: WARNING -
Unable to load the Wrapper's native library 'wrapper.dll'.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
The file is located on the path at the following location but
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
could not be loaded:
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
C:\...\..\lib\wrapper.dll
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
Please verify that the file is readable by the current user
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
and that the file has not been corrupted in any way.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
One common cause of this problem is running a 32-bit version
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           of
the Wrapper with a 64-bit version of Java, or vica versa.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
This is a 64-bit JVM.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
Reported cause:
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
C:\...\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit
platform
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
System signals will not be handled correctly.
---

2) The second problem is showing that the Wrapper is thinking that the
JVM is frozen and killing it.  When it restarts, the system is still
so heavily loaded that it fails again.   In both cases, the JVM
process is completely unresponsive for an extended amount of time.
This is most likely because another process on your system is
consuming all available CPU, or worse, memory.

Java (Not related to the Wrapper) is notoriously bad about performance
in cases where its memory being swapped.   It is common for a JVM to
run at 1/00th or 1/1000th the speed if even a small amount of its
memory is being swapped.

---
ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2010/08/05 06:31:18 | Launching a JVM...
INFO   | jvm 2    | 2010/08/05 06:31:21 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)
ERROR  | wrapper  | 2010/08/05 06:31:50 | Startup failed: Timed out
waiting for a signal from the JVM.
ERROR  | wrapper  | 2010/08/05 06:31:50 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2010/08/05 06:31:55 | Launching a JVM...
---

The Wrapper does a lot to automatically extend timeouts when the
system is under heavy load, but that is not foolproof under extreme
conditions.  We have to reach a balance to make sure the Wrapper is
responsive to actual JVM failures.   It is possible to completely
control all of these timeouts however.
The first one is the ping timeout which is hit when the JVM fails to
respond to pings for longer than this timeout.
http://wrapper.tanukisoftware.com/doc/english/prop-ping-interval.html
You can control the startup timeout with this:
http://wrapper.tanukisoftware.com/doc/english/prop-startup-timeout.html
And shutdown timeouts with the following two properties:
http://wrapper.tanukisoftware.com/doc/english/prop-shutdown-timeout.html
http://wrapper.tanukisoftware.com/doc/english/prop-jvm-exit-timeout.html

If you are sure that there is not any memory swapping going on, please
let me know as I would like to look into it further in that case.  If
so, please send me a full wrapper.log file with wrapper.debug=true
set, along with your wrapper.conf, directly to me.

BE SURE TO READ the above pages before changing their values however.
If you set the ping timeout to one hour for example then the Wrapper
will NEVER kill the JVM for a whole hour if it does indeed freeze at
some point.

We have been working on ways of detecting when the system is
undergoing heavy swapping in a reliable way.  Hopefully that will be
in a near future version.

Please let me know if you have any questions about the above.
Cheers,
Leif

On Fri, Aug 6, 2010 at 2:48 AM, Tasso Angelidis <ta...@rb...> wrote:
> Sorry for the repost but message got blocked because it was too big.
>
>
>
> This is General question...
>
>
>
> I started stress testing my application and after a couple of hours I got...
>
>
>
> ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
> waiting for signal from JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
> terminated
>
>
>
> My profiler showed that I had reached the maximum heap. But the app should
> have recorded an OutOfMemory exception. I would have seen it in the
> wrapper.log right? Or is it because I used 32 bit wrapper with 64bit vm?
>
>
>
>
>
> STATUS | wrapper  | 2010/08/04 17:02:36 | --> Wrapper Started as Service
>
> STATUS | wrapper  | 2010/08/04 17:02:36 | Java Service Wrapper Community
> Edition 32-bit 3.3.9
>
> STATUS | wrapper  | 2010/08/04 17:02:36 |   Copyright (C) 1999-2009 Tanuki
> Software, Ltd.  All Rights Reserved.
>
> STATUS | wrapper  | 2010/08/04 17:02:36 |
> http://wrapper.tanukisoftware.org
>
> STATUS | wrapper  | 2010/08/04 17:02:36 |
>
> STATUS | wrapper  | 2010/08/04 17:02:36 | Launching a JVM...
>
> INFO   | jvm 1    | 2010/08/04 17:02:36 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> INFO   | jvm 1    | 2010/08/04 17:02:53 | Profiler Agent: Established
> connection with the tool
>
> INFO   | jvm 1    | 2010/08/04 17:02:54 | Profiler Agent: Standard session
>
> INFO   | jvm 1    | 2010/08/04 17:02:55 | WrapperManager: Initializing...
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: WARNING - Unable
> to load the Wrapper's native library 'wrapper.dll'.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           The file
> is located on the path at the following location but
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           could
> not be loaded:
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
> C:\...\..\lib\wrapper.dll
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           Please
> verify that the file is readable by the current user
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           and that
> the file has not been corrupted in any way.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           One
> common cause of this problem is running a 32-bit version
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           of the
> Wrapper with a 64-bit version of Java, or vica versa.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           This is
> a 64-bit JVM.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           Reported
> cause:
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
> C:\...\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           System
> signals will not be handled correctly.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Profiler engine warning: class
> sun.reflect.GeneratedConstructorAccessor1 that should be instrumented is not
> loaded by target VM
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Requested classloader:
> sun.reflect.DelegatingClassLoader@199155be, its class = class
> sun.reflect.DelegatingClassLoader, index = 7, hashcode = 428955070
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Profiler engine warning:
> target VM cannot load class to instrument
> sun.reflect.GeneratedConstructorAccessor1
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** probably it has been unloaded
> recently
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Acquirer_$$_javassist_0 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Currency_$$_javassist_1 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Merchant_$$_javassist_2 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Transaction_$$_javassist_3 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.DirectoryServer_$$_javassist_4 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.PayerAuthentication_$$_javassist_5 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.STNCryptURL_$$_javassist_6 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Scheme_$$_javassist_7 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Certificate_$$_javassist_8 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.VerifyEnrollment_$$_javassist_9 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.services.broker.dto.BrokerMessageLog_$$_javassist_10
> in ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.CertificateType_$$_javassist_11 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.MerchantAcquirer_$$_javassist_12 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Configuration_$$_javassist_13 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Profiler engine warning: class
> sun.reflect.GeneratedConstructorAccessor2 that should be instrumented is not
> loaded by target VM
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Requested classloader:
> sun.reflect.DelegatingClassLoader@6b055af0, its class = class
> sun.reflect.DelegatingClassLoader, index = 11, hashcode = 1795513072
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Profiler engine warning:
> target VM cannot load class to instrument
> sun.reflect.GeneratedConstructorAccessor2
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** probably it has been unloaded
> recently
>
> ... Message repeats for 298 times
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Profiler engine warning: class
> sun.reflect.GeneratedConstructorAccessor298 that should be instrumented is
> not loaded by target VM
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Requested classloader:
> sun.reflect.DelegatingClassLoader@57dd79fe, its class = class
> sun.reflect.DelegatingClassLoader, index = 1621, hashcode = 1474132478
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Profiler engine warning:
> target VM cannot load class to instrument
> sun.reflect.GeneratedConstructorAccessor298
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** probably it has been unloaded
> recently
>
> ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
> waiting for signal from JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:31:18 | Launching a JVM...
>
> INFO   | jvm 2    | 2010/08/05 06:31:21 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:31:50 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:31:50 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:31:55 | Launching a JVM...
>
> INFO   | jvm 3    | 2010/08/05 06:31:55 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:32:27 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:32:27 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:32:32 | Launching a JVM...
>
> INFO   | jvm 4    | 2010/08/05 06:32:32 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:33:04 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:33:04 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:33:09 | Launching a JVM...
>
> INFO   | jvm 5    | 2010/08/05 06:33:10 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:33:41 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:33:41 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:33:46 | Launching a JVM...
>
> INFO   | jvm 6    | 2010/08/05 06:33:46 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:34:18 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:34:18 | JVM did not exit on request,
> terminated
>
> FATAL  | wrapper  | 2010/08/05 06:34:19 | There were 5 failed launches in a
> row, each lasting less than 300 seconds.  Giving up.
>
> FATAL  | wrapper  | 2010/08/05 06:34:19 |   There may be a configuration
> problem: please check the logs.
>
> STATUS | wrapper  | 2010/08/05 06:34:19 | <-- Wrapper Stopped

-- 
Leif Mortenson
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel/Fax: +81-3-3878-3211
http://www.tanukisoftware.com
lei...@ta...

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] JVM appears to be hung message.

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

Tasso,
1) The first warning you get on startup is because you are running a
64-bit JVM with a 32-bit version of the Wrapper.  Please download a
64-bit version and request a trial license to run your tests:
http://wrapper.tanukisoftware.com/doc/english/requestTrial.jsp

---
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: WARNING -
Unable to load the Wrapper's native library 'wrapper.dll'.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
The file is located on the path at the following location but
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
could not be loaded:
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
C:\...\..\lib\wrapper.dll
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
Please verify that the file is readable by the current user
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
and that the file has not been corrupted in any way.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
One common cause of this problem is running a 32-bit version
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           of
the Wrapper with a 64-bit version of Java, or vica versa.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
This is a 64-bit JVM.
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
Reported cause:
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
C:\...\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit
platform
INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
System signals will not be handled correctly.
---

2) The second problem is showing that the Wrapper is thinking that the
JVM is frozen and killing it.  When it restarts, the system is still
so heavily loaded that it fails again.   In both cases, the JVM
process is completely unresponsive for an extended amount of time.
This is most likely because another process on your system is
consuming all available CPU, or worse, memory.

Java (Not related to the Wrapper) is notoriously bad about performance
in cases where its memory being swapped.   It is common for a JVM to
run at 1/00th or 1/1000th the speed if even a small amount of its
memory is being swapped.

---
ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2010/08/05 06:31:18 | Launching a JVM...
INFO   | jvm 2    | 2010/08/05 06:31:21 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)
ERROR  | wrapper  | 2010/08/05 06:31:50 | Startup failed: Timed out
waiting for a signal from the JVM.
ERROR  | wrapper  | 2010/08/05 06:31:50 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2010/08/05 06:31:55 | Launching a JVM...
---

The Wrapper does a lot to automatically extend timeouts when the
system is under heavy load, but that is not foolproof under extreme
conditions.  We have to reach a balance to make sure the Wrapper is
responsive to actual JVM failures.   It is possible to completely
control all of these timeouts however.
The first one is the ping timeout which is hit when the JVM fails to
respond to pings for longer than this timeout.
http://wrapper.tanukisoftware.com/doc/english/prop-ping-interval.html
You can control the startup timeout with this:
http://wrapper.tanukisoftware.com/doc/english/prop-startup-timeout.html
And shutdown timeouts with the following two properties:
http://wrapper.tanukisoftware.com/doc/english/prop-shutdown-timeout.html
http://wrapper.tanukisoftware.com/doc/english/prop-jvm-exit-timeout.html

If you are sure that there is not any memory swapping going on, please
let me know as I would like to look into it further in that case.  If
so, please send me a full wrapper.log file with wrapper.debug=true
set, along with your wrapper.conf, directly to me.

BE SURE TO READ the above pages before changing their values however.
If you set the ping timeout to one hour for example then the Wrapper
will NEVER kill the JVM for a whole hour if it does indeed freeze at
some point.

We have been working on ways of detecting when the system is
undergoing heavy swapping in a reliable way.  Hopefully that will be
in a near future version.

Please let me know if you have any questions about the above.
Cheers,
Leif

On Fri, Aug 6, 2010 at 2:48 AM, Tasso Angelidis <ta...@rb...> wrote:
> Sorry for the repost but message got blocked because it was too big.
>
>
>
> This is General question…
>
>
>
> I started stress testing my application and after a couple of hours I got…
>
>
>
> ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
> waiting for signal from JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
> terminated
>
>
>
> My profiler showed that I had reached the maximum heap. But the app should
> have recorded an OutOfMemory exception. I would have seen it in the
> wrapper.log right? Or is it because I used 32 bit wrapper with 64bit vm?
>
>
>
>
>
> STATUS | wrapper  | 2010/08/04 17:02:36 | --> Wrapper Started as Service
>
> STATUS | wrapper  | 2010/08/04 17:02:36 | Java Service Wrapper Community
> Edition 32-bit 3.3.9
>
> STATUS | wrapper  | 2010/08/04 17:02:36 |   Copyright (C) 1999-2009 Tanuki
> Software, Ltd.  All Rights Reserved.
>
> STATUS | wrapper  | 2010/08/04 17:02:36 |
> http://wrapper.tanukisoftware.org
>
> STATUS | wrapper  | 2010/08/04 17:02:36 |
>
> STATUS | wrapper  | 2010/08/04 17:02:36 | Launching a JVM...
>
> INFO   | jvm 1    | 2010/08/04 17:02:36 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> INFO   | jvm 1    | 2010/08/04 17:02:53 | Profiler Agent: Established
> connection with the tool
>
> INFO   | jvm 1    | 2010/08/04 17:02:54 | Profiler Agent: Standard session
>
> INFO   | jvm 1    | 2010/08/04 17:02:55 | WrapperManager: Initializing...
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: WARNING - Unable
> to load the Wrapper's native library 'wrapper.dll'.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           The file
> is located on the path at the following location but
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           could
> not be loaded:
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
> C:\...\..\lib\wrapper.dll
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           Please
> verify that the file is readable by the current user
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           and that
> the file has not been corrupted in any way.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           One
> common cause of this problem is running a 32-bit version
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           of the
> Wrapper with a 64-bit version of Java, or vica versa.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           This is
> a 64-bit JVM.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           Reported
> cause:
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
> C:\...\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           System
> signals will not be handled correctly.
>
> INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Profiler engine warning: class
> sun.reflect.GeneratedConstructorAccessor1 that should be instrumented is not
> loaded by target VM
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Requested classloader:
> sun.reflect.DelegatingClassLoader@199155be, its class = class
> sun.reflect.DelegatingClassLoader, index = 7, hashcode = 428955070
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Profiler engine warning:
> target VM cannot load class to instrument
> sun.reflect.GeneratedConstructorAccessor1
>
> INFO   | jvm 1    | 2010/08/04 17:03:01 | *** probably it has been unloaded
> recently
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Acquirer_$$_javassist_0 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Currency_$$_javassist_1 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Merchant_$$_javassist_2 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Transaction_$$_javassist_3 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.DirectoryServer_$$_javassist_4 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.PayerAuthentication_$$_javassist_5 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.STNCryptURL_$$_javassist_6 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Scheme_$$_javassist_7 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Certificate_$$_javassist_8 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.VerifyEnrollment_$$_javassist_9 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.services.broker.dto.BrokerMessageLog_$$_javassist_10
> in ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.CertificateType_$$_javassist_11 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.MerchantAcquirer_$$_javassist_12 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning: could
> not get .class file for a synthetic class
> com.rbs.threedsecure.mpi.domain.Configuration_$$_javassist_13 in
> ClassBytesLoader.getClassFileBytes
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Profiler engine warning: class
> sun.reflect.GeneratedConstructorAccessor2 that should be instrumented is not
> loaded by target VM
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Requested classloader:
> sun.reflect.DelegatingClassLoader@6b055af0, its class = class
> sun.reflect.DelegatingClassLoader, index = 11, hashcode = 1795513072
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Profiler engine warning:
> target VM cannot load class to instrument
> sun.reflect.GeneratedConstructorAccessor2
>
> INFO   | jvm 1    | 2010/08/04 17:03:08 | *** probably it has been unloaded
> recently
>
> … Message repeats for 298 times
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Profiler engine warning: class
> sun.reflect.GeneratedConstructorAccessor298 that should be instrumented is
> not loaded by target VM
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Requested classloader:
> sun.reflect.DelegatingClassLoader@57dd79fe, its class = class
> sun.reflect.DelegatingClassLoader, index = 1621, hashcode = 1474132478
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Profiler engine warning:
> target VM cannot load class to instrument
> sun.reflect.GeneratedConstructorAccessor298
>
> INFO   | jvm 1    | 2010/08/05 01:34:40 | *** probably it has been unloaded
> recently
>
> ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
> waiting for signal from JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:31:18 | Launching a JVM...
>
> INFO   | jvm 2    | 2010/08/05 06:31:21 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:31:50 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:31:50 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:31:55 | Launching a JVM...
>
> INFO   | jvm 3    | 2010/08/05 06:31:55 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:32:27 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:32:27 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:32:32 | Launching a JVM...
>
> INFO   | jvm 4    | 2010/08/05 06:32:32 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:33:04 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:33:04 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:33:09 | Launching a JVM...
>
> INFO   | jvm 5    | 2010/08/05 06:33:10 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:33:41 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:33:41 | JVM did not exit on request,
> terminated
>
> STATUS | wrapper  | 2010/08/05 06:33:46 | Launching a JVM...
>
> INFO   | jvm 6    | 2010/08/05 06:33:46 | Profiler Agent: Waiting for
> connection on port 5140 (Protocol version: 10)
>
> ERROR  | wrapper  | 2010/08/05 06:34:18 | Startup failed: Timed out waiting
> for a signal from the JVM.
>
> ERROR  | wrapper  | 2010/08/05 06:34:18 | JVM did not exit on request,
> terminated
>
> FATAL  | wrapper  | 2010/08/05 06:34:19 | There were 5 failed launches in a
> row, each lasting less than 300 seconds.  Giving up.
>
> FATAL  | wrapper  | 2010/08/05 06:34:19 |   There may be a configuration
> problem: please check the logs.
>
> STATUS | wrapper  | 2010/08/05 06:34:19 | <-- Wrapper Stopped

-- 
Leif Mortenson
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel/Fax: +81-3-3878-3211
http://www.tanukisoftware.com
lei...@ta...

[Wrapper-user] JVM appears to be hung message.

[Tasso A. <ta...@rb...>]

Sorry for the repost but message got blocked because it was too big.

 

This is General question...

 

I started stress testing my application and after a couple of hours I
got...

 

ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
waiting for signal from JVM.

ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
terminated

 

My profiler showed that I had reached the maximum heap. But the app
should have recorded an OutOfMemory exception. I would have seen it in
the wrapper.log right? Or is it because I used 32 bit wrapper with 64bit
vm?

 

 

STATUS | wrapper  | 2010/08/04 17:02:36 | --> Wrapper Started as Service

STATUS | wrapper  | 2010/08/04 17:02:36 | Java Service Wrapper Community
Edition 32-bit 3.3.9

STATUS | wrapper  | 2010/08/04 17:02:36 |   Copyright (C) 1999-2009
Tanuki Software, Ltd.  All Rights Reserved.

STATUS | wrapper  | 2010/08/04 17:02:36 |
http://wrapper.tanukisoftware.org

STATUS | wrapper  | 2010/08/04 17:02:36 | 

STATUS | wrapper  | 2010/08/04 17:02:36 | Launching a JVM...

INFO   | jvm 1    | 2010/08/04 17:02:36 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)

INFO   | jvm 1    | 2010/08/04 17:02:53 | Profiler Agent: Established
connection with the tool

INFO   | jvm 1    | 2010/08/04 17:02:54 | Profiler Agent: Standard
session

INFO   | jvm 1    | 2010/08/04 17:02:55 | WrapperManager:
Initializing...

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: 

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: WARNING -
Unable to load the Wrapper's native library 'wrapper.dll'.

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           The
file is located on the path at the following location but

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
could not be loaded:

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
C:\...\..\lib\wrapper.dll

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
Please verify that the file is readable by the current user

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           and
that the file has not been corrupted in any way.

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           One
common cause of this problem is running a 32-bit version

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           of
the Wrapper with a 64-bit version of Java, or vica versa.

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:           This
is a 64-bit JVM.

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
Reported cause:

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
C:\...\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit
platform

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager:
System signals will not be handled correctly.

INFO   | jvm 1    | 2010/08/04 17:02:56 | WrapperManager: 

INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Profiler engine warning:
class sun.reflect.GeneratedConstructorAccessor1 that should be
instrumented is not loaded by target VM

INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Requested classloader:
sun.reflect.DelegatingClassLoader@199155be, its class = class
sun.reflect.DelegatingClassLoader, index = 7, hashcode = 428955070

INFO   | jvm 1    | 2010/08/04 17:03:01 | *** Profiler engine warning:
target VM cannot load class to instrument
sun.reflect.GeneratedConstructorAccessor1

INFO   | jvm 1    | 2010/08/04 17:03:01 | *** probably it has been
unloaded recently

INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Acquirer_$$_javassist_0 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Currency_$$_javassist_1 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Merchant_$$_javassist_2 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Transaction_$$_javassist_3 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.DirectoryServer_$$_javassist_4 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:06 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.PayerAuthentication_$$_javassist_5 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.STNCryptURL_$$_javassist_6 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Scheme_$$_javassist_7 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Certificate_$$_javassist_8 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.VerifyEnrollment_$$_javassist_9 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.services.broker.dto.BrokerMessageLog_$$_javassi
st_10 in ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.CertificateType_$$_javassist_11 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.MerchantAcquirer_$$_javassist_12 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:07 | ***Profiler agent warning:
could not get .class file for a synthetic class
com.rbs.threedsecure.mpi.domain.Configuration_$$_javassist_13 in
ClassBytesLoader.getClassFileBytes

INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Profiler engine warning:
class sun.reflect.GeneratedConstructorAccessor2 that should be
instrumented is not loaded by target VM

INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Requested classloader:
sun.reflect.DelegatingClassLoader@6b055af0, its class = class
sun.reflect.DelegatingClassLoader, index = 11, hashcode = 1795513072

INFO   | jvm 1    | 2010/08/04 17:03:08 | *** Profiler engine warning:
target VM cannot load class to instrument
sun.reflect.GeneratedConstructorAccessor2

INFO   | jvm 1    | 2010/08/04 17:03:08 | *** probably it has been
unloaded recently

... Message repeats for 298 times

INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Profiler engine warning:
class sun.reflect.GeneratedConstructorAccessor298 that should be
instrumented is not loaded by target VM

INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Requested classloader:
sun.reflect.DelegatingClassLoader@57dd79fe, its class = class
sun.reflect.DelegatingClassLoader, index = 1621, hashcode = 1474132478

INFO   | jvm 1    | 2010/08/05 01:34:40 | *** Profiler engine warning:
target VM cannot load class to instrument
sun.reflect.GeneratedConstructorAccessor298

INFO   | jvm 1    | 2010/08/05 01:34:40 | *** probably it has been
unloaded recently

ERROR  | wrapper  | 2010/08/05 06:31:12 | JVM appears hung: Timed out
waiting for signal from JVM.

ERROR  | wrapper  | 2010/08/05 06:31:13 | JVM did not exit on request,
terminated

STATUS | wrapper  | 2010/08/05 06:31:18 | Launching a JVM...

INFO   | jvm 2    | 2010/08/05 06:31:21 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)

ERROR  | wrapper  | 2010/08/05 06:31:50 | Startup failed: Timed out
waiting for a signal from the JVM.

ERROR  | wrapper  | 2010/08/05 06:31:50 | JVM did not exit on request,
terminated

STATUS | wrapper  | 2010/08/05 06:31:55 | Launching a JVM...

INFO   | jvm 3    | 2010/08/05 06:31:55 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)

ERROR  | wrapper  | 2010/08/05 06:32:27 | Startup failed: Timed out
waiting for a signal from the JVM.

ERROR  | wrapper  | 2010/08/05 06:32:27 | JVM did not exit on request,
terminated

STATUS | wrapper  | 2010/08/05 06:32:32 | Launching a JVM...

INFO   | jvm 4    | 2010/08/05 06:32:32 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)

ERROR  | wrapper  | 2010/08/05 06:33:04 | Startup failed: Timed out
waiting for a signal from the JVM.

ERROR  | wrapper  | 2010/08/05 06:33:04 | JVM did not exit on request,
terminated

STATUS | wrapper  | 2010/08/05 06:33:09 | Launching a JVM...

INFO   | jvm 5    | 2010/08/05 06:33:10 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)

ERROR  | wrapper  | 2010/08/05 06:33:41 | Startup failed: Timed out
waiting for a signal from the JVM.

ERROR  | wrapper  | 2010/08/05 06:33:41 | JVM did not exit on request,
terminated

STATUS | wrapper  | 2010/08/05 06:33:46 | Launching a JVM...

INFO   | jvm 6    | 2010/08/05 06:33:46 | Profiler Agent: Waiting for
connection on port 5140 (Protocol version: 10)

ERROR  | wrapper  | 2010/08/05 06:34:18 | Startup failed: Timed out
waiting for a signal from the JVM.

ERROR  | wrapper  | 2010/08/05 06:34:18 | JVM did not exit on request,
terminated

FATAL  | wrapper  | 2010/08/05 06:34:19 | There were 5 failed launches
in a row, each lasting less than 300 seconds.  Giving up.

FATAL  | wrapper  | 2010/08/05 06:34:19 |   There may be a configuration
problem: please check the logs.

STATUS | wrapper  | 2010/08/05 06:34:19 | <-- Wrapper Stopped

 

[Wrapper-user] Can't stop service in dependency

[Alain P. <Ala...@bl...>]

Hi

 

I have problems with the service I created with Java Service Wrapper.

 

This service (named "A") installs and works well. Another service (named
"B") has the service "A" in dependency.

 

If both services are stopped, and I restart service "B", the two
services start very well.

 

 

I saw the service dependency "A" in the windows service manager for the
the service "B".

 

 

My problem is this: if the two services are started and I want to remove
the "A" service (stop it before), neither service "A" nor service "B"
are stopped.

 

I had this message in the log:

 

                Attempt to Stop the "A" service failed. Status: RUNNING

 

 

 

Thanks

 

 

A Perreault

 


Alain Perreault, Programmer Analyst / Analyste-programmeur

bluberi gaming technologies inc.
Drummondville, Quebec Canada
819.475.5155 (telephone) 819.475.5156 (fax) bluberi.com


--------------------------------------------------------------------------
This e-mail and any attachments transmitted with it are personal, privileged and confidential and solely for the use of the individual to whom they are addressed and intended. If you have received this e-mail in error, please notify the sender by return e-mail. If you are not the intended recipient or if you believe that you are not, you are hereby notified that the dissemination, distribution, plagiarism or copying of this e-mail and attachments transmitted with it is strictly prohibited.

Ce courriel et les pièces jointes s’y rattachant sont de nature personnelle, privilégiée et confidentielle et pour l’usage exclusif du destinataire à qui ils sont adressés et destinés. Si vous avez reçu ce courriel par erreur, veuillez s’il vous plaît le renvoyer à l’expéditeur. Si vous n’êtes pas le bon destinataire ou si vous croyez ne pas l’être, nous vous informons immédiatement que la publication, distribution, diffusion, copie ou plagiat de ce courriel et de ses pièces jointes sont strictement interdits.
--------------------------------------------------------------------------

[Wrapper-user] Java Service Wrapper 3.5.3

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

Hi all,
I would like to announce the release of 3.5.3 of the Java Service Wrapper.
This versions adds the ability to send authenticated emails (non-SSL
for now), as well as fixes a few issues with the 3.5.x series.

3.5.0 was the fist version to be fully localized to Japanese, with
German coming soon.   The Wrapper is also now fully UNICODE based
internally which makes it possible to set pretty much any property
value to non-ascii characters.

Please see the release notes for a full list of changes:
http://wrapper.tanukisoftware.org/doc/english/release-notes.html#3.5.3

As always, please let us know how we can continue to improve the
Wrapper to meet your needs.

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.
http://www.tanukisoftware.com

Re: [Wrapper-user] Antw: Re: org.apache.xerces.parsers.XIncludeAwareParserConfiguration when trying to stop an XMLServer service

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

Niambh,
Sorry for the silence on this issue.  What is its current status?
Please let me know if you are still having problems getting things
working.

Cheers,
Leif

On Fri, Jul 9, 2010 at 9:23 PM, Niambh Scullion
<NSc...@cu...> wrote:
> Hi there,
> I have checked that as that was my first approach. The XMLServer that I am installing is pretty much a standalone application, it does ship xerces-2.9.1.jar. However and the build script has a classpath setting set, to ensure the version we ship is used. The application has a start and stop command, and both of these have a classpath set. I have also checked my own classpath to see if I had a reference to xerces or xerces-impl, and I don't
>
> Over the past few weeks I have been testing our installer infrastructure, and I have been installing and deploying applications on Websphere. I was having problems logging in to the application and was looking at the SystemError.log file and I spotted a similar issue
> org.apache.xerces.parsers.XIncludeAwareParserConfiguration incompatible with org.apache.xerces.xni.parser.XMLParserConfiguration
> I did some more investigations (we are using WAS 7.0.0.7) and came across this known issue with IBM
> http://www-01.ibm.com/support/docview.wss?uid=swg1PK95911 .
>
> Obviously the calling classes are different but this is the same error I am getting in the wrapper log file, only the calling class appears to be
>        at org.tanukisoftware.wrapper.WrapperStartStopApp.stop(WrapperStartStopApp.java:423)
>        at org.tanukisoftware.wrapper.WrapperManager$13.run(WrapperManager.java:3341).
>
> When I am testing our XMLServer, I have to be very careful of what version of JAVA is used and I must have JAVA_HOME set to Suns version of Java.
>
> Many thanks,
> Niambh
>
>
> -----Original Message-----
> From: Hubert Felber [mailto:Hub...@ab...]
> Sent: 09 July 2010 12:56
> To: wra...@li...
> Subject: [Wrapper-user] Antw: Re: org.apache.xerces.parsers.XIncludeAwareParserConfiguration when trying to stop an XMLServer service
>
> Niambh
>
> Could it be, that there are different versions of Xerces jars  used?
>
>
>>>> Niambh Scullion <NSc...@cu...> 07.07.2010 12:34 >>>
> Hi Leif,
> Many thanks for your response, I have tried what you have suggested and
> I am still seeing the same error.  I have tried attaching the log,
> however it is too large, so I will attach a portion of the log. I have
> attempted to stop the service four times. Each time I stop my service
> the same error appears.
>
> 1)      I added logging - wrapper.java.command.loglevel=INFO  (this is
> my base).
>
> 2)      I updated my path to look at the sun java.   The stop failed.
>
> 3)      I had a local variable called JAVA_HOME_OVERRIDE - this was set
> to look at a WAS version of java, I removed this, I also updated a
> J2EE_JAR to point to Suns version of j2ee.jar, I checked my Java version
> which is 1.5.0_06. The stop failed.
>
> 4)      I changed wrapper.java.command.loglevel=DEBUG, to see if I
> could see anything else.
>
> I am attaching the logs, I am not sure if this is local as I have run
> this on another machine with the same issue.
>
> Many thanks,
> Niambh
>
>
> From: Leif Mortenson [mailto:lei...@ta...]
> Sent: 05 July 2010 21:13
> To: wra...@li...
> Subject: Re: [Wrapper-user]
> org.apache.xerces.parsers.XIncludeAwareParserConfiguration when trying
> to stop an XMLServer service
>
> Niambh,
> My first guess is that you are using the wrong JVM.  By default, the
> Wrapper locates a JVM on the system path.  this can be different when
> running as a service vs running in a console.
>
> Please add the wrapper.java.command.loglevel=INFO property and make
> sure that the JVM being used is valid.
> If that is the problem then you can be more specific with the following
> property as follows:
>
> wrapper.java.command=%JAVA_HOME%/bin/java
>
> Please let me know how this works for you.
>
> Cheers,
> Leif
> On Tue, Jul 6, 2010 at 3:45 AM, Niambh Scullion
> <NSc...@cu...<mailto:NSc...@cu...>>
> wrote:
> Hi Guys,
>
> I hope someone can be of help to me, I am creating a service as part of
> an XMLServer installation. When I install my XMLServer via the control
> panle, when I start my service, the service as expected starts
> successfully. However when I restart or stop my service the following
> error is appearing in the log:
>
> The version of Xerces, the xmlserver build file is using is
> xerces-2.9.1.jar.
>
> BUILD FAILED
> INFO   | jvm 1    | 2010/07/05 16:25:25 | java.lang.ClassCastException:
> org.apache.xerces.parsers.XIncludeAwareParserConfiguration
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.xerces.parsers.SAXParser.<init>(Unknown Source)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.<init>(Unknown
> Source)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.xerces.jaxp.SAXParserImpl.<init>(Unknown Source)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.xerces.jaxp.SAXParserFactoryImpl.newSAXParser(Unknown
> Source)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.util.JAXPUtils.newSAXParser(JAXPUtils.java:215)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.util.JAXPUtils.getNamespaceXMLReader(JAXPUtils.java:172)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:185)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:140)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.Main.runBuild(Main.java:743)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.Main.startAnt(Main.java:217)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> java.lang.reflect.Method.invoke(Method.java:585)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.tanukisoftware.wrapper.WrapperStartStopApp.stop(WrapperStartStopApp.java:423)
> INFO   | jvm 1    | 2010/07/05 16:25:25 |                 at
> org.tanukisoftware.wrapper.WrapperManager$13.run(WrapperManager.java:3341)
>
> The thing is, when I stop the service via the command prompt, it stops
> successfully
> C:\Curam\XmlServer\bin>Wrapper.exe -r ..\conf\wrapper.conf
> wrapper  | Service is running.  Stopping it...
> wrapper  | Curam XML Server service stopped.
> wrapper  | Curam XML Server service removed.
>
> Has any one seen this issue before?
>
> Many thanks in advance,
> Niambh

Re: [Wrapper-user] Trying to understand a simpleapp issue.

[<Jay...@sc...>]

yep that did it! 

Thanks!
Jay

Jay McGaffigan | Consulting Software Engineer
SeaChange International, Inc.
50 Nagog Park, Acton, MA 01720
www.schange.com | jay...@sc... 
O: 978-889-3136 | F: 978-987-5065
This e-mail and any attachments may contain information which is SeaChange 
International confidential. The information enclosed is intended only for 
the addressees herein and may not be copied or forwarded without 
permission from SeaChange International.





From:
Leif Mortenson <lei...@ta...>
To:
wra...@li...
Date:
07/27/2010 03:02 PM
Subject:
Re: [Wrapper-user] Trying to understand a simpleapp issue.



Jay,
You were very close.  The configured "main class" needs to be a Wrapper 
helper class or a user class which implements the WrapperListener 
interface.

Please try the following:
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=org.jruby.Main 
wrapper.app.parameter.2=-S 
wrapper.app.parameter.3=glassfish

The following property also didn't have a valid value.  Try this:
wrapper.java.command.loglevel=INFO

Please let me know how this works for you.

Cheers,
Leif

On Wed, Jul 28, 2010 at 12:29 AM, <Jay...@sc...> wrote:
Hi, 

Re: [Wrapper-user] Trying to understand a simpleapp issue.

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

Jay,
You were very close.  The configured "main class" needs to be a Wrapper
helper class or a user class which implements the WrapperListener interface.

Please try the following:
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=org.jruby.Main
wrapper.app.parameter.2=-S
wrapper.app.parameter.3=glassfish

The following property also didn't have a valid value.  Try this:
wrapper.java.command.loglevel=INFO

Please let me know how this works for you.

Cheers,
Leif

On Wed, Jul 28, 2010 at 12:29 AM, <Jay...@sc...> wrote:

> Hi,
>
> I am trying to use the Simple wrapper approach to launch a webserver and am
> running into issues.
>
> I was wondering if anyone could offer up some suggestions of where to look
> etc.
>
> First:
>   I am using Jruby and the glassfish gem  which launches the glassfish
> server.
> Second
>   when I setup using the "simple wrapper" approach
>   It looks like things are starting up... then I get a timeout in the
> wrapper log.
>
> I'm not 100% sure that this approach is the right one to be taking here.
>  but it seems so close to working :).
>
> Without the wrapper I launch glassfish thusly:
> jruby -S glassfish
>
> this produces a process :
> java -client -Djruby.memory.max=500m -Djruby.stack.max=1024k -Xmx500m
> -Xss1024k -Djffi.boot.library.path=jruby-1.5.0/lib/native/x86_64-Linux
> -Xbootclasspath/a:jruby-1.5.0/lib/jruby.jar -classpath
> jruby-1.5.0/lib/jna.jar:jruby-1.5.0/lib/profile.jar:
> -Djruby.home=jruby-1.5.0 -Djruby.lib=jruby-1.5.0/lib -Djruby.script=jruby
> -Djruby.shell=/bin/sh org.jruby.Main -S glassfish
>
>
> I'm thinking that the problem may be that launching this app never
> returns...
> or ... I know in the past jruby stuff I've done does not launch any non
> daemon threads and this interfered with the wrapper's ability to keep my app
> running.
>
> Any thoughts?
>
>
>
> here is a snippet of the wrapper log file  following this is my
> wrapper.conf file :
> ERROR  | wrapper  | 2010/07/27 11:04:07 | Startup failed: Timed out waiting
> for a signal from the JVM.
> ADVICE | wrapper  | 2010/07/27 11:04:07 |
> ADVICE | wrapper  | 2010/07/27 11:04:07 |
> ------------------------------------------------------------------------
> ADVICE | wrapper  | 2010/07/27 11:04:07 | Advice:
> ADVICE | wrapper  | 2010/07/27 11:04:07 | The Wrapper consists of a native
> component as well as a set of classes
> ADVICE | wrapper  | 2010/07/27 11:04:07 | which run within the JVM that it
> launches.  The Java component of the
> ADVICE | wrapper  | 2010/07/27 11:04:07 | Wrapper must be initialized
> promptly after the JVM is launched or the
> ADVICE | wrapper  | 2010/07/27 11:04:07 | Wrapper will timeout, as just
> happened.  Most likely the main class
> ADVICE | wrapper  | 2010/07/27 11:04:07 | specified in the Wrapper
> configuration file is not correctly initializing
> ADVICE | wrapper  | 2010/07/27 11:04:07 | the Wrapper classes:
> ADVICE | wrapper  | 2010/07/27 11:04:07 |     org.jruby.Main
> ADVICE | wrapper  | 2010/07/27 11:04:07 | While it is possible to do so
> manually, the Wrapper ships with helper
> ADVICE | wrapper  | 2010/07/27 11:04:07 | classes to make this
> initialization processes automatic.
> ADVICE | wrapper  | 2010/07/27 11:04:07 | Please review the integration
> section of the Wrapper's documentation
> ADVICE | wrapper  | 2010/07/27 11:04:07 | for the various methods which can
> be employed to launch an application
> ADVICE | wrapper  | 2010/07/27 11:04:07 | within the Wrapper:
> ADVICE | wrapper  | 2010/07/27 11:04:07 |
> http://wrapper.tanukisoftware.org/doc/english/integrate.html
> ADVICE | wrapper  | 2010/07/27 11:04:07 |
> ------------------------------------------------------------------------
> ADVICE | wrapper  | 2010/07/27 11:04:07 |
> ERROR  | wrapper  | 2010/07/27 11:04:08 | JVM did not exit on request,
> terminated
> DEBUG  | wrapper  | 2010/07/27 11:04:08 | Signal trapped.  Details:
> DEBUG  | wrapper  | 2010/07/27 11:04:08 |   signal number=17 (SIGCHLD),
> source="unknown"
> DEBUG  | wrapper  | 2010/07/27 11:04:08 | Received SIGCHLD, checking JVM
> process status.
> STATUS | wrapper  | 2010/07/27 11:04:08 | JVM received a signal SIGKILL
> (9).
> DEBUG  | wrapper  | 2010/07/27 11:04:08 | JVM was only running for 29
> seconds leading to a failed restart count of 1.
> DEBUG  | wrapper  | 2010/07/27 11:04:08 | Waiting 5 seconds before
> launching another JVM.
> DEBUG  | wrapper  | 2010/07/27 11:04:12 | Ping settings:
> wrapper.ping.interval=5, wrapper.ping.interval.logged=1,
> wrapper.ping.timeout=3600
> STATUS | wrapper  | 2010/07/27 11:04:12 | Launching a JVM...
> INFO   | jvm 2    | 2010/07/27 11:04:16 | Parsing config file:
> /var/www/seaviewlx/config/glassfish.yml
> INFO   | jvm 2    | 2010/07/27 11:04:16 | Starting GlassFish server at:
> 0.0.0.0:3000 in production environment...
> INFO   | jvm 2    | 2010/07/27 11:04:16 | Writing log messages to:
> /var/www/seaviewlx/log/production.log.
> INFO   | jvm 2    | 2010/07/27 11:04:16 | Press Ctrl+C to stop.
> INFO   | jvm 2    | 2010/07/27 11:04:16 |
>
>
>
>
>
> wrapper.conf
>
> #********************************************************************
> # Wrapper License Properties (Ignored by Community Edition)
> #********************************************************************
> # Professional and Standard Editions of the Wrapper require a valid
> #  License Key to start.  Licenses can be purchased or a trial license
> #  requested on the following pages:
> # http://wrapper.tanukisoftware.org/purchase
> # http://wrapper.tanukisoftware.org/trial
>
> # Include file problems can be debugged by removing the first '#'
> #  from the following line:
> ##include.debug
>
> # The Wrapper will look for either of the following optional files for a
> #  valid License Key.  License Key properties can optionally be included
> #  directly in this configuration file.
> #include /var/www/seaviewlx/config/wrapper-license.conf
> #include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf
>
> # The following property will output information about which License Key(s)
> #  are being found, and can aid in resolving any licensing problems.
> wrapper.license.debug=TRUE
>
> #********************************************************************
> # Wrapper Java Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=java
>
> # Tell the Wrapper to log the full generated Java command line.
> wrapper.java.command.loglevel=ALL
>
> # Java Main class.  This class must implement the WrapperListener interface
> #  or guarantee that the WrapperManager class is initialized.  Helper
> #  classes are provided to do this for you.  See the Integration section
> #  of the documentation for details.
> wrapper.java.mainclass=org.jruby.Main
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=/var/www/seaviewlx/lib/wrapper.jar
> wrapper.java.classpath.2=/var/www/seaviewlx/jruby-1.5.0/lib/jna.jar
> wrapper.java.classpath.3=/var/www/seaviewlx/jruby-1.5.0/lib/profile.jar
> wrapper.java.classpath.4=/var/www/seaviewlx/lib/util.jar
> wrapper.java.classpath.5=/var/www/seaviewlx/lib/args4j-2.0.9.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=/var/www/seaviewlx/lib
>
> # Java Bits.  On applicable platforms, tells the JVM to run in 32 or 64-bit
> mode.
> wrapper.java.additional.auto_bits=TRUE
>
> # Java Additional Parameters
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Djruby.memory.max=500m
> wrapper.java.additional.3=-Djruby.stack.max=1024k
> wrapper.java.additional.4=-Xmx500m
> wrapper.java.additional.5=-Xss1024k
>
> wrapper.java.additional.6=-Djffi.boot.library.path=/var/www/seaviewlx/jruby-1.5.0/lib/native/x86_64-Linux
>
> wrapper.java.additional.7=-Xbootclasspath/a:/var/www/seaviewlx/jruby-1.5.0/lib/jruby.jar
> wrapper.java.additional.8=-Djruby.home=/var/www/seaviewlx/jruby-1.5.0
> wrapper.java.additional.9=-Djruby.lib=/var/www/seaviewlx/jruby-1.5.0/lib
> wrapper.java.additional.10=-Djruby.script=jruby
> wrapper.java.additional.11=-Djruby.shell=/bin/sh
>
> # Initial Java Heap Size (in MB)
> #wrapper.java.initmemory=3
>
> # Maximum Java Heap Size (in MB)
> #wrapper.java.maxmemory=64
>
> # Application parameters.  Add parameters as needed starting from 1
> wrapper.app.parameter.1=-S
> wrapper.app.parameter.2=glassfish
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Enables Debug output from the Wrapper.
>  wrapper.debug=TRUE
>
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=ALL
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=/var/www/seaviewlx/log/wrapper.log
>
> # Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=LPTM
> wrapper.ping.timeout=3600
>
> # Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=INFO
>
> # Maximum size that the log file will be allowed to grow to before
> #  the log is rolled. Size is specified in bytes.  The default value
> #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
> #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
> wrapper.logfile.maxsize=0
>
> # Maximum number of rolled log files which will be allowed before old
> #  files are deleted.  The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=0
>
> # Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=ALL
>
> #********************************************************************
> # Wrapper General Properties
> #********************************************************************
> # Allow for the use of non-contiguous numbered properties
> wrapper.ignore_sequence_gaps=TRUE
>
> # Title to use when running as a console
> wrapper.console.title=Test Wrapper Sample Application
>
> #********************************************************************
> # Wrapper JVM Checks
> #********************************************************************
> # Detect DeadLocked Threads in the JVM. (Requires Standard Edition)
> wrapper.check.deadlock=TRUE
> wrapper.check.deadlock.interval=60
> wrapper.check.deadlock.action=RESTART
> wrapper.check.deadlock.output=FULL
>
> # Out Of Memory detection.
> wrapper.filter.trigger.1000=java.lang.OutOfMemoryError
> wrapper.filter.action.1000=RESTART
> wrapper.filter.message.1000=The JVM has run out of memory.
>
> #********************************************************************
> # Wrapper Email Notifications. (Requires Professional Edition)
> #********************************************************************
> # Common Event Email settings.
> #wrapper.event.default.email.debug=TRUE
> #wrapper.event.default.email.smtp.host=<SMTP_Host>
> #wrapper.event.default.email.smtp.port=25
> #wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%]
> Event Notification
> #wrapper.event.default.email.sender=<Sender email>
> #wrapper.event.default.email.recipient=<Recipient email>
>
> # Configure the log attached to event emails.
> #wrapper.event.default.email.attach_log=TRUE
> #wrapper.event.default.email.maillog.lines=50
> #wrapper.event.default.email.maillog.format=LPTM
> #wrapper.event.default.email.maillog.loglevel=INFO
>
> # Enable specific event emails.
> #wrapper.event.wrapper_start.email=TRUE
> #wrapper.event.jvm_prelaunch.email=TRUE
> #wrapper.event.jvm_start.email=TRUE
> #wrapper.event.jvm_started.email=TRUE
> #wrapper.event.jvm_stop.email=TRUE
> #wrapper.event.jvm_stopped.email=TRUE
> #wrapper.event.jvm_restart.email=TRUE
> #wrapper.event.jvm_failed_invocation.email=TRUE
> #wrapper.event.jvm_max_failed_invocations.email=TRUE
> #wrapper.event.jvm_kill.email=TRUE
> #wrapper.event.jvm_killed.email=TRUE
> #wrapper.event.jvm_unexpected_exit.email=TRUE
> #wrapper.event.wrapper_stop.email=TRUE
>
> # Specify custom mail content
> wrapper.event.jvm_restart.email.body=The JVM was restarted.\n\nPlease check
> on its status.\n
>
> #********************************************************************
> # Wrapper Windows NT/2000/XP Service Properties
> #********************************************************************
> # WARNING - Do not modify any of these properties when an application
> #  using this configuration file has been installed as a service.
> #  Please uninstall the service before modifying this section.  The
> #  service can then be reinstalled.
>
> # Name of the service
> wrapper.name=testwrapper
>
> # Display name of the service
> wrapper.displayname=Test Wrapper Sample Application
>
> # Description of the service
> wrapper.description=Test Wrapper Sample Application Description
>
> # Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START, DELAY_START or
> DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>  *Jay McGaffigan *| Consulting Software Engineer*
> SeaChange International, Inc.*
> 50 Nagog Park, Acton, MA 01720*
> **www.schange.com* <http://www.schange.com/> | *jay...@sc...
> * <%3Ca+href=>
> O: 978-889-3136 | F: 978-987-5065 This e-mail and any attachments may
> contain information which is SeaChange International confidential. The
> information enclosed is intended only for the addressees herein and may not
> be copied or forwarded without permission from SeaChange International.
>

Re: [Wrapper-user] Trying to understand a simpleapp issue.

[<Jay...@sc...>]

figured it out...

we had the wrong main class...

we switched to org.tanukisoftware.wrapper.WrapperSimpleApp as the main 
method, org.jruby.Main as an app parameter
and now we are working.


:P



Jay McGaffigan | Consulting Software Engineer
SeaChange International, Inc.
50 Nagog Park, Acton, MA 01720
www.schange.com | jay...@sc... 
O: 978-889-3136 | F: 978-987-5065
This e-mail and any attachments may contain information which is SeaChange 
International confidential. The information enclosed is intended only for 
the addressees herein and may not be copied or forwarded without 
permission from SeaChange International.





From:
Jay...@sc...
To:
wra...@li...
Date:
07/27/2010 11:45 AM
Subject:
[Wrapper-user] Trying to understand a simpleapp issue.



Hi, 

I am trying to use the Simple wrapper approach to launch a webserver and 
am running into issues. 

I was wondering if anyone could offer up some suggestions of where to look 
etc. 

First: 
  I am using Jruby and the glassfish gem  which launches the glassfish 
server. 
Second 
  when I setup using the "simple wrapper" approach 
  It looks like things are starting up... then I get a timeout in the 
wrapper log. 

I'm not 100% sure that this approach is the right one to be taking here. 
but it seems so close to working :). 

Without the wrapper I launch glassfish thusly: 
jruby -S glassfish 

this produces a process : 
java -client -Djruby.memory.max=500m -Djruby.stack.max=1024k -Xmx500m 
-Xss1024k -Djffi.boot.library.path=jruby-1.5.0/lib/native/x86_64-Linux 
-Xbootclasspath/a:jruby-1.5.0/lib/jruby.jar -classpath 
jruby-1.5.0/lib/jna.jar:jruby-1.5.0/lib/profile.jar: 
-Djruby.home=jruby-1.5.0 -Djruby.lib=jruby-1.5.0/lib -Djruby.script=jruby 
-Djruby.shell=/bin/sh org.jruby.Main -S glassfish 


I'm thinking that the problem may be that launching this app never 
returns... 
or ... I know in the past jruby stuff I've done does not launch any non 
daemon threads and this interfered with the wrapper's ability to keep my 
app running. 

Any thoughts? 



here is a snippet of the wrapper log file  following this is my 
wrapper.conf file : 
ERROR  | wrapper  | 2010/07/27 11:04:07 | Startup failed: Timed out 
waiting for a signal from the JVM. 
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
------------------------------------------------------------------------ 
ADVICE | wrapper  | 2010/07/27 11:04:07 | Advice: 
ADVICE | wrapper  | 2010/07/27 11:04:07 | The Wrapper consists of a native 
component as well as a set of classes 
ADVICE | wrapper  | 2010/07/27 11:04:07 | which run within the JVM that it 
launches.  The Java component of the 
ADVICE | wrapper  | 2010/07/27 11:04:07 | Wrapper must be initialized 
promptly after the JVM is launched or the 
ADVICE | wrapper  | 2010/07/27 11:04:07 | Wrapper will timeout, as just 
happened.  Most likely the main class 
ADVICE | wrapper  | 2010/07/27 11:04:07 | specified in the Wrapper 
configuration file is not correctly initializing 
ADVICE | wrapper  | 2010/07/27 11:04:07 | the Wrapper classes: 
ADVICE | wrapper  | 2010/07/27 11:04:07 |     org.jruby.Main 
ADVICE | wrapper  | 2010/07/27 11:04:07 | While it is possible to do so 
manually, the Wrapper ships with helper 
ADVICE | wrapper  | 2010/07/27 11:04:07 | classes to make this 
initialization processes automatic. 
ADVICE | wrapper  | 2010/07/27 11:04:07 | Please review the integration 
section of the Wrapper's documentation 
ADVICE | wrapper  | 2010/07/27 11:04:07 | for the various methods which 
can be employed to launch an application 
ADVICE | wrapper  | 2010/07/27 11:04:07 | within the Wrapper: 
ADVICE | wrapper  | 2010/07/27 11:04:07 |     
http://wrapper.tanukisoftware.org/doc/english/integrate.html 
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
------------------------------------------------------------------------ 
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
ERROR  | wrapper  | 2010/07/27 11:04:08 | JVM did not exit on request, 
terminated 
DEBUG  | wrapper  | 2010/07/27 11:04:08 | Signal trapped.  Details: 
DEBUG  | wrapper  | 2010/07/27 11:04:08 |   signal number=17 (SIGCHLD), 
source="unknown" 
DEBUG  | wrapper  | 2010/07/27 11:04:08 | Received SIGCHLD, checking JVM 
process status. 
STATUS | wrapper  | 2010/07/27 11:04:08 | JVM received a signal SIGKILL 
(9). 
DEBUG  | wrapper  | 2010/07/27 11:04:08 | JVM was only running for 29 
seconds leading to a failed restart count of 1. 
DEBUG  | wrapper  | 2010/07/27 11:04:08 | Waiting 5 seconds before 
launching another JVM. 
DEBUG  | wrapper  | 2010/07/27 11:04:12 | Ping settings: 
wrapper.ping.interval=5, wrapper.ping.interval.logged=1, 
wrapper.ping.timeout=3600 
STATUS | wrapper  | 2010/07/27 11:04:12 | Launching a JVM... 
INFO   | jvm 2    | 2010/07/27 11:04:16 | Parsing config file: 
/var/www/seaviewlx/config/glassfish.yml 
INFO   | jvm 2    | 2010/07/27 11:04:16 | Starting GlassFish server at: 
0.0.0.0:3000 in production environment... 
INFO   | jvm 2    | 2010/07/27 11:04:16 | Writing log messages to: 
/var/www/seaviewlx/log/production.log. 
INFO   | jvm 2    | 2010/07/27 11:04:16 | Press Ctrl+C to stop. 
INFO   | jvm 2    | 2010/07/27 11:04:16 | 





wrapper.conf 

#******************************************************************** 
# Wrapper License Properties (Ignored by Community Edition) 
#******************************************************************** 
# Professional and Standard Editions of the Wrapper require a valid 
#  License Key to start.  Licenses can be purchased or a trial license 
#  requested on the following pages: 
# http://wrapper.tanukisoftware.org/purchase 
# http://wrapper.tanukisoftware.org/trial 

# Include file problems can be debugged by removing the first '#' 
#  from the following line: 
##include.debug 

# The Wrapper will look for either of the following optional files for a 
#  valid License Key.  License Key properties can optionally be included 
#  directly in this configuration file. 
#include /var/www/seaviewlx/config/wrapper-license.conf 
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf 

# The following property will output information about which License 
Key(s) 
#  are being found, and can aid in resolving any licensing problems. 
wrapper.license.debug=TRUE 

#******************************************************************** 
# Wrapper Java Properties 
#******************************************************************** 
# Java Application 
wrapper.java.command=java 

# Tell the Wrapper to log the full generated Java command line. 
wrapper.java.command.loglevel=ALL 

# Java Main class.  This class must implement the WrapperListener 
interface 
#  or guarantee that the WrapperManager class is initialized.  Helper 
#  classes are provided to do this for you.  See the Integration section 
#  of the documentation for details. 
wrapper.java.mainclass=org.jruby.Main 

# Java Classpath (include wrapper.jar)  Add class path elements as 
#  needed starting from 1 
wrapper.java.classpath.1=/var/www/seaviewlx/lib/wrapper.jar 
wrapper.java.classpath.2=/var/www/seaviewlx/jruby-1.5.0/lib/jna.jar 
wrapper.java.classpath.3=/var/www/seaviewlx/jruby-1.5.0/lib/profile.jar 
wrapper.java.classpath.4=/var/www/seaviewlx/lib/util.jar 
wrapper.java.classpath.5=/var/www/seaviewlx/lib/args4j-2.0.9.jar 

# Java Library Path (location of Wrapper.DLL or libwrapper.so) 
wrapper.java.library.path.1=/var/www/seaviewlx/lib 

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 
64-bit mode. 
wrapper.java.additional.auto_bits=TRUE 

# Java Additional Parameters 
wrapper.java.additional.1=-server 
wrapper.java.additional.2=-Djruby.memory.max=500m 
wrapper.java.additional.3=-Djruby.stack.max=1024k 
wrapper.java.additional.4=-Xmx500m 
wrapper.java.additional.5=-Xss1024k 
wrapper.java.additional.6=-Djffi.boot.library.path=/var/www/seaviewlx/jruby-1.5.0/lib/native/x86_64-Linux 

wrapper.java.additional.7=-Xbootclasspath/a:/var/www/seaviewlx/jruby-1.5.0/lib/jruby.jar 

wrapper.java.additional.8=-Djruby.home=/var/www/seaviewlx/jruby-1.5.0 
wrapper.java.additional.9=-Djruby.lib=/var/www/seaviewlx/jruby-1.5.0/lib 
wrapper.java.additional.10=-Djruby.script=jruby 
wrapper.java.additional.11=-Djruby.shell=/bin/sh 

# Initial Java Heap Size (in MB) 
#wrapper.java.initmemory=3 

# Maximum Java Heap Size (in MB) 
#wrapper.java.maxmemory=64 

# Application parameters.  Add parameters as needed starting from 1 
wrapper.app.parameter.1=-S 
wrapper.app.parameter.2=glassfish 

#******************************************************************** 
# Wrapper Logging Properties 
#******************************************************************** 
# Enables Debug output from the Wrapper. 
 wrapper.debug=TRUE 

# Format of output for the console.  (See docs for formats) 
wrapper.console.format=PM 

# Log Level for console output.  (See docs for log levels) 
wrapper.console.loglevel=ALL 

# Log file to use for wrapper output logging. 
wrapper.logfile=/var/www/seaviewlx/log/wrapper.log 

# Format of output for the log file.  (See docs for formats) 
wrapper.logfile.format=LPTM 
wrapper.ping.timeout=3600 

# Log Level for log file output.  (See docs for log levels) 
wrapper.logfile.loglevel=INFO 

# Maximum size that the log file will be allowed to grow to before 
#  the log is rolled. Size is specified in bytes.  The default value 
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or 
#  'm' (mb) suffix.  For example: 10m = 10 megabytes. 
wrapper.logfile.maxsize=0 

# Maximum number of rolled log files which will be allowed before old 
#  files are deleted.  The default value of 0 implies no limit. 
wrapper.logfile.maxfiles=0 

# Log Level for sys/event log output.  (See docs for log levels) 
wrapper.syslog.loglevel=ALL 

#******************************************************************** 
# Wrapper General Properties 
#******************************************************************** 
# Allow for the use of non-contiguous numbered properties 
wrapper.ignore_sequence_gaps=TRUE 

# Title to use when running as a console 
wrapper.console.title=Test Wrapper Sample Application 

#******************************************************************** 
# Wrapper JVM Checks 
#******************************************************************** 
# Detect DeadLocked Threads in the JVM. (Requires Standard Edition) 
wrapper.check.deadlock=TRUE 
wrapper.check.deadlock.interval=60 
wrapper.check.deadlock.action=RESTART 
wrapper.check.deadlock.output=FULL 

# Out Of Memory detection. 
wrapper.filter.trigger.1000=java.lang.OutOfMemoryError 
wrapper.filter.action.1000=RESTART 
wrapper.filter.message.1000=The JVM has run out of memory. 

#******************************************************************** 
# Wrapper Email Notifications. (Requires Professional Edition) 
#******************************************************************** 
# Common Event Email settings. 
#wrapper.event.default.email.debug=TRUE 
#wrapper.event.default.email.smtp.host=<SMTP_Host> 
#wrapper.event.default.email.smtp.port=25 
#wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] 
Event Notification 
#wrapper.event.default.email.sender=<Sender email> 
#wrapper.event.default.email.recipient=<Recipient email> 

# Configure the log attached to event emails. 
#wrapper.event.default.email.attach_log=TRUE 
#wrapper.event.default.email.maillog.lines=50 
#wrapper.event.default.email.maillog.format=LPTM 
#wrapper.event.default.email.maillog.loglevel=INFO 

# Enable specific event emails. 
#wrapper.event.wrapper_start.email=TRUE 
#wrapper.event.jvm_prelaunch.email=TRUE 
#wrapper.event.jvm_start.email=TRUE 
#wrapper.event.jvm_started.email=TRUE 
#wrapper.event.jvm_stop.email=TRUE 
#wrapper.event.jvm_stopped.email=TRUE 
#wrapper.event.jvm_restart.email=TRUE 
#wrapper.event.jvm_failed_invocation.email=TRUE 
#wrapper.event.jvm_max_failed_invocations.email=TRUE 
#wrapper.event.jvm_kill.email=TRUE 
#wrapper.event.jvm_killed.email=TRUE 
#wrapper.event.jvm_unexpected_exit.email=TRUE 
#wrapper.event.wrapper_stop.email=TRUE 

# Specify custom mail content 
wrapper.event.jvm_restart.email.body=The JVM was restarted.\n\nPlease 
check on its status.\n 

#******************************************************************** 
# Wrapper Windows NT/2000/XP Service Properties 
#******************************************************************** 
# WARNING - Do not modify any of these properties when an application 
#  using this configuration file has been installed as a service. 
#  Please uninstall the service before modifying this section.  The 
#  service can then be reinstalled. 

# Name of the service 
wrapper.name=testwrapper 

# Display name of the service 
wrapper.displayname=Test Wrapper Sample Application 

# Description of the service 
wrapper.description=Test Wrapper Sample Application Description 

# Service dependencies.  Add dependencies as needed starting from 1 
wrapper.ntservice.dependency.1= 

# Mode in which the service is installed.  AUTO_START, DELAY_START or 
DEMAND_START 
wrapper.ntservice.starttype=AUTO_START 

# Allow the service to interact with the desktop. 
wrapper.ntservice.interactive=false 
Jay McGaffigan | Consulting Software Engineer
SeaChange International, Inc.
50 Nagog Park, Acton, MA 01720
www.schange.com | jay...@sc... 
O: 978-889-3136 | F: 978-987-5065 
This e-mail and any attachments may contain information which is SeaChange 
International confidential. The information enclosed is intended only for 
the addressees herein and may not be copied or forwarded without 
permission from SeaChange International.

------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
of $1 Million in cash or HP Products. Visit us here for more details:
http://ad.doubleclick.net/clk;226879339;13503038;l?
http://clk.atdmt.com/CRS/go/247765532/direct/01/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] Trying to understand a simpleapp issue.

[<Jay...@sc...>]

Hi, 

I am trying to use the Simple wrapper approach to launch a webserver and 
am running into issues.

I was wondering if anyone could offer up some suggestions of where to look 
etc.

First:
  I am using Jruby and the glassfish gem  which launches the glassfish 
server.
Second 
  when I setup using the "simple wrapper" approach
  It looks like things are starting up... then I get a timeout in the 
wrapper log.

I'm not 100% sure that this approach is the right one to be taking here. 
but it seems so close to working :).

Without the wrapper I launch glassfish thusly: 
jruby -S glassfish

this produces a process :
java -client -Djruby.memory.max=500m -Djruby.stack.max=1024k -Xmx500m 
-Xss1024k -Djffi.boot.library.path=jruby-1.5.0/lib/native/x86_64-Linux 
-Xbootclasspath/a:jruby-1.5.0/lib/jruby.jar -classpath 
jruby-1.5.0/lib/jna.jar:jruby-1.5.0/lib/profile.jar: 
-Djruby.home=jruby-1.5.0 -Djruby.lib=jruby-1.5.0/lib -Djruby.script=jruby 
-Djruby.shell=/bin/sh org.jruby.Main -S glassfish


I'm thinking that the problem may be that launching this app never 
returns... 
or ... I know in the past jruby stuff I've done does not launch any non 
daemon threads and this interfered with the wrapper's ability to keep my 
app running. 

Any thoughts?



here is a snippet of the wrapper log file  following this is my 
wrapper.conf file :
ERROR  | wrapper  | 2010/07/27 11:04:07 | Startup failed: Timed out 
waiting for a signal from the JVM.
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
------------------------------------------------------------------------
ADVICE | wrapper  | 2010/07/27 11:04:07 | Advice:
ADVICE | wrapper  | 2010/07/27 11:04:07 | The Wrapper consists of a native 
component as well as a set of classes
ADVICE | wrapper  | 2010/07/27 11:04:07 | which run within the JVM that it 
launches.  The Java component of the
ADVICE | wrapper  | 2010/07/27 11:04:07 | Wrapper must be initialized 
promptly after the JVM is launched or the
ADVICE | wrapper  | 2010/07/27 11:04:07 | Wrapper will timeout, as just 
happened.  Most likely the main class
ADVICE | wrapper  | 2010/07/27 11:04:07 | specified in the Wrapper 
configuration file is not correctly initializing
ADVICE | wrapper  | 2010/07/27 11:04:07 | the Wrapper classes:
ADVICE | wrapper  | 2010/07/27 11:04:07 |     org.jruby.Main
ADVICE | wrapper  | 2010/07/27 11:04:07 | While it is possible to do so 
manually, the Wrapper ships with helper
ADVICE | wrapper  | 2010/07/27 11:04:07 | classes to make this 
initialization processes automatic.
ADVICE | wrapper  | 2010/07/27 11:04:07 | Please review the integration 
section of the Wrapper's documentation
ADVICE | wrapper  | 2010/07/27 11:04:07 | for the various methods which 
can be employed to launch an application
ADVICE | wrapper  | 2010/07/27 11:04:07 | within the Wrapper:
ADVICE | wrapper  | 2010/07/27 11:04:07 |     
http://wrapper.tanukisoftware.org/doc/english/integrate.html
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
------------------------------------------------------------------------
ADVICE | wrapper  | 2010/07/27 11:04:07 | 
ERROR  | wrapper  | 2010/07/27 11:04:08 | JVM did not exit on request, 
terminated
DEBUG  | wrapper  | 2010/07/27 11:04:08 | Signal trapped.  Details:
DEBUG  | wrapper  | 2010/07/27 11:04:08 |   signal number=17 (SIGCHLD), 
source="unknown"
DEBUG  | wrapper  | 2010/07/27 11:04:08 | Received SIGCHLD, checking JVM 
process status.
STATUS | wrapper  | 2010/07/27 11:04:08 | JVM received a signal SIGKILL 
(9).
DEBUG  | wrapper  | 2010/07/27 11:04:08 | JVM was only running for 29 
seconds leading to a failed restart count of 1.
DEBUG  | wrapper  | 2010/07/27 11:04:08 | Waiting 5 seconds before 
launching another JVM.
DEBUG  | wrapper  | 2010/07/27 11:04:12 | Ping settings: 
wrapper.ping.interval=5, wrapper.ping.interval.logged=1, 
wrapper.ping.timeout=3600
STATUS | wrapper  | 2010/07/27 11:04:12 | Launching a JVM...
INFO   | jvm 2    | 2010/07/27 11:04:16 | Parsing config file: 
/var/www/seaviewlx/config/glassfish.yml
INFO   | jvm 2    | 2010/07/27 11:04:16 | Starting GlassFish server at: 
0.0.0.0:3000 in production environment...
INFO   | jvm 2    | 2010/07/27 11:04:16 | Writing log messages to: 
/var/www/seaviewlx/log/production.log.
INFO   | jvm 2    | 2010/07/27 11:04:16 | Press Ctrl+C to stop.
INFO   | jvm 2    | 2010/07/27 11:04:16 | 





wrapper.conf

#********************************************************************
# Wrapper License Properties (Ignored by Community Edition)
#********************************************************************
# Professional and Standard Editions of the Wrapper require a valid
#  License Key to start.  Licenses can be purchased or a trial license
#  requested on the following pages:
# http://wrapper.tanukisoftware.org/purchase
# http://wrapper.tanukisoftware.org/trial

# Include file problems can be debugged by removing the first '#'
#  from the following line:
##include.debug

# The Wrapper will look for either of the following optional files for a
#  valid License Key.  License Key properties can optionally be included
#  directly in this configuration file.
#include /var/www/seaviewlx/config/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

# The following property will output information about which License 
Key(s)
#  are being found, and can aid in resolving any licensing problems.
wrapper.license.debug=TRUE

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
wrapper.java.command=java

# Tell the Wrapper to log the full generated Java command line.
wrapper.java.command.loglevel=ALL

# Java Main class.  This class must implement the WrapperListener 
interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=org.jruby.Main

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=/var/www/seaviewlx/lib/wrapper.jar
wrapper.java.classpath.2=/var/www/seaviewlx/jruby-1.5.0/lib/jna.jar
wrapper.java.classpath.3=/var/www/seaviewlx/jruby-1.5.0/lib/profile.jar
wrapper.java.classpath.4=/var/www/seaviewlx/lib/util.jar
wrapper.java.classpath.5=/var/www/seaviewlx/lib/args4j-2.0.9.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=/var/www/seaviewlx/lib

# Java Bits.  On applicable platforms, tells the JVM to run in 32 or 
64-bit mode.
wrapper.java.additional.auto_bits=TRUE

# Java Additional Parameters
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Djruby.memory.max=500m
wrapper.java.additional.3=-Djruby.stack.max=1024k
wrapper.java.additional.4=-Xmx500m
wrapper.java.additional.5=-Xss1024k
wrapper.java.additional.6=-Djffi.boot.library.path=/var/www/seaviewlx/jruby-1.5.0/lib/native/x86_64-Linux
wrapper.java.additional.7=-Xbootclasspath/a:/var/www/seaviewlx/jruby-1.5.0/lib/jruby.jar
wrapper.java.additional.8=-Djruby.home=/var/www/seaviewlx/jruby-1.5.0
wrapper.java.additional.9=-Djruby.lib=/var/www/seaviewlx/jruby-1.5.0/lib
wrapper.java.additional.10=-Djruby.script=jruby
wrapper.java.additional.11=-Djruby.shell=/bin/sh

# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3

# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=-S
wrapper.app.parameter.2=glassfish

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Enables Debug output from the Wrapper.
 wrapper.debug=TRUE

# Format of output for the console.  (See docs for formats)
wrapper.console.format=PM

# Log Level for console output.  (See docs for log levels)
wrapper.console.loglevel=ALL

# Log file to use for wrapper output logging.
wrapper.logfile=/var/www/seaviewlx/log/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM
wrapper.ping.timeout=3600

# Log Level for log file output.  (See docs for log levels)
wrapper.logfile.loglevel=INFO

# Maximum size that the log file will be allowed to grow to before
#  the log is rolled. Size is specified in bytes.  The default value
#  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
#  'm' (mb) suffix.  For example: 10m = 10 megabytes.
wrapper.logfile.maxsize=0

# Maximum number of rolled log files which will be allowed before old
#  files are deleted.  The default value of 0 implies no limit.
wrapper.logfile.maxfiles=0

# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=ALL

#********************************************************************
# Wrapper General Properties
#********************************************************************
# Allow for the use of non-contiguous numbered properties
wrapper.ignore_sequence_gaps=TRUE

# Title to use when running as a console
wrapper.console.title=Test Wrapper Sample Application

#********************************************************************
# Wrapper JVM Checks
#********************************************************************
# Detect DeadLocked Threads in the JVM. (Requires Standard Edition)
wrapper.check.deadlock=TRUE
wrapper.check.deadlock.interval=60
wrapper.check.deadlock.action=RESTART
wrapper.check.deadlock.output=FULL

# Out Of Memory detection.
wrapper.filter.trigger.1000=java.lang.OutOfMemoryError
wrapper.filter.action.1000=RESTART
wrapper.filter.message.1000=The JVM has run out of memory.

#********************************************************************
# Wrapper Email Notifications. (Requires Professional Edition)
#********************************************************************
# Common Event Email settings.
#wrapper.event.default.email.debug=TRUE
#wrapper.event.default.email.smtp.host=<SMTP_Host>
#wrapper.event.default.email.smtp.port=25
#wrapper.event.default.email.subject=[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] 
Event Notification
#wrapper.event.default.email.sender=<Sender email>
#wrapper.event.default.email.recipient=<Recipient email>

# Configure the log attached to event emails.
#wrapper.event.default.email.attach_log=TRUE
#wrapper.event.default.email.maillog.lines=50
#wrapper.event.default.email.maillog.format=LPTM
#wrapper.event.default.email.maillog.loglevel=INFO

# Enable specific event emails.
#wrapper.event.wrapper_start.email=TRUE
#wrapper.event.jvm_prelaunch.email=TRUE
#wrapper.event.jvm_start.email=TRUE
#wrapper.event.jvm_started.email=TRUE
#wrapper.event.jvm_stop.email=TRUE
#wrapper.event.jvm_stopped.email=TRUE
#wrapper.event.jvm_restart.email=TRUE
#wrapper.event.jvm_failed_invocation.email=TRUE
#wrapper.event.jvm_max_failed_invocations.email=TRUE
#wrapper.event.jvm_kill.email=TRUE
#wrapper.event.jvm_killed.email=TRUE
#wrapper.event.jvm_unexpected_exit.email=TRUE
#wrapper.event.wrapper_stop.email=TRUE

# Specify custom mail content
wrapper.event.jvm_restart.email.body=The JVM was restarted.\n\nPlease 
check on its status.\n

#********************************************************************
# Wrapper Windows NT/2000/XP Service Properties
#********************************************************************
# WARNING - Do not modify any of these properties when an application
#  using this configuration file has been installed as a service.
#  Please uninstall the service before modifying this section.  The
#  service can then be reinstalled.

# Name of the service
wrapper.name=testwrapper

# Display name of the service
wrapper.displayname=Test Wrapper Sample Application

# Description of the service
wrapper.description=Test Wrapper Sample Application Description

# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=

# Mode in which the service is installed.  AUTO_START, DELAY_START or 
DEMAND_START
wrapper.ntservice.starttype=AUTO_START

# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false

Jay McGaffigan | Consulting Software Engineer
SeaChange International, Inc.
50 Nagog Park, Acton, MA 01720
www.schange.com | jay...@sc... 
O: 978-889-3136 | F: 978-987-5065
This e-mail and any attachments may contain information which is SeaChange 
International confidential. The information enclosed is intended only for 
the addressees herein and may not be copied or forwarded without 
permission from SeaChange International.

Re: [Wrapper-user] Many syscalls per second: EAGAIN (Resourcetemporarily unavailable)

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

Holger,
The main wrapper loop has a 100ms sleep in it, so it loops 10 times
per second.   The Wrapper only pings the JVM once every 5 seconds by
default.
The 10 loops per second is low enough that it is trivial with respect
to performance, but the loop is tight enough to make the Wrapper feel
very responsive.

Cheers,
Leif

On Tue, Jul 27, 2010 at 5:38 PM, Isenberg, Holger <ise...@e-...> wrote:
> It doesn't cause any problems, I'm only wondering if the high frequency of calls per second is normal as we have other problems on that system and I just checked with strace. I thought the wrapper only checks about 1 time per second.
>
>
> --
>
> Holger Isenberg
> e-Spirit AG
>
>
>
>> -----Original Message-----
>> From: Leif Mortenson [mailto:lei...@ta...]
>> Sent: Monday, July 26, 2010 1:05 PM
>> To: wra...@li...
>> Subject: Re: [Wrapper-user] Many syscalls per second: EAGAIN
>> (Resourcetemporarily unavailable)
>>
>> Holger,
>> The Wrapper used to be a single threaded application.  Its main loop
>> still does non-blocking reads on the pipes and sockets. I believe this
>> is what you are seeing.
>>
>> Is this causing any problems?  It is possible to change this logic and
>> use more dedicated threads if necessary.  I would appreciate your
>> input here.
>>
>> Cheers,
>> Leif
>>
>> On Mon, Jul 26, 2010 at 6:32 PM, Isenberg, Holger
>> <ise...@e-...> wrote:
>> > Hallo,
>> >
>> > when monitoring the wrapper process with "strace -p
>> Wrapper-PID" on Linux, I'm wondering about the high frequency
>> of read() and recvfrom() calls on the pipe and TCP socket
>> connection to the Java process and each of them returning
>> with "EAGAIN (Resource temporarily unavailable)". The
>> frequency is about 10 per second.
>> >
>> > Is this a bug of strace or does the wrapper calls these
>> functions really that fast and why don't they block when
>> waiting for data?
>> >
>> > STATUS | wrapper  | 2009/07/10 12:04:50 | --> Wrapper
>> Started as Daemon
>> > STATUS | wrapper  | 2009/07/10 12:04:50 | Java Service
>> Wrapper Standard Edition 64-bit 3.3.5
>> >
>> > Linux [...] 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC
>> 2009 x86_64 GNU/Linux
>> >
>> > java version "1.6.0_21"
>> > Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
>> > Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>> >
>> > gettimeofday({1280134204, 517914}, NULL) = 0
>> > read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN
>> (Resource temporarily unavailable)
>> > gettimeofday({1280134204, 518004}, NULL) = 0
>> > recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN
>> (Resource temporarily unavailable)
>> > wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
>> > nanosleep({0, 100000000}, NULL)         = 0
>> > gettimeofday({1280134204, 618287}, NULL) = 0
>> > read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN
>> (Resource temporarily unavailable)
>> > gettimeofday({1280134204, 618392}, NULL) = 0
>> > recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN
>> (Resource temporarily unavailable)
>> > wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
>> > nanosleep({0, 100000000}, NULL)         = 0
>> > gettimeofday({1280134204, 718729}, NULL) = 0
>> > read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN
>> (Resource temporarily unavailable)
>> > gettimeofday({1280134204, 718831}, NULL) = 0
>> > recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN
>> (Resource temporarily unavailable)
>> > wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
>> > nanosleep({0, 100000000}, NULL)         = 0
>> > gettimeofday({1280134204, 819092}, NULL) = 0

Re: [Wrapper-user] Many syscalls per second: EAGAIN (Resourcetemporarily unavailable)

[Isenberg, H. <ise...@e-...>]

It doesn't cause any problems, I'm only wondering if the high frequency of calls per second is normal as we have other problems on that system and I just checked with strace. I thought the wrapper only checks about 1 time per second.


--  
 
Holger Isenberg
e-Spirit AG 

 

> -----Original Message-----
> From: Leif Mortenson [mailto:lei...@ta...] 
> Sent: Monday, July 26, 2010 1:05 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Many syscalls per second: EAGAIN 
> (Resourcetemporarily unavailable)
> 
> Holger,
> The Wrapper used to be a single threaded application.  Its main loop
> still does non-blocking reads on the pipes and sockets. I believe this
> is what you are seeing.
> 
> Is this causing any problems?  It is possible to change this logic and
> use more dedicated threads if necessary.  I would appreciate your
> input here.
> 
> Cheers,
> Leif
> 
> On Mon, Jul 26, 2010 at 6:32 PM, Isenberg, Holger 
> <ise...@e-...> wrote:
> > Hallo,
> >
> > when monitoring the wrapper process with "strace -p 
> Wrapper-PID" on Linux, I'm wondering about the high frequency 
> of read() and recvfrom() calls on the pipe and TCP socket 
> connection to the Java process and each of them returning 
> with "EAGAIN (Resource temporarily unavailable)". The 
> frequency is about 10 per second.
> >
> > Is this a bug of strace or does the wrapper calls these 
> functions really that fast and why don't they block when 
> waiting for data?
> >
> > STATUS | wrapper  | 2009/07/10 12:04:50 | --> Wrapper 
> Started as Daemon
> > STATUS | wrapper  | 2009/07/10 12:04:50 | Java Service 
> Wrapper Standard Edition 64-bit 3.3.5
> >
> > Linux [...] 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 
> 2009 x86_64 GNU/Linux
> >
> > java version "1.6.0_21"
> > Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> > Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
> >
> > gettimeofday({1280134204, 517914}, NULL) = 0
> > read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN 
> (Resource temporarily unavailable)
> > gettimeofday({1280134204, 518004}, NULL) = 0
> > recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN 
> (Resource temporarily unavailable)
> > wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
> > nanosleep({0, 100000000}, NULL)         = 0
> > gettimeofday({1280134204, 618287}, NULL) = 0
> > read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN 
> (Resource temporarily unavailable)
> > gettimeofday({1280134204, 618392}, NULL) = 0
> > recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN 
> (Resource temporarily unavailable)
> > wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
> > nanosleep({0, 100000000}, NULL)         = 0
> > gettimeofday({1280134204, 718729}, NULL) = 0
> > read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN 
> (Resource temporarily unavailable)
> > gettimeofday({1280134204, 718831}, NULL) = 0
> > recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN 
> (Resource temporarily unavailable)
> > wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
> > nanosleep({0, 100000000}, NULL)         = 0
> > gettimeofday({1280134204, 819092}, NULL) = 0
> 
> --------------------------------------------------------------
> ----------------
> The Palm PDK Hot Apps Program offers developers who use the
> Plug-In Development Kit to bring their C/C++ apps to Palm for a share 
> of $1 Million in cash or HP Products. Visit us here for more details:
> http://ad.doubleclick.net/clk;226879339;13503038;l?
> http://clk.atdmt.com/CRS/go/247765532/direct/01/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> 

Re: [Wrapper-user] Many syscalls per second: EAGAIN (Resource temporarily unavailable)

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

Holger,
The Wrapper used to be a single threaded application.  Its main loop
still does non-blocking reads on the pipes and sockets. I believe this
is what you are seeing.

Is this causing any problems?  It is possible to change this logic and
use more dedicated threads if necessary.  I would appreciate your
input here.

Cheers,
Leif

On Mon, Jul 26, 2010 at 6:32 PM, Isenberg, Holger <ise...@e-...> wrote:
> Hallo,
>
> when monitoring the wrapper process with "strace -p Wrapper-PID" on Linux, I'm wondering about the high frequency of read() and recvfrom() calls on the pipe and TCP socket connection to the Java process and each of them returning with "EAGAIN (Resource temporarily unavailable)". The frequency is about 10 per second.
>
> Is this a bug of strace or does the wrapper calls these functions really that fast and why don't they block when waiting for data?
>
> STATUS | wrapper  | 2009/07/10 12:04:50 | --> Wrapper Started as Daemon
> STATUS | wrapper  | 2009/07/10 12:04:50 | Java Service Wrapper Standard Edition 64-bit 3.3.5
>
> Linux [...] 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 2009 x86_64 GNU/Linux
>
> java version "1.6.0_21"
> Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
> Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)
>
> gettimeofday({1280134204, 517914}, NULL) = 0
> read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN (Resource temporarily unavailable)
> gettimeofday({1280134204, 518004}, NULL) = 0
> recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
> wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
> nanosleep({0, 100000000}, NULL)         = 0
> gettimeofday({1280134204, 618287}, NULL) = 0
> read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN (Resource temporarily unavailable)
> gettimeofday({1280134204, 618392}, NULL) = 0
> recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
> wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
> nanosleep({0, 100000000}, NULL)         = 0
> gettimeofday({1280134204, 718729}, NULL) = 0
> read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN (Resource temporarily unavailable)
> gettimeofday({1280134204, 718831}, NULL) = 0
> recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
> wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
> nanosleep({0, 100000000}, NULL)         = 0
> gettimeofday({1280134204, 819092}, NULL) = 0

[Wrapper-user] Many syscalls per second: EAGAIN (Resource temporarily unavailable)

[Isenberg, H. <ise...@e-...>]

Hallo,

when monitoring the wrapper process with "strace -p Wrapper-PID" on Linux, I'm wondering about the high frequency of read() and recvfrom() calls on the pipe and TCP socket connection to the Java process and each of them returning with "EAGAIN (Resource temporarily unavailable)". The frequency is about 10 per second.

Is this a bug of strace or does the wrapper calls these functions really that fast and why don't they block when waiting for data?

STATUS | wrapper  | 2009/07/10 12:04:50 | --> Wrapper Started as Daemon
STATUS | wrapper  | 2009/07/10 12:04:50 | Java Service Wrapper Standard Edition 64-bit 3.3.5

Linux [...] 2.6.26-2-amd64 #1 SMP Wed Aug 19 22:33:18 UTC 2009 x86_64 GNU/Linux

java version "1.6.0_21"
Java(TM) SE Runtime Environment (build 1.6.0_21-b06)
Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)

gettimeofday({1280134204, 517914}, NULL) = 0
read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1280134204, 518004}, NULL) = 0
recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
nanosleep({0, 100000000}, NULL)         = 0
gettimeofday({1280134204, 618287}, NULL) = 0
read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1280134204, 618392}, NULL) = 0
recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
nanosleep({0, 100000000}, NULL)         = 0
gettimeofday({1280134204, 718729}, NULL) = 0
read(5, 0x7fff030c5130, 1024)           = -1 EAGAIN (Resource temporarily unavailable)
gettimeofday({1280134204, 718831}, NULL) = 0
recvfrom(7, 0x7fff030c554f, 1, 0, 0, 0) = -1 EAGAIN (Resource temporarily unavailable)
wait4(30121, 0x7fff030c5544, WNOHANG|WSTOPPED, NULL) = 0
nanosleep({0, 100000000}, NULL)         = 0
gettimeofday({1280134204, 819092}, NULL) = 0

Re: [Wrapper-user] UnsupportedClassVersionError

[Tasso A. <ta...@rb...>]

Yes. In addition...

The wrapper is installed on a server machine...

So in my dev computer when I go to cmd and type

Java -version I get 

Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)

On the server I get...

Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)

But %JAVA_HOME% on the server is set to jdk 1.5 Interesting, when you
install JRE it overrides the JAVA_HOME and PATH variables on Windows.

Ok I will set the proper JAVA_HOME thanks


Thanks

-----Original Message-----
From: Niambh Scullion [mailto:NSc...@cu...] 
Sent: Friday, July 23, 2010 11:00 AM
To: wra...@li...
Subject: Re: [Wrapper-user] UnsupportedClassVersionError

Have you this property set 
wrapper.java.command=%JAVA_HOME%\bin\java

N..

-----Original Message-----
From: Tasso Angelidis [mailto:ta...@rb...] 
Sent: 23 July 2010 15:56
To: wra...@li...
Subject: Re: [Wrapper-user] UnsupportedClassVersionError

My wrapper.conf doesn't specify the version.

The only jre installed in eclipse (Windows, Preferences, Installed JREs)
is jre6 and  it's pointing to the JRE not the JDK

-----Original Message-----
From: Niambh Scullion [mailto:NSc...@cu...] 
Sent: Friday, July 23, 2010 10:40 AM
To: wra...@li...
Subject: Re: [Wrapper-user] UnsupportedClassVersionError

Can you check what version of java you built the application with and is
it the same version of java that is set in the wrapper.conf.

Niambh


-----Original Message-----
From: Tasso Angelidis [mailto:ta...@rb...] 
Sent: 23 July 2010 15:15
To: wra...@li...
Subject: [Wrapper-user] UnsupportedClassVersionError

Hi I tried wrapper 3.3.9 and the latest 3.5.2

My application was working a couple of weeks ago until I had to rebuild
my application jar and now I'm getting...

INFO   | jvm 1    | 2010/07/22 16:48:15 | WrapperSimpleApp: Class
com.mycom.MyApp found but could not be initialized:
java.lang.UnsupportedClassVersionError: Bad version number in .class
file

I'm using JDK 1.6u20 b02

The application inside eclipse works fine.




------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


The information in this email is confidential and may be legally
privileged.
It is intended solely for the addressee. Access to this email by anyone
else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank
you.


------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


The information in this email is confidential and may be legally
privileged.
It is intended solely for the addressee. Access to this email by anyone
else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank
you.


------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] UnsupportedClassVersionError

[Niambh S. <NSc...@cu...>]

Have you this property set 
wrapper.java.command=%JAVA_HOME%\bin\java

N..

-----Original Message-----
From: Tasso Angelidis [mailto:ta...@rb...] 
Sent: 23 July 2010 15:56
To: wra...@li...
Subject: Re: [Wrapper-user] UnsupportedClassVersionError

My wrapper.conf doesn't specify the version.

The only jre installed in eclipse (Windows, Preferences, Installed JREs)
is jre6 and  it's pointing to the JRE not the JDK

-----Original Message-----
From: Niambh Scullion [mailto:NSc...@cu...] 
Sent: Friday, July 23, 2010 10:40 AM
To: wra...@li...
Subject: Re: [Wrapper-user] UnsupportedClassVersionError

Can you check what version of java you built the application with and is
it the same version of java that is set in the wrapper.conf.

Niambh


-----Original Message-----
From: Tasso Angelidis [mailto:ta...@rb...] 
Sent: 23 July 2010 15:15
To: wra...@li...
Subject: [Wrapper-user] UnsupportedClassVersionError

Hi I tried wrapper 3.3.9 and the latest 3.5.2

My application was working a couple of weeks ago until I had to rebuild
my application jar and now I'm getting...

INFO   | jvm 1    | 2010/07/22 16:48:15 | WrapperSimpleApp: Class
com.mycom.MyApp found but could not be initialized:
java.lang.UnsupportedClassVersionError: Bad version number in .class
file

I'm using JDK 1.6u20 b02

The application inside eclipse works fine.




------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


The information in this email is confidential and may be legally
privileged.
It is intended solely for the addressee. Access to this email by anyone
else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank
you.


------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.

Re: [Wrapper-user] UnsupportedClassVersionError

[Tasso A. <ta...@rb...>]

My wrapper.conf doesn't specify the version.

The only jre installed in eclipse (Windows, Preferences, Installed JREs)
is jre6 and  it's pointing to the JRE not the JDK

-----Original Message-----
From: Niambh Scullion [mailto:NSc...@cu...] 
Sent: Friday, July 23, 2010 10:40 AM
To: wra...@li...
Subject: Re: [Wrapper-user] UnsupportedClassVersionError

Can you check what version of java you built the application with and is
it the same version of java that is set in the wrapper.conf.

Niambh


-----Original Message-----
From: Tasso Angelidis [mailto:ta...@rb...] 
Sent: 23 July 2010 15:15
To: wra...@li...
Subject: [Wrapper-user] UnsupportedClassVersionError

Hi I tried wrapper 3.3.9 and the latest 3.5.2

My application was working a couple of weeks ago until I had to rebuild
my application jar and now I'm getting...

INFO   | jvm 1    | 2010/07/22 16:48:15 | WrapperSimpleApp: Class
com.mycom.MyApp found but could not be initialized:
java.lang.UnsupportedClassVersionError: Bad version number in .class
file

I'm using JDK 1.6u20 b02

The application inside eclipse works fine.




------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


The information in this email is confidential and may be legally
privileged.
It is intended solely for the addressee. Access to this email by anyone
else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank
you.


------------------------------------------------------------------------
------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] UnsupportedClassVersionError

[Niambh S. <NSc...@cu...>]

Can you check what version of java you built the application with and is it the same version of java that is set in the wrapper.conf.

Niambh


-----Original Message-----
From: Tasso Angelidis [mailto:ta...@rb...] 
Sent: 23 July 2010 15:15
To: wra...@li...
Subject: [Wrapper-user] UnsupportedClassVersionError

Hi I tried wrapper 3.3.9 and the latest 3.5.2

My application was working a couple of weeks ago until I had to rebuild
my application jar and now I'm getting...

INFO   | jvm 1    | 2010/07/22 16:48:15 | WrapperSimpleApp: Class
com.mycom.MyApp found but could not be initialized:
java.lang.UnsupportedClassVersionError: Bad version number in .class
file

I'm using JDK 1.6u20 b02

The application inside eclipse works fine.




------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in reliance
on it, is prohibited and may be unlawful. If you are not the intended
addressee please contact the sender and dispose of this e-mail. Thank you.

[Wrapper-user] UnsupportedClassVersionError

[Tasso A. <ta...@rb...>]

Hi I tried wrapper 3.3.9 and the latest 3.5.2

My application was working a couple of weeks ago until I had to rebuild
my application jar and now I'm getting...

INFO   | jvm 1    | 2010/07/22 16:48:15 | WrapperSimpleApp: Class
com.mycom.MyApp found but could not be initialized:
java.lang.UnsupportedClassVersionError: Bad version number in .class
file

I'm using JDK 1.6u20 b02

The application inside eclipse works fine.

[Wrapper-user] 64bit VM with 32bit wrapper

[Tasso A. <ta...@rb...>]

If you are running 64 bit JAVA with 32 bit wrapper you get an error that
the wrapper.dll cannot be loaded. But does it really matter or affect
anything? It seems to work anyways...

Re: [Wrapper-user] How to accept 32 bit java on 64 bit OS

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

No problem, glad it worked for you.
Let us know if you have any other questions.

That feature was added to actually try and make it easier for users to
run the correct version of the JVM with the Wrapper being used.  If
you ran the 32 bit Wrapper then it would have worked.   The 32-bit JVM
is going to require the 32-bit .so file.  It may be that you are using
the Delta pack.  If so, you may wish to simply remove the 64-bit
Wrapper binaries so the scripts use the 32-bit versions.

Cheers,
Leif

On Thu, Jul 15, 2010 at 12:27 AM, drekbour <dre...@fa...> wrote:
> Thanks, that was an easy RTFM for you.  Will do better next time!

-- 
Leif Mortenson
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel/Fax: +81-3-3878-3211
http://www.tanukisoftware.com
lei...@ta...

Re: [Wrapper-user] How to accept 32 bit java on 64 bit OS

[drekbour <dre...@fa...>]

Thanks, that was an easy RTFM for you.  Will do better next time!

-- 
http://www.fastmail.fm - The professional email service

Re: [Wrapper-user] How to accept 32 bit java on 64 bit OS

[Christian M. <chr...@ta...>]

Hi,

you might want to have a look at the auto bits property:
http://wrapper.tanukisoftware.com/doc/english/prop-java-additional-auto-bits.html


Cheers,
Christian

On Wed, Jul 14, 2010 at 11:53 PM, drekbour <dre...@fa...> wrote:
> I have been trying to install JSW onto a 64bit Solaris box that just
> happened to have a 32bit java installed.  There is nothing illegal about
> this combination but I cannot find how to stop JSW insisting on
> attempting a 64bit invocation which ends up looking rather like this:
>
> bash-3.00# isainfo -b
> 64
> bash-3.00# java -d64 -version
> execve(): No such file or directory
> Error trying to exec /usr/jdk/instances/jdk1.6.0/bin/amd64/java.
> Check if file exists and permissions are set correctly.
> Failed to start a 64-bit JVM process from a 32-bit JVM.
> Either 64-bit processes are not supported by this platform
> or the 64-bit components have not been installed.
>
> Any thoughts or is it not currently possible to override this behaviour?
>
> --
> http://www.fastmail.fm - The professional email service
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] How to enable jmx

[Sabyasachi B. <sab...@gm...>]

Hi,

I am trying to use the wrapper to expose our application as a windows
service . I am stuck in one point , how to enable enable jmx monitoring for
the application .
I have tried setting the following in the wrapper.conf

wrapper.java.additional.4=-Dcom.sun.management.jmxremote
wrapper.java.additional.5=-Dcom.sun.management.jmxremote.port=8812
wrapper.java.additional.6=-Dcom.sun.management.jmxremote.authenticate=false
(I have other jvm properties as well)
But, whenever I tried to access the application management through jconsole
, I am getting a connection failure.

I am using  Java Service Wrapper Community Edition 3.3.2 with JDK 1.6.

Is there anything special I need to do. Please can you advice.

Thank you in advance.

Regards,
Saby...

[Wrapper-user] How to accept 32 bit java on 64 bit OS

[drekbour <dre...@fa...>]

I have been trying to install JSW onto a 64bit Solaris box that just
happened to have a 32bit java installed.  There is nothing illegal about
this combination but I cannot find how to stop JSW insisting on
attempting a 64bit invocation which ends up looking rather like this:

bash-3.00# isainfo -b
64
bash-3.00# java -d64 -version
execve(): No such file or directory
Error trying to exec /usr/jdk/instances/jdk1.6.0/bin/amd64/java.
Check if file exists and permissions are set correctly.
Failed to start a 64-bit JVM process from a 32-bit JVM.
Either 64-bit processes are not supported by this platform
or the 64-bit components have not been installed.

Any thoughts or is it not currently possible to override this behaviour?

-- 
http://www.fastmail.fm - The professional email service