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

[Wrapper-user] Swing GUI not working in Windows 7

[Gaurav P. <gau...@tc...>]

Hi

We have an application that uses swings to display pop up messages and 
accept user inputs. For e.g.

JOptionPane.showInputDialog("Enter User Id");

This when converted to Windows service works perfectly fine in Windows XP. 
It displays proper pop ups as expected.

But same service when installed in Windows 7 does not show pop ups. The 
program just waits there. We added following in conf file, but to no 
avail.

wrapper.ntservice.interactive=true
wrapper.ntservice.hide_console=true

We also checked Windows Registry and set 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\NoInteractiveServices 
to 0. But the same does not work.

Below is the conf file:

wrapper.lang.folder=../lang

#********************************************************************
# Wrapper Java Properties
#********************************************************************
# Java Application
#  Locate the java binary on the system PATH:
wrapper.java.command=java

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

# 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=../lib/auto-upload.jar
wrapper.java.classpath.3=../lib/log4j-1.2.11.jar
wrapper.java.classpath.4=../lib/commons-io-2.0.jar
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib

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

wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=FALSE

# Java Additional Parameters
#wrapper.java.additional.2=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.maxStartMainWait=300

# 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=com.auto.upload.client.AutoFileUpload

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

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

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

# Log file to use for wrapper output logging.
wrapper.logfile=../system.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=2m

# 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=NONE

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

# Title to use when running as a console
wrapper.console.title=Automatic File Upload Service

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

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

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

# Name of the service
wrapper.name=Automatic File Upload

# Display name of the service
wrapper.displayname=Automatic File Upload Service

# Description of the service
wrapper.description=Automatic File Upload Application.

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

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

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

Please help.

Thanks & Regards
Gaurav
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

[Wrapper-user] Version 3.5.4 works in XP but not in Windows 7.

[Gaurav P. <gau...@tc...>]

Hi,

We are using Java wrapper service version 3.5.4. It works fine in Windows 
XP machine. But the same does not work in Windows 7. 

The application starts by displaying a swing pop up and prompts user to 
enter user id. As mentioned above, same works fine in XP but not in 
windows 7. Windows 7 does not display pop up. 

Do I need to upgrade java wrapper service version to make it work in 
windows 7 as well?

Thanks & Regards
Gaurav Goel
Tata Consultancy Services
1st, 2nd, 3rd & 6th Floor
Empire Plaza, L B S Marg, Vikhroli (West)
Mumbai - 400083,Maharashtra
India
Ph:- 9122677 86259
Mailto: gau...@tc...
Website: http://www.tcs.com
____________________________________________
Experience certainty.   IT Services
                        Business Solutions
                        Consulting
____________________________________________
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you

[Wrapper-user] sorry, forgot to include wrapper version

[Neuendorf, D. <DNe...@me...>]

We have a service that is being successfully installed in Windows 7, but not Windows 8. We had hoped to be able to debug this using information from the log file, but that file is created only in Windows 7, not Windows 8. Any thoughts on why the log file is not being generated on Windows 8? Thanks.

Wrapper version: 3.5.22

Contents of the wrapper.conf file below:

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=./jre160_00/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=com.medplus.autosend.client.ARService

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=autosend.jar
wrapper.java.classpath.2=axis.jar
wrapper.java.classpath.3=commons-discovery-0.2.jar
wrapper.java.classpath.4=commons-lang-2.4.jar
wrapper.java.classpath.5=commons-logging-1.0.4.jar
wrapper.java.classpath.6=jaxrpc.jar
wrapper.java.classpath.7=log4j-1.2.8.jar
wrapper.java.classpath.8=saaj.jar
wrapper.java.classpath.9=us.jar
wrapper.java.classpath.10=webserviceclient+ssl.jar
wrapper.java.classpath.11=wrapper.jar
wrapper.java.classpath.12=wsdl4j-1.5.1.jar
wrapper.java.classpath.13=pjx-1.4.0.jar
wrapper.java.classpath.14=commons-io-1.1.jar
wrapper.java.classpath.15=hapi-base-0.6.jar
wrapper.java.classpath.16=hapi-structures-v23-0.6.jar
wrapper.java.classpath.17=hapi-structures-v231-0.6.jar
wrapper.java.classpath.18=iText-2.1.4.jar

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

# Java Additional Parameters
#wrapper.java.additional.1=

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

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

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=

#********************************************************************
# 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/service.log

wrapper.debug=true

# 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

# 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=1m

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

# 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=AutoReceive

#********************************************************************
# 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=AutoReceive

# Display name of the service
wrapper.ntservice.displayname=AutoReceive

# Description of the service
wrapper.ntservice.description=AutoReceive service application

# 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=true



______________________________________________________________________
The contents of this message, together with any attachments, are intended only for the use of the person(s) to which they are addressed and may contain confidential and/or privileged information. Further, any medical information herein is confidential and protected by law. It is unlawful for unauthorized persons to use, review, copy, disclose, or disseminate confidential medical information. If you are not the intended recipient, immediately advise the sender and delete this message and any attachments. Any distribution, or copying of this message, or any attachment, is prohibited.

[Wrapper-user] wrapper logging anomaly

[Neuendorf, D. <DNe...@me...>]

We have a service that is being successfully installed in Windows 7, but not Windows 8. We had hoped to be able to debug this using information from the log file, but that file is created only in Windows 7, not Windows 8. Any thoughts on why the log file is not being generated on Windows 8? Thanks.

Contents of the wrapper.conf file below:

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=./jre160_00/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=com.medplus.autosend.client.ARService

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=autosend.jar
wrapper.java.classpath.2=axis.jar
wrapper.java.classpath.3=commons-discovery-0.2.jar
wrapper.java.classpath.4=commons-lang-2.4.jar
wrapper.java.classpath.5=commons-logging-1.0.4.jar
wrapper.java.classpath.6=jaxrpc.jar
wrapper.java.classpath.7=log4j-1.2.8.jar
wrapper.java.classpath.8=saaj.jar
wrapper.java.classpath.9=us.jar
wrapper.java.classpath.10=webserviceclient+ssl.jar
wrapper.java.classpath.11=wrapper.jar
wrapper.java.classpath.12=wsdl4j-1.5.1.jar
wrapper.java.classpath.13=pjx-1.4.0.jar
wrapper.java.classpath.14=commons-io-1.1.jar
wrapper.java.classpath.15=hapi-base-0.6.jar
wrapper.java.classpath.16=hapi-structures-v23-0.6.jar
wrapper.java.classpath.17=hapi-structures-v231-0.6.jar
wrapper.java.classpath.18=iText-2.1.4.jar

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

# Java Additional Parameters
#wrapper.java.additional.1=

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

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

# Application parameters.  Add parameters as needed starting from 1
wrapper.app.parameter.1=

#********************************************************************
# 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/service.log

wrapper.debug=true

# 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

# 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=1m

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

# 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=AutoReceive

#********************************************************************
# 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=AutoReceive

# Display name of the service
wrapper.ntservice.displayname=AutoReceive

# Description of the service
wrapper.ntservice.description=AutoReceive service application

# 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=true


______________________________________________________________________
The contents of this message, together with any attachments, are intended only for the use of the person(s) to which they are addressed and may contain confidential and/or privileged information. Further, any medical information herein is confidential and protected by law. It is unlawful for unauthorized persons to use, review, copy, disclose, or disseminate confidential medical information. If you are not the intended recipient, immediately advise the sender and delete this message and any attachments. Any distribution, or copying of this message, or any attachment, is prohibited.

[Wrapper-user] wrapper works in Windows 7, not Windows 8

[Neuendorf, D. <DNe...@me...>]

I'm running the latest version of wrapper.exe (community edition). It installs the service correctly in Windows 7, but under Windows 8 it fails with "access denied." If I run it in Win 8 from a command window that was started using "run as administrator", it installs the service correctly, but it needs to run from Runtime.getRuntime().exec() in our java program. I've tried adding an external wrapper.manifest file specifying "runAsAdministrator", but that has no effect as far as I can tell. Any thoughts on how to get wrapper.exe to run as administrator in Windows 8 from a java program?


______________________________________________________________________
The contents of this message, together with any attachments, are intended only for the use of the person(s) to which they are addressed and may contain confidential and/or privileged information. Further, any medical information herein is confidential and protected by law. It is unlawful for unauthorized persons to use, review, copy, disclose, or disseminate confidential medical information. If you are not the intended recipient, immediately advise the sender and delete this message and any attachments. Any distribution, or copying of this message, or any attachment, is prohibited.

Re: [Wrapper-user] Stop wrapper from sending "kill -9"?

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

Graham,
What version of the Wrapper are you using? And what platform is it running on?
Could you please send me your wrapper.conf file so I can have a look at it?

The Wrapper is first of all timing out because the JVM is frozen for
longer than the ping timeout. (wrapper.ping.timeout)
That is what is initiating the shutdown at 07:53:51.
The Wrapper should then start to shutdown the JVM and then kill it
after it fails to exit on its own.  That is all happening immediately
in your case.

To avoid the ping timeouts, you should set it to a very large value or
0 to disable it all together.
wrapper.ping.timeout=true

The current version looks like this:
---
INFO   | jvm 1    | 2013/10/08 14:05:53 | WrapperManager: WARNING:
Making JVM appear to be hung...
STATUS | wrapper  | 2013/10/08 14:06:27 | JVM appears hung: Timed out
waiting for signal from JVM.  Restarting JVM.
ERROR  | wrapper  | 2013/10/08 14:07:02 | Shutdown failed: Timed out
waiting for signal from JVM.
ERROR  | wrapper  | 2013/10/08 14:07:02 | JVM did not exit on request,
termination requested.
STATUS | wrapper  | 2013/10/08 14:07:02 | JVM received a signal SIGKILL (9).
STATUS | wrapper  | 2013/10/08 14:07:02 | JVM process is gone.
STATUS | wrapper  | 2013/10/08 14:07:02 | JVM exited after being
requested to terminate.
---
See that the original hang was detected at 14:06:27.  The JVM is asked
to shutdown on its own. But that fails after 30 seconds and the
Wrapper decides to kill it forcibly.
This second timeout is the wrapper.shutdown.timeout and
wrapper.jvm_exit.timeout, depending on which part of the shutdown is
getting stuck.
In your case, it is best to simply disable the ping timeouts all together.

In recent versions, you can request that slow pings be logged for your
reference as follows:
wrapper.ping.alert.threshold=1
Also see the jvm_ping_slow and jvm_ping_response_slow events to be
able to respond to these slow pings in your own way:
http://wrapper.tanukisoftware.com/doc/english/props-event.html#events

Sincerely,
Leif Mortenson
Tanuki Software, Ltd.

On Tue, Oct 8, 2013 at 9:08 PM, Graham Leggett <mi...@sh...> wrote:
> Hi all,
>
> I am currently trying to get the service wrapper to not send the -9 signal at all to (in my case) activemq, as activemq reverts to an older version of the queue and the additional messages being repreocessed is killing our system.
>
> INFO   | jvm 1    | 2013/10/08 07:53:19 | [Full GC
> INFO   | jvm 1    | 2013/10/08 07:53:22 |  2048661K->2038472K(2092928K), 3.5312760 secs]
> ERROR  | wrapper  | 2013/10/08 07:53:51 | JVM appears hung: Timed out waiting for signal from JVM.
> ERROR  | wrapper  | 2013/10/08 07:53:51 | JVM did not exit on request, terminated
> INFO   | wrapper  | 2013/10/08 07:53:51 | JVM exited on its own while waiting to kill the application.
> STATUS | wrapper  | 2013/10/08 07:53:51 | JVM exited in response to signal SIGKILL (9).
>
> I don't mind the service wrapper complaining that the JVM is too slow, what I want is the wrapper to just ask for a graceful restart or no restart at all.
>
> Any ideas?
>
> Regards,
> Graham
> --
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user



-- 
Leif Mortenson
President & CEO
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
モートンソン リーフ
代表取締役
タヌキソフトウェア有限会社
〒134-0088 東京都江戸川区西葛西6-16-7-1001 第2 白子ビル
Tel: 03-3878-3211
Fax: 03-3878-0313
http://www.tanukisoftware.com
lei...@ta...

[Wrapper-user] Stop wrapper from sending "kill -9"?

[Graham L. <mi...@sh...>]

Hi all,

I am currently trying to get the service wrapper to not send the -9 signal at all to (in my case) activemq, as activemq reverts to an older version of the queue and the additional messages being repreocessed is killing our system.

INFO   | jvm 1    | 2013/10/08 07:53:19 | [Full GC
INFO   | jvm 1    | 2013/10/08 07:53:22 |  2048661K->2038472K(2092928K), 3.5312760 secs]
ERROR  | wrapper  | 2013/10/08 07:53:51 | JVM appears hung: Timed out waiting for signal from JVM.
ERROR  | wrapper  | 2013/10/08 07:53:51 | JVM did not exit on request, terminated
INFO   | wrapper  | 2013/10/08 07:53:51 | JVM exited on its own while waiting to kill the application.
STATUS | wrapper  | 2013/10/08 07:53:51 | JVM exited in response to signal SIGKILL (9).

I don't mind the service wrapper complaining that the JVM is too slow, what I want is the wrapper to just ask for a graceful restart or no restart at all.

Any ideas?

Regards,
Graham
--

[Wrapper-user] how to send Tomcat console logs via syslog to a remote machine

[Mary_Tang <hon...@ho...>]

Hello,

I am pretty new to Tomcat. my firm uses Tomcat console with java service
wrapper. In the configuration file, there is wraper.syslog.loglevel and
other information (e.g. wrapper.syslog. facility). I filled the information,
but the logs did not go to the remote machine. can someone share with me how
to do that? Thank you! 



--
View this message in context: http://java-service-wrapper.996253.n3.nabble.com/how-to-send-Tomcat-console-logs-via-syslog-to-a-remote-machine-tp2942.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

[Wrapper-user] Wrapper Timeout

[Michael B. <mic...@we...>]

Hi!

I have an issue with the restart behavior of the service wrapper, I have set the following properties:


wrapper.ping.timeout.action=NONE

wrapper.disable_restarts=TRUE



But in the log, it seems an automatic restart is still happening:



WrapperManager: The timer fell behind the system clock by 15,300 ms.

2013-09-09 11:30:54,119  INFO  [security.sync.ChainingUserRegistrySynchronizer] [DefaultScheduler_Worker-7] ldap1 Group Analysis: Commencing batch of 42 entries



JVM appears hung: Timed out waiting for signal from JVM.

Dumping JVM state.

JVM did not exit on request, terminated

Automatic JVM Restarts disabled.  Shutting down.

<-- Wrapper Stopped

--> Wrapper Started as Daemon

Java Service Wrapper Community Edition 64-bit 3.5.14

  Copyright (C) 1999-2011 Tanuki Software, Ltd. All Rights Reserved.

    http://wrapper.tanukisoftware.com


Launching a JVM...

WrapperManager: Initializing...


Any idea what is going on here?

Best regards,
Michael

--

Michael Böckling
Westernacher Products & Services AG



Telefon: +49 (0)711 72 25 95 33
E-Mail:    mic...@we...<mailto:mic...@we...>



Innovating Business & IT

Westernacher Products & Services AG
Königstraße 26 · 70173 Stuttgart

Telefon:  +49 711 72 25 95 22
Telefax:  +49 711 72 25 95 99
Internet:  www.westernacher.com<http://www.westernacher.com/>

Amtsgericht Stuttgart HRB 733577
Vorstandsvorsitzender: Dr. Michael Schäfer
Vorstand: Dr.-Ing. Bernd Bergner, Dipl.-Ing. Roeland Hofkens
Vorsitzender des Aufsichtsrates: Dr.-Ing. Martin Weiss M.S.
Aufsichtsrat: Tino Jezewski, Fabian Fritz M.S.

Vertraulichkeitsklausel:
Diese E-Mail enthält vertrauliche oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie die Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail oder deren Inhalt ist nicht gestattet.

Re: [Wrapper-user] Can the wrapper.ping.timeout.action option take multiple values?

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

David,
Yes, I am sorry that the documentation is not clear.  All actions in
the Wrapper are able to take multiple actions as of version 3.5.0.
wrapper.ping.timeout.action=DUMP,RESTART

Note that if the JVM is actually frozen, the DUMP action will not do
anything as the JVM will not be able to act on the request.

Please let me know if you have any questions getting it working.

Cheers,
Leif

On Tue, Sep 3, 2013 at 9:35 PM, David R Robison
<drr...@op...> wrote:
> Can I specify multiple values for the wrapper.ping.timeout.action
> property? Such as:
>
> wrapper.ping.timeout.action=DUMP,RESTART
>
>
> Thanks, David

[Wrapper-user] Can the wrapper.ping.timeout.action option take multiple values?

[David R R. <drr...@op...>]

Can I specify multiple values for the wrapper.ping.timeout.action 
property? Such as:

wrapper.ping.timeout.action=DUMP,RESTART


Thanks, David

-- 

David R Robison
Open Roads Consulting, Inc.
103 Watson Road, Chesapeake, VA 23320
phone: (757) 546-3401
e-mail: drr...@op...
web: http://openroadsconsulting.com
blog: http://therobe.blogspot.com
book: http://www.xulonpress.com/bookstore/bookdetail.php?PB_ISBN=9781597816526



This email communication (including any attachments) may contain confidential and/or privileged material intended solely for the individual or entity to which it is addressed.
If you are not the intended recipient, please delete this email immediately.

Re: [Wrapper-user] issues with wrapper.logfile.format=LPZM

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

Kajal
Answered this in another mail.  The 'Z' format was not added until 3.2.2.
Please consider using a newer version as 3.2.1 as there have been a
lot of other improvements as well.  The current version is 3.5.20.

Cheers,
Leif


On Wed, Aug 21, 2013 at 11:45 PM, Mahindrakar, Kajal
<Kaj...@ve...> wrote:
> I am using Wrapper version 3.2.1 on Windows 7 Enterprise. Following are the
> contents from wrapper.conf file
>
>
>
> #********************************************************************
>
> # Wrapper Properties
>
> #********************************************************************
>
> # Java Application
>
> wrapper.java.command=%I360_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=com.witness.sa.extraction.core.ExtractionService
>
>
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
>
> #  needed starting from 1
>
> wrapper.java.classpath.1=../lib/wrapper.jar;../lib/Extraction-Engine.jar;../lib/commons-logging-1.1.jar;../lib/log4j-1.2.13.jar;../conf/log4j.properties;../lib/org.springframework.aop-3.1.2.RELEASE.jar;../lib/aopalliance.jar;../lib/org.springframework.jdbc-3.1.2.RELEASE.jar;../lib/org.springframework.core-3.1.2.RELEASE.jar;../lib/org.springframework.expression-3.1.2.RELEASE.jar;../lib/org.springframework.beans-3.1.2.RELEASE.jar;../lib/org.springframework.context-3.1.2.RELEASE.jar;../lib/org.springframework.transaction-3.1.2.RELEASE.jar;../lib/org.springframework.context.support-3.1.2.RELEASE.jar;../lib/org.springframework.asm-3.1.2.RELEASE.jar;../conf/ExtractionConfig.xml;../lib/commons-dbcp-1.2.1.jar;../lib/commons-discovery.jar;../lib/commons-pool-1.3.jar;../lib/sqljdbc.jar;../lib/quartz-all-1.8.4.jar;../lib/slf4j-log4j12-1.6.0.jar;../lib/slf4j-api-1.6.0.jar;../lib/jaxme2-0.5.1.jar;../lib/jaxme2-rt-0.5.1.jar;../lib/xml-apis.jar;../lib/jaxmeapi-0.5.1.jar;../lib/jaxmexs-0.5.1.jar;../lib/jaxmepm-0.5.1.jar;../lib/jaxmejs-0.5.1.jar;../lib/Extraction-XML.jar;../lib/commons-io-2.0.1.jar;../lib/jdom.jar;../lib/jaxen-full.jar;../lib/ant.jar;../lib/saxpath.jar;../lib/JXMLComm.jar;../lib/jdom.jar;../lib/ant.jar;;../lib/XmlSchema-1.3.2.jar;../lib/activation-1.1.jar;../lib/axiom-api-1.2.5.jar;../lib/axis2-adb-1.3.jar;../lib/axis2-kernel-1.3.jar;../lib/wsdl4j-1.6.2.jar;../lib/axiom-dom-1.2.5.jar;../lib/axiom-impl-1.2.5.jar;../lib/commons-codec-1.3.jar;../lib/stax-api-1.0.1.jar;../lib/wstx-asl-3.2.1.jar;../lib/Tidy.jar;../lib/classes12.jar;../lib/c3p0-0.9.1.2.jar;../lib/c3p0-oracle-thin-extras-0.9.1.2.jar;../lib/commons-codec-1.3.jar;../lib/commons-collections-3.2.1.jar;../lib/commons-httpclient-3.0.1.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/configuration.jar;../lib/xbean.jar;../lib/xbean_xpath.jar;../lib/saxon9.jar;../lib/saxon9-dom.jar;../lib/jsr173_1.0_api.jar;../lib/AlarmConfig.jar;../lib/WitnessCommon.jar;../lib/dom4j.jar;../lib/commonEjbTierUtils.jar;../lib/coreEjbTierUtils.jar;../lib/xercesImpl.jar;../lib/JRegistryKey.jar
>
>
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
>
> wrapper.java.library.path.1=.;
>
> wrapper.java.library.path.2=%IMPACT360SOFTWAREDIR%/ContactStore;
>
>
>
> # Environment variables
>
> set.SPRING_CONF_PATH=../conf/ExtractionConfig.xml;
>
> set.WITS_SA_DIR=%IMPACT360DATADIR%/ExtractionEngine
>
>
>
> # Java Additional Parameters
>
> wrapper.ignore_sequence_gaps=TRUE
>
> wrapper.java.additional.1=-server
>
> wrapper.java.additional.2=-Dcom.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
>
> #wrapper.java.additional.3=-javaagent:%IMPACT360SOFTWAREDIR%/ExtractionEngine/lib/jacocoagent.jar=dumponexit=true,output=file,append=true,destfile=%IMPACT360DATADIR%/Logs/IEM/coreData.exec
>
>
>
> # Java service wraper PID file..
>
> wrapper.java.pidfile=./extraction.java.pid
>
>
>
> #********************************************************************
>
> # Wrapper Logging Properties
>
> #********************************************************************
>
> # Format of output for the console.  (See docs for formats)
>
> wrapper.console.format=PM
>
>
>
> # Log file to use for wrapper output logging.
>
> wrapper.logfile=%IMPACT360DATADIR%/Logs/IEM/wrapper.log
>
>
>
> # Format of output for the log file.  (See docs for formats)
>
> wrapper.logfile.format=LPZM
>
>
>
> #wrapper.debug=true
>
>
>
> # 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=ExtractionService
>
>
>
> #********************************************************************
>
> # 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=Recorder Import Export Engine
>
>
>
> # Display name of the service
>
> wrapper.ntservice.displayname=Recorder Import Export Engine
>
>
>
> # Description of the service
>
> wrapper.ntservice.description=Recorder Import Export Engine
>
>
>
>
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
>
> wrapper.ntservice.starttype=DEMAND_START
>
>
>
> # Allow the service to interact with the desktop.
>
> wrapper.ntservice.interactive=false
>
>
>
> # Allow the JVM to shutdown when the Extraction exe is killed..
>
> wrapper.on_exit.default=SHUTDOWN
>
>
>
>
>
> My log file(contents below) does not get formatted to include millisecond
> time when I user LPZM. LPTM format works but I need time up to milliseconds
>
>
>
> STATUS | wrapper  | --> Wrapper Started as Console
>
> STATUS | wrapper  | Launching a JVM...
>
> INFO   | jvm 1    | WinSvcTest MAIN called
>
> INFO   | jvm 1    | Wrapper (Version 3.2.1)
> http://wrapper.tanukisoftware.org
>
> INFO   | jvm 1    |
>
> INFO   | jvm 1    | Extraction Service Starting
>
> INFO   | jvm 1    | Starting application....
>
> INFO   | jvm 1    | Application base
> directory:C:\Impact360\Software\ExtractionEngine
>
> INFO   | jvm 1    | Loading Log4J property configurator
>
> INFO   | jvm 1    | log4j:WARN No appenders could be found for logger
> (com.witness.sa.extraction.v11.utils.V11Utils).
>
> INFO   | jvm 1    | log4j:WARN Please initialize the log4j system properly.
>
> INFO   | jvm 1    | Chose log backend JNI
>
>
>
> Does my conf file need some additional changes?
>
>
>
> Thanks

Re: [Wrapper-user] issues with logfile.format=LPZM

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

Kajal
Is there a reason why you are using such an old version?  The 'Z'
format was added in 3.2.2.  There have been a lot of other
improvements since 2006. :-)

Please see the documentation for more information:
http://wrapper.tanukisoftware.com/doc/english/prop-logfile-format.html

Cheers,
Leif

On Wed, Aug 21, 2013 at 11:42 PM, Mahindrakar, Kajal
<Kaj...@ve...> wrote:
> I am using Wrapper version 3.2.1 on Windows 7 Enterprise. Following are the
> contents from wrapper.conf file
>
>
>
> #********************************************************************
>
> # Wrapper Properties
>
> #********************************************************************
>
> # Java Application
>
> wrapper.java.command=%I360_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=com.witness.sa.extraction.core.ExtractionService
>
>
>
> # Java Classpath (include wrapper.jar)  Add class path elements as
>
> #  needed starting from 1
>
> wrapper.java.classpath.1=../lib/wrapper.jar;../lib/Extraction-Engine.jar;../lib/commons-logging-1.1.jar;../lib/log4j-1.2.13.jar;../conf/log4j.properties;../lib/org.springframework.aop-3.1.2.RELEASE.jar;../lib/aopalliance.jar;../lib/org.springframework.jdbc-3.1.2.RELEASE.jar;../lib/org.springframework.core-3.1.2.RELEASE.jar;../lib/org.springframework.expression-3.1.2.RELEASE.jar;../lib/org.springframework.beans-3.1.2.RELEASE.jar;../lib/org.springframework.context-3.1.2.RELEASE.jar;../lib/org.springframework.transaction-3.1.2.RELEASE.jar;../lib/org.springframework.context.support-3.1.2.RELEASE.jar;../lib/org.springframework.asm-3.1.2.RELEASE.jar;../conf/ExtractionConfig.xml;../lib/commons-dbcp-1.2.1.jar;../lib/commons-discovery.jar;../lib/commons-pool-1.3.jar;../lib/sqljdbc.jar;../lib/quartz-all-1.8.4.jar;../lib/slf4j-log4j12-1.6.0.jar;../lib/slf4j-api-1.6.0.jar;../lib/jaxme2-0.5.1.jar;../lib/jaxme2-rt-0.5.1.jar;../lib/xml-apis.jar;../lib/jaxmeapi-0.5.1.jar;../lib/jaxmexs-0.5.1.jar;../lib/jaxmepm-0.5.1.jar;../lib/jaxmejs-0.5.1.jar;../lib/Extraction-XML.jar;../lib/commons-io-2.0.1.jar;../lib/jdom.jar;../lib/jaxen-full.jar;../lib/ant.jar;../lib/saxpath.jar;../lib/JXMLComm.jar;../lib/jdom.jar;../lib/ant.jar;;../lib/XmlSchema-1.3.2.jar;../lib/activation-1.1.jar;../lib/axiom-api-1.2.5.jar;../lib/axis2-adb-1.3.jar;../lib/axis2-kernel-1.3.jar;../lib/wsdl4j-1.6.2.jar;../lib/axiom-dom-1.2.5.jar;../lib/axiom-impl-1.2.5.jar;../lib/commons-codec-1.3.jar;../lib/stax-api-1.0.1.jar;../lib/wstx-asl-3.2.1.jar;../lib/Tidy.jar;../lib/classes12.jar;../lib/c3p0-0.9.1.2.jar;../lib/c3p0-oracle-thin-extras-0.9.1.2.jar;../lib/commons-codec-1.3.jar;../lib/commons-collections-3.2.1.jar;../lib/commons-httpclient-3.0.1.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/configuration.jar;../lib/xbean.jar;../lib/xbean_xpath.jar;../lib/saxon9.jar;../lib/saxon9-dom.jar;../lib/jsr173_1.0_api.jar;../lib/AlarmConfig.jar;../lib/WitnessCommon.jar;../lib/dom4j.jar;../lib/commonEjbTierUtils.jar;../lib/coreEjbTierUtils.jar;../lib/xercesImpl.jar;../lib/JRegistryKey.jar
>
>
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
>
> wrapper.java.library.path.1=.;
>
> wrapper.java.library.path.2=%IMPACT360SOFTWAREDIR%/ContactStore;
>
>
>
> # Environment variables
>
> set.SPRING_CONF_PATH=../conf/ExtractionConfig.xml;
>
> set.WITS_SA_DIR=%IMPACT360DATADIR%/ExtractionEngine
>
>
>
> # Java Additional Parameters
>
> wrapper.ignore_sequence_gaps=TRUE
>
> wrapper.java.additional.1=-server
>
> wrapper.java.additional.2=-Dcom.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
>
> #wrapper.java.additional.3=-javaagent:%IMPACT360SOFTWAREDIR%/ExtractionEngine/lib/jacocoagent.jar=dumponexit=true,output=file,append=true,destfile=%IMPACT360DATADIR%/Logs/IEM/coreData.exec
>
>
>
> # Java service wraper PID file..
>
> wrapper.java.pidfile=./extraction.java.pid
>
>
>
> #********************************************************************
>
> # Wrapper Logging Properties
>
> #********************************************************************
>
> # Format of output for the console.  (See docs for formats)
>
> wrapper.console.format=PM
>
>
>
> # Log file to use for wrapper output logging.
>
> wrapper.logfile=%IMPACT360DATADIR%/Logs/IEM/wrapper.log
>
>
>
> # Format of output for the log file.  (See docs for formats)
>
> wrapper.logfile.format=LPZM
>
>
>
> #wrapper.debug=true
>
>
>
> # 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=ExtractionService
>
>
>
> #********************************************************************
>
> # 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=Recorder Import Export Engine
>
>
>
> # Display name of the service
>
> wrapper.ntservice.displayname=Recorder Import Export Engine
>
>
>
> # Description of the service
>
> wrapper.ntservice.description=Recorder Import Export Engine
>
>
>
>
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
>
> wrapper.ntservice.starttype=DEMAND_START
>
>
>
> # Allow the service to interact with the desktop.
>
> wrapper.ntservice.interactive=false
>
>
>
> # Allow the JVM to shutdown when the Extraction exe is killed..
>
> wrapper.on_exit.default=SHUTDOWN
>
>
>
>
>
> My log file(contents below) does not get formatted to include millisecond
> time when I user LPZM. LPTM format works but I need time up to milliseconds
>
>
>
> STATUS | wrapper  | --> Wrapper Started as Console
>
> STATUS | wrapper  | Launching a JVM...
>
> INFO   | jvm 1    | WinSvcTest MAIN called
>
> INFO   | jvm 1    | Wrapper (Version 3.2.1)
> http://wrapper.tanukisoftware.org
>
> INFO   | jvm 1    |
>
> INFO   | jvm 1    | Extraction Service Starting
>
> INFO   | jvm 1    | Starting application....
>
> INFO   | jvm 1    | Application base
> directory:C:\Impact360\Software\ExtractionEngine
>
> INFO   | jvm 1    | Loading Log4J property configurator
>
> INFO   | jvm 1    | log4j:WARN No appenders could be found for logger
> (com.witness.sa.extraction.v11.utils.V11Utils).
>
> INFO   | jvm 1    | log4j:WARN Please initialize the log4j system properly.
>
> INFO   | jvm 1    | Chose log backend JNI
>
>
>
> Does my conf file need some additional changes?
>
>
>
> Thanks,
>
> Kajal

[Wrapper-user] issues with logfile.format=LPZM

[Mahindrakar, K. <Kaj...@ve...>]

I am using Wrapper version 3.2.1 on Windows 7 Enterprise. Following are the contents from wrapper.conf file

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=%I360_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=com.witness.sa.extraction.core.ExtractionService

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar;../lib/Extraction-Engine.jar;../lib/commons-logging-1.1.jar;../lib/log4j-1.2.13.jar;../conf/log4j.properties;../lib/org.springframework.aop-3.1.2.RELEASE.jar;../lib/aopalliance.jar;../lib/org.springframework.jdbc-3.1.2.RELEASE.jar;../lib/org.springframework.core-3.1.2.RELEASE.jar;../lib/org.springframework.expression-3.1.2.RELEASE.jar;../lib/org.springframework.beans-3.1.2.RELEASE.jar;../lib/org.springframework.context-3.1.2.RELEASE.jar;../lib/org.springframework.transaction-3.1.2.RELEASE.jar;../lib/org.springframework.context.support-3.1.2.RELEASE.jar;../lib/org.springframework.asm-3.1.2.RELEASE.jar;../conf/ExtractionConfig.xml;../lib/commons-dbcp-1.2.1.jar;../lib/commons-discovery.jar;../lib/commons-pool-1.3.jar;../lib/sqljdbc.jar;../lib/quartz-all-1.8.4.jar;../lib/slf4j-log4j12-1.6.0.jar;../lib/slf4j-api-1.6.0.jar;../lib/jaxme2-0.5.1.jar;../lib/jaxme2-rt-0.5.1.jar;../lib/xml-apis.jar;../lib/jaxmeapi-0.5.1.jar;../lib/jaxmexs-0.5.1.jar;../lib/jaxmepm-0.5.1.jar;../lib/jaxmejs-0.5.1.jar;../lib/Extraction-XML.jar;../lib/commons-io-2.0.1.jar;../lib/jdom.jar;../lib/jaxen-full.jar;../lib/ant.jar;../lib/saxpath.jar;../lib/JXMLComm.jar;../lib/jdom.jar;../lib/ant.jar;;../lib/XmlSchema-1.3.2.jar;../lib/activation-1.1.jar;../lib/axiom-api-1.2.5.jar;../lib/axis2-adb-1.3.jar;../lib/axis2-kernel-1.3.jar;../lib/wsdl4j-1.6.2.jar;../lib/axiom-dom-1.2.5.jar;../lib/axiom-impl-1.2.5.jar;../lib/commons-codec-1.3.jar;../lib/stax-api-1.0.1.jar;../lib/wstx-asl-3.2.1.jar;../lib/Tidy.jar;../lib/classes12.jar;../lib/c3p0-0.9.1.2.jar;../lib/c3p0-oracle-thin-extras-0.9.1.2.jar;../lib/commons-codec-1.3.jar;../lib/commons-collections-3.2.1.jar;../lib/commons-httpclient-3.0.1.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/configuration.jar;../lib/xbean.jar;../lib/xbean_xpath.jar;../lib/saxon9.jar;../lib/saxon9-dom.jar;../lib/jsr173_1.0_api.jar;../lib/AlarmConfig.jar;../lib/WitnessCommon.jar;../lib/dom4j.jar;../lib/commonEjbTierUtils.jar;../lib/coreEjbTierUtils.jar;../lib/xercesImpl.jar;../lib/JRegistryKey.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=.;
wrapper.java.library.path.2=%IMPACT360SOFTWAREDIR%/ContactStore;

# Environment variables
set.SPRING_CONF_PATH=../conf/ExtractionConfig.xml;
set.WITS_SA_DIR=%IMPACT360DATADIR%/ExtractionEngine

# Java Additional Parameters
wrapper.ignore_sequence_gaps=TRUE
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Dcom.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
#wrapper.java.additional.3=-javaagent:%IMPACT360SOFTWAREDIR%/ExtractionEngine/lib/jacocoagent.jar=dumponexit=true,output=file,append=true,destfile=%IMPACT360DATADIR%/Logs/IEM/coreData.exec

# Java service wraper PID file..
wrapper.java.pidfile=./extraction.java.pid

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

# Log file to use for wrapper output logging.
wrapper.logfile=%IMPACT360DATADIR%/Logs/IEM/wrapper.log

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

#wrapper.debug=true

# 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=ExtractionService

#********************************************************************
# 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=Recorder Import Export Engine

# Display name of the service
wrapper.ntservice.displayname=Recorder Import Export Engine

# Description of the service
wrapper.ntservice.description=Recorder Import Export Engine


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

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

# Allow the JVM to shutdown when the Extraction exe is killed..
wrapper.on_exit.default=SHUTDOWN


My log file(contents below) does not get formatted to include millisecond time when I user LPZM. LPTM format works but I need time up to milliseconds

STATUS | wrapper  | --> Wrapper Started as Console
STATUS | wrapper  | Launching a JVM...
INFO   | jvm 1    | WinSvcTest MAIN called
INFO   | jvm 1    | Wrapper (Version 3.2.1) http://wrapper.tanukisoftware.org
INFO   | jvm 1    |
INFO   | jvm 1    | Extraction Service Starting
INFO   | jvm 1    | Starting application....
INFO   | jvm 1    | Application base directory:C:\Impact360\Software\ExtractionEngine
INFO   | jvm 1    | Loading Log4J property configurator
INFO   | jvm 1    | log4j:WARN No appenders could be found for logger (com.witness.sa.extraction.v11.utils.V11Utils).
INFO   | jvm 1    | log4j:WARN Please initialize the log4j system properly.
INFO   | jvm 1    | Chose log backend JNI

Does my conf file need some additional changes?

Thanks,
Kajal



This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries.
The information is intended to be for the use of the individual(s) or entity(ies) named above.
If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient),
you may not use, copy, disclose or distribute to anyone this message or any information contained in this message.
If you have received this electronic message in error, please notify us by replying to this e-mail.

[Wrapper-user] issues with wrapper.logfile.format=LPZM

[Mahindrakar, K. <Kaj...@ve...>]

I am using Wrapper version 3.2.1 on Windows 7 Enterprise. Following are the contents from wrapper.conf file

#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=%I360_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=com.witness.sa.extraction.core.ExtractionService

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar;../lib/Extraction-Engine.jar;../lib/commons-logging-1.1.jar;../lib/log4j-1.2.13.jar;../conf/log4j.properties;../lib/org.springframework.aop-3.1.2.RELEASE.jar;../lib/aopalliance.jar;../lib/org.springframework.jdbc-3.1.2.RELEASE.jar;../lib/org.springframework.core-3.1.2.RELEASE.jar;../lib/org.springframework.expression-3.1.2.RELEASE.jar;../lib/org.springframework.beans-3.1.2.RELEASE.jar;../lib/org.springframework.context-3.1.2.RELEASE.jar;../lib/org.springframework.transaction-3.1.2.RELEASE.jar;../lib/org.springframework.context.support-3.1.2.RELEASE.jar;../lib/org.springframework.asm-3.1.2.RELEASE.jar;../conf/ExtractionConfig.xml;../lib/commons-dbcp-1.2.1.jar;../lib/commons-discovery.jar;../lib/commons-pool-1.3.jar;../lib/sqljdbc.jar;../lib/quartz-all-1.8.4.jar;../lib/slf4j-log4j12-1.6.0.jar;../lib/slf4j-api-1.6.0.jar;../lib/jaxme2-0.5.1.jar;../lib/jaxme2-rt-0.5.1.jar;../lib/xml-apis.jar;../lib/jaxmeapi-0.5.1.jar;../lib/jaxmexs-0.5.1.jar;../lib/jaxmepm-0.5.1.jar;../lib/jaxmejs-0.5.1.jar;../lib/Extraction-XML.jar;../lib/commons-io-2.0.1.jar;../lib/jdom.jar;../lib/jaxen-full.jar;../lib/ant.jar;../lib/saxpath.jar;../lib/JXMLComm.jar;../lib/jdom.jar;../lib/ant.jar;;../lib/XmlSchema-1.3.2.jar;../lib/activation-1.1.jar;../lib/axiom-api-1.2.5.jar;../lib/axis2-adb-1.3.jar;../lib/axis2-kernel-1.3.jar;../lib/wsdl4j-1.6.2.jar;../lib/axiom-dom-1.2.5.jar;../lib/axiom-impl-1.2.5.jar;../lib/commons-codec-1.3.jar;../lib/stax-api-1.0.1.jar;../lib/wstx-asl-3.2.1.jar;../lib/Tidy.jar;../lib/classes12.jar;../lib/c3p0-0.9.1.2.jar;../lib/c3p0-oracle-thin-extras-0.9.1.2.jar;../lib/commons-codec-1.3.jar;../lib/commons-collections-3.2.1.jar;../lib/commons-httpclient-3.0.1.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/bcprov-ext-jdk15-140.jar;../lib/configuration.jar;../lib/xbean.jar;../lib/xbean_xpath.jar;../lib/saxon9.jar;../lib/saxon9-dom.jar;../lib/jsr173_1.0_api.jar;../lib/AlarmConfig.jar;../lib/WitnessCommon.jar;../lib/dom4j.jar;../lib/commonEjbTierUtils.jar;../lib/coreEjbTierUtils.jar;../lib/xercesImpl.jar;../lib/JRegistryKey.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=.;
wrapper.java.library.path.2=%IMPACT360SOFTWAREDIR%/ContactStore;

# Environment variables
set.SPRING_CONF_PATH=../conf/ExtractionConfig.xml;
set.WITS_SA_DIR=%IMPACT360DATADIR%/ExtractionEngine

# Java Additional Parameters
wrapper.ignore_sequence_gaps=TRUE
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Dcom.mchange.v2.c3p0.management.ManagementCoordinator=com.mchange.v2.c3p0.management.NullManagementCoordinator
#wrapper.java.additional.3=-javaagent:%IMPACT360SOFTWAREDIR%/ExtractionEngine/lib/jacocoagent.jar=dumponexit=true,output=file,append=true,destfile=%IMPACT360DATADIR%/Logs/IEM/coreData.exec

# Java service wraper PID file..
wrapper.java.pidfile=./extraction.java.pid

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

# Log file to use for wrapper output logging.
wrapper.logfile=%IMPACT360DATADIR%/Logs/IEM/wrapper.log

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

#wrapper.debug=true

# 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=ExtractionService

#********************************************************************
# 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=Recorder Import Export Engine

# Display name of the service
wrapper.ntservice.displayname=Recorder Import Export Engine

# Description of the service
wrapper.ntservice.description=Recorder Import Export Engine


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

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

# Allow the JVM to shutdown when the Extraction exe is killed..
wrapper.on_exit.default=SHUTDOWN


My log file(contents below) does not get formatted to include millisecond time when I user LPZM. LPTM format works but I need time up to milliseconds

STATUS | wrapper  | --> Wrapper Started as Console
STATUS | wrapper  | Launching a JVM...
INFO   | jvm 1    | WinSvcTest MAIN called
INFO   | jvm 1    | Wrapper (Version 3.2.1) http://wrapper.tanukisoftware.org
INFO   | jvm 1    |
INFO   | jvm 1    | Extraction Service Starting
INFO   | jvm 1    | Starting application....
INFO   | jvm 1    | Application base directory:C:\Impact360\Software\ExtractionEngine
INFO   | jvm 1    | Loading Log4J property configurator
INFO   | jvm 1    | log4j:WARN No appenders could be found for logger (com.witness.sa.extraction.v11.utils.V11Utils).
INFO   | jvm 1    | log4j:WARN Please initialize the log4j system properly.
INFO   | jvm 1    | Chose log backend JNI

Does my conf file need some additional changes?

Thanks




This electronic message may contain proprietary and confidential information of Verint Systems Inc., its affiliates and/or subsidiaries.
The information is intended to be for the use of the individual(s) or entity(ies) named above.
If you are not the intended recipient (or authorized to receive this e-mail for the intended recipient),
you may not use, copy, disclose or distribute to anyone this message or any information contained in this message.
If you have received this electronic message in error, please notify us by replying to this e-mail.

Re: [Wrapper-user] JVM crash on armv7 using java service wrapper

[Roberto E. <rob...@ta...>]

Hello Jahanzeb,

This is Roberto from Tanuki Software.

Sorry for the late reply.
I was checking the wrapper.log and it seems there is a version mismatch
between the JAR you are using and the Wrapper version.

According to your log, you are using the 3.5.19 version but you are trying
to load a JAR from the version 3.2.3.

Could you download the latest version from our website? (3.5.20)
http://wrapper.tanukisoftware.com/doc/english/download.jsp


Make sure you replace the wrapper native binary in the bin folder
(bin/wrapper), the shared native library and the jar in the lib folder
(lib/libwrapper.so  and  lib/wrapper.jar).

After this, could you run your application again and if you experiment the
same error, could you send your new wrapper.log?


Thank you,
Roberto


On Tue, Jul 30, 2013 at 10:25 AM, Syed. Jahanzeb Maqbool Hashmi <
jah...@gm...> wrote:

> Hi Leif,
>
> Here is the Wrapper.log file.
>
> What happens is, when MPJ-Express tries to start daemons on all the
> machines specified in a machinefile (including itself). It successfully
> launches daemons on all of them EXCEPT itself and here is the log file.
>
>
>
> On Tue, Jul 30, 2013 at 9:49 AM, Leif Mortenson <
> lei...@ta...> wrote:
>
>> Jahanzeb,
>> Ok. Thanks.  Can you send me your wrapper.conf file along with the
>> wrapper.log file with wrapper.debug=true set?  I will need those to be able
>> to investigate your problem.
>>
>> Cheers,
>> Leif
>>
>>
>> On Tue, Jul 30, 2013 at 12:58 AM, Syed. Jahanzeb Maqbool Hashmi <
>> jah...@gm...> wrote:
>>
>>> Hi Mr Leif,
>>>
>>> Thanks for replying to the email.
>>>
>>> The version of JWS I mentioned before was a typo, I actually used
>>> "3.5.20" community edition. I am using another application "MPJ-Express" to
>>> be exact, which launches daemons on remote machines. It didnt have support
>>> for ARM which I am trying to add by using JWS
>>>
>>>
>>> Regards
>>> -Jahanzeb
>>>
>>>
>>> On Mon, Jul 29, 2013 at 10:28 AM, Leif Mortenson <
>>> lei...@ta...> wrote:
>>>
>>>> Syed
>>>> Sorry for the delay getting back to you.
>>>> Is this a build that you made yourself from the Community Edition?
>>>> We did not add support for ARM platforms until version 3.5.16.  There
>>>> were some changes needed to make it work, so I would suggest trying one of
>>>> our official builds (3.5.20) and seeing how that works for you.
>>>>
>>>> If you still see a problem with 3.5.20, please send your wrapper.conf
>>>> file along with the wrapper.log file with wrapper.debug=true set.
>>>>
>>>> Cheers,
>>>> Leif
>>>>
>>>>
>>>> On Fri, Jul 19, 2013 at 12:11 PM, Syed. Jahanzeb Maqbool Hashmi <
>>>> jah...@gm...> wrote:
>>>>
>>>>> Hello
>>>>>
>>>>> I am trying to run a software that uses JSW internally to launch
>>>>> daemons on remote machines.
>>>>> But my JVM is gettin crashed by throwing error in
>>>>> "org.tanukisoftware.wrapper.WrapperManager.nativeGetControlEvent()I"
>>>>> (see attached files)
>>>>>
>>>>> I have searched the forum and found that it was an issue with 64-bit
>>>>> older versions because of synchronization but 32bit was safe. Though bugs
>>>>> did happen but they were solved in issue 3.3 onwards.
>>>>>
>>>>> P.S: I am using v3.5.0 with armhf and OS is Ubuntu Linaro 12.04.
>>>>> kernel version 3.0.6
>>>>>
>>>>>
>>
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>>
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>


-- 
Roberto Espinoza
Tanuki Software, Ltd.

Re: [Wrapper-user] Wrapper Service Shutting Down on Log Out

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

Shannon.
Ok great.  Glad you got things working.

Cheers,
Leif

On Wed, Aug 7, 2013 at 10:24 PM, Shannon Sumner <sha...@gm...>wrote:

> Hi Leif,
>
> I need to apologize. It was a simple fix.  Just adding the dll and the
> application worked fine.  Thanks for your time.
>
> Shannon
>
>
> On Wed, Aug 7, 2013 at 9:07 AM, Shannon Sumner <sha...@gm...>wrote:
>
>> Hi Leif,
>>
>> I'm running on Windows Server 2003.  The Java version is 1.6.0_37.  The
>> Wrapper version is 3.5.20.
>>
>> I am getting a DLL error!
>>
>> WARNING - Unable to load the Wrapper's native library because none of the
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> following files:
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> wrapper-windows-x86-32.dll
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> wrapper.dll
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           could
>> be located on the following java.library.path:
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> C:\XXX\PCI\AspectSSLDaemon\bin\.
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> Please see the documentation for the wrapper.java.library.path
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> configuration property.
>> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
>> System signals will not be handled correctly.
>>
>>
>> Let me look into fixing this.
>>
>> Thanks,
>>
>> Shannon
>>
>>
>> On Tue, Aug 6, 2013 at 10:04 PM, Leif Mortenson <
>> lei...@ta...> wrote:
>>
>>> Shannon,
>>> I am sorry for the trouble.  What environment are you running on?  Java
>>> version and bits?  OS version and bits? Wrapper version and bits?
>>>
>>> When the Wrapper first launches the JVM, are you seeing any warnings
>>> about the Wrapper.dll being missing or failing to load?  The Wrapper.dll is
>>> required for this and several other functions to work correctly.
>>>
>>> Cheers,
>>> Leif
>>>
>>>
>>> On Wed, Aug 7, 2013 at 12:55 AM, Shannon Sumner <sha...@gm...
>>> > wrote:
>>>
>>>> Hello All,
>>>>
>>>> I've created a Java Socket Listener Service extending WrapperListener.
>>>> It works wonderfully as a service until I logout.
>>>>
>>>> This is what appears in the logs:
>>>>
>>>>
>>>> INFO   | wrapper  | 2013/08/06 11:25:48 | User logged out.  Ignored.
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>>>> ShutdownHook started
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>>>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Send a
>>>> packet STOP : 0
>>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Pausing
>>>> for 1,000ms to allow a clean shutdown...
>>>>
>>>>
>>>> I'm not sure how to fix this
>>>>
>>>> Here is my config file:
>>>>
>>>> # 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=com.xxx.pci.executor.AspectSSLDaemon
>>>>
>>>> # Java Classpath (include wrapper.jar) Add class path elements as
>>>> wrapper.java.classpath.1=../lib/*.jar
>>>>
>>>> # Name of the service
>>>> wrapper.name=AspectSSLDaemon
>>>>
>>>> # Display name of the service
>>>> wrapper.displayname=Aspect SSL Daemon
>>>>
>>>> # Description of the service
>>>> wrapper.description=Secure Aspect Daemon
>>>>
>>>> # Mode in which the service is installed. AUTO_START, DELAY_START or
>>>> DEMAND_START
>>>> wrapper.ntservice.starttype=AUTO_START
>>>> wrapper.debug=true
>>>> wrapper.ignore_user_logoffs=TRUE
>>>> wrapper.ignore_signals=TRUE
>>>>
>>>> # 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.ntservice.interactive=false
>>>>
>>>> Thanks,
>>>>
>>>> Shannon Sumner
>>>>
>>>>

Re: [Wrapper-user] Wrapper Service Shutting Down on Log Out

[Shannon S. <sha...@gm...>]

Hi Leif,

I need to apologize. It was a simple fix.  Just adding the dll and the
application worked fine.  Thanks for your time.

Shannon


On Wed, Aug 7, 2013 at 9:07 AM, Shannon Sumner <sha...@gm...>wrote:

> Hi Leif,
>
> I'm running on Windows Server 2003.  The Java version is 1.6.0_37.  The
> Wrapper version is 3.5.20.
>
> I am getting a DLL error!
>
> WARNING - Unable to load the Wrapper's native library because none of the
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
> following files:
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
> wrapper-windows-x86-32.dll
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
> wrapper.dll
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           could
> be located on the following java.library.path:
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
> C:\XXX\PCI\AspectSSLDaemon\bin\.
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           Please
> see the documentation for the wrapper.java.library.path
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
> configuration property.
> INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           System
> signals will not be handled correctly.
>
>
> Let me look into fixing this.
>
> Thanks,
>
> Shannon
>
>
> On Tue, Aug 6, 2013 at 10:04 PM, Leif Mortenson <
> lei...@ta...> wrote:
>
>> Shannon,
>> I am sorry for the trouble.  What environment are you running on?  Java
>> version and bits?  OS version and bits? Wrapper version and bits?
>>
>> When the Wrapper first launches the JVM, are you seeing any warnings
>> about the Wrapper.dll being missing or failing to load?  The Wrapper.dll is
>> required for this and several other functions to work correctly.
>>
>> Cheers,
>> Leif
>>
>>
>> On Wed, Aug 7, 2013 at 12:55 AM, Shannon Sumner <sha...@gm...>wrote:
>>
>>> Hello All,
>>>
>>> I've created a Java Socket Listener Service extending WrapperListener.
>>> It works wonderfully as a service until I logout.
>>>
>>> This is what appears in the logs:
>>>
>>>
>>> INFO   | wrapper  | 2013/08/06 11:25:48 | User logged out.  Ignored.
>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>>> ShutdownHook started
>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Send a
>>> packet STOP : 0
>>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Pausing
>>> for 1,000ms to allow a clean shutdown...
>>>
>>>
>>> I'm not sure how to fix this
>>>
>>> Here is my config file:
>>>
>>> # 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=com.xxx.pci.executor.AspectSSLDaemon
>>>
>>> # Java Classpath (include wrapper.jar) Add class path elements as
>>> wrapper.java.classpath.1=../lib/*.jar
>>>
>>> # Name of the service
>>> wrapper.name=AspectSSLDaemon
>>>
>>> # Display name of the service
>>> wrapper.displayname=Aspect SSL Daemon
>>>
>>> # Description of the service
>>> wrapper.description=Secure Aspect Daemon
>>>
>>> # Mode in which the service is installed. AUTO_START, DELAY_START or
>>> DEMAND_START
>>> wrapper.ntservice.starttype=AUTO_START
>>> wrapper.debug=true
>>> wrapper.ignore_user_logoffs=TRUE
>>> wrapper.ignore_signals=TRUE
>>>
>>> # 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.ntservice.interactive=false
>>>
>>> Thanks,
>>>
>>> Shannon Sumner
>>>
>>>
>> --
>> Leif Mortenson
>> Tanuki Software, Ltd.
>> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
>> Tokyo 134-0088 Japan
>> Tel: +81-3-3878-3211
>> Fax: +81-3-3878-0313
>> http://www.tanukisoftware.com
>> lei...@ta...
>>
>>
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite!
>> It's a free troubleshooting tool designed for production.
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>

Re: [Wrapper-user] Wrapper Service Shutting Down on Log Out

[Shannon S. <sha...@gm...>]

Hi Leif,

I'm running on Windows Server 2003.  The Java version is 1.6.0_37.  The
Wrapper version is 3.5.20.

I am getting a DLL error!

WARNING - Unable to load the Wrapper's native library because none of the
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
following files:
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
wrapper-windows-x86-32.dll
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
wrapper.dll
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           could
be located on the following java.library.path:
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
C:\XXX\PCI\AspectSSLDaemon\bin\.
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           Please
see the documentation for the wrapper.java.library.path
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:
configuration property.
INFO   | jvm 1    | 2013/08/06 11:25:33 | WrapperManager:           System
signals will not be handled correctly.


Let me look into fixing this.

Thanks,

Shannon


On Tue, Aug 6, 2013 at 10:04 PM, Leif Mortenson <
lei...@ta...> wrote:

> Shannon,
> I am sorry for the trouble.  What environment are you running on?  Java
> version and bits?  OS version and bits? Wrapper version and bits?
>
> When the Wrapper first launches the JVM, are you seeing any warnings about
> the Wrapper.dll being missing or failing to load?  The Wrapper.dll is
> required for this and several other functions to work correctly.
>
> Cheers,
> Leif
>
>
> On Wed, Aug 7, 2013 at 12:55 AM, Shannon Sumner <sha...@gm...>wrote:
>
>> Hello All,
>>
>> I've created a Java Socket Listener Service extending WrapperListener.
>> It works wonderfully as a service until I logout.
>>
>> This is what appears in the logs:
>>
>>
>> INFO   | wrapper  | 2013/08/06 11:25:48 | User logged out.  Ignored.
>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>> ShutdownHook started
>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
>> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Send a
>> packet STOP : 0
>> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Pausing
>> for 1,000ms to allow a clean shutdown...
>>
>>
>> I'm not sure how to fix this
>>
>> Here is my config file:
>>
>> # 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=com.xxx.pci.executor.AspectSSLDaemon
>>
>> # Java Classpath (include wrapper.jar) Add class path elements as
>> wrapper.java.classpath.1=../lib/*.jar
>>
>> # Name of the service
>> wrapper.name=AspectSSLDaemon
>>
>> # Display name of the service
>> wrapper.displayname=Aspect SSL Daemon
>>
>> # Description of the service
>> wrapper.description=Secure Aspect Daemon
>>
>> # Mode in which the service is installed. AUTO_START, DELAY_START or
>> DEMAND_START
>> wrapper.ntservice.starttype=AUTO_START
>> wrapper.debug=true
>> wrapper.ignore_user_logoffs=TRUE
>> wrapper.ignore_signals=TRUE
>>
>> # 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.ntservice.interactive=false
>>
>> Thanks,
>>
>> Shannon Sumner
>>
>>
> --
> Leif Mortenson
> Tanuki Software, Ltd.
> 6-16-7-1001 Nishi-Kasai, Edogawa-ku
> Tokyo 134-0088 Japan
> Tel: +81-3-3878-3211
> Fax: +81-3-3878-0313
> http://www.tanukisoftware.com
> lei...@ta...
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>

Re: [Wrapper-user] Wrapper Service Shutting Down on Log Out

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

Shannon,
I am sorry for the trouble.  What environment are you running on?  Java
version and bits?  OS version and bits? Wrapper version and bits?

When the Wrapper first launches the JVM, are you seeing any warnings about
the Wrapper.dll being missing or failing to load?  The Wrapper.dll is
required for this and several other functions to work correctly.

Cheers,
Leif

On Wed, Aug 7, 2013 at 12:55 AM, Shannon Sumner <sha...@gm...>wrote:

> Hello All,
>
> I've created a Java Socket Listener Service extending WrapperListener.  It
> works wonderfully as a service until I logout.
>
> This is what appears in the logs:
>
>
> INFO   | wrapper  | 2013/08/06 11:25:48 | User logged out.  Ignored.
> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
> ShutdownHook started
> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
> WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Send a
> packet STOP : 0
> INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Pausing
> for 1,000ms to allow a clean shutdown...
>
>
> I'm not sure how to fix this
>
> Here is my config file:
>
> # 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=com.xxx.pci.executor.AspectSSLDaemon
>
> # Java Classpath (include wrapper.jar) Add class path elements as
> wrapper.java.classpath.1=../lib/*.jar
>
> # Name of the service
> wrapper.name=AspectSSLDaemon
>
> # Display name of the service
> wrapper.displayname=Aspect SSL Daemon
>
> # Description of the service
> wrapper.description=Secure Aspect Daemon
>
> # Mode in which the service is installed. AUTO_START, DELAY_START or
> DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
> wrapper.debug=true
> wrapper.ignore_user_logoffs=TRUE
> wrapper.ignore_signals=TRUE
>
> # 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.ntservice.interactive=false
>
> Thanks,
>
> Shannon Sumner
>
>
--
Leif Mortenson
Tanuki Software, Ltd.
6-16-7-1001 Nishi-Kasai, Edogawa-ku
Tokyo 134-0088 Japan
Tel: +81-3-3878-3211
Fax: +81-3-3878-0313
http://www.tanukisoftware.com
lei...@ta...

[Wrapper-user] Wrapper Service Shutting Down on Log Out

[Shannon S. <sha...@gm...>]

Hello All,

I've created a Java Socket Listener Service extending WrapperListener.  It
works wonderfully as a service until I logout.

This is what appears in the logs:


INFO   | wrapper  | 2013/08/06 11:25:48 | User logged out.  Ignored.
INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
ShutdownHook started
INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug:
WrapperManager.stop(0) called by thread: Wrapper-Shutdown-Hook
INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Send a
packet STOP : 0
INFO   | jvm 1    | 2013/08/06 11:25:48 | WrapperManager Debug: Pausing for
1,000ms to allow a clean shutdown...


I'm not sure how to fix this

Here is my config file:

# 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=com.xxx.pci.executor.AspectSSLDaemon

# Java Classpath (include wrapper.jar) Add class path elements as
wrapper.java.classpath.1=../lib/*.jar

# Name of the service
wrapper.name=AspectSSLDaemon

# Display name of the service
wrapper.displayname=Aspect SSL Daemon

# Description of the service
wrapper.description=Secure Aspect Daemon

# Mode in which the service is installed. AUTO_START, DELAY_START or
DEMAND_START
wrapper.ntservice.starttype=AUTO_START
wrapper.debug=true
wrapper.ignore_user_logoffs=TRUE
wrapper.ignore_signals=TRUE

# 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.ntservice.interactive=false

Thanks,

Shannon Sumner

Re: [Wrapper-user] how to identify and monitor different java-processes

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

Jeroen,
To be clear, you have 20 Wrappers and 20 JVMs on the same machine?

Do have any idea whether it is the Wrapper or a Java process that is
leaking? or is that what you are asking?

What version of the Wrapper are you using?  There are a few known leaks in
older versions.

There is an undocumented feature that works on Windows that will log the
memory stats of the Wrapper and its Java process at regular intervals.
This might help depending on the nature of the leak.
wrapper.memory_output=TRUE
wrapper.memory_output.interval=60

You can also try the perfmon tool to track the process memories over time.

Please follow up with what you find out.

Cheers,
Leif

On Wed, Jul 31, 2013 at 11:15 PM, Jeroen Vranckx <jvr...@gm...>wrote:

> Hey everyone,
>
> I've got a little problem where i can't seem to think a workaround for.
> We are currently using the java service wrapper to host 20 or more java
> processes on a microsoft cluster.
>
> We've noticed that the available memory on the server get's depleted to
> 100% each day. They've asked me to start transfering processes to another
> server to reduce the load on the server but i don't think that this will
> solve the problem. I think that some processes have memory leaks which
> cause the server to run out of available memory.
>
> Is this thinking-route correct?
>
> Thing is; i would like to know which specific process it is so i can
> feedback it to the programmer. Just to prevent further issues in the
> future. any idea how to start with this little chore?
>
> tnx for the feedback
>
>

Re: [Wrapper-user] In some Windows2008/Windows7, "wmic" cannot found

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

Seiyamiro
What script and Wrapper version are you seeing a reference to wmic in?  The
Wrapper scripts on their own don't reference it.

Cheers,
Leif

On Wed, Jul 31, 2013 at 8:16 PM, seiyamiro <sei...@16...> wrote:

> **
> In Windows2008/Windows7, "wmic" may
> be in the path of C:\Windows\System32\wbem?
> but in service.bat
> the varialbe %PATH% does not include the above path, therefore wmic not
> found
>
> ------------------------------
> seiyamiro
>
>

[Wrapper-user] how to identify and monitor different java-processes

[Jeroen V. <jvr...@gm...>]

Hey everyone,

I've got a little problem where i can't seem to think a workaround for.
We are currently using the java service wrapper to host 20 or more java
processes on a microsoft cluster.

We've noticed that the available memory on the server get's depleted to
100% each day. They've asked me to start transfering processes to another
server to reduce the load on the server but i don't think that this will
solve the problem. I think that some processes have memory leaks which
cause the server to run out of available memory.

Is this thinking-route correct?

Thing is; i would like to know which specific process it is so i can
feedback it to the programmer. Just to prevent further issues in the
future. any idea how to start with this little chore?

tnx for the feedback

[Wrapper-user] In some Windows2008/Windows7, "wmic" cannot found

[seiyamiro <sei...@16...>]

In Windows2008/Windows7, "wmic" may be in the path of C:\Windows\System32\wbem? 
but in service.bat 
the varialbe %PATH% does not include the above path, therefore wmic not found




seiyamiro