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

Re: [Wrapper-user] Question: how to invoke API from one wrapper to another?

[Uri S. <ur...@no...>]

Hi Leif, 

Thanks a lot for the help on this matter (I was able to overcome my issue in
another way, but still good to know!)

Uri




-----Original Message-----
From: Leif Mortenson [mailto:lei...@ta...] 
Sent: Monday, December 29, 2008 6:32 AM
To: wra...@li...
Subject: Re: [Wrapper-user] Question: how to invoke API from one wrapper to
another?

Uri,
This is possible on Windows by making use of the
WrapperManager.sendServiceControlCode(...) method.   The methods to
access services require that a SecurityManager be set in the JVM.
The documentation on this is still quite weak on the web site.  I have
summarized the process below.

Setting the security manager:
1) In the Wrapper.conf file, add the following lines:
---
wrapper.java.additional.1=-Djava.security.manager
wrapper.java.additional.2=-Djava.security.policy=../conf/java.policy
---
The first tells Java to use a security manager.  The second specifies
where the java policy file is located.
When you set a security manager, you are in effect overriding Java's
default security policy.   Many things that normally work will start
throwing security errors unless those functions are specifically
authorized in the policy file.

2) Create the java.policy file so it contains at least the following:
---
// Give Wrapper classes full permissions
grant codeBase "file:../lib/wrapper.jar" {
	permission java.security.AllPermission;
};

// Grant various permissions to a specific service.
grant codeBase "file:../lib/-" {
	permission
org.tanukisoftware.wrapper.security.WrapperServicePermission
"myservice", "interrogate,start,stop";
};
---
The first block lets the classes wrapper.jar do anything.  This is
advised as the Wrapper needs to be able to launch your entire
application meaning that anything your application does is originating
from the Wrapper.

The second block means that any other classes in jars in your lib
directory are able to make calls to interrogate, start, and stop the
"myservice" service via the Wrapper.   If this is not there then the
calls will result in SecurityExceptions being thrown.

Please let me know if you have any questions,
Cheers,
Leif


On Sun, Dec 28, 2008 at 3:51 PM, Uri Scheiner <ur...@no...> wrote:
> Hi All,
>
>
>
> I would like to use 2 different instances of wrappers in my application.
>  Part of the functionality that I need, is that one wrapper will be able
to
> control the other (stop, start, get its status, etc).
>
> Can anyone suggest how to do it?
>
> Thanks,
>
>  Uri

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

----------------------------------------------------------------------------
--
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] java.io.IOException: The handle is invalid

[Sou V. <sv...@mi...>]

Leif,

java version "1.6.0_11"
windows xp sp2

When will 3.3.2 be released?

Thanks,

Sou

-----Original Message-----
From: Leif Mortenson [mailto:lei...@ta...] 
Sent: Thursday, December 25, 2008 7:59 PM
To: wra...@li...
Subject: Re: [Wrapper-user] java.io.IOException: The handle is invalid

Sal,
Sorry for the trouble.  We had another user report this problem
earlier as well.    Could you please tell me the exact version of Java
you are running along with the platform?

The Wrapper makes it possible to read console input through the
Wrapper but for some reason, some JVMs seem to be having a problem
with this feature.

If you run the TestWrapper batch file that comes with the wrapper you
should see a dialog with several buttons.   The one labeled "Console"
lets you test this read feature.  On our tests, it is working
correctly.

3.3.2 which will be released soon contains a new property to work
around this problem:
wrapper.disable_console_input=TRUE

You can try out the latest development build if you like:
http://wrapper.tanukisoftware.org/download/3.3.2-e/wrapper-windows-x86-3
2-3.3.2-e.zip

Cheers,
Leif

On Wed, Dec 24, 2008 at 6:00 AM, Sou Vang <sv...@mi...> wrote:
> Hi all,
>
>
>
> I am getting an error (java.io.IOException: The handle is invalid) on
> System.in.read() when executing "net start MyService".
>
>
>
> The weird thing is that it runs perfectly fine when I run the bat file
> "MyService.bat".
>
>
>
> I have no idea why it would fail when starting the service after it
has been
> installed.
>
>
>
> Thanks in advance.
>
>
>
> Sou
>
>
------------------------------------------------------------------------
------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>



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

------------------------------------------------------------------------
------
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Question: how to invoke API from one wrapper to another?

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

Uri,
This is possible on Windows by making use of the
WrapperManager.sendServiceControlCode(...) method.   The methods to
access services require that a SecurityManager be set in the JVM.
The documentation on this is still quite weak on the web site.  I have
summarized the process below.

Setting the security manager:
1) In the Wrapper.conf file, add the following lines:
---
wrapper.java.additional.1=-Djava.security.manager
wrapper.java.additional.2=-Djava.security.policy=../conf/java.policy
---
The first tells Java to use a security manager.  The second specifies
where the java policy file is located.
When you set a security manager, you are in effect overriding Java's
default security policy.   Many things that normally work will start
throwing security errors unless those functions are specifically
authorized in the policy file.

2) Create the java.policy file so it contains at least the following:
---
// Give Wrapper classes full permissions
grant codeBase "file:../lib/wrapper.jar" {
	permission java.security.AllPermission;
};

// Grant various permissions to a specific service.
grant codeBase "file:../lib/-" {
	permission org.tanukisoftware.wrapper.security.WrapperServicePermission
"myservice", "interrogate,start,stop";
};
---
The first block lets the classes wrapper.jar do anything.  This is
advised as the Wrapper needs to be able to launch your entire
application meaning that anything your application does is originating
from the Wrapper.

The second block means that any other classes in jars in your lib
directory are able to make calls to interrogate, start, and stop the
"myservice" service via the Wrapper.   If this is not there then the
calls will result in SecurityExceptions being thrown.

Please let me know if you have any questions,
Cheers,
Leif


On Sun, Dec 28, 2008 at 3:51 PM, Uri Scheiner <ur...@no...> wrote:
> Hi All,
>
>
>
> I would like to use 2 different instances of wrappers in my application.
>  Part of the functionality that I need, is that one wrapper will be able to
> control the other (stop, start, get its status, etc).
>
> Can anyone suggest how to do it?
>
> Thanks,
>
>  Uri

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

[Wrapper-user] Question: how to invoke API from one wrapper to another?

[Uri S. <ur...@no...>]

Hi All, 

 

I would like to use 2 different instances of wrappers in my application.
Part of the functionality that I need, is that one wrapper will be able to
control the other (stop, start, get its status, etc).

Can anyone suggest how to do it? 

Thanks, 

 Uri

Re: [Wrapper-user] java.io.IOException: The handle is invalid

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

Sal,
Sorry for the trouble.  We had another user report this problem
earlier as well.    Could you please tell me the exact version of Java
you are running along with the platform?

The Wrapper makes it possible to read console input through the
Wrapper but for some reason, some JVMs seem to be having a problem
with this feature.

If you run the TestWrapper batch file that comes with the wrapper you
should see a dialog with several buttons.   The one labeled "Console"
lets you test this read feature.  On our tests, it is working
correctly.

3.3.2 which will be released soon contains a new property to work
around this problem:
wrapper.disable_console_input=TRUE

You can try out the latest development build if you like:
http://wrapper.tanukisoftware.org/download/3.3.2-e/wrapper-windows-x86-32-3.3.2-e.zip

Cheers,
Leif

On Wed, Dec 24, 2008 at 6:00 AM, Sou Vang <sv...@mi...> wrote:
> Hi all,
>
>
>
> I am getting an error (java.io.IOException: The handle is invalid) on
> System.in.read() when executing "net start MyService".
>
>
>
> The weird thing is that it runs perfectly fine when I run the bat file
> "MyService.bat".
>
>
>
> I have no idea why it would fail when starting the service after it has been
> installed.
>
>
>
> Thanks in advance.
>
>
>
> Sou
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>



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

Re: [Wrapper-user] Installing service as Network Service

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

Pavel,
There are also a few properties available which make it possible to
set the password.  The first sets it directly in the wrapper.conf
file.
http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-password.html

Towards the bottom of the page, you will find recommendations on how
to hide your password in case you want to avoid having it in your
wrapper.conf file directly.

Cheers,
Leif

On Wed, Dec 24, 2008 at 8:26 PM,  <pav...@gm...> wrote:
> Hi.
> I need to install my service as a Network Service with specific user
> profile.
> The user is exist and has all permissions.
> I want to define the user with "wrapper.ntservice.account" property.
> According to documentation - this property get {domain name}\{user name}
> arguments. My question is: How may I pass user's password with this
> property.
> Thank you.
> Pavel.
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>



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

[Wrapper-user] Installing service as Network Service

[<pav...@gm...>]

Hi.
I need to install my service as a Network Service with specific user  
profile.
The user is exist and has all permissions.
I want to define the user with "wrapper.ntservice.account" property.  
According to documentation - this property get {domain name}\{user name}  
arguments. My question is: How may I pass user's password with this  
property.
Thank you.
Pavel.

[Wrapper-user] java.io.IOException: The handle is invalid

[Sou V. <sv...@mi...>]

Hi all,

 

I am getting an error (java.io.IOException: The handle is invalid) on
System.in.read() when executing "net start MyService".

 

The weird thing is that it runs perfectly fine when I run the bat file
"MyService.bat".

 

I have no idea why it would fail when starting the service after it has
been installed.

 

Thanks in advance.

 

Sou

Re: [Wrapper-user] Installing service as Network Service

[Malia N. <mn...@us...>]

Thank you so much Leif!  That worked!  And yes, adding this to the 
documentation would certainly help future users. 

Thanks again,
-Malia





"Leif Mortenson" <le...@ta...> 
12/20/2008 11:59 AM
Please respond to
wra...@li...


To
wra...@li...
cc

Subject
Re: [Wrapper-user] Installing service as Network Service






Malia,
I will add something to the documentation about this, but you can do
this by setting the following in the wrapper.conf file.
wrapper.ntservice.account=NT AUTHORITY\NetworkService

Note that you will have to uninstall and then reinstall the wrapper as
a service for this change to take effect.

Cheers,
Leif


On Sat, Dec 20, 2008 at 3:45 AM, Malia Noori <mn...@us...> wrote:
>
> I need to install my service as a Network Service instead of the default
> Local System.  From the documentation, it seems that if I enter a login
> account in the property wrapper.ntservice.account then the service is
> installed under that account.  But I don't want to specify a specific 
login
> account/password.  I just want to install it as a Network Service.  How 
can
> I do that?  I would appreciate your help.
>
> Thanks,
> Malia
> 
------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>



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

------------------------------------------------------------------------------
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Installing service as Network Service

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

Malia,
I will add something to the documentation about this, but you can do
this by setting the following in the wrapper.conf file.
wrapper.ntservice.account=NT AUTHORITY\NetworkService

Note that you will have to uninstall and then reinstall the wrapper as
a service for this change to take effect.

Cheers,
Leif


On Sat, Dec 20, 2008 at 3:45 AM, Malia Noori <mn...@us...> wrote:
>
> I need to install my service as a Network Service instead of the default
> Local System.  From the documentation, it seems that if I enter a login
> account in the property wrapper.ntservice.account then the service is
> installed under that account.  But I don't want to specify a specific login
> account/password.  I just want to install it as a Network Service.  How can
> I do that?  I would appreciate your help.
>
> Thanks,
> Malia
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>



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

[Wrapper-user] Installing service as Network Service

[Malia N. <mn...@us...>]

I need to install my service as a Network Service instead of the default 
Local System.  From the documentation, it seems that if I enter a login 
account in the property wrapper.ntservice.account then the service is 
installed under that account.  But I don't want to specify a specific 
login account/password.  I just want to install it as a Network Service. 
How can I do that?  I would appreciate your help.

Thanks,
Malia

Re: [Wrapper-user] Wrapper not respecting wrapper.restart.delay

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

Matt,
Thanks for your support.  Unfortunately, that shows that the restart
feature failed for you.   I would suggest at some point upgrading to a
newer version.  There have been several problems fixed in 3.3.0 and
3.3.1 which may affect you, including the mentioned issue which may
have been causing this problem.   See the release notes on our site.
http://wrapper.tanukisoftware.org/doc/english/release-notes.html

Let me know if you have any other questions,

Cheers,
Leif

On Tue, Dec 16, 2008 at 12:44 AM, Matt Pierce <Mat...@co...> wrote:
> Leif,
>
> Thanks for the quick and thorough response!  Unfortunately it's going to
> be difficult to reproduce.  This was only happening on our production
> instance and we've now fixed the root cause of the JVM hangage.  The
> effort to create the same set of circumstances in a test environment is
> large enough that it won't realistically ever be given priority unless
> we start having production issues again.  I was hoping to hear about a
> quick-win known issue but apparently it's not going to be that easy.
>
> I think we're going to have to table indefinitely figuring this out.
> Again, thanks for the effort--it's what I use as an argument to
> management to keep using the wrapper when we have issues like this one.
> Sorry to leave you with a mystery!
>
> --matt
>
> -----Original Message-----
> From: Leif Mortenson [mailto:lei...@ta...]
> Sent: Friday, December 12, 2008 9:23 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Wrapper not respecting wrapper.restart.delay
>
> Matt,
> I just went back and retested this with 3.2.3 and appears to be working
> as expected.  The following log shows a normal restart with the
> wrapper.restart.delay=30 property set:
>
> ---
> STATUS | wrapper  | 2008/12/13 11:01:52 | JVM requested a restart.
> INFO   | jvm 1    | 2008/12/13 11:01:53 | stop(0)
> STATUS | wrapper  | 2008/12/13 11:02:24 | Launching a JVM...
> ---
>
> This second test is for the case where the JVM is frozen and is forcibly
> killed.
>
> ---
> ERROR  | wrapper  | 2008/12/13 11:07:01 | JVM appears hung: Timed out
> waiting for signal from JVM.
> ERROR  | wrapper  | 2008/12/13 11:07:01 | JVM did not exit on request,
> terminated
> INFO   | wrapper  | 2008/12/13 11:07:01 | JVM exited on its own while
> waiting to kill the application.
> STATUS | wrapper  | 2008/12/13 11:07:01 | JVM exited in response to
> signal SIGKILL (9).
> STATUS | wrapper  | 2008/12/13 11:07:30 | Launching a JVM...
> ---
>
> Your configuration file appears to be correct.  From the log fragment
> you sent, it is not even waiting for the default 5 seconds.
>
> There was a related bug fixed in 3.3.0 which you may be seeing here:
> ---
> Fix a problem where the UNIX versions of the Wrapper would shutdown
> rather than restarting a frozen JVM if the arrival of the SIGCHLD signal
> from the old JVM process was delayed by more than a second or two.
> ---
>
> The "Unable to start a JVM" message shows up when the attempt to execute
> the JVM process is failing.  That does not explain why it is happening
> immediately rather than after a 30 second wait.
>
> Is this a problem that you are able to reproduce?  If so, would it be
> possible for you set the wrapper.debug=true property then send me the
> log file?  The log file would contain information that would help me
> narrow this down.
>
> If this is reproduceable it would also be useful to see the debug output
> using version 3.3.1.
>
> Thanks in advance,
> Leif
>
>
>
> On Sat, Dec 13, 2008 at 4:29 AM, Matt Pierce <Mat...@co...>
> wrote:
>> I am using wrapper version 3.2.3 for an app running on Java Version:
>> 1.6.0_04-b12 Java HotSpot(TM) Server VM on Redhat Enterprise
>> 2.6.18-53.el5xen.  I am having a problem I have seen in many other
>> forums, which has the following signature:
>>
>> ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM appears hung: Timed out
>> waiting for signal from JVM.
>> ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM did not exit on request,
>
>> terminated STATUS | wrapper  | 2008/12/11 08:04:01 | JVM exited in
>> response to signal SIGKILL (9).
>> ERROR  | wrapper  | 2008/12/11 08:04:01 | Unable to start a JVM
>>
>> The explanation in the other cases is that there are resources which
>> have not been freed up when the wrapper tries to restart.  The fix
>> suggested is to set the wrapper.restart.delay property to some value
>> high enough for the resources to be freed again.  I have set it to 30,
>
>> but it doesn't seem to be taking effect.  The output from my log above
>
>> is from after having set the property and restarted the app with the
>> wrapper.  Below is the content of our wrapper.conf.  Any suggestions
> would be appreciated!
>>
>> Thanks,
>> Matt Pierce
>>
>> #********************************************************************
>> # Wrapper Properties
>> #********************************************************************
>> # Java Application
>> wrapper.java.command=%JAVA_HOME%/bin/java
>>
>> # 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.tanukisoftware.wrapper.WrapperStartStopApp
>>
>> # Java Classpath (include wrapper.jar)  Add class path elements as #
>> needed starting from 1 wrapper.java.classpath.1=../wrapper/wrapper.jar
>> wrapper.java.classpath.2=../bin/bootstrap.jar
>> wrapper.java.classpath.3=../bin/commons-logging-api.jar
>> wrapper.java.classpath.4=%JAVA_HOME%/lib/tools.jar
>>
>> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
>> wrapper.java.library.path.1=../wrapper
>> wrapper.java.library.path.2=../webapps/catalog_engine/WEB-INF/lib
>>
>> # Java Additional Parameters
>> wrapper.java.additional.1=-server
>> wrapper.java.additional.2=-Dapp=CATENGINE
>> wrapper.java.additional.3=-Djava.endorsed.dirs=/home/catengine/tomcat/
>> common/endorsed
>> wrapper.java.additional.4=-Dcatalina.base=/home/catengine/tomcat
>> wrapper.java.additional.5=-Dcatalina.home=/home/catengine/tomcat
>> wrapper.java.additional.6=-Djava.io.tmpdir=/home/catengine/tomcat/temp
>> #wrapper.java.additional.7=-XX:+DisableExplicitGC
>> wrapper.java.additional.7=-Dmail.smtp.connectiontimeout=300000
>> wrapper.java.additional.8=-Dmail.smtp.timeout=300000
>> #wrapper.java.additional.10=-XX:-OmitStackTraceInFastThrow
>> #wrapper.java.additional.10=-XX:SurvivorRatio=6
>> #wrapper.java.additional.11=-XX:MaxNewSize=384M
>> wrapper.java.additional.9=-Xss256k
>> wrapper.java.additional.10=-XX:NewSize=768M
>> wrapper.java.additional.11=-XX:MaxNewSize=768M
>> wrapper.java.additional.12=-XX:+UseConcMarkSweepGC
>> wrapper.java.additional.13=-Djava.net.preferIPv4Stack=true
>> wrapper.java.additional.14=-Dcom.sun.management.jmxremote
>> wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1099
>> wrapper.java.additional.16=-Dcom.sun.management.jmxremote.authenticate
>> =true
>> wrapper.java.additional.17=-Dcom.sun.management.jmxremote.ssl=false
>> wrapper.java.additional.18=-Dcom.sun.management.jmxremote.password.fil
>> e=/home/catengine/jmxremote.password
>> wrapper.java.additional.19=-verbose:gc
>> wrapper.java.additional.20=-XX:+PrintGCDetails
>>
>> # Initial Java Heap Size (in MB)
>> wrapper.java.initmemory=2560
>>
>> # Maximum Java Heap Size (in MB)
>> wrapper.java.maxmemory=2560
>>
>> # Application parameters.  Add parameters as needed starting from 1
>> wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
>> wrapper.app.parameter.2=1
>> wrapper.app.parameter.3=start
>> wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
>> wrapper.app.parameter.5=true
>> wrapper.app.parameter.6=1
>> wrapper.app.parameter.7=stop
>>
>> #********************************************************************
>> # Wrapper Logging Properties
>> #********************************************************************
>> # 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=DEBUG
>>
>> # Log file to use for wrapper output logging.
>> wrapper.logfile=../logs/wrapper.log
>>
>> # Format of output for the log file.  (See docs for formats)
>> wrapper.logfile.format=LPTM
>>
>> # Log Level for log file output.  (See docs for log levels)
>> #wrapper.logfile.loglevel=DEBUG 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=50m
>>
>> # 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=10
>>
>> # Log Level for sys/event log output.  (See docs for log levels)
>> wrapper.syslog.loglevel=ERROR
>>
>> #********************************************************************
>> # Wrapper NT 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.
>>
>> wrapper.ping.timeout=300
>>
>> # Name of the service
>> wrapper.ntservice.name=prodtomcat
>>
>> # Display name of the service
>> wrapper.ntservice.displayname=Production Tomcat
>>
>> # Description of the service
>> wrapper.ntservice.description=Production Tomcat
>>
>> # Service dependencies.  Add dependencies as needed starting from 1
>> wrapper.ntservice.dependency.1=
>>
>> # Mode in which the service is installed.  AUTO_START or DEMAND_START
>> wrapper.ntservice.starttype=AUTO_START
>>
>> # Allow the service to interact with the desktop.
>> wrapper.ntservice.interactive=false
>>
>> wrapper.restart.delay=30

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

Re: [Wrapper-user] Wrapper not respecting wrapper.restart.delay

[Matt P. <Mat...@co...>]

Leif,

Thanks for the quick and thorough response!  Unfortunately it's going to
be difficult to reproduce.  This was only happening on our production
instance and we've now fixed the root cause of the JVM hangage.  The
effort to create the same set of circumstances in a test environment is
large enough that it won't realistically ever be given priority unless
we start having production issues again.  I was hoping to hear about a
quick-win known issue but apparently it's not going to be that easy.

I think we're going to have to table indefinitely figuring this out.
Again, thanks for the effort--it's what I use as an argument to
management to keep using the wrapper when we have issues like this one.
Sorry to leave you with a mystery!

--matt

-----Original Message-----
From: Leif Mortenson [mailto:lei...@ta...] 
Sent: Friday, December 12, 2008 9:23 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Wrapper not respecting wrapper.restart.delay

Matt,
I just went back and retested this with 3.2.3 and appears to be working
as expected.  The following log shows a normal restart with the
wrapper.restart.delay=30 property set:

---
STATUS | wrapper  | 2008/12/13 11:01:52 | JVM requested a restart.
INFO   | jvm 1    | 2008/12/13 11:01:53 | stop(0)
STATUS | wrapper  | 2008/12/13 11:02:24 | Launching a JVM...
---

This second test is for the case where the JVM is frozen and is forcibly
killed.

---
ERROR  | wrapper  | 2008/12/13 11:07:01 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2008/12/13 11:07:01 | JVM did not exit on request,
terminated
INFO   | wrapper  | 2008/12/13 11:07:01 | JVM exited on its own while
waiting to kill the application.
STATUS | wrapper  | 2008/12/13 11:07:01 | JVM exited in response to
signal SIGKILL (9).
STATUS | wrapper  | 2008/12/13 11:07:30 | Launching a JVM...
---

Your configuration file appears to be correct.  From the log fragment
you sent, it is not even waiting for the default 5 seconds.

There was a related bug fixed in 3.3.0 which you may be seeing here:
---
Fix a problem where the UNIX versions of the Wrapper would shutdown
rather than restarting a frozen JVM if the arrival of the SIGCHLD signal
from the old JVM process was delayed by more than a second or two.
---

The "Unable to start a JVM" message shows up when the attempt to execute
the JVM process is failing.  That does not explain why it is happening
immediately rather than after a 30 second wait.

Is this a problem that you are able to reproduce?  If so, would it be
possible for you set the wrapper.debug=true property then send me the
log file?  The log file would contain information that would help me
narrow this down.

If this is reproduceable it would also be useful to see the debug output
using version 3.3.1.

Thanks in advance,
Leif



On Sat, Dec 13, 2008 at 4:29 AM, Matt Pierce <Mat...@co...>
wrote:
> I am using wrapper version 3.2.3 for an app running on Java Version:
> 1.6.0_04-b12 Java HotSpot(TM) Server VM on Redhat Enterprise 
> 2.6.18-53.el5xen.  I am having a problem I have seen in many other 
> forums, which has the following signature:
>
> ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM appears hung: Timed out 
> waiting for signal from JVM.
> ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM did not exit on request,

> terminated STATUS | wrapper  | 2008/12/11 08:04:01 | JVM exited in 
> response to signal SIGKILL (9).
> ERROR  | wrapper  | 2008/12/11 08:04:01 | Unable to start a JVM
>
> The explanation in the other cases is that there are resources which 
> have not been freed up when the wrapper tries to restart.  The fix 
> suggested is to set the wrapper.restart.delay property to some value 
> high enough for the resources to be freed again.  I have set it to 30,

> but it doesn't seem to be taking effect.  The output from my log above

> is from after having set the property and restarted the app with the 
> wrapper.  Below is the content of our wrapper.conf.  Any suggestions
would be appreciated!
>
> Thanks,
> Matt Pierce
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=%JAVA_HOME%/bin/java
>
> # 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.tanukisoftware.wrapper.WrapperStartStopApp
>
> # Java Classpath (include wrapper.jar)  Add class path elements as #  
> needed starting from 1 wrapper.java.classpath.1=../wrapper/wrapper.jar
> wrapper.java.classpath.2=../bin/bootstrap.jar
> wrapper.java.classpath.3=../bin/commons-logging-api.jar
> wrapper.java.classpath.4=%JAVA_HOME%/lib/tools.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so) 
> wrapper.java.library.path.1=../wrapper
> wrapper.java.library.path.2=../webapps/catalog_engine/WEB-INF/lib
>
> # Java Additional Parameters
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Dapp=CATENGINE
> wrapper.java.additional.3=-Djava.endorsed.dirs=/home/catengine/tomcat/
> common/endorsed 
> wrapper.java.additional.4=-Dcatalina.base=/home/catengine/tomcat
> wrapper.java.additional.5=-Dcatalina.home=/home/catengine/tomcat
> wrapper.java.additional.6=-Djava.io.tmpdir=/home/catengine/tomcat/temp
> #wrapper.java.additional.7=-XX:+DisableExplicitGC
> wrapper.java.additional.7=-Dmail.smtp.connectiontimeout=300000
> wrapper.java.additional.8=-Dmail.smtp.timeout=300000
> #wrapper.java.additional.10=-XX:-OmitStackTraceInFastThrow
> #wrapper.java.additional.10=-XX:SurvivorRatio=6
> #wrapper.java.additional.11=-XX:MaxNewSize=384M
> wrapper.java.additional.9=-Xss256k
> wrapper.java.additional.10=-XX:NewSize=768M
> wrapper.java.additional.11=-XX:MaxNewSize=768M
> wrapper.java.additional.12=-XX:+UseConcMarkSweepGC
> wrapper.java.additional.13=-Djava.net.preferIPv4Stack=true
> wrapper.java.additional.14=-Dcom.sun.management.jmxremote
> wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1099
> wrapper.java.additional.16=-Dcom.sun.management.jmxremote.authenticate
> =true 
> wrapper.java.additional.17=-Dcom.sun.management.jmxremote.ssl=false
> wrapper.java.additional.18=-Dcom.sun.management.jmxremote.password.fil
> e=/home/catengine/jmxremote.password
> wrapper.java.additional.19=-verbose:gc
> wrapper.java.additional.20=-XX:+PrintGCDetails
>
> # Initial Java Heap Size (in MB)
> wrapper.java.initmemory=2560
>
> # Maximum Java Heap Size (in MB)
> wrapper.java.maxmemory=2560
>
> # Application parameters.  Add parameters as needed starting from 1 
> wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.2=1
> wrapper.app.parameter.3=start
> wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.5=true
> wrapper.app.parameter.6=1
> wrapper.app.parameter.7=stop
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # 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=DEBUG
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=../logs/wrapper.log
>
> # Format of output for the log file.  (See docs for formats) 
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output.  (See docs for log levels) 
> #wrapper.logfile.loglevel=DEBUG 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=50m
>
> # 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=10
>
> # Log Level for sys/event log output.  (See docs for log levels) 
> wrapper.syslog.loglevel=ERROR
>
> #********************************************************************
> # Wrapper NT 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.
>
> wrapper.ping.timeout=300
>
> # Name of the service
> wrapper.ntservice.name=prodtomcat
>
> # Display name of the service
> wrapper.ntservice.displayname=Production Tomcat
>
> # Description of the service
> wrapper.ntservice.description=Production Tomcat
>
> # Service dependencies.  Add dependencies as needed starting from 1 
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START 
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>
> wrapper.restart.delay=30
> ----------------------------------------------------------------------
> -------- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las 
> Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to 
> help pave the way to the Next Web now. Learn more and register at 
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmi
> x.com/ _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

------------------------------------------------------------------------
------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
Nevada.
The future of the web can't happen without you.  Join us at MIX09 to
help pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.
com/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Wrapper not respecting wrapper.restart.delay

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

Matt,
I just went back and retested this with 3.2.3 and appears to be
working as expected.  The following log shows a normal restart with
the wrapper.restart.delay=30 property set:

---
STATUS | wrapper  | 2008/12/13 11:01:52 | JVM requested a restart.
INFO   | jvm 1    | 2008/12/13 11:01:53 | stop(0)
STATUS | wrapper  | 2008/12/13 11:02:24 | Launching a JVM...
---

This second test is for the case where the JVM is frozen and is forcibly killed.

---
ERROR  | wrapper  | 2008/12/13 11:07:01 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2008/12/13 11:07:01 | JVM did not exit on request,
terminated
INFO   | wrapper  | 2008/12/13 11:07:01 | JVM exited on its own while
waiting to kill the application.
STATUS | wrapper  | 2008/12/13 11:07:01 | JVM exited in response to
signal SIGKILL (9).
STATUS | wrapper  | 2008/12/13 11:07:30 | Launching a JVM...
---

Your configuration file appears to be correct.  From the log fragment
you sent, it is not even waiting for the default 5 seconds.

There was a related bug fixed in 3.3.0 which you may be seeing here:
---
Fix a problem where the UNIX versions of the Wrapper would shutdown
rather than restarting a frozen JVM if the arrival of the SIGCHLD
signal from the old JVM process was delayed by more than a second or
two.
---

The "Unable to start a JVM" message shows up when the attempt to
execute the JVM process is failing.  That does not explain why it is
happening immediately rather than after a 30 second wait.

Is this a problem that you are able to reproduce?  If so, would it be
possible for you set the wrapper.debug=true property then send me the
log file?  The log file would contain information that would help me
narrow this down.

If this is reproduceable it would also be useful to see the debug
output using version 3.3.1.

Thanks in advance,
Leif



On Sat, Dec 13, 2008 at 4:29 AM, Matt Pierce <Mat...@co...> wrote:
> I am using wrapper version 3.2.3 for an app running on Java Version:
> 1.6.0_04-b12 Java HotSpot(TM) Server VM on Redhat Enterprise
> 2.6.18-53.el5xen.  I am having a problem I have seen in many other forums,
> which has the following signature:
>
> ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM appears hung: Timed out
> waiting for signal from JVM.
> ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM did not exit on request,
> terminated
> STATUS | wrapper  | 2008/12/11 08:04:01 | JVM exited in response to signal
> SIGKILL (9).
> ERROR  | wrapper  | 2008/12/11 08:04:01 | Unable to start a JVM
>
> The explanation in the other cases is that there are resources which have
> not been freed up when the wrapper tries to restart.  The fix suggested is
> to set the wrapper.restart.delay property to some value high enough for the
> resources to be freed again.  I have set it to 30, but it doesn't seem to be
> taking effect.  The output from my log above is from after having set the
> property and restarted the app with the wrapper.  Below is the content of
> our wrapper.conf.  Any suggestions would be appreciated!
>
> Thanks,
> Matt Pierce
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=%JAVA_HOME%/bin/java
>
> # 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.tanukisoftware.wrapper.WrapperStartStopApp
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=../wrapper/wrapper.jar
> wrapper.java.classpath.2=../bin/bootstrap.jar
> wrapper.java.classpath.3=../bin/commons-logging-api.jar
> wrapper.java.classpath.4=%JAVA_HOME%/lib/tools.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../wrapper
> wrapper.java.library.path.2=../webapps/catalog_engine/WEB-INF/lib
>
> # Java Additional Parameters
> wrapper.java.additional.1=-server
> wrapper.java.additional.2=-Dapp=CATENGINE
> wrapper.java.additional.3=-Djava.endorsed.dirs=/home/catengine/tomcat/common/endorsed
> wrapper.java.additional.4=-Dcatalina.base=/home/catengine/tomcat
> wrapper.java.additional.5=-Dcatalina.home=/home/catengine/tomcat
> wrapper.java.additional.6=-Djava.io.tmpdir=/home/catengine/tomcat/temp
> #wrapper.java.additional.7=-XX:+DisableExplicitGC
> wrapper.java.additional.7=-Dmail.smtp.connectiontimeout=300000
> wrapper.java.additional.8=-Dmail.smtp.timeout=300000
> #wrapper.java.additional.10=-XX:-OmitStackTraceInFastThrow
> #wrapper.java.additional.10=-XX:SurvivorRatio=6
> #wrapper.java.additional.11=-XX:MaxNewSize=384M
> wrapper.java.additional.9=-Xss256k
> wrapper.java.additional.10=-XX:NewSize=768M
> wrapper.java.additional.11=-XX:MaxNewSize=768M
> wrapper.java.additional.12=-XX:+UseConcMarkSweepGC
> wrapper.java.additional.13=-Djava.net.preferIPv4Stack=true
> wrapper.java.additional.14=-Dcom.sun.management.jmxremote
> wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1099
> wrapper.java.additional.16=-Dcom.sun.management.jmxremote.authenticate=true
> wrapper.java.additional.17=-Dcom.sun.management.jmxremote.ssl=false
> wrapper.java.additional.18=-Dcom.sun.management.jmxremote.password.file=/home/catengine/jmxremote.password
> wrapper.java.additional.19=-verbose:gc
> wrapper.java.additional.20=-XX:+PrintGCDetails
>
> # Initial Java Heap Size (in MB)
> wrapper.java.initmemory=2560
>
> # Maximum Java Heap Size (in MB)
> wrapper.java.maxmemory=2560
>
> # Application parameters.  Add parameters as needed starting from 1
> wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.2=1
> wrapper.app.parameter.3=start
> wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
> wrapper.app.parameter.5=true
> wrapper.app.parameter.6=1
> wrapper.app.parameter.7=stop
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # 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=DEBUG
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=../logs/wrapper.log
>
> # Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output.  (See docs for log levels)
> #wrapper.logfile.loglevel=DEBUG
> 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=50m
>
> # 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=10
>
> # Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=ERROR
>
> #********************************************************************
> # Wrapper NT 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.
>
> wrapper.ping.timeout=300
>
> # Name of the service
> wrapper.ntservice.name=prodtomcat
>
> # Display name of the service
> wrapper.ntservice.displayname=Production Tomcat
>
> # Description of the service
> wrapper.ntservice.description=Production Tomcat
>
> # Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>
> wrapper.restart.delay=30
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] Wrapper not respecting wrapper.restart.delay

[Matt P. <Mat...@co...>]

I am using wrapper version 3.2.3 for an app running on Java Version:
1.6.0_04-b12 Java HotSpot(TM) Server VM on Redhat Enterprise
2.6.18-53.el5xen.  I am having a problem I have seen in many other
forums, which has the following signature:
 
ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM appears hung: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2008/12/11 08:03:59 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2008/12/11 08:04:01 | JVM exited in response to
signal SIGKILL (9).
ERROR  | wrapper  | 2008/12/11 08:04:01 | Unable to start a JVM
 
The explanation in the other cases is that there are resources which
have not been freed up when the wrapper tries to restart.  The fix
suggested is to set the wrapper.restart.delay property to some value
high enough for the resources to be freed again.  I have set it to 30,
but it doesn't seem to be taking effect.  The output from my log above
is from after having set the property and restarted the app with the
wrapper.  Below is the content of our wrapper.conf.  Any suggestions
would be appreciated!
 
Thanks,
Matt Pierce
 
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=%JAVA_HOME%/bin/java
 
# 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.tanukisoftware.wrapper.WrapperStartStopApp
 

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=../wrapper/wrapper.jar
wrapper.java.classpath.2=../bin/bootstrap.jar
wrapper.java.classpath.3=../bin/commons-logging-api.jar
wrapper.java.classpath.4=%JAVA_HOME%/lib/tools.jar
 

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../wrapper
wrapper.java.library.path.2=../webapps/catalog_engine/WEB-INF/lib
 

# Java Additional Parameters
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Dapp=CATENGINE
wrapper.java.additional.3=-Djava.endorsed.dirs=/home/catengine/tomcat/co
mmon/endorsed
wrapper.java.additional.4=-Dcatalina.base=/home/catengine/tomcat
wrapper.java.additional.5=-Dcatalina.home=/home/catengine/tomcat
wrapper.java.additional.6=-Djava.io.tmpdir=/home/catengine/tomcat/temp
#wrapper.java.additional.7=-XX:+DisableExplicitGC
wrapper.java.additional.7=-Dmail.smtp.connectiontimeout=300000
wrapper.java.additional.8=-Dmail.smtp.timeout=300000
#wrapper.java.additional.10=-XX:-OmitStackTraceInFastThrow
#wrapper.java.additional.10=-XX:SurvivorRatio=6
#wrapper.java.additional.11=-XX:MaxNewSize=384M
wrapper.java.additional.9=-Xss256k
wrapper.java.additional.10=-XX:NewSize=768M
wrapper.java.additional.11=-XX:MaxNewSize=768M
wrapper.java.additional.12=-XX:+UseConcMarkSweepGC
wrapper.java.additional.13=-Djava.net.preferIPv4Stack=true
wrapper.java.additional.14=-Dcom.sun.management.jmxremote
wrapper.java.additional.15=-Dcom.sun.management.jmxremote.port=1099
wrapper.java.additional.16=-Dcom.sun.management.jmxremote.authenticate=t
rue
wrapper.java.additional.17=-Dcom.sun.management.jmxremote.ssl=false
wrapper.java.additional.18=-Dcom.sun.management.jmxremote.password.file=
/home/catengine/jmxremote.password
wrapper.java.additional.19=-verbose:gc
wrapper.java.additional.20=-XX:+PrintGCDetails
 
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=2560
 
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=2560
 
# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
wrapper.app.parameter.2=1
wrapper.app.parameter.3=start
wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
wrapper.app.parameter.5=true
wrapper.app.parameter.6=1
wrapper.app.parameter.7=stop
 
#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# 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=DEBUG
 
# Log file to use for wrapper output logging.
wrapper.logfile=../logs/wrapper.log
 
# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=LPTM
 
# Log Level for log file output.  (See docs for log levels)
#wrapper.logfile.loglevel=DEBUG
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=50m
 
# 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=10
 
# Log Level for sys/event log output.  (See docs for log levels)
wrapper.syslog.loglevel=ERROR
 
#********************************************************************
# Wrapper NT 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.
 
wrapper.ping.timeout=300
 
# Name of the service
wrapper.ntservice.name=prodtomcat
 
# Display name of the service
wrapper.ntservice.displayname=Production Tomcat
 
# Description of the service
wrapper.ntservice.description=Production Tomcat
 
# Service dependencies.  Add dependencies as needed starting from 1
wrapper.ntservice.dependency.1=
 
# Mode in which the service is installed.  AUTO_START or DEMAND_START
wrapper.ntservice.starttype=AUTO_START
 
# Allow the service to interact with the desktop.
wrapper.ntservice.interactive=false
 

wrapper.restart.delay=30

[Wrapper-user] [WRAPPER] Licence aquisition

[Cyril C. <cch...@bs...>]

Hello,

I would like to buy a development licence of the standard edition of the 
java service wrapper.
To do that, i click on the paypal button on the account licenses page:

Standard Edition (32-bit) 	Development 
<http://wrapper.tanukisoftware.org/doc/english/licenseDevelopment.html> 	1 
year 	US$1500.00 	



But i don't understand japanese, so i'm not able to fill the chart.
Is there an english version so i could order my licence ?

Best regards,

-- 
Cyril CHAMPIER
Bsv. Electronic Publishing
129 rue Jules Guesde
92300  Levallois
Tel :   01 47 56 99 66
Fax :  01 47 56 99 52
cch...@bs...

[Wrapper-user] Setting custom ulimit

[Erik D. <eri...@fj...>]

Hi!
I have an application which needs custom ulimits. I need to set 
something like

ulimit -n 65000
ulimit -s 256

and it must be set in same shell as the application runs in.

Where should I add the ulimit commands?


For the record; I'm on Fedora/RedHat.


-- 
Best regards,

Erik Drolshammer

Re: [Wrapper-user] Java Service Wrapper error in HPUX

[stanic <st...@mv...>]

HI Leif,

Thanks for your reply. I not sure how can i check the version of HPUX but
when i run the cmd "uname -a" it show "HP-UX dbsvr B.11.23 U ia64 0404690275
unlimited-user license". 
Is this HPUX 11i system?




Leif Mortenson-3 wrote:
> 
> Stanic,
> Sorry for the delay getting back to you.
> 
> This is being caused incompatible versions of a system library.
> Meaning that the Wrapper was built on a newer version of HP-UX than
> the one you are running.
> We build on an HP-UX 11i system.   What version of HP-UX are you using?
> 
> Thanks,
> Leif
> 
> On Tue, Nov 4, 2008 at 12:59 PM, stanic <st...@mv...> wrote:
>>
>> Hi! I solve the previous problem, it because my HP-UX Itanium cpu is not
>> supported by Java Service Wrapper 3.2.3 so i change to use 3.3.1. But i
>> having other error. the following is the error.
>>
>> $ sh JSW-Test_App start
>> -n Starting Test_APP1...
>> /usr/lib/hpux64/dld.so: Unsatisfied code symbol 'sigActionChildDeath' in
>> load module '/devtest/testapp/bin/./wrapper'.
>> /usr/lib/hpux64/dld.so: Unsatisfied code symbol 'sigActionHangup' in load
>> module '/devtest/testapp/bin/./wrapper'.
>> JSW-Test_App[7]: 5380 Killed
>>
>> Anyone know what causing it?
>>
>> Thanks in advance.
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Java-Service-Wrapper-error-in-HPUX-tp20299253p20315874.html
>> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
> 
> 
> 
> -- 
> Leif Mortenson
> President
> Tanuki Software, Ltd.
> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
> Tokyo 134-0088 Japan
> Tel/Fax: +81-3-3878-0415
> http://www.tanukisoftware.com
> lei...@ta...
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> 

-- 
View this message in context: http://www.nabble.com/Java-Service-Wrapper-error-in-HPUX-tp20299253p20676606.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

Re: [Wrapper-user] Java Service Wrapper error in HPUX

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

Stanic,
Sorry for the delay getting back to you.

This is being caused incompatible versions of a system library.
Meaning that the Wrapper was built on a newer version of HP-UX than
the one you are running.
We build on an HP-UX 11i system.   What version of HP-UX are you using?

Thanks,
Leif

On Tue, Nov 4, 2008 at 12:59 PM, stanic <st...@mv...> wrote:
>
> Hi! I solve the previous problem, it because my HP-UX Itanium cpu is not
> supported by Java Service Wrapper 3.2.3 so i change to use 3.3.1. But i
> having other error. the following is the error.
>
> $ sh JSW-Test_App start
> -n Starting Test_APP1...
> /usr/lib/hpux64/dld.so: Unsatisfied code symbol 'sigActionChildDeath' in
> load module '/devtest/testapp/bin/./wrapper'.
> /usr/lib/hpux64/dld.so: Unsatisfied code symbol 'sigActionHangup' in load
> module '/devtest/testapp/bin/./wrapper'.
> JSW-Test_App[7]: 5380 Killed
>
> Anyone know what causing it?
>
> Thanks in advance.
>
> --
> View this message in context: http://www.nabble.com/Java-Service-Wrapper-error-in-HPUX-tp20299253p20315874.html
> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>



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

Re: [Wrapper-user] Log file doesn't roll when running as a Windows Service

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

Muthu,
Are you referring to the ../logs/ForkManager.log log file, defined in
the log4j properties file, as not rolling correctly?

The Wrapper itself should not be doing which should directly affect
that or any other file created by the JVM.

What are the permissions on the directory in which the log file is
located?   When running as a service, the JVM will be running as the
SYSTEM user by default.   The problem may be being caused by that user
not being able to rename the file.
What happens if you first delete the log file and then start your
service?   Does the log file get created correctly?

Cheers,
Leif

On Thu, Nov 20, 2008 at 11:57 PM, muthukumaran_m
<mut...@ho...> wrote:
>
> To too have a similar issue with Jboss Server and specific to 64bit Windows
>
> The log files not rolling out when I start the server using the service but
> if I start the server from the console it's rolling properly.
>
> Please let me know if you have any solutions.
>
>
> homejob sl wrote:
>>
>> I'm using java Wrapper (32bit community edition v3.3.0) under windows XP
>> environment.
>> I wanna roll up the log file for each day & size. so i have written a
>> class
>> to incorporate it.
>> The log file rolls when the application run from the console,
>> however It keep on growing when run as a service.(doesn't roll for the
>> criteria specified in log4j.property)
>>
>> Below you can find the Configuration files.
>>
>> Thanks,
>> Safraz
>>
>>
>> #********************************************************************
>> # Wrapper License Properties (Ignored by Community Edition)
>> #********************************************************************
>> #include ../conf/wrapper-license.conf
>>
>> #********************************************************************
>> # Wrapper Java Properties
>> #********************************************************************
>> # Java Application
>> wrapper.java.command=java
>>
>> # 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.tanukisoftware.wrapper.WrapperSimpleApp
>>
>>
>> # Java Classpath (include wrapper.jar)  Add class path elements as
>> #  needed starting from 1
>> wrapper.java.classpath.1=../lib/wrapper.jar
>> wrapper.java.classpath.2=../FM.jar
>> wrapper.java.classpath.3=../lib/InfoLogger.jar
>> wrapper.java.classpath.4=../lib/log4j-1.2.15.jar
>> wrapper.java.classpath.5=../lib/ant.jar
>> wrapper.java.classpath.6=../lib/hibernate/antlr-2.7.6.jar
>> wrapper.java.classpath.7=../lib/hibernate/asm-attrs.jar
>> wrapper.java.classpath.8=../lib/hibernate/asm.jar
>> wrapper.java.classpath.9=../lib/hibernate/cglib-2.1.3.jar
>> wrapper.java.classpath.10=../lib/hibernate/commons-collections-2.1.1.jar
>> wrapper.java.classpath.11=../lib/hibernate/commons-logging-1.0.4.jar
>> wrapper.java.classpath.12=../lib/hibernate/dom4j-1.6.1.jar
>> wrapper.java.classpath.13=../lib/hibernate/hibernate3.jar
>> wrapper.java.classpath.14=../lib/hibernate/jta.jar
>> wrapper.java.classpath.15=../lib/mysql-connector-java-5.1.5-bin.jar
>> wrapper.java.classpath.16=../lib/RemoteProcess.jar
>> wrapper.java.classpath.17=../lib/jftp.jar
>> wrapper.java.classpath.18=../lib/jconn2.jar
>> wrapper.java.classpath.19=../lib/mail.jar
>> wrapper.java.classpath.20=../lib/activation.jar
>> wrapper.java.classpath.21=../lib/TestFork.jar
>> wrapper.java.classpath.22=../lib/ConfigurationManager.jar
>> wrapper.java.classpath.23=../Distributor/Distributor.jar
>>
>>
>> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
>> wrapper.java.library.path.1=../lib
>>
>> # Java Additional Parameters
>> wrapper.java.additional.1=-Dlog4j.configuration=file:../conf/log4j.properties
>> wrapper.java.additional.2=-DforkManager.rmi.port=1099
>> wrapper.java.additional.3=-Dterminate.startedProcesses=false
>> wrapper.java.additional.4=-DforkManager.useSecurityManager=true
>> wrapper.java.additional.5=-Djava.rmi.server.codebase=file:../FM.jar
>> wrapper.java.additional.6=-Djava.rmi.server.hostname=192.168.11.232
>> wrapper.java.additional.7=-Djava.security.policy=../server.policy
>> wrapper.java.additional.8=-Dprocessmanager.hibernate.configuration=file:../conf/processmanager-hibernate.cfg.xml
>>
>>
>> # 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=lk.informatics.infomediation.forkmanager.ForkManager
>>
>> #********************************************************************
>> # Wrapper Logging Properties
>> #********************************************************************
>> # 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=INFO
>>
>> # Log file to use for wrapper output logging.
>> wrapper.logfile=../logs/wrapper.log
>>
>> # Format of output for the log file.  (See docs for formats)
>> wrapper.logfile.format=LPTM
>>
>> # 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=NONE
>>
>> #********************************************************************
>> # Wrapper Windows Properties
>> #********************************************************************
>> # Title to use when running as a console
>> wrapper.console.title=AvaBill Fork Manager
>>
>> #********************************************************************
>> # 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.ntservice.name=AvaBill Fork Manager
>>
>> # Display name of the service
>> wrapper.ntservice.displayname=AvaBill Fork Manager
>>
>>
>> # Description of the service
>> wrapper.ntservice.description=AvaBill Fork Manager
>>
>> # Service dependencies.  Add dependencies as needed starting from 1
>> wrapper.ntservice.dependency.1=
>>
>> # Mode in which the service is installed.  AUTO_START or DEMAND_START
>> wrapper.ntservice.starttype=AUTO_START
>>
>> # Allow the service to interact with the desktop.
>> wrapper.ntservice.interactive=false
>>
>>
>> ----------------------------
>> log4j.property file
>>
>>
>> ### direct log messages to stdout ###
>> log4j.appender.stdout=org.apache.log4j.ConsoleAppender
>> log4j.appender.stdout.Target=System.out
>> log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
>> log4j.appender.stdout.layout.ConversionPattern=%d %-5p [%c{2}][%t] - %m%n
>>
>> log4j.appender.forkManager=lk.informatics.logging.appender.RollingFileAppenderWithDate
>> log4j.appender.forkManager.File=../logs/ForkManager.log
>> log4j.appender.forkManager.MaxFileSize=1KB
>> log4j.appender.forkManager.DateFormat=ddMMyyyy_HHmmss
>> log4j.appender.forkManager.layout=org.apache.log4j.PatternLayout
>> log4j.appender.forkManager.layout.ConversionPattern=%d %-5p [%c{2}][%t] -
>> %m%n
>>
>> ### direct messages to file logs/message.log ###
>> log4j.appender.distfile=lk.informatics.logging.appender.RollingFileAppenderWithDate
>> log4j.appender.distfile.File=../logs/dist-message.log
>> log4j.appender.distfile.MaxFileSize=256KB
>> log4j.appender.distfile.DateFormat=ddMMyyyy_HHmmss
>> log4j.appender.distfile.layout=org.apache.log4j.PatternLayout
>> log4j.appender.distfile.layout.ConversionPattern=%d %-5p [%c{2}][%t] -
>> %m%n
>>
>>
>> log4j.rootLogger=info,stdout,distfile
>> log4j.logger.lk.informatics.infomediation.forkmanager=debug, forkManager


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

Re: [Wrapper-user] Fwd: Wierd Error only on Using Tanuki Wrapper

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

Anand,
I took a look at your files.    The command line generated by the
JBoss run.bat file and that generated by the Wrapper have quite a few
differences.  Most likely most of the changes were intentional, but
some of them may be behind your problems.

The main difference is with the classpath.   There are a few values in
the run.bat version which do not exist in the wrapper version.  What
is the current working directory of the run.bat script?  Is it the bin
directory?
Here are the missing values:
.    (../bin ?)
\conf\resources  (from the file system root?)
\conf\properties\system  (from the file system root?)
\properties  (from the file system root?)
../properties

There are several other additions to the classpath in the Wrapper
version as well.

Also, there appears to be 3 different jasperreports jar versions on
your classpath.  Is this intentional?
../lib/jasperreports-0.6.0.jar;
../lib/jasperreports-2.0.1.jar;
../lib/jasperreports.jar;

One of the quickest things I would suggest is to go look at the JBoss
source and see what is happening where the errors are being thrown.
The appear to be being caused by an NPE registering a class loader.

Caused by: java.lang.NullPointerException
	at org.jboss.deployment.SimpleSubDeployerSupport.registerClassLoader(SimpleSubDeployerSupport.java:249)

The JBoss error here is not very good though so it is difficult to say
what the exact cause without digging into the JBoss source.

Cheers,
Leif



On Sat, Nov 22, 2008 at 3:51 AM, Anand HS <an...@gm...> wrote:
>
>
> Hello Leif,
> Thanks for suggesting the idea of echoing java commands when run.bat
> directly runs and when wrapper runs jboss.
> I have attached 3 files -
> run_bat.txt - JAVA command when running run.bat
> wrapper_params.txt - logs when I enable INFO level on wrapper and run my
> JBOSS.
> wrapper.log - wrapper log file.
>
> I was not able to determine which JVMs each one is using though.
> I have JRE 1.4.2 and JRE 1.6.0_10 in my computer and I want wrapper to make
> use of JRE 1.6.0_10.
>
> Wierder still is the fact that the wrapper logs show that the JBOSS server
> is being started even though I have commented out the start up part in by
> run.bat.
> Does this mean that wrapper has another hook by which it starts JBOSS other
> than plainly running run.bat. ?
>
> Let me know what you think.
>
>
> BTW, here is the link to the original post on sourceforge,
> https://sourceforge.net/mailarchive/message.php?msg_name=c0afdf360811202221k7dc8e0p1afcd93d33a84b7e%40mail.gmail.com
> Thanks,
> Anand
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

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

[Wrapper-user] Fwd: Wierd Error only on Using Tanuki Wrapper

[Anand H. <an...@gm...>]

"D:\PSI-OPS-HOME\sdk\jdk1.6.0_10\bin\java"
-server 
-Dpsi.ops.server.log.dir=D:\PSI-OPS-HOME/logs 
-Dpsi.ops.jboss.log.dir=../logs/JBOSS 
-Dlog4j.configuration=file:D:\PSI-OPS-HOME/conf/properties/user/log4j.properties 
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl 
-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl 
-Dorg.xml.sax.driver=org.apache.xerces.parsers.SAXParser 
-Dprogram.name=run.bat 
-server -Xms128m -Xmx512m 
-Dsun.rmi.dgc.client.gcInterval=3600000 
-Dsun.rmi.dgc.server.gcInterval=3600000    
-Djava.endorsed.dirs="D:\PSI-OPS-HOME\servers\jboss-4.2.3.GA\lib\endorsed"   
-classpath ".;;\conf\resources;
		\conf\properties\system;
		\properties;
		D:\PSI-OPS-HOME\properties;
		D:\PSI-OPS-HOME\conf\properties\user;
		;D:\PSI-OPS-HOME\lib;;D:\PSI-OPS-HOME\conf\resources;
		D:\PSI-OPS-HOME\conf\resources\fonts;
		D:\PSI-OPS-HOME\conf\resources\images;
		;D:\PSI-OPS-HOME\lib\commons-beanutils-1.5.jar;
		D:\PSI-OPS-HOME\lib\commons-collections.jar;
		D:\PSI-OPS-HOME\lib\commons-digester-1.7.jar;
		;;D:\PSI-OPS-HOME\lib\commons-logging.jar;
		;;D:\PSI-OPS-HOME\lib\itext-1.01.jar;
		;;D:\PSI-OPS-HOME\lib\jasperreports-0.6.0.jar;
		;;D:\PSI-OPS-HOME\lib\jasperreports-2.0.1.jar;
		;;D:\PSI-OPS-HOME\lib\jasperreports.jar;
		;;D:\PSI-OPS-HOME\lib\poi-2.5-final-20040302.jar;;
		;D:\PSI-OPS-HOME\lib\psiutils.jar;
		D:\PSI-OPS-HOME\sdk\jdk1.6.0_10\lib\tools.jar;
		D:\PSI-OPS-HOME\servers\jboss-4.2.3.GA\bin\run.jar"
		org.jboss.Main -b 0.0.0.0

Re: [Wrapper-user] Wierd Error only on Using Tanuki Wrapper

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

Anand,
The Wrapper itself does nothing that should affect this.    Most
likely there is something in your configuration which is different
from the run.bat.

One common problem is that the Wrapper may run a differennt JVM than
the run.bat.  This can lead to all kinds of problems.

Please edit your run.bat so it does an echo of the java command rather
than running it.

Then modify your wrapper.conf file and add the
wrapper.java.command.loglevel=INFO property and rerun.  This will
cause the Wrapper to display its java command line as well.

You can now then compare the two and see what is different.  My first
guess is the JVM.    The Wrapper may be looking for java.exe on the
PATH while your run.bat is looking on JAVA_HOME/bin for example.    If
you are unsure, please post both of the above command lines and I will
take a look at them for you.

Cheers,
Leif

On Fri, Nov 21, 2008 at 10:10 AM, Anand HS <an...@gm...> wrote:
> Hi,
> I am facing a wierd error that fails to deploy an ejb library inside my ear
> when I try to start JBOSS through Tanuki Wrapper only.
> The error is about
>
> 16:54:46,218 ERROR [MainDeployer] Could not create deployment:
> file:/D:/PSI-OPS-HOME/servers/jboss-4.2.3.GA/server/default/deploy/atlas-lc-ops.ear/corecccejb-1.0.jar
> INFO   | jvm 1    | 2008/11/18 16:54:46 |
> org.jboss.deployment.DeploymentException: ejb-jar.xml must either obey the
> right xml schema or define a valid DOCTYPE!
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMetaData.java:339)
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:166)
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:541)
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
> java.lang.reflect.Method.invoke(Method.java:597)
>
> Although this seems that there is an error in my deployment descriptor, the
> same ejb library is deployed succesfully when I start JBOSS through console
> by using run.bat.
>
> The error is the same even when I use wrapper in console based mode.
>
> Has any faced a similar problem before. ?
> Any pointers or solutions are most welcome.
>
> Thanks,
> Anand



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

[Wrapper-user] Wierd Error only on Using Tanuki Wrapper

[Anand H. <an...@gm...>]

Hi,
I am facing a wierd error that fails to deploy an ejb library inside my ear
when I try to start JBOSS through Tanuki Wrapper only.
The error is about

16:54:46,218 ERROR [MainDeployer] Could not create deployment:
file:/D:/PSI-OPS-HOME/servers/
jboss-4.2.3.GA/server/default/deploy/atlas-lc-ops.ear/corecccejb-1.0.jar
INFO   | jvm 1    | 2008/11/18 16:54:46 |
org.jboss.deployment.DeploymentException: ejb-jar.xml must either obey the
right xml schema or define a valid DOCTYPE!
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
org.jboss.metadata.ApplicationMetaData.importEjbJarXml(ApplicationMetaData.java:339)
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
org.jboss.metadata.XmlFileLoader.load(XmlFileLoader.java:166)
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
org.jboss.ejb.EJBDeployer.create(EJBDeployer.java:541)
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
INFO   | jvm 1    | 2008/11/18 16:54:46 |  at
java.lang.reflect.Method.invoke(Method.java:597)

Although this seems that there is an error in my deployment descriptor, the
same ejb library is deployed succesfully when I start JBOSS through console
by using run.bat.

The error is the same even when I use wrapper in console based mode.

Has any faced a similar problem before. ?
Any pointers or solutions are most welcome.

Thanks,
Anand

Re: [Wrapper-user] How to point to a custom JAVA_HOME and JRE_HOME in wrapper.conf

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

Anand,
The Wrapper has the ability to set arbitrary environment variables
from within the wrapper.conf file.  See the following page for
details:
http://wrapper.tanukisoftware.org/doc/english/props-envvars.html

You would add something like following to your wrapper.conf anywhere
BEFORE the JAVA_HOME variable needs to be referenced:
set.JAVA_HOME=C:/Sun/jdk1.4

Let me know if you have any questions getting it working.

Cheers,
Leif

On Fri, Nov 21, 2008 at 5:52 AM, Anand HS <an...@gm...> wrote:
> Hello,
> I have gone through the wrapper documentaiton, but was not able to find the
> answer to a question of mine.
> For my application, I am setting
> wrapper.java.command to point to my java.exe as needed.
>
> My question is, is this information suffficient for the wrapper to figure
> out the values of JAVA_HOME and JRE_HOME values. ?
> I know i can possibly point to the Java_home in the registry, but I cant do
> that unfortunately as it is being set in my application through a separate
> batch file.
>
> The system on which installation is being done has multiple versions of java
> in it and I have to be able to specify the correct version of JAVA and JRE
> to use for my application.
> Is there any way to do it in the wrapper.conf file. ?
>
> Any pointers to it are most welcome, as it is urgently needed.
>
> Thank you,
> Anand


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