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

Re: [Wrapper-user] wrapper.daemonize: signal trap problem

[John Q. <jqu...@jq...>]

I believe I've discovered the root of my problem; this has led me to a few other questions that I hope you'll be good enough to answer for me.

The problem appears to have been the result of my sending the TERM signal to the wrong process.  We don't want to be signaling the binary 'wrapper' but rather the Java process itself that the wrapper spawns.  Is this correct?  I expected the wrapper process to be the entity that would catch these signals.

My original assumption that we should be signaling the binary itself came from the behavior of the init.d script provided with the binary distribution.  This script creates a pid file based upon the process number of the wrapper binary, and sends the kill to the process number gathered from this file at time of shutdown.  Is this a bug?

Thanks so much for you help!

- John Quigley

[Wrapper-user] login event to start process for painting tray icon?

[Frank M. <fra...@gm...>]

hi,

i want to implement my java service with "wrapper.ntservice.interactive=false" (for security reasons and because vista doesn't allow this anymore).

When a user logs into the system, the service process should start a separate plain user java process (not a second service) for this user (via JNI) with the windows API "CreateProcessAsUser". This process should paint the trayIcon and communicate with the service process via sockets or named pipes.

But to achieve this, the service process needs to be triggered, if a user logs into the system and the userID of this user to be able to call the "CreateProcessAsUser" Win32 API function.

I've found a logoff and a shutdown event, but no login event (and also no boot event) in the service wrapper. Has someone an idea how to achieve this?


Thanks in advance,
 Frank

-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

Re: [Wrapper-user] helper class to start application

[Mirko P. <m.p...@gm...>]

Hi Bob,

I hope you're fine now. But its still an interesting problem how to
handle Java applicationsm which do an exec() to start other process.

2007/8/21, Robert Pepersack <RPe...@md...>:
> Hi Mirko,
>
> I'm glad you found a solution.  Sorry it's taken me so long to get back to you.  I've been sick.
>
> Bob
>
> Robert Pepersack
> Senior Lead Developer
> Maryland Insurance Administration
> 410-468-2054
>
> >>> "Mirko Pluhar" <m.p...@gm...> 08/18/2007 3:14 PM >>>
> I found a workaround for my problem. So not any investigation necessary ...
>
>
> 2007/8/18, Mirko Pluhar <m.p...@gm...>:
> > Hi Bob,
> >
> > thanks for your answer, but maybe you misunterstood my problem:
> > The problem ist not that I got class A for starting and class B for
> > stopping the application.
> > Class A inititializes the application, calls class B and finishes with
> > System.exit()
> >
> > I read the docs and all configuration properties, but there seems to
> > be no option for such a construction.
> >
> > 2007/8/17, Robert Pepersack <RPe...@md...>:
> > > Hi Mirko,
> > >
> > > I don't know.  It worked for me without a problem.  I run the Quartz scheduler and the JBoss naming server.  Here is the content of my wrapper.conf file.  I hope it can help you.
> > >
> > > #********************************************************************
> > > # Wrapper Properties
> > > #********************************************************************
> > >
> > > wrapper.debug=true
> > >
> > > # Java Application
> > > wrapper.java.command=../jdk1.5.0_11/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=../jdk1.5.0_11/lib/tools.jar
> > > wrapper.java.classpath.2=../java/startup/lib/wrapper.jar
> > > wrapper.java.classpath.3=../java/startup/lib/log4j-1.2.14.jar
> > > wrapper.java.classpath.4=../java/startup/lib/startup.jar
> > >
> > > # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> > > wrapper.java.library.path.1=../bin
> > >
> > > # Java Additional Parameters
> > > wrapper.java.additional.1=-Dlog4j.properties.file="../java/startup/lib/log4j.properties"
> > > wrapper.java.additional.2=-Dserver.class.dir="../java/common/classes"
> > > wrapper.java.additional.3=-Dserver.lib.dir="../java/common/lib"
> > > wrapper.java.additional.4=-Ddata.source.dir="../datasource"
> > > wrapper.java.additional.5=-Djava.naming.factory.initial="org.jnp.interfaces.NamingContextFactory"
> > > wrapper.java.additional.6=-Djava.naming.factory.url.pkgs="org.jnp.interfaces"
> > > #wrapper.java.additional.7=-Djava.naming.provider.url="localhost"
> > >
> > > # 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
> > > # The first application parameter is the name of the class whose main
> > > # method is to be called when the application is launched.  The class
> > > # name is followed by the number of parameters to be passed to its main
> > > # method.  Then comes the actual parameters.
> > > wrapper.app.parameter.1=miaJs.server.Bootstrap
> > > wrapper.app.parameter.2=1
> > > wrapper.app.parameter.3=start
> > >
> > > # The start parameters are followed by the name of the class whose main
> > > # method is to be called to stop the application.  The stop class name
> > > # is followed by a flag which controls whether or not the Wrapper should
> > > # wait for all non daemon threads to complete before exiting the JVM.
> > > # The flag is followed by the number of parameters to be passed to the
> > > # stop class's main method.  Finally comes the actual parameters.
> > > wrapper.app.parameter.4=miaJs.server.Bootstrap
> > > wrapper.app.parameter.5=false
> > > 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=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=Java Job Scheduler
> > >
> > > #********************************************************************
> > > # 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=JJS
> > >
> > > # Display name of the service
> > > wrapper.ntservice.displayname=JJS
> > >
> > > # Description of the service
> > > wrapper.ntservice.description=Java Job Scheduler
> > >
> > > # 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
> > > # AUTO_START starts the service automatically when the system is rebooted.
> > > # DEMAND_START requires that the service must be started manually.
> > > wrapper.ntservice.starttype=DEMAND_START
> > >
> > > # Allow the service to interact with the desktop.
> > > wrapper.ntservice.interactive=false
> > >
> > >
> > >
> > > Robert Pepersack
> > > Senior Lead Developer
> > > Maryland Insurance Administration
> > > 410-468-2054
> > >
> > > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 8:56 AM >>>
> > > Hi Bob,
> > >
> > > thanks for your response. Yes, the AgentDaemon keeps running. But how
> > > to tell the Java Service Wrapper that this is the process it should
> > > concern about ?
> > >
> > > 2007/8/17, Robert Pepersack <RPe...@md...>:
> > > > Hi Mirko,
> > > >
> > > > I'm fairly new at using the wrapper, too, but maybe I can help.
> > > >
> > > > Does your AgentDaemon class start a process that keeps running?  Or, does it execute a simple method and terminate?  To keep the wrapper running, I've found that you have to run something that keeps the Java VM alive.  For example, I run a JNDI naming server.
> > > >
> > > > Bob
> > > >
> > > > Robert Pepersack
> > > > Senior Lead Developer
> > > > Maryland Insurance Administration
> > > > 410-468-2054
> > > >
> > > > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
> > > > Hi all,
> > > >
> > > > I'm trying to integrate an application with Java Service Wrapper but
> > > > I'm stuck with a problem:
> > > > To start the application a class AgentClient ist called , which is
> > > > only a helper to run class AgentDaemon.
> > > > So I define class AgentClient as the initial class in java service
> > > > wrapper configuration . When starting the wrapper it calls this class,
> > > > AgentClient calls AgentDaemon and exit with
> > > > success. The service wrapper recognizes that and exits also, because
> > > > its focussed on AgentClient.
> > > > Do you have any hints to use such a construct within java service wrapper ?
> > > > Thanks in advance.
> > > >
> > > > --
> > > > With regards
> > > > Mirko Pluhar
> > > >
> > > > -------------------------------------------------------------------------
> > > > This SF.net email is sponsored by: Splunk Inc.
> > > > Still grepping through log files to find problems?  Stop.
> > > > Now Search log events and configuration files using AJAX and a browser.
> > > > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > > > _______________________________________________
> > > > Wrapper-user mailing list
> > > > Wra...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > > >
> > > >
> > > > -------------------------------------------------------------------------
> > > > This SF.net email is sponsored by: Splunk Inc.
> > > > Still grepping through log files to find problems?  Stop.
> > > > Now Search log events and configuration files using AJAX and a browser.
> > > > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > > > _______________________________________________
> > > > Wrapper-user mailing list
> > > > Wra...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > > >
> > >
> > >
> > > --
> > > Mit freundlichen Gruessen
> > > Mirko Pluhar
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > >
> >
> >
> > --
> > Mit freundlichen Gruessen
> > Mirko Pluhar
> >
>
>
> --
> Mit freundlichen Gruessen
> Mirko Pluhar
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>


-- 
Mit freundlichen Gruessen
Mirko Pluhar

Re: [Wrapper-user] helper class to start application

[Robert P. <RPe...@md...>]

Hi Mirko,

I'm glad you found a solution.  Sorry it's taken me so long to get back to =
you.  I've been sick.

Bob

Robert Pepersack
Senior Lead Developer
Maryland Insurance Administration
410-468-2054

>>> "Mirko Pluhar" <m.p...@gm...> 08/18/2007 3:14 PM >>>
I found a workaround for my problem. So not any investigation necessary =
...


2007/8/18, Mirko Pluhar <m.p...@gm...>:
> Hi Bob,
>
> thanks for your answer, but maybe you misunterstood my problem:
> The problem ist not that I got class A for starting and class B for
> stopping the application.
> Class A inititializes the application, calls class B and finishes with
> System.exit()
>
> I read the docs and all configuration properties, but there seems to
> be no option for such a construction.
>
> 2007/8/17, Robert Pepersack <RPe...@md...>:
> > Hi Mirko,
> >
> > I don't know.  It worked for me without a problem.  I run the Quartz =
scheduler and the JBoss naming server.  Here is the content of my =
wrapper.conf file.  I hope it can help you.
> >
> > #********************************************************************
> > # Wrapper Properties
> > #********************************************************************
> >
> > wrapper.debug=3Dtrue
> >
> > # Java Application
> > wrapper.java.command=3D../jdk1.5.0_11/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=3Dorg.tanukisoftware.wrapper.WrapperStartStopApp=

> >
> > # Java Classpath (include wrapper.jar)  Add class path elements as
> > #  needed starting from 1
> > wrapper.java.classpath.1=3D../jdk1.5.0_11/lib/tools.jar
> > wrapper.java.classpath.2=3D../java/startup/lib/wrapper.jar
> > wrapper.java.classpath.3=3D../java/startup/lib/log4j-1.2.14.jar
> > wrapper.java.classpath.4=3D../java/startup/lib/startup.jar
> >
> > # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> > wrapper.java.library.path.1=3D../bin
> >
> > # Java Additional Parameters
> > wrapper.java.additional.1=3D-Dlog4j.properties.file=3D"../java/startup/=
lib/log4j.properties"
> > wrapper.java.additional.2=3D-Dserver.class.dir=3D"../java/common/classe=
s"
> > wrapper.java.additional.3=3D-Dserver.lib.dir=3D"../java/common/lib"
> > wrapper.java.additional.4=3D-Ddata.source.dir=3D"../datasource"
> > wrapper.java.additional.5=3D-Djava.naming.factory.initial=3D"org.jnp.in=
terfaces.NamingContextFactory"
> > wrapper.java.additional.6=3D-Djava.naming.factory.url.pkgs=3D"org.jnp.i=
nterfaces"
> > #wrapper.java.additional.7=3D-Djava.naming.provider.url=3D"localhost"
> >
> > # Initial Java Heap Size (in MB)
> > #wrapper.java.initmemory=3D3
> >
> > # Maximum Java Heap Size (in MB)
> > #wrapper.java.maxmemory=3D64
> >
> > # Application parameters.  Add parameters as needed starting from 1
> > # The first application parameter is the name of the class whose main
> > # method is to be called when the application is launched.  The class
> > # name is followed by the number of parameters to be passed to its =
main
> > # method.  Then comes the actual parameters.
> > wrapper.app.parameter.1=3DmiaJs.server.Bootstrap
> > wrapper.app.parameter.2=3D1
> > wrapper.app.parameter.3=3Dstart
> >
> > # The start parameters are followed by the name of the class whose =
main
> > # method is to be called to stop the application.  The stop class name
> > # is followed by a flag which controls whether or not the Wrapper =
should
> > # wait for all non daemon threads to complete before exiting the JVM.
> > # The flag is followed by the number of parameters to be passed to the
> > # stop class's main method.  Finally comes the actual parameters.
> > wrapper.app.parameter.4=3DmiaJs.server.Bootstrap
> > wrapper.app.parameter.5=3Dfalse
> > wrapper.app.parameter.6=3D1
> > wrapper.app.parameter.7=3Dstop
> >
> > #********************************************************************
> > # Wrapper Logging Properties
> > #********************************************************************
> > # Format of output for the console.  (See docs for formats)
> > wrapper.console.format=3DPM
> >
> > # Log Level for console output.  (See docs for log levels)
> > wrapper.console.loglevel=3DDEBUG
> >
> > # Log file to use for wrapper output logging.
> > wrapper.logfile=3D../logs/wrapper.log
> >
> > # Format of output for the log file.  (See docs for formats)
> > wrapper.logfile.format=3DLPTM
> >
> > # Log Level for log file output.  (See docs for log levels)
> > wrapper.logfile.loglevel=3DINFO
> >
> > # 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 =3D 10 megabytes.
> > wrapper.logfile.maxsize=3D0
> >
> > # 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=3D0
> >
> > # Log Level for sys/event log output.  See docs for log levels.
> > wrapper.syslog.loglevel=3DNONE
> >
> > #********************************************************************
> > # Wrapper Windows Properties
> > #********************************************************************
> > # Title to use when running as a console
> > wrapper.console.title=3DJava Job Scheduler
> >
> > #********************************************************************
> > # 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=3DJJS
> >
> > # Display name of the service
> > wrapper.ntservice.displayname=3DJJS
> >
> > # Description of the service
> > wrapper.ntservice.description=3DJava Job Scheduler
> >
> > # Service dependencies.  Add dependencies as needed starting from 1
> > wrapper.ntservice.dependency.1=3D
> >
> > # Mode in which the service is installed.  AUTO_START or DEMAND_START
> > # AUTO_START starts the service automatically when the system is =
rebooted.
> > # DEMAND_START requires that the service must be started manually.
> > wrapper.ntservice.starttype=3DDEMAND_START
> >
> > # Allow the service to interact with the desktop.
> > wrapper.ntservice.interactive=3Dfalse
> >
> >
> >
> > Robert Pepersack
> > Senior Lead Developer
> > Maryland Insurance Administration
> > 410-468-2054
> >
> > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 8:56 AM >>>
> > Hi Bob,
> >
> > thanks for your response. Yes, the AgentDaemon keeps running. But how
> > to tell the Java Service Wrapper that this is the process it should
> > concern about ?
> >
> > 2007/8/17, Robert Pepersack <RPe...@md...>:
> > > Hi Mirko,
> > >
> > > I'm fairly new at using the wrapper, too, but maybe I can help.
> > >
> > > Does your AgentDaemon class start a process that keeps running?  Or, =
does it execute a simple method and terminate?  To keep the wrapper =
running, I've found that you have to run something that keeps the Java VM =
alive.  For example, I run a JNDI naming server.
> > >
> > > Bob
> > >
> > > Robert Pepersack
> > > Senior Lead Developer
> > > Maryland Insurance Administration
> > > 410-468-2054
> > >
> > > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
> > > Hi all,
> > >
> > > I'm trying to integrate an application with Java Service Wrapper but
> > > I'm stuck with a problem:
> > > To start the application a class AgentClient ist called , which is
> > > only a helper to run class AgentDaemon.
> > > So I define class AgentClient as the initial class in java service
> > > wrapper configuration . When starting the wrapper it calls this =
class,
> > > AgentClient calls AgentDaemon and exit with
> > > success. The service wrapper recognizes that and exits also, because
> > > its focussed on AgentClient.
> > > Do you have any hints to use such a construct within java service =
wrapper ?
> > > Thanks in advance.
> > >
> > > --
> > > With regards
> > > Mirko Pluhar
> > >
> > > ---------------------------------------------------------------------=
----
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a =
browser.
> > > Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...=20
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
> > >
> > >
> > > ---------------------------------------------------------------------=
----
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a =
browser.
> > > Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...=20
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
> > >
> >
> >
> > --
> > Mit freundlichen Gruessen
> > Mirko Pluhar
> >
> > -----------------------------------------------------------------------=
--
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a =
browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...=20
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
> >
> > -----------------------------------------------------------------------=
--
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a =
browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...=20
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
> >
>
>
> --
> Mit freundlichen Gruessen
> Mirko Pluhar
>


--=20
Mit freundlichen Gruessen
Mirko Pluhar

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
_______________________________________________
Wrapper-user mailing list
Wra...@li...=20
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] helper class to start application

[Mirko P. <m.p...@gm...>]

I found a workaround for my problem. So not any investigation necessary ...


2007/8/18, Mirko Pluhar <m.p...@gm...>:
> Hi Bob,
>
> thanks for your answer, but maybe you misunterstood my problem:
> The problem ist not that I got class A for starting and class B for
> stopping the application.
> Class A inititializes the application, calls class B and finishes with
> System.exit()
>
> I read the docs and all configuration properties, but there seems to
> be no option for such a construction.
>
> 2007/8/17, Robert Pepersack <RPe...@md...>:
> > Hi Mirko,
> >
> > I don't know.  It worked for me without a problem.  I run the Quartz scheduler and the JBoss naming server.  Here is the content of my wrapper.conf file.  I hope it can help you.
> >
> > #********************************************************************
> > # Wrapper Properties
> > #********************************************************************
> >
> > wrapper.debug=true
> >
> > # Java Application
> > wrapper.java.command=../jdk1.5.0_11/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=../jdk1.5.0_11/lib/tools.jar
> > wrapper.java.classpath.2=../java/startup/lib/wrapper.jar
> > wrapper.java.classpath.3=../java/startup/lib/log4j-1.2.14.jar
> > wrapper.java.classpath.4=../java/startup/lib/startup.jar
> >
> > # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> > wrapper.java.library.path.1=../bin
> >
> > # Java Additional Parameters
> > wrapper.java.additional.1=-Dlog4j.properties.file="../java/startup/lib/log4j.properties"
> > wrapper.java.additional.2=-Dserver.class.dir="../java/common/classes"
> > wrapper.java.additional.3=-Dserver.lib.dir="../java/common/lib"
> > wrapper.java.additional.4=-Ddata.source.dir="../datasource"
> > wrapper.java.additional.5=-Djava.naming.factory.initial="org.jnp.interfaces.NamingContextFactory"
> > wrapper.java.additional.6=-Djava.naming.factory.url.pkgs="org.jnp.interfaces"
> > #wrapper.java.additional.7=-Djava.naming.provider.url="localhost"
> >
> > # 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
> > # The first application parameter is the name of the class whose main
> > # method is to be called when the application is launched.  The class
> > # name is followed by the number of parameters to be passed to its main
> > # method.  Then comes the actual parameters.
> > wrapper.app.parameter.1=miaJs.server.Bootstrap
> > wrapper.app.parameter.2=1
> > wrapper.app.parameter.3=start
> >
> > # The start parameters are followed by the name of the class whose main
> > # method is to be called to stop the application.  The stop class name
> > # is followed by a flag which controls whether or not the Wrapper should
> > # wait for all non daemon threads to complete before exiting the JVM.
> > # The flag is followed by the number of parameters to be passed to the
> > # stop class's main method.  Finally comes the actual parameters.
> > wrapper.app.parameter.4=miaJs.server.Bootstrap
> > wrapper.app.parameter.5=false
> > 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=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=Java Job Scheduler
> >
> > #********************************************************************
> > # 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=JJS
> >
> > # Display name of the service
> > wrapper.ntservice.displayname=JJS
> >
> > # Description of the service
> > wrapper.ntservice.description=Java Job Scheduler
> >
> > # 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
> > # AUTO_START starts the service automatically when the system is rebooted.
> > # DEMAND_START requires that the service must be started manually.
> > wrapper.ntservice.starttype=DEMAND_START
> >
> > # Allow the service to interact with the desktop.
> > wrapper.ntservice.interactive=false
> >
> >
> >
> > Robert Pepersack
> > Senior Lead Developer
> > Maryland Insurance Administration
> > 410-468-2054
> >
> > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 8:56 AM >>>
> > Hi Bob,
> >
> > thanks for your response. Yes, the AgentDaemon keeps running. But how
> > to tell the Java Service Wrapper that this is the process it should
> > concern about ?
> >
> > 2007/8/17, Robert Pepersack <RPe...@md...>:
> > > Hi Mirko,
> > >
> > > I'm fairly new at using the wrapper, too, but maybe I can help.
> > >
> > > Does your AgentDaemon class start a process that keeps running?  Or, does it execute a simple method and terminate?  To keep the wrapper running, I've found that you have to run something that keeps the Java VM alive.  For example, I run a JNDI naming server.
> > >
> > > Bob
> > >
> > > Robert Pepersack
> > > Senior Lead Developer
> > > Maryland Insurance Administration
> > > 410-468-2054
> > >
> > > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
> > > Hi all,
> > >
> > > I'm trying to integrate an application with Java Service Wrapper but
> > > I'm stuck with a problem:
> > > To start the application a class AgentClient ist called , which is
> > > only a helper to run class AgentDaemon.
> > > So I define class AgentClient as the initial class in java service
> > > wrapper configuration . When starting the wrapper it calls this class,
> > > AgentClient calls AgentDaemon and exit with
> > > success. The service wrapper recognizes that and exits also, because
> > > its focussed on AgentClient.
> > > Do you have any hints to use such a construct within java service wrapper ?
> > > Thanks in advance.
> > >
> > > --
> > > With regards
> > > Mirko Pluhar
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > >
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems?  Stop.
> > > Now Search log events and configuration files using AJAX and a browser.
> > > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > > _______________________________________________
> > > Wrapper-user mailing list
> > > Wra...@li...
> > > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> > >
> >
> >
> > --
> > Mit freundlichen Gruessen
> > Mirko Pluhar
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
>
>
> --
> Mit freundlichen Gruessen
> Mirko Pluhar
>


-- 
Mit freundlichen Gruessen
Mirko Pluhar

Re: [Wrapper-user] helper class to start application

[Mirko P. <m.p...@gm...>]

Hi Bob,

thanks for your answer, but maybe you misunterstood my problem:
The problem ist not that I got class A for starting and class B for
stopping the application.
Class A inititializes the application, calls class B and finishes with
System.exit()

I read the docs and all configuration properties, but there seems to
be no option for such a construction.

2007/8/17, Robert Pepersack <RPe...@md...>:
> Hi Mirko,
>
> I don't know.  It worked for me without a problem.  I run the Quartz scheduler and the JBoss naming server.  Here is the content of my wrapper.conf file.  I hope it can help you.
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
>
> wrapper.debug=true
>
> # Java Application
> wrapper.java.command=../jdk1.5.0_11/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=../jdk1.5.0_11/lib/tools.jar
> wrapper.java.classpath.2=../java/startup/lib/wrapper.jar
> wrapper.java.classpath.3=../java/startup/lib/log4j-1.2.14.jar
> wrapper.java.classpath.4=../java/startup/lib/startup.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../bin
>
> # Java Additional Parameters
> wrapper.java.additional.1=-Dlog4j.properties.file="../java/startup/lib/log4j.properties"
> wrapper.java.additional.2=-Dserver.class.dir="../java/common/classes"
> wrapper.java.additional.3=-Dserver.lib.dir="../java/common/lib"
> wrapper.java.additional.4=-Ddata.source.dir="../datasource"
> wrapper.java.additional.5=-Djava.naming.factory.initial="org.jnp.interfaces.NamingContextFactory"
> wrapper.java.additional.6=-Djava.naming.factory.url.pkgs="org.jnp.interfaces"
> #wrapper.java.additional.7=-Djava.naming.provider.url="localhost"
>
> # 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
> # The first application parameter is the name of the class whose main
> # method is to be called when the application is launched.  The class
> # name is followed by the number of parameters to be passed to its main
> # method.  Then comes the actual parameters.
> wrapper.app.parameter.1=miaJs.server.Bootstrap
> wrapper.app.parameter.2=1
> wrapper.app.parameter.3=start
>
> # The start parameters are followed by the name of the class whose main
> # method is to be called to stop the application.  The stop class name
> # is followed by a flag which controls whether or not the Wrapper should
> # wait for all non daemon threads to complete before exiting the JVM.
> # The flag is followed by the number of parameters to be passed to the
> # stop class's main method.  Finally comes the actual parameters.
> wrapper.app.parameter.4=miaJs.server.Bootstrap
> wrapper.app.parameter.5=false
> 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=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=Java Job Scheduler
>
> #********************************************************************
> # 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=JJS
>
> # Display name of the service
> wrapper.ntservice.displayname=JJS
>
> # Description of the service
> wrapper.ntservice.description=Java Job Scheduler
>
> # 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
> # AUTO_START starts the service automatically when the system is rebooted.
> # DEMAND_START requires that the service must be started manually.
> wrapper.ntservice.starttype=DEMAND_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>
>
>
> Robert Pepersack
> Senior Lead Developer
> Maryland Insurance Administration
> 410-468-2054
>
> >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 8:56 AM >>>
> Hi Bob,
>
> thanks for your response. Yes, the AgentDaemon keeps running. But how
> to tell the Java Service Wrapper that this is the process it should
> concern about ?
>
> 2007/8/17, Robert Pepersack <RPe...@md...>:
> > Hi Mirko,
> >
> > I'm fairly new at using the wrapper, too, but maybe I can help.
> >
> > Does your AgentDaemon class start a process that keeps running?  Or, does it execute a simple method and terminate?  To keep the wrapper running, I've found that you have to run something that keeps the Java VM alive.  For example, I run a JNDI naming server.
> >
> > Bob
> >
> > Robert Pepersack
> > Senior Lead Developer
> > Maryland Insurance Administration
> > 410-468-2054
> >
> > >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
> > Hi all,
> >
> > I'm trying to integrate an application with Java Service Wrapper but
> > I'm stuck with a problem:
> > To start the application a class AgentClient ist called , which is
> > only a helper to run class AgentDaemon.
> > So I define class AgentClient as the initial class in java service
> > wrapper configuration . When starting the wrapper it calls this class,
> > AgentClient calls AgentDaemon and exit with
> > success. The service wrapper recognizes that and exits also, because
> > its focussed on AgentClient.
> > Do you have any hints to use such a construct within java service wrapper ?
> > Thanks in advance.
> >
> > --
> > With regards
> > Mirko Pluhar
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
>
>
> --
> Mit freundlichen Gruessen
> Mirko Pluhar
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>


-- 
Mit freundlichen Gruessen
Mirko Pluhar

Re: [Wrapper-user] helper class to start application

[Robert P. <RPe...@md...>]

Hi Mirko,

I don't know.  It worked for me without a problem.  I run the Quartz =
scheduler and the JBoss naming server.  Here is the content of my =
wrapper.conf file.  I hope it can help you.

#********************************************************************
# Wrapper Properties
#********************************************************************

wrapper.debug=3Dtrue

# Java Application
wrapper.java.command=3D../jdk1.5.0_11/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=3Dorg.tanukisoftware.wrapper.WrapperStartStopApp

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=3D../jdk1.5.0_11/lib/tools.jar
wrapper.java.classpath.2=3D../java/startup/lib/wrapper.jar
wrapper.java.classpath.3=3D../java/startup/lib/log4j-1.2.14.jar
wrapper.java.classpath.4=3D../java/startup/lib/startup.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=3D../bin

# Java Additional Parameters
wrapper.java.additional.1=3D-Dlog4j.properties.file=3D"../java/startup/lib/=
log4j.properties"
wrapper.java.additional.2=3D-Dserver.class.dir=3D"../java/common/classes"
wrapper.java.additional.3=3D-Dserver.lib.dir=3D"../java/common/lib"
wrapper.java.additional.4=3D-Ddata.source.dir=3D"../datasource"
wrapper.java.additional.5=3D-Djava.naming.factory.initial=3D"org.jnp.interf=
aces.NamingContextFactory"
wrapper.java.additional.6=3D-Djava.naming.factory.url.pkgs=3D"org.jnp.inter=
faces"
#wrapper.java.additional.7=3D-Djava.naming.provider.url=3D"localhost"

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

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

# Application parameters.  Add parameters as needed starting from 1
# The first application parameter is the name of the class whose main
# method is to be called when the application is launched.  The class
# name is followed by the number of parameters to be passed to its main
# method.  Then comes the actual parameters.
wrapper.app.parameter.1=3DmiaJs.server.Bootstrap
wrapper.app.parameter.2=3D1
wrapper.app.parameter.3=3Dstart

# The start parameters are followed by the name of the class whose main
# method is to be called to stop the application.  The stop class name
# is followed by a flag which controls whether or not the Wrapper should
# wait for all non daemon threads to complete before exiting the JVM.
# The flag is followed by the number of parameters to be passed to the
# stop class's main method.  Finally comes the actual parameters.
wrapper.app.parameter.4=3DmiaJs.server.Bootstrap
wrapper.app.parameter.5=3Dfalse
wrapper.app.parameter.6=3D1
wrapper.app.parameter.7=3Dstop

#********************************************************************
# Wrapper Logging Properties
#********************************************************************
# Format of output for the console.  (See docs for formats)
wrapper.console.format=3DPM

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

# Log file to use for wrapper output logging.
wrapper.logfile=3D../logs/wrapper.log

# Format of output for the log file.  (See docs for formats)
wrapper.logfile.format=3DLPTM

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

# 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 =3D 10 megabytes.
wrapper.logfile.maxsize=3D0

# 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=3D0

# Log Level for sys/event log output.  See docs for log levels.
wrapper.syslog.loglevel=3DNONE

#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=3DJava Job Scheduler

#********************************************************************
# 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=3DJJS

# Display name of the service
wrapper.ntservice.displayname=3DJJS

# Description of the service
wrapper.ntservice.description=3DJava Job Scheduler

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

# Mode in which the service is installed.  AUTO_START or DEMAND_START
# AUTO_START starts the service automatically when the system is =
rebooted.=20
# DEMAND_START requires that the service must be started manually.
wrapper.ntservice.starttype=3DDEMAND_START

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



Robert Pepersack
Senior Lead Developer
Maryland Insurance Administration
410-468-2054

>>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 8:56 AM >>>
Hi Bob,

thanks for your response. Yes, the AgentDaemon keeps running. But how
to tell the Java Service Wrapper that this is the process it should
concern about ?

2007/8/17, Robert Pepersack <RPe...@md...>:
> Hi Mirko,
>
> I'm fairly new at using the wrapper, too, but maybe I can help.
>
> Does your AgentDaemon class start a process that keeps running?  Or, =
does it execute a simple method and terminate?  To keep the wrapper =
running, I've found that you have to run something that keeps the Java VM =
alive.  For example, I run a JNDI naming server.
>
> Bob
>
> Robert Pepersack
> Senior Lead Developer
> Maryland Insurance Administration
> 410-468-2054
>
> >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
> Hi all,
>
> I'm trying to integrate an application with Java Service Wrapper but
> I'm stuck with a problem:
> To start the application a class AgentClient ist called , which is
> only a helper to run class AgentDaemon.
> So I define class AgentClient as the initial class in java service
> wrapper configuration . When starting the wrapper it calls this class,
> AgentClient calls AgentDaemon and exit with
> success. The service wrapper recognizes that and exits also, because
> its focussed on AgentClient.
> Do you have any hints to use such a construct within java service =
wrapper ?
> Thanks in advance.
>
> --
> With regards
> Mirko Pluhar
>
> -------------------------------------------------------------------------=

> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...=20
> https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
>
>
> -------------------------------------------------------------------------=

> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...=20
> https://lists.sourceforge.net/lists/listinfo/wrapper-user=20
>


--=20
Mit freundlichen Gruessen
Mirko Pluhar

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
_______________________________________________
Wrapper-user mailing list
Wra...@li...=20
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] helper class to start application

[Mirko P. <m.p...@gm...>]

Hi Bob,

thanks for your response. Yes, the AgentDaemon keeps running. But how
to tell the Java Service Wrapper that this is the process it should
concern about ?

2007/8/17, Robert Pepersack <RPe...@md...>:
> Hi Mirko,
>
> I'm fairly new at using the wrapper, too, but maybe I can help.
>
> Does your AgentDaemon class start a process that keeps running?  Or, does it execute a simple method and terminate?  To keep the wrapper running, I've found that you have to run something that keeps the Java VM alive.  For example, I run a JNDI naming server.
>
> Bob
>
> Robert Pepersack
> Senior Lead Developer
> Maryland Insurance Administration
> 410-468-2054
>
> >>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
> Hi all,
>
> I'm trying to integrate an application with Java Service Wrapper but
> I'm stuck with a problem:
> To start the application a class AgentClient ist called , which is
> only a helper to run class AgentDaemon.
> So I define class AgentClient as the initial class in java service
> wrapper configuration . When starting the wrapper it calls this class,
> AgentClient calls AgentDaemon and exit with
> success. The service wrapper recognizes that and exits also, because
> its focussed on AgentClient.
> Do you have any hints to use such a construct within java service wrapper ?
> Thanks in advance.
>
> --
> With regards
> Mirko Pluhar
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>


-- 
Mit freundlichen Gruessen
Mirko Pluhar

Re: [Wrapper-user] helper class to start application

[Robert P. <RPe...@md...>]

Hi Mirko,

I'm fairly new at using the wrapper, too, but maybe I can help.

Does your AgentDaemon class start a process that keeps running?  Or, does =
it execute a simple method and terminate?  To keep the wrapper running, =
I've found that you have to run something that keeps the Java VM alive.  =
For example, I run a JNDI naming server.

Bob

Robert Pepersack
Senior Lead Developer
Maryland Insurance Administration
410-468-2054

>>> "Mirko Pluhar" <m.p...@gm...> 08/17/2007 1:30 AM >>>
Hi all,

I'm trying to integrate an application with Java Service Wrapper but
I'm stuck with a problem:
To start the application a class AgentClient ist called , which is
only a helper to run class AgentDaemon.
So I define class AgentClient as the initial class in java service
wrapper configuration . When starting the wrapper it calls this class,
AgentClient calls AgentDaemon and exit with
success. The service wrapper recognizes that and exits also, because
its focussed on AgentClient.
Do you have any hints to use such a construct within java service wrapper =
?
Thanks in advance.

--=20
With regards
Mirko Pluhar

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/=20
_______________________________________________
Wrapper-user mailing list
Wra...@li...=20
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Cant get a thread-dump

[Markus S. <sc...@gm...>]

I don't know if this is the answer you are looking for, but we use JConsole
from the 1.5-Jdk to inspect the server if it has some troubles.
When we don't run in production, you can simply start your server with the
cmd-line flags:

wrapper.java.additional.10=-Dcom.sun.management.jmxremote.port=9999
wrapper.java.additional.11=-Dcom.sun.management.jmxremote.authenticate=false
wrapper.java.additional.12=-Dcom.sun.management.jmxremote.ssl=false

Then you can login on the specified port without any authentication.
In JConsole, go to the "Thread"-Tab and insoect all of your threads at
runtime.
For Production-Server, you have to configure the JMX-Authentication of
corse.

Markus


2007/8/16, miken <mik...@gm...>:
>
>
> Hi there,
>
> I'm interested in option 1. Does anybody have a simple example showing how
> to use requestThreadDump()? Especially, how to log on to the JMX console
> if
> there's a form based authentication mechanism (which will rely on a
> database
> to provide user / role information) in place.
>
> Thanks for your help in advance,
>
> Mike
>
>
> Leif Mortenson-2 wrote:
> >
> > Freddy,
> > There are a few ways to do this.
> >
> > 1) Make use of the WrapperManager.requestThreadDump() method.
> > This of course requires a hook into your application.
> >
> > 2) Make use of the WrapperActionServer class.
> > You have to add some code to initialize this class, but other than that
> > it is quite simple.  You can then initiate a thread dump or perform
> > other functions via telnet.
> >
> > 3) Use the command file feature to invoke the thread dump:
> > http://wrapper.tanukisoftware.org/doc/english/prop-commandfile.html
> > Please note that there is currently a problem in current versions
> > where the Wrapper can not invoke a thread dump unless a console
> > window exists for the service.   This has been fixed for the upcoming
> > 3.2.0 release.
> > To work around this in the current version you must either add a
> > console with the wrapper.ntservice.console=true property
> >
> http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-console.html
> > Or tell the wrapper to execute thread dumps if a shutdown failure
> > occurs: wrapper.request_thread_dump_on_failed_jvm_exit=true
> >
> http://wrapper.tanukisoftware.org/doc/english/prop-request-thread-dump-on-failed-jvm-exit.html
> >
> > Cheers,
> > Leif
> >
> > Freddy Andersen wrote:
> >> I'm running this on windows XP for now and I'm trying to figure out
> >> how I can get a thread-dump from the running wrapper (JBoss 4.0.2)
> >>
> >> I don't want to run this in a console window but as a service. When
> >> the server has issues I would like to send a signal to the jvm and get
> >> a thread-dump, is this not possible?
> >>
> >> Here is my config:
> > (snip)
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems?  Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >>  http://get.splunk.com/
> > _______________________________________________
> > Wrapper-user mailing list
> > Wra...@li...
> > https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Re%3A-Cant-get-a-thread-dump-tf4154131.html#a12189421
> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] helper class to start application

[Mirko P. <m.p...@gm...>]

Hi all,

I'm trying to integrate an application with Java Service Wrapper but
I'm stuck with a problem:
To start the application a class AgentClient ist called , which is
only a helper to run class AgentDaemon.
So I define class AgentClient as the initial class in java service
wrapper configuration . When starting the wrapper it calls this class,
AgentClient calls AgentDaemon and exit with
success. The service wrapper recognizes that and exits also, because
its focussed on AgentClient.
Do you have any hints to use such a construct within java service wrapper ?
Thanks in advance.

-- 
With regards
Mirko Pluhar

Re: [Wrapper-user] Cant get a thread-dump

[miken <mik...@gm...>]

Hi there,

I'm interested in option 1. Does anybody have a simple example showing how
to use requestThreadDump()? Especially, how to log on to the JMX console if
there's a form based authentication mechanism (which will rely on a database
to provide user / role information) in place.

Thanks for your help in advance,

Mike


Leif Mortenson-2 wrote:
> 
> Freddy,
> There are a few ways to do this.
> 
> 1) Make use of the WrapperManager.requestThreadDump() method.
> This of course requires a hook into your application.
> 
> 2) Make use of the WrapperActionServer class.
> You have to add some code to initialize this class, but other than that
> it is quite simple.  You can then initiate a thread dump or perform
> other functions via telnet.
> 
> 3) Use the command file feature to invoke the thread dump:
> http://wrapper.tanukisoftware.org/doc/english/prop-commandfile.html
> Please note that there is currently a problem in current versions
> where the Wrapper can not invoke a thread dump unless a console
> window exists for the service.   This has been fixed for the upcoming
> 3.2.0 release.
> To work around this in the current version you must either add a
> console with the wrapper.ntservice.console=true property
> http://wrapper.tanukisoftware.org/doc/english/prop-ntservice-console.html
> Or tell the wrapper to execute thread dumps if a shutdown failure
> occurs: wrapper.request_thread_dump_on_failed_jvm_exit=true
> http://wrapper.tanukisoftware.org/doc/english/prop-request-thread-dump-on-failed-jvm-exit.html
> 
> Cheers,
> Leif
> 
> Freddy Andersen wrote:
>> I'm running this on windows XP for now and I'm trying to figure out 
>> how I can get a thread-dump from the running wrapper (JBoss 4.0.2)
>>
>> I don't want to run this in a console window but as a service. When 
>> the server has issues I would like to send a signal to the jvm and get 
>> a thread-dump, is this not possible?
>>
>> Here is my config:
> (snip)
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 
> 

-- 
View this message in context: http://www.nabble.com/Re%3A-Cant-get-a-thread-dump-tf4154131.html#a12189421
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

Re: [Wrapper-user] IOException when run inside wrapper

[Stephen K. <st...@sp...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
The quick fix would be to process the file as a stream without
transferring the whole file to memory.<br>
<br>
Have you tried running it directly as the user the service is running
as.<br>
<br>
Try add the following to your code to make sure that your memory flags
are indeed being used. I assume you set this in the wrapper.conf file.<br>
<br>
<font face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono">R</font><font
 face="Courier New, Courier, mono" size="2">untime runtime =
Runtime.getRuntime();<br>
<strong><font color="#000080">long</font></strong> maxMemory =
runtime.maxMemory(); <br>
</font><font face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2"><strong><font
 color="#000080">long</font></strong></font></font><font
 face="Courier New, Courier, mono" size="2"> allocatedMemory =
runtime.totalMemory(); <br>
</font><font face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2"><strong><font
 color="#000080">long</font></strong></font></font><font
 face="Courier New, Courier, mono" size="2"> freeMemory =
runtime.freeMemory(); <br>
</font><font face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2">System.out.println(<font
 color="#000080">"free memory: "</font> + </font><font
 face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2">freeMemory</font></font><font
 face="Courier New, Courier, mono" size="2"> / <font color="#000080">1024</font>);</font><font
 face="Arial, Helvetica, sans-serif" size="2"> </font></font><br>
<font face="Courier New, Courier, mono" size="2"> </font><font
 face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2">System.out.println(<font
 color="#000080">"allocated memory: "</font> + </font><font
 face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2">allocatedMemory</font></font><font
 face="Courier New, Courier, mono" size="2"> / <font color="#000080">1024</font>);</font><font
 face="Arial, Helvetica, sans-serif" size="2"> </font></font><br>
<font face="Courier New, Courier, mono" size="2">System.out.println(<font
 color="#000080">"max memory: "</font> + </font><font
 face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2">maxMemory</font></font><font
 face="Courier New, Courier, mono" size="2"> / <font color="#000080">1024</font>);<br>
System.out.println(<font color="#000080">"total free memory: "</font> +
(freeMemory + (maxMemory - allocatedMemory)) / <font color="#000080">1024</font>);</font></font><br>
<br>
Also try add<br>
# Java Additional Parameters<br>
wrapper.java.additional.1=-server<br>
<br>
<font face="Arial, Helvetica, sans-serif" size="2"><font
 face="Courier New, Courier, mono" size="2"><br>
<br>
HTH<br>
Stephen<br>
</font></font><br>
Andrew Rhodes wrote:
<blockquote
 cite="mid...@ma..."
 type="cite">
  <div><span class="067531607-04082007"><font face="Arial" size="2">Hi,</font></span></div>
  <div><span class="067531607-04082007"></span>&nbsp;</div>
  <div><span class="067531607-04082007"><font face="Arial" size="2">I
have a simple app which runs a timer task at scheduled intervals and
reads files off of the file system into a byte array and then does some
other processing (not relevant).&nbsp; When run&nbsp;as a service on a windows
machine (using the simple wrapper method), I get an IOException -
Insufficient system resources exist to complete the requested service
for large files.&nbsp; Large seems to be anything above 66 Mb and always
causes the same error message.&nbsp; I adjusted the jvm min/max to 64 and
512 (and 1024), with still the same result.&nbsp; The exception is thrown
when reading the file into the byte array.&nbsp; It reads smaller files no
problem.
  </font></span></div>
  <div><span class="067531607-04082007"></span>&nbsp;</div>
  <div><span class="067531607-04082007"><font face="Arial" size="2">I'm
not sure if it is related to jsw, but I tested the same file reader
function code outside jsw and could read a 320 Mb file Ok with same jvm
params, hence why I posted this message.&nbsp;
  </font></span></div>
  <div><span class="067531607-04082007"></span>&nbsp;</div>
  <div><font face="Arial" size="2"><span class="067531607-04082007">Grateful
for any thoughts on this.</span></font></div>
  <div><font face="Arial" size="2"><span class="067531607-04082007"></span></font>&nbsp;</div>
  <div><font face="Arial" size="2"><span class="067531607-04082007">Andy</span></font></div>
  <pre wrap="">
<hr size="4" width="90%">
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now &gt;&gt;  <a class="moz-txt-link-freetext" href="http://get.splunk.com/">http://get.splunk.com/</a></pre>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Wrapper-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Wra...@li...">Wra...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/wrapper-user">https://lists.sourceforge.net/lists/listinfo/wrapper-user</a>
  </pre>
</blockquote>
</body>
</html>

[Wrapper-user] IOException when run inside wrapper

[Andrew R. <and...@gm...>]

Hi,

I have a simple app which runs a timer task at scheduled intervals and reads
files off of the file system into a byte array and then does some other
processing (not relevant).  When run as a service on a windows machine
(using the simple wrapper method), I get an IOException - Insufficient
system resources exist to complete the requested service for large files.
Large seems to be anything above 66 Mb and always causes the same error
message.  I adjusted the jvm min/max to 64 and 512 (and 1024), with still
the same result.  The exception is thrown when reading the file into the
byte array.  It reads smaller files no problem.

I'm not sure if it is related to jsw, but I tested the same file reader
function code outside jsw and could read a 320 Mb file Ok with same jvm
params, hence why I posted this message.

Grateful for any thoughts on this.

Andy

[Wrapper-user] JSW and Windows Vista

[Dave H. <DH...@xr...>]

Are there any guidelines regarding using JSW on Windows Vista with UAC?
Specifically installation locations and log file locations.  If I
install to the Program Files location, will I have trouble writing log
files in this location?  Is there a way to direct log files to a
non-relative path?  If so, where is the best location for log files
since I doubt there is a valid user.home value since the service is run
as a system account.  It seems that directing log info to the event
viewer would solve this issue, but is this possible?

Any thoughts or ideas?

-Dave

Re: [Wrapper-user] Automatic JVM Restart

[Hubert F. <hub...@ab...>]

Let your application write "Restart me now." to the console every 7
days. Use the Wrapper filter option to catch that output and do whatever
you want with it.
Hubert


# The string being filtered can contain spaces. But due to the way
# the configuration properties are loaded in general, any leading
# of trailing spaces will be trimmed when the property is loaded.
wrapper.filter.trigger.1=Restart me now.
wrapper.filter.action.1=RESTART


>>> "Jacob Caniparoli" <jca...@gm...> 01.08.2007 20:57 >>>
Is there any way to have the JVM restart itself every X amount of time?
 For
example, I want mine to restart itself every 7 days.  Is this something
that
is doable with the wrapper?

>>> "Jacob Caniparoli" <jca...@gm...> 01.08.2007 20:57 >>>
Is there any way to have the JVM restart itself every X amount of time?
 For
example, I want mine to restart itself every 7 days.  Is this something
that
is doable with the wrapper?

Re: [Wrapper-user] Wrapper compilation on HP-UX IA64 ?

[Tim W. <Tim...@or...>]

QnkgImZhaWxzIHdpdGggZXJyb3IiIEkgYWN0dWFsbHkgbWVhbiAic2hvd3MgdGhlIHNhbWUgd2Fy
bmluZyIuDQpUaGUgd3JhcHBlciBhY3R1YWxseSBidWlsZHMgYW5kIGV4ZWN1dGVzIGZpbmUuDQoN
CnRpbQ0KDQogIA0KDQpUaW0gV2hpdHRpbmd0b24NCkRldmVsb3BtZW50IFVuaXQgTWFuYWdlciAt
IENvbmNlcnRvIFBvcnRhbA0KVGltLldoaXR0aW5ndG9uQG9yaW9uaGVhbHRoLmNvbQ0KUDogKzY0
IDkgNjM4IDA2MDAgeDM4NzMNCk06ICs2NCAyMSAzMDcgOTI1IA0KRjogKzY0IDkgNjM4IDA2OTkN
ClM6IHRpbS53aGl0dGluZ3Rvbg0Kd3d3Lm9yaW9uaGVhbHRoLmNvbSANCg0KDQpUaGlzIGUtbWFp
bCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBpbnRlbmRlZCBvbmx5IGZvciB0aGUgcGVyc29uIHRv
IHdob20gaXQgaXMgYWRkcmVzc2VkIGFuZCBtYXkgY29udGFpbiBwcml2aWxlZ2VkLCBwcm9wcmll
dGFyeSwgb3Igb3RoZXIgZGF0YSBwcm90ZWN0ZWQgZnJvbSBkaXNjbG9zdXJlIHVuZGVyIGFwcGxp
Y2FibGUgbGF3LiBJZiB5b3UgYXJlIG5vdCB0aGUgYWRkcmVzc2VlIG9yIHRoZSBwZXJzb24gcmVz
cG9uc2libGUgZm9yIGRlbGl2ZXJpbmcgdGhpcyB0byB0aGUgYWRkcmVzc2VlIHlvdSBhcmUgaGVy
ZWJ5IG5vdGlmaWVkIHRoYXQgcmVhZGluZywgY29weWluZyBvciBkaXN0cmlidXRpbmcgdGhpcyB0
cmFuc21pc3Npb24gaXMgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlLW1h
aWwgaW4gZXJyb3IsIHBsZWFzZSB0ZWxlcGhvbmUgdXMgaW1tZWRpYXRlbHkgYW5kIHJlbW92ZSBh
bGwgY29waWVzIG9mIGl0IGZyb20geW91ciBzeXN0ZW0uIFRoYW5rIHlvdSBmb3IgeW91ciBjby1v
cGVyYXRpb24uDQoNCg0KPj4+IE9uIDIvMDgvMjAwNyBhdCAyOjA0IHAubS4sIGluIG1lc3NhZ2Ug
PDQ2QjFFNDg1LjVBNTcuMDBBQS4wQG9yaW9uaGVhbHRoLmNvbT4sICJUaW0gV2hpdHRpbmd0b24i
IDxUaW0uV2hpdHRpbmd0b25Ab3Jpb25oZWFsdGguY29tPiB3cm90ZToNCg0KSSd2ZSBidWlsdCB0
aGUgMy4yLjMgdmVyc2lvbiAoYnV0IG5vdCB0cnVuaykgb2YgdGhlIHdyYXBwZXIgb24gSFAtVVgg
SUE2NCBydW5uaW5nIDExLjIzIHdpdGggZWZmZWN0aXZlbHkgdGhlIHNhbWUgYnVpbGQgZmlsZSB5
b3UncmUgdHJ5aW5nIHRvIHVzZS4NCk15IHRydW5rIGJ1aWxkIGZhaWxzIHdpdGggdGhlIHNhbWUg
ZXJyb3IuDQpJJ2QgYXNzdW1lIHRoZW4gdGhhdCB0aGlzIGlzIGEgY29kZSBwcm9ibGVtIC0geW91
IGNvdWxkIHRyeSBidWlsZGluZyBmb3IgcGFyaXNjIGJ1dCBJIHN1c3BlY3QgeW91J2xsIGdldCB0
aGUgc2FtZSBpc3N1ZS4NCg0KdGltDQoNCiAgDQoNClRpbSBXaGl0dGluZ3Rvbg0KRGV2ZWxvcG1l
bnQgVW5pdCBNYW5hZ2VyIC0gQ29uY2VydG8gUG9ydGFsDQpUaW0uV2hpdHRpbmd0b25Ab3Jpb25o
ZWFsdGguY29tDQpQOiArNjQgOSA2MzggMDYwMCB4Mzg3Mw0KTTogKzY0IDIxIDMwNyA5MjUgDQpG
OiArNjQgOSA2MzggMDY5OQ0KUzogdGltLndoaXR0aW5ndG9uDQp3d3cub3Jpb25oZWFsdGguY29t
IA0KDQoNClRoaXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGludGVuZGVkIG9ubHkg
Zm9yIHRoZSBwZXJzb24gdG8gd2hvbSBpdCBpcyBhZGRyZXNzZWQgYW5kIG1heSBjb250YWluIHBy
aXZpbGVnZWQsIHByb3ByaWV0YXJ5LCBvciBvdGhlciBkYXRhIHByb3RlY3RlZCBmcm9tIGRpc2Ns
b3N1cmUgdW5kZXIgYXBwbGljYWJsZSBsYXcuIElmIHlvdSBhcmUgbm90IHRoZSBhZGRyZXNzZWUg
b3IgdGhlIHBlcnNvbiByZXNwb25zaWJsZSBmb3IgZGVsaXZlcmluZyB0aGlzIHRvIHRoZSBhZGRy
ZXNzZWUgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCByZWFkaW5nLCBjb3B5aW5nIG9yIGRp
c3RyaWJ1dGluZyB0aGlzIHRyYW5zbWlzc2lvbiBpcyBwcm9oaWJpdGVkLiBJZiB5b3UgaGF2ZSBy
ZWNlaXZlZCB0aGlzIGUtbWFpbCBpbiBlcnJvciwgcGxlYXNlIHRlbGVwaG9uZSB1cyBpbW1lZGlh
dGVseSBhbmQgcmVtb3ZlIGFsbCBjb3BpZXMgb2YgaXQgZnJvbSB5b3VyIHN5c3RlbS4gVGhhbmsg
eW91IGZvciB5b3VyIGNvLW9wZXJhdGlvbi4NCg0KDQo+Pj4gT24gMi8wOC8yMDA3IGF0IDU6NDUg
YS5tLiwgaW4gbWVzc2FnZSA8MjA1RjlCRDBDQjNEQUQ0QUI2MDU0QTU2NEFEMkE0REM3MTc0OTI3
QzNFQEczVzExMTIuYW1lcmljYXMuaHBxY29ycC5uZXQ+LCAiTWFyemlvdSwgR2FlbCIgPGdhZWwu
bWFyemlvdUBocC5jb20+IHdyb3RlOg0KDQoNCkhlbGxvLA0KDQpJIGxvb2tlZCBhdCB0aGUgU1ZO
IHRydW5rICMxMzc2IGFuZCB0cmllZCB0byBjb21waWxlIG9uIGFuIEl0YW5pdW0gc2VydmVyIHJ1
bm5pbmcgSFAtVVggMTEuMjMsIGl0IGZhaWxzIHdoaWxlIGxvb2tpbmcgZm9yIGEgbWlzc2luZyBt
YWtlZmlsZTogTWFrZWZpbGUtaHB1eC1JQTY0Ti0zMi5nbWFrZQ0KDQpTbywgSSB0cmllZCB0byB1
c2UgTWFrZWZpbGUtaHB1eC1wYXJpc2MtMzIuZ21ha2UgYW5kIHdoaWxlIGl0IHNheXMgc3VjY2Vz
c2Z1bCBpdCByYWlzZWQgc29tZSB3ZWlyZCB3YXJuaW5nczoNCg0KICAgICBbZXhlY10gZ2NjIC1P
MyAtV2FsbCAtLXBlZGFudGljIC1ESFBVWCAtRF9YT1BFTl9TT1VSQ0VfRVhURU5ERUQgd3JhcHBl
ci5jIHdyYXBwZXJpbmZvLmMgd3JhcHBlcmV2ZW50bG9vcC5jIHdyYXBwZXJfdW5peC5jIHByb3Bl
cnR5LmMgbG9nZ2VyLmMgLWxtIC1scHRocmVhZCAtbyAuLi8uLi9iaW4vd3JhcHBlcg0KICAgICBb
ZXhlY10gd3JhcHBlci5jOiBJbiBmdW5jdGlvbiAncHJvdG9jb2xPcGVuJzoNCiAgICAgW2V4ZWNd
IHdyYXBwZXIuYzo1MzQ6IHdhcm5pbmc6IHBhc3NpbmcgYXJndW1lbnQgMyBvZiAnYWNjZXB0JyBm
cm9tIGluY29tcGF0aWJsZSBwb2ludGVyIHR5cGUNCg0KSSBoYXZlbid0IHRyaWVkIHlldCB0byBy
dW4gaXQgYXMgSSBuZWVkIHRvIHdyaXRlIGEgbGl0dGxlIGphdmEgY2xhc3MgZm9yIHRoaXMuDQoN
CklzIHRoZXJlIHNvbWVvbmUgd2hvIGFscmVhZHkgZGlkIHRoaXM/DQpXb3VsZCBpdCBiZSBiZXR0
ZXIgdG8gdXNlIHRoZSBQQS1SSVNDIGJpbmFyaWVzPw0KDQpUaGFua3MsDQoNCkdhZWwNCg0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLQ0KVGhpcyBTRi5uZXQgZW1haWwgaXMgc3BvbnNvcmVkIGJ5OiBTcGx1bmsg
SW5jLg0KU3RpbGwgZ3JlcHBpbmcgdGhyb3VnaCBsb2cgZmlsZXMgdG8gZmluZCBwcm9ibGVtcz8g
IFN0b3AuDQpOb3cgU2VhcmNoIGxvZyBldmVudHMgYW5kIGNvbmZpZ3VyYXRpb24gZmlsZXMgdXNp
bmcgQUpBWCBhbmQgYSBicm93c2VyLg0KRG93bmxvYWQgeW91ciBGUkVFIGNvcHkgb2YgU3BsdW5r
IG5vdyA+PiAgaHR0cDovL2dldC5zcGx1bmsuY29tLw0KX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCldyYXBwZXItdXNlciBtYWlsaW5nIGxpc3QNCldyYXBw
ZXItdXNlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCmh0dHBzOi8vbGlzdHMuc291cmNlZm9yZ2Uu
bmV0L2xpc3RzL2xpc3RpbmZvL3dyYXBwZXItdXNlcg==

Re: [Wrapper-user] Wrapper compilation on HP-UX IA64 ?

[Tim W. <Tim...@or...>]

SSd2ZSBidWlsdCB0aGUgMy4yLjMgdmVyc2lvbiAoYnV0IG5vdCB0cnVuaykgb2YgdGhlIHdyYXBw
ZXIgb24gSFAtVVggSUE2NCBydW5uaW5nIDExLjIzIHdpdGggZWZmZWN0aXZlbHkgdGhlIHNhbWUg
YnVpbGQgZmlsZSB5b3UncmUgdHJ5aW5nIHRvIHVzZS4NCk15IHRydW5rIGJ1aWxkIGZhaWxzIHdp
dGggdGhlIHNhbWUgZXJyb3IuDQpJJ2QgYXNzdW1lIHRoZW4gdGhhdCB0aGlzIGlzIGEgY29kZSBw
cm9ibGVtIC0geW91IGNvdWxkIHRyeSBidWlsZGluZyBmb3IgcGFyaXNjIGJ1dCBJIHN1c3BlY3Qg
eW91J2xsIGdldCB0aGUgc2FtZSBpc3N1ZS4NCg0KdGltDQoNCiAgDQoNClRpbSBXaGl0dGluZ3Rv
bg0KRGV2ZWxvcG1lbnQgVW5pdCBNYW5hZ2VyIC0gQ29uY2VydG8gUG9ydGFsDQpUaW0uV2hpdHRp
bmd0b25Ab3Jpb25oZWFsdGguY29tDQpQOiArNjQgOSA2MzggMDYwMCB4Mzg3Mw0KTTogKzY0IDIx
IDMwNyA5MjUgDQpGOiArNjQgOSA2MzggMDY5OQ0KUzogdGltLndoaXR0aW5ndG9uDQp3d3cub3Jp
b25oZWFsdGguY29tIA0KDQoNClRoaXMgZS1tYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGlu
dGVuZGVkIG9ubHkgZm9yIHRoZSBwZXJzb24gdG8gd2hvbSBpdCBpcyBhZGRyZXNzZWQgYW5kIG1h
eSBjb250YWluIHByaXZpbGVnZWQsIHByb3ByaWV0YXJ5LCBvciBvdGhlciBkYXRhIHByb3RlY3Rl
ZCBmcm9tIGRpc2Nsb3N1cmUgdW5kZXIgYXBwbGljYWJsZSBsYXcuIElmIHlvdSBhcmUgbm90IHRo
ZSBhZGRyZXNzZWUgb3IgdGhlIHBlcnNvbiByZXNwb25zaWJsZSBmb3IgZGVsaXZlcmluZyB0aGlz
IHRvIHRoZSBhZGRyZXNzZWUgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCByZWFkaW5nLCBj
b3B5aW5nIG9yIGRpc3RyaWJ1dGluZyB0aGlzIHRyYW5zbWlzc2lvbiBpcyBwcm9oaWJpdGVkLiBJ
ZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGUtbWFpbCBpbiBlcnJvciwgcGxlYXNlIHRlbGVwaG9u
ZSB1cyBpbW1lZGlhdGVseSBhbmQgcmVtb3ZlIGFsbCBjb3BpZXMgb2YgaXQgZnJvbSB5b3VyIHN5
c3RlbS4gVGhhbmsgeW91IGZvciB5b3VyIGNvLW9wZXJhdGlvbi4NCg0KDQo+Pj4gT24gMi8wOC8y
MDA3IGF0IDU6NDUgYS5tLiwgaW4gbWVzc2FnZSA8MjA1RjlCRDBDQjNEQUQ0QUI2MDU0QTU2NEFE
MkE0REM3MTc0OTI3QzNFQEczVzExMTIuYW1lcmljYXMuaHBxY29ycC5uZXQ+LCAiTWFyemlvdSwg
R2FlbCIgPGdhZWwubWFyemlvdUBocC5jb20+IHdyb3RlOg0KDQoNCkhlbGxvLA0KDQpJIGxvb2tl
ZCBhdCB0aGUgU1ZOIHRydW5rICMxMzc2IGFuZCB0cmllZCB0byBjb21waWxlIG9uIGFuIEl0YW5p
dW0gc2VydmVyIHJ1bm5pbmcgSFAtVVggMTEuMjMsIGl0IGZhaWxzIHdoaWxlIGxvb2tpbmcgZm9y
IGEgbWlzc2luZyBtYWtlZmlsZTogTWFrZWZpbGUtaHB1eC1JQTY0Ti0zMi5nbWFrZQ0KDQpTbywg
SSB0cmllZCB0byB1c2UgTWFrZWZpbGUtaHB1eC1wYXJpc2MtMzIuZ21ha2UgYW5kIHdoaWxlIGl0
IHNheXMgc3VjY2Vzc2Z1bCBpdCByYWlzZWQgc29tZSB3ZWlyZCB3YXJuaW5nczoNCg0KICAgICBb
ZXhlY10gZ2NjIC1PMyAtV2FsbCAtLXBlZGFudGljIC1ESFBVWCAtRF9YT1BFTl9TT1VSQ0VfRVhU
RU5ERUQgd3JhcHBlci5jIHdyYXBwZXJpbmZvLmMgd3JhcHBlcmV2ZW50bG9vcC5jIHdyYXBwZXJf
dW5peC5jIHByb3BlcnR5LmMgbG9nZ2VyLmMgLWxtIC1scHRocmVhZCAtbyAuLi8uLi9iaW4vd3Jh
cHBlcg0KICAgICBbZXhlY10gd3JhcHBlci5jOiBJbiBmdW5jdGlvbiAncHJvdG9jb2xPcGVuJzoN
CiAgICAgW2V4ZWNdIHdyYXBwZXIuYzo1MzQ6IHdhcm5pbmc6IHBhc3NpbmcgYXJndW1lbnQgMyBv
ZiAnYWNjZXB0JyBmcm9tIGluY29tcGF0aWJsZSBwb2ludGVyIHR5cGUNCg0KSSBoYXZlbid0IHRy
aWVkIHlldCB0byBydW4gaXQgYXMgSSBuZWVkIHRvIHdyaXRlIGEgbGl0dGxlIGphdmEgY2xhc3Mg
Zm9yIHRoaXMuDQoNCklzIHRoZXJlIHNvbWVvbmUgd2hvIGFscmVhZHkgZGlkIHRoaXM/DQpXb3Vs
ZCBpdCBiZSBiZXR0ZXIgdG8gdXNlIHRoZSBQQS1SSVNDIGJpbmFyaWVzPw0KDQpUaGFua3MsDQoN
CkdhZWwNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KVGhpcyBTRi5uZXQgZW1haWwgaXMgc3BvbnNvcmVk
IGJ5OiBTcGx1bmsgSW5jLg0KU3RpbGwgZ3JlcHBpbmcgdGhyb3VnaCBsb2cgZmlsZXMgdG8gZmlu
ZCBwcm9ibGVtcz8gIFN0b3AuDQpOb3cgU2VhcmNoIGxvZyBldmVudHMgYW5kIGNvbmZpZ3VyYXRp
b24gZmlsZXMgdXNpbmcgQUpBWCBhbmQgYSBicm93c2VyLg0KRG93bmxvYWQgeW91ciBGUkVFIGNv
cHkgb2YgU3BsdW5rIG5vdyA+PiAgaHR0cDovL2dldC5zcGx1bmsuY29tLw0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCldyYXBwZXItdXNlciBtYWlsaW5n
IGxpc3QNCldyYXBwZXItdXNlckBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCmh0dHBzOi8vbGlzdHMu
c291cmNlZm9yZ2UubmV0L2xpc3RzL2xpc3RpbmZvL3dyYXBwZXItdXNlcg==

[Wrapper-user] How to customize wrapper startup error messages?

[coderobo <cod...@gm...>]

I would like to customize (and if possible internationalize) the error
messages that come out of wrapper start up script (Linux). For example if
wrapper can not locate java on the path, it spits out -

STATUS | wrapper  | main    | 2007/08/01 04:23:58.138 | Launching a JVM...
ERROR  | wrapper  | main    | 2007/08/01 04:23:58.142 | Unable to start JVM:
No such file or directory (2)
ERROR  | wrapper  | main    | 2007/08/01 04:23:58.252 | Unable to start a
JVM

I would like to give a more detailed message explaining what is expected of
the admin. In this instance my wrapper.conf contains
"wrapper.java.command=%MY_JAVA_HOME%/bin/java" . I would like to spit out an
error message asking the admin to set the MY_JAVA_HOME env variable. Short
of changing the code, any way to customize this via wrapper.conf properties
? I looked through the docs couldn't find any thing relevant.

Thanks
-- 
View this message in context: http://www.nabble.com/How-to-customize-wrapper-startup-error-messages--tf4203212.html#a11955492
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

Re: [Wrapper-user] Automatic JVM Restart

[Kit P. <kit...@gm...>]

I'm sure you could combine JSW and cron to do something of the sort.  Are
you on Winders or *nix?


On 8/1/07, Jacob Caniparoli <jca...@gm...> wrote:
>
> Is there any way to have the JVM restart itself every X amount of time?
> For example, I want mine to restart itself every 7 days.  Is this something
> that is doable with the wrapper?
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>


-- 
Kit Plummer
Nobody-in-Charge @ Black:Hole:Logic
http://www.blackholelogic.com

[Wrapper-user] Automatic JVM Restart

[Jacob C. <jca...@gm...>]

Is there any way to have the JVM restart itself every X amount of time?  For
example, I want mine to restart itself every 7 days.  Is this something that
is doable with the wrapper?

[Wrapper-user] Wrapper compilation on HP-UX IA64 ?

[Marziou, G. <gae...@hp...>]

Hello,

I looked at the SVN trunk #1376 and tried to compile on an Itanium server r=
unning HP-UX 11.23, it fails while looking for a missing makefile: Makefile=
-hpux-IA64N-32.gmake

So, I tried to use Makefile-hpux-parisc-32.gmake and while it says successf=
ul it raised some weird warnings:

     [exec] gcc -O3 -Wall --pedantic -DHPUX -D_XOPEN_SOURCE_EXTENDED wrappe=
r.c wrapperinfo.c wrappereventloop.c wrapper_unix.c property.c logger.c -lm=
 -lpthread -o ../../bin/wrapper
     [exec] wrapper.c: In function 'protocolOpen':
     [exec] wrapper.c:534: warning: passing argument 3 of 'accept' from inc=
ompatible pointer type

I haven't tried yet to run it as I need to write a little java class for th=
is.

Is there someone who already did this?
Would it be better to use the PA-RISC binaries?

Thanks,

Gael

[Wrapper-user] In there a way to know why the wrapper has been stopped.

[Xavier R. <xR...@in...>]

Hi,

Currently I'm using the Java Service Wrapper and everything works fine.

My application is managing others applications and I would like to know
if an application has been well stopped or not.
By example I would like to know if the application has been stopped
normally (Requested by the user) or stopped because
the wrapper gives up to restart the application after too many failed
launches.

Is there any way to do this ?

Thanks in advance for your answer.

Xavier.

Re: [Wrapper-user] How to print STATUS log level?

[Ram N. <ra...@gm...>]

Leif,
I will explain a little more what I am doing,
I'm running a Tomcat server on Windows machine, the server is started by the
wrapper and this is working well.
My web application uses both Java and JNI calls to dll's I wrote.
The Java part of the application is working well and log levels are OK, my
problem is when I want to use log levels on the messages written to the
console from the dll's.
Currently the dll is using simple printf(), all those messages are written
by the wrapper as if they were INFO level logs.
I am looking for away to control the log level for those messages.
Thanks
-Ram

[Wrapper-user] Wrapping ServiceMix on Linux...

[Kit P. <kit...@gm...>]

I'm having a problem with getting the classloader's config file to the
classloader's Launcher.

here's the output of the wrapper:

wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
jvm 1    | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org
jvm 1    |   Copyright 1999-2006 Tanuki Software, Inc.  All Rights Reserved.
jvm 1    |
jvm 1    |
jvm 1    | WrapperSimpleApp: Encountered an error running main:
java.io.FileNotFoundException: "/home/tsb/deploy/conf/servicemix.conf" (No
such file or directory)
jvm 1    | java.io.FileNotFoundException:
"/home/tsb/deploy/conf/servicemix.conf" (No such file or directory)
jvm 1    |      at java.io.FileInputStream.open(Native Method)
jvm 1    |      at java.io.FileInputStream.<init>(FileInputStream.java:106)
jvm 1    |      at java.io.FileInputStream.<init>(FileInputStream.java :66)
jvm 1    |      at org.codehaus.classworlds.Launcher.main(Launcher.java:435)
jvm 1    |      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
Method)
jvm 1    |      at sun.reflect.NativeMethodAccessorImpl.invoke (
NativeMethodAccessorImpl.java:39)
jvm 1    |      at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
jvm 1    |      at java.lang.reflect.Method.invoke(Method.java:597)
jvm 1    |      at org.tanukisoftware.wrapper.WrapperSimpleApp.run(
WrapperSimpleApp.java:240)
jvm 1    |      at java.lang.Thread.run(Thread.java:619)
wrapper  | <-- Wrapper Stopped

And, here's the config:
<snip>
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
wrapper.app.parameter.1=org.codehaus.classworlds.Launcher

# 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=../lib/classworlds-1.0.1.jar
wrapper.java.classpath.3=../.
wrapper.java.classpath.4=../conf

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

# Java Additional Parameters
#wrapper.java.additional.1=
#wrapper.java.additional.1=-Dderby.system.home="var"
#wrapper.java.additional.2=- Dderby.storage.fileSyncTransactionLog=true
wrapper.java.additional.1=-Dcom.sun.management.jmxremote
wrapper.java.additional.2=-Dclassworlds.conf="/home/tsb/deploy/conf/servicemix.conf"

wrapper.java.additional.3=-Dservicemix.home= "."

</snip>

I'm running the thing from the deploy/ subdir - but, I don't think this is a
classpath issue, and the Launcher is looking for file path.

Any ideas?  Anything obvious?

TIA,
Kit


-- 
Kit Plummer
Nobody-in-Charge @ Black:Hole:Logic
http://www.blackholelogic.com