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

Re: [Wrapper-user] Issues With Windows v3.2

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

Bill,
One more question.   In your log from running as a service.  There were 
a couple places
where the line feeds were missing.   There used to be an old bug that 
looked a little like
this that was being caused by synchronization problems.  I have never 
seen it since it
was fixed.   But I wanted to confirm whether or not you are seeing these 
missing line
feeds in your original unmodified log file or whether this is just an 
artifact of the email?
> DEBUG  | wrapper  | 2006/05/30 11:32:16 | Service command: "C:\Program 
> Files\VCS Server\wrapper.exe" -s wrapper.conf
> STATUS | wrapper  | 2006/05/30 11:32:17 | VCS installed.
> STATUS | wrapper  | 2006/05/30 11:32:23 | --> Wrapper Started as Service
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | Using tick timer.
> DEBUG  | wrapperp | 2006/05/30 11:32:23 | server listening on port 32000.
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | Classpath element, 
> wrapper.java.classpath.2 , does not exist: C:\Program Files\VCS 
> Server\wrappertesta.jar
> STATUS | wrapper  | 2006/05/30 11:32:23 | Launching a JVM...
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | command: 
> "C:\WINDOWS\system32\java.exe" - Duser.timezone=UTC 
> -Duser.dir="C:\Program Files\VCS Server" -Xms128m -Xmx256m 
> -Djava.library.path="C:\Program Files\VCS Server\vcsNative" -classpath 
> "C:\Program Files\VCS Server\wrapper.jar;C:\Program Files\VCS 
> Server\wrappertesta.jar;C:\Program Files\VCS Server\ImageServer.jar" - 
> Dwrapper.key="xEe2o3phm7_2ayOo" -Dwrapper.port=32000 
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
> -Dwrapper.debug="TRUE" -Dwrapper.pid=640 -Dwrapper.version="3.2.0" 
> -Dwrapper.native_library= "wrapper" -Dwrapper.service="TRUE" 
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 
> org.tanukisoftware.wrapper.WrapperSimpleApp ImageServerDEBUG  | 
> wrapper  | 2006/05/30 11:32:23 | JVM started (PID=3952)
> INFO   | jvm 1    | 2006/05/30 11:32:23 | 
> java.lang.NoClassDefFoundError: 
> org/tanukisoftware/wrapper/WrapperSimpleAppINFO   | jvm 1    | 
> 2006/05/30 11:32:23 | Exception in thread "main"
There are two examples of this above

1) "... ImageServerDEBUG ..."
Should be:
"... ImageServer
DEBUG ..."

2) "...WrapperSimpleAppINFO..."
Shoulb be:
"...WrapperSimpleApp
INFO..."

If you are seeing the missing line feeds.  Are they happening reliably 
in the same place
every time you run the wrapper or are they happening at random locations.

I noticed that they do not appear in the log file from when you run as a 
console app.

Cheers,
Leif

Re: [Wrapper-user] Issues With Windows v3.2

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

David, Bill,

David Hayes wrote:
>
> I noticed from the output of your log files, it keeps mentioning 
> wrappertest*/_a_/*.jar which your classpath doesn’t have (Java is 
> complaining about the fact it cannot find it).
>
> One thing I would suggest trying, since the classpath has a couple of 
> spaces in it, is to single quote (or maybe double quote) the thing 
> after the equals sign on the classpath, e.g.
>
Thanks for the reply. But the addition of quotes are not needed. The 
Wrapper will
automatically enclose the full classpath in quotes to make it possible 
to use spaces in
the paths. See the generated command below:
>
> DEBUG | wrapper | 2006/05/30 11:32:23 | command: 
> "C:\WINDOWS\system32\java.exe" - Duser.timezone=UTC 
> -Duser.dir="C:\Program Files\VCS Server" -Xms128m -Xmx256m 
> -Djava.library.path="C:\Program Files\VCS Server\vcsNative" -classpath 
> "C:\Program Files\VCS Server\wrapper.jar;C:\Program Files\VCS 
> Server\wrappertesta.jar;C:\Program Files\VCS Server\ImageServer.jar" - 
> Dwrapper.key="xEe2o3phm7_2ayOo" -Dwrapper.port=32000 
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
> -Dwrapper.debug="TRUE" -Dwrapper.pid=640 -Dwrapper.version="3.2.0" 
> -Dwrapper.native_library= "wrapper" -Dwrapper.service="TRUE" 
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 
> org.tanukisoftware.wrapper.WrapperSimpleApp ImageServer
>
Cheers,
Leif

Re: [Wrapper-user] Issues With Windows v3.2

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

Bill,
> I'm trying to use v3.2 of the Java Service Wrapper and have run into 
> an issue that I can't seem to get past. Here is my wrapper.conf file:
<snip most of config file as it is fine with the following exception>
> # Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=FINEST
There is no such log level.  The Wrapper will default to DEBUG in this case.
> Here is the output that is produced from the log when I attempt to 
> install and run the service:
>
> DEBUG  | wrapper  | 2006/05/30 11:32:16 | Service command: "C:\Program 
> Files\VCS Server\wrapper.exe" -s wrapper.conf
> STATUS | wrapper  | 2006/05/30 11:32:17 | VCS installed.
> STATUS | wrapper  | 2006/05/30 11:32:23 | --> Wrapper Started as Service
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | Using tick timer.
> DEBUG  | wrapperp | 2006/05/30 11:32:23 | server listening on port 32000.
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | Classpath element, 
> wrapper.java.classpath.2 , does not exist: C:\Program Files\VCS 
> Server\wrappertesta.jar
> STATUS | wrapper  | 2006/05/30 11:32:23 | Launching a JVM...
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | command: 
> "C:\WINDOWS\system32\java.exe" - Duser.timezone=UTC 
> -Duser.dir="C:\Program Files\VCS Server" -Xms128m -Xmx256m 
> -Djava.library.path="C:\Program Files\VCS Server\vcsNative" -classpath 
> "C:\Program Files\VCS Server\wrapper.jar;C:\Program Files\VCS 
> Server\wrappertesta.jar;C:\Program Files\VCS Server\ImageServer.jar" - 
> Dwrapper.key="xEe2o3phm7_2ayOo" -Dwrapper.port=32000 
> -Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 
> -Dwrapper.debug="TRUE" -Dwrapper.pid=640 -Dwrapper.version="3.2.0" 
> -Dwrapper.native_library= "wrapper" -Dwrapper.service="TRUE" 
> -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 
> org.tanukisoftware.wrapper.WrapperSimpleApp ImageServerDEBUG  | 
> wrapper  | 2006/05/30 11:32:23 | JVM started (PID=3952)
> INFO   | jvm 1    | 2006/05/30 11:32:23 | 
> java.lang.NoClassDefFoundError: 
> org/tanukisoftware/wrapper/WrapperSimpleAppINFO   | jvm 1    | 
> 2006/05/30 11:32:23 | Exception in thread "main"
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | JVM process exited with a 
> code of 1, setting the wrapper exit code to 1.
> ERROR  | wrapper  | 2006/05/30 11:32:23 | JVM exited while loading the 
> application.
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | JVM was only running for 0 
> seconds leading to a failed restart count of 1.
> DEBUG  | wrapper  | 2006/05/30 11:32:23 | Waiting 5 seconds before 
> launching another JVM.
    This result is strange.  Your classpath:
"C:\Program Files\VCS Server\wrapper.jar;C:\Program Files\VCS 
Server\wrappertesta.jar;C:\Program Files\VCS Server\ImageServer.jar"
looks fine.   The wrappertesta.jar file does not appear to exist as the 
warning in the log
states, but I assume that you just changed the name to try skipping it.  
The main class
org.tanukisoftware.wrapper.WrapperSimpleApp is also correct and should 
be located
in the wrapper.jar file.

    Because you say that it works correctly when run as a console app, 
that means that
the wrapper.jar file is most likely not corrupted in any way.   My next 
guess would be
that the JVM is having difficulties reading the jar for some reason.
    I have seen cases in the past where users have protected directories 
to access only
by specific user accounts.   In your case, you are not specifying a 
particular account to
run the service as so it is being run by the SYSTEM account.
    If you have restricted access to that directory then it may be 
possible that the
account you are logged in as can see the jar files, but that the SYSTEM 
account
can not.
> Running as a console produces this output:
<snip  console output all looks fine for a normal app>

This first line of the log is odd though.  What OS version are you running?
 > wrapper  | Attempt to set the console title failed: The handle is 
invalid. (0x6)

This is Windows XP sp2?
 > jvm 1    | Windows version: 5.1.2600

Googling on this didn't turn up anything.  Most programs I saw that call the
SetConsoleTitle method appear to ignore the return value and would thus not
notice an error...  The method doesn't take a handle directly but must be
referring to a handle located using the current process id.

How exactly are you launching the wrapper when you run it in a console?
Are you running the bat script from within an open command prompt?
Double clicking on the batch script in the file explorer?  Or something
else?  Knowing what you are doing could help me to track down what is
going on here.

At any rate this isn't directly causing you any problems other than that the
console window is not having its title set correctly.
> There was no file wrapper-windows-x86-32.dll included in the zip file 
> I downloaded. Am I missing something? There is a wrapper.dll file 
> which I copied to my native directory.
I assume you are concerned about the following from the logs:
jvm 1    | Load native library.  One or more attempts may fail if 
platform specific libraries do not exist.
jvm 1    | Loading native library failed: wrapper-windows-x86-32.dll  
Cause: java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in 
java.library.path
jvm 1    | Loaded native library: wrapper.dll

This is normal operation.  As of 3.2, the Wrapper has the ability to 
load in its native library
based on platform specific naming.   The delta-pack distribution of the 
Wrapper takes
advantage of this feature by providing wrapper binaries for all 
supported platforms.

The  Wrapper first attempts to load the platform specific dll, then 
falls back to loading the
default dll.

Cheers,
Leif

RE: [Wrapper-user] Issues With Windows v3.2

[David H. <da...@sm...>]

Bill,

 

Others may tell me I am wrong, but you should only need a wrapper.dll in
your directory. The way that Leif coded it, was to look for the platform
specific version (catering for 32bit/64bit windows) first, and if it
couldn't load that, then to simply load the wrapper.dll (also for legacy
support). So I wouldn't worry about the fact you don't have a
wrapper-x86-32.dll.

 

I noticed from the output of your log files, it keeps mentioning
wrappertesta.jar which your classpath doesn't have (Java is complaining
about the fact it cannot find it).

 

One thing I would suggest trying, since the classpath has a couple of spaces
in it, is to single quote (or maybe double quote) the thing after the equals
sign on the classpath, e.g.

 

# Java Classpath (include wrapper.jar )  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1='C:\Program Files\VCS Server\wrapper.jar'
wrapper.java.classpath.2='C:\Program Files\VCS Server\wrappertest.jar'
wrapper.java.classpath.3='C:\Program Files\VCS Server\ImageServer.jar'

 

Or

 

# Java Classpath (include wrapper.jar )  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1="C:\Program Files\VCS Server\wrapper.jar"
wrapper.java.classpath.2="C:\Program Files\VCS Server\wrappertest.jar"
wrapper.java.classpath.3="C:\Program Files\VCS Server\ImageServer.jar"

 

And see if that gets you any further. I don't expect that it will, but it
just might!

 

David

  _____  

From: wra...@li...
[mailto:wra...@li...] On Behalf Of Bill Rees
Sent: 30 May 2006 13:43
To: wra...@li...
Subject: [Wrapper-user] Issues With Windows v3.2

 

Hello,

I'm trying to use v3.2 of the Java Service Wrapper and have run into an
issue that I can't seem to get past. Here is my wrapper.conf file:

#******************************************************************** 
# TestWrapper Properties
#
# NOTE - Please use src/conf/wrapper.conf.in as a template for your
#        own application rather than the values used for the
#        TestWrapper sample.
#******************************************************************** 
# Java Application
wrapper.java.command=java
wrapper.debug=true

# 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=C:\Program Files\VCS Server\wrapper.jar
wrapper.java.classpath.2=C:\Program Files\VCS Server\wrappertest.jar
wrapper.java.classpath.3=C:\Program Files\VCS Server\ImageServer.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=C:\Program Files\VCS Server\vcsNative

# Java Additional Parameters
wrapper.java.additional.1=-Duser.timezone=UTC 
wrapper.java.additional.2=-Duser.dir="C:\Program Files\VCS Server"

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

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

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

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

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

# Log file to use for wrapper output logging.
wrapper.logfile=server.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=FINEST

# 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=10mb

# 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 Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=VCS

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

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

# Description of the service
wrapper.ntservice.description=VCS

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

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

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



Here is the output that is produced from the log when I attempt to install
and run the service: 

DEBUG  | wrapper  | 2006/05/30 11:32:16 | Service command: "C:\Program
Files\VCS Server\wrapper.exe" -s wrapper.conf
STATUS | wrapper  | 2006/05/30 11:32:17 | VCS installed.
STATUS | wrapper  | 2006/05/30 11:32:23 | --> Wrapper Started as Service 
DEBUG  | wrapper  | 2006/05/30 11:32:23 | Using tick timer.
DEBUG  | wrapperp | 2006/05/30 11:32:23 | server listening on port 32000.
DEBUG  | wrapper  | 2006/05/30 11:32:23 | Classpath element,
wrapper.java.classpath.2 , does not exist: C:\Program Files\VCS
Server\wrappertesta.jar
STATUS | wrapper  | 2006/05/30 11:32:23 | Launching a JVM...
DEBUG  | wrapper  | 2006/05/30 11:32:23 | command:
"C:\WINDOWS\system32\java.exe" - Duser.timezone=UTC -Duser.dir="C:\Program
Files\VCS Server" -Xms128m -Xmx256m -Djava.library.path="C:\Program
Files\VCS Server\vcsNative" -classpath "C:\Program Files\VCS
Server\wrapper.jar;C:\Program Files\VCS Server\wrappertesta.jar;C:\Program
Files\VCS Server\ImageServer.jar" - Dwrapper.key="xEe2o3phm7_2ayOo"
-Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000
-Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=640
-Dwrapper.version="3.2.0" -Dwrapper.native_library= "wrapper"
-Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
org.tanukisoftware.wrapper.WrapperSimpleApp ImageServerDEBUG  | wrapper  |
2006/05/30 11:32:23 | JVM started (PID=3952) 
INFO   | jvm 1    | 2006/05/30 11:32:23 | java.lang.NoClassDefFoundError:
org/tanukisoftware/wrapper/WrapperSimpleAppINFO   | jvm 1    | 2006/05/30
11:32:23 | Exception in thread "main" 
DEBUG  | wrapper  | 2006/05/30 11:32:23 | JVM process exited with a code of
1, setting the wrapper exit code to 1. 
ERROR  | wrapper  | 2006/05/30 11:32:23 | JVM exited while loading the
application.
DEBUG  | wrapper  | 2006/05/30 11:32:23 | JVM was only running for 0 seconds
leading to a failed restart count of 1.
DEBUG  | wrapper  | 2006/05/30 11:32:23 | Waiting 5 seconds before launching
another JVM. 


Running as a console produces this output:

wrapper  | Attempt to set the console title failed: The handle is invalid.
(0x6)
wrapper  | --> Wrapper Started as Console
wrapper  | Using tick timer. 
wrapperp | server listening on port 32000.
wrapper  | Launching a JVM...
wrapper  | command: "c:\WINDOWS\system32\java.exe" -Duser.timezone=UTC
-Duser.dir="C:\Program Files\VCS Server" -Xms128m -Xmx256m -
Djava.library.path="C:\Program Files\VCS Server\vcsNative" -classpath
"C:\Program Files\VCS Server\wrapper.jar;C:\Program Files\VCS
Server\wrappertest.jar;C:\Program Files\VCS Server\ImageServer.jar" -
Dwrapper.key="E6uyLkDxlffbFLn5" -Dwrapper.port=32000
-Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999
-Dwrapper.debug="TRUE" -Dwrapper.pid=4408 -Dwrapper.version="3.2.0"
-Dwrapper.native_library= "wrapper" -Dwrapper.cpu.timeout="10"
-Dwrapper.jvmid=1 org.tanukisoftware.wrapper.WrapperSimpleApp ImageServer
wrapper  | JVM started (PID=4508)
jvm 1    | WrapperManager class initialized by thread: main  Using
classloader: sun.misc.Launcher$AppClassLoader@e39a3e
jvm 1    | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
jvm 1    | 
jvm 1    | Wrapper Manager: JVM #1
jvm 1    | Running a 32-bit JVM. 
jvm 1    | Wrapper Manager: Registering shutdown hook
jvm 1    | Wrapper Manager: Using wrapper
jvm 1    | Load native library.  One or more attempts may fail if platform
specific libraries do not exist.
jvm 1    | Loading native library failed: wrapper-windows-x86-32.dll  Cause:
java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in
java.library.path
jvm 1    | Loaded native library: wrapper.dll
jvm 1    | Calling native initialization method.
jvm 1    | Initializing WrapperManager native library. 
jvm 1    | Java Executable: c:\WINDOWS\system32\java.exe
jvm 1    | Windows version: 5.1.2600
jvm 1    | Java Version   : 1.5.0_06-b05 Java HotSpot(TM) Client VM
jvm 1    | Java VM Vendor : Sun Microsystems Inc. 
jvm 1    | 
jvm 1    |
WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@c5c3ac,
args[]) called by thread: main
jvm 1    | Open socket to wrapper...Wrapper-Connection
jvm 1    | Opened Socket from 31000 to 32000 
jvm 1    | Send a packet KEY : E6uyLkDxlffbFLn5
jvm 1    | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
wrapperp | accepted a socket from 127.0.0.1 on port 31000 
wrapperp | read a packet KEY : E6uyLkDxlffbFLn5
wrapper  | Got key from JVM: E6uyLkDxlffbFLn5
wrapperp | send a packet LOW_LOG_LEVEL : 1
wrapperp | send a packet PING_TIMEOUT : 30
wrapperp | send a packet PROPERTIES : (Property Values) 
wrapper  | Start Application.
wrapperp | send a packet START : start
jvm 1    | Received a packet LOW_LOG_LEVEL : 1
jvm 1    | Wrapper Manager: LowLogLevel from Wrapper is 1
jvm 1    | Received a packet PING_TIMEOUT : 30 
jvm 1    | Wrapper Manager: PingTimeout from Wrapper is 30000
jvm 1    | Received a packet PROPERTIES : (Property Values)
jvm 1    | Monitoring of the JVM thread count will be delayed for 1 seconds.
jvm 1    | Received a packet START : start 
jvm 1    | calling listener.start()
jvm 1    | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the
main method to complete.
jvm 1    | WrapperSimpleApp: invoking main method
jvm 1    | Send a packet START_PENDING : 5000 
wrapperp | read a packet START_PENDING : 5000
wrapper  | JVM signalled a start pending with waitHint of 5000 millis.
jvm 1    | Send a packet START_PENDING : 5000
jvm 1    | WrapperSimpleApp: start(args) end.  Main Completed=false,
exitCode=null 
jvm 1    | returned from listener.start()
jvm 1    | Send a packet STARTED : 
wrapperp | read a packet START_PENDING : 5000
wrapper  | JVM signalled a start pending with waitHint of 5000 millis.
wrapperp | read a packet STARTED : 
wrapper  | JVM signalled that it was started.
wrapperp | send a packet PING : ping
jvm 1    | Received a packet PING : ping
jvm 1    | Send a packet PING : ok
jvm 1    | Non-daemon thread count = 4 - 1(system) = 3 
wrapperp | read a packet PING : ok
wrapper  | Got ping response from JVM
jvm 1    | Got Control Signal 2->201
jvm 1    | Handled signal
jvm 1    | Processing control event(WRAPPER_CTRL_CLOSE_EVENT)
jvm 1    | WrapperSimpleApp: controlEvent(201) Stopping 
jvm 1    | WrapperManager.stop(0) called by thread:
Wrapper-Control-Event-Monitor
jvm 1    | Send a packet STOP : 0
wrapperp | read a packet STOP : 0
wrapper  | JVM requested a shutdown. (0)
wrapper  | wrapperStopProcess(0) called. 
wrapper  | Sending stop signal to JVM
wrapperp | send a packet STOP : NULL
jvm 1    | Received a packet STOP : 
jvm 1    | Non-daemon thread count = 4 - 1(system) = 3
jvm 1    | Thread, Wrapper-Control-Event-Monitor, handling the shutdown
process. 
jvm 1    | calling listener.stop()
jvm 1    | WrapperSimpleApp: stop(0)
jvm 1    | returned from listener.stop()
jvm 1    | Send a packet STOPPED : 0
wrapperp | read a packet STOPPED : 0
wrapper  | JVM signalled that it was stopped. 
jvm 1    | Closing socket.
jvm 1    | Closed socket: java.net.SocketException: socket closed
wrapperp | socket read no code (closed?).
wrapperp | server listening on port 32001.
jvm 1    | Server daemon shut down 
jvm 1    | calling System.exit(0)
wrapper  | JVM process exited with a code of 0, leaving the wrapper exit
code set to 0.
wrapper  | JVM exited normally.
wrapper  | <-- Wrapper Stopped


There was no file wrapper-windows-x86-32.dll included in the zip file I
downloaded. Am I missing something? There is a wrapper.dll file which I
copied to my native directory.

thanks in advance,
Bill Rees

[Wrapper-user] Issues With Windows v3.2

[Bill R. <ws...@gm...>]

Hello,

I'm trying to use v3.2 of the Java Service Wrapper and have run into an
issue that I can't seem to get past. Here is my wrapper.conf file:

#********************************************************************
# TestWrapper Properties
#
# NOTE - Please use src/conf/wrapper.conf.in as a template for your
#        own application rather than the values used for the
#        TestWrapper sample.
#********************************************************************
# Java Application
wrapper.java.command=java
wrapper.debug=true

# 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=C:\Program Files\VCS Server\wrapper.jar
wrapper.java.classpath.2=C:\Program Files\VCS Server\wrappertest.jar
wrapper.java.classpath.3=C:\Program Files\VCS Server\ImageServer.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=C:\Program Files\VCS Server\vcsNative

# Java Additional Parameters
wrapper.java.additional.1=-Duser.timezone=UTC
wrapper.java.additional.2=-Duser.dir="C:\Program Files\VCS Server"

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

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

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

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

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

# Log file to use for wrapper output logging.
wrapper.logfile=server.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=FINEST

# 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=10mb

# 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 Windows Properties
#********************************************************************
# Title to use when running as a console
wrapper.console.title=VCS

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

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

# Description of the service
wrapper.ntservice.description=VCS

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

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

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



Here is the output that is produced from the log when I attempt to install
and run the service:

DEBUG  | wrapper  | 2006/05/30 11:32:16 | Service command: "C:\Program
Files\VCS Server\wrapper.exe" -s wrapper.conf
STATUS | wrapper  | 2006/05/30 11:32:17 | VCS installed.
STATUS | wrapper  | 2006/05/30 11:32:23 | --> Wrapper Started as Service
DEBUG  | wrapper  | 2006/05/30 11:32:23 | Using tick timer.
DEBUG  | wrapperp | 2006/05/30 11:32:23 | server listening on port 32000.
DEBUG  | wrapper  | 2006/05/30 11:32:23 | Classpath element,
wrapper.java.classpath.2, does not exist: C:\Program Files\VCS
Server\wrappertesta.jar
STATUS | wrapper  | 2006/05/30 11:32:23 | Launching a JVM...
DEBUG  | wrapper  | 2006/05/30 11:32:23 | command:
"C:\WINDOWS\system32\java.exe" -Duser.timezone=UTC -Duser.dir="C:\Program
Files\VCS Server" -Xms128m -Xmx256m -Djava.library.path="C:\Program
Files\VCS Server\vcsNative" -classpath "C:\Program Files\VCS
Server\wrapper.jar;C:\Program Files\VCS Server\wrappertesta.jar;C:\Program
Files\VCS Server\ImageServer.jar" -Dwrapper.key="xEe2o3phm7_2ayOo" -
Dwrapper.port=32000 -Dwrapper.jvm.port.min=31000 -
Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE" -Dwrapper.pid=640 -
Dwrapper.version="3.2.0" -Dwrapper.native_library="wrapper" -
Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
org.tanukisoftware.wrapper.WrapperSimpleApp ImageServerDEBUG  | wrapper  |
2006/05/30 11:32:23 | JVM started (PID=3952)
INFO   | jvm 1    | 2006/05/30 11:32:23 | java.lang.NoClassDefFoundError:
org/tanukisoftware/wrapper/WrapperSimpleAppINFO   | jvm 1    | 2006/05/30
11:32:23 | Exception in thread "main"
DEBUG  | wrapper  | 2006/05/30 11:32:23 | JVM process exited with a code of
1, setting the wrapper exit code to 1.
ERROR  | wrapper  | 2006/05/30 11:32:23 | JVM exited while loading the
application.
DEBUG  | wrapper  | 2006/05/30 11:32:23 | JVM was only running for 0 seconds
leading to a failed restart count of 1.
DEBUG  | wrapper  | 2006/05/30 11:32:23 | Waiting 5 seconds before launching
another JVM.


Running as a console produces this output:

wrapper  | Attempt to set the console title failed: The handle is invalid.
(0x6)
wrapper  | --> Wrapper Started as Console
wrapper  | Using tick timer.
wrapperp | server listening on port 32000.
wrapper  | Launching a JVM...
wrapper  | command: "c:\WINDOWS\system32\java.exe" -Duser.timezone=UTC -
Duser.dir="C:\Program Files\VCS Server" -Xms128m -Xmx256m -
Djava.library.path="C:\Program Files\VCS Server\vcsNative" -classpath
"C:\Program Files\VCS Server\wrapper.jar;C:\Program Files\VCS
Server\wrappertest.jar;C:\Program Files\VCS Server\ImageServer.jar" -
Dwrapper.key="E6uyLkDxlffbFLn5" -Dwrapper.port=32000 -
Dwrapper.jvm.port.min=31000 -Dwrapper.jvm.port.max=31999 -Dwrapper.debug="TRUE"
-Dwrapper.pid=4408 -Dwrapper.version="3.2.0" -Dwrapper.native_library="wrapper"
-Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
org.tanukisoftware.wrapper.WrapperSimpleApp ImageServer
wrapper  | JVM started (PID=4508)
jvm 1    | WrapperManager class initialized by thread: main  Using
classloader: sun.misc.Launcher$AppClassLoader@e39a3e
jvm 1    | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
jvm 1    |
jvm 1    | Wrapper Manager: JVM #1
jvm 1    | Running a 32-bit JVM.
jvm 1    | Wrapper Manager: Registering shutdown hook
jvm 1    | Wrapper Manager: Using wrapper
jvm 1    | Load native library.  One or more attempts may fail if platform
specific libraries do not exist.
jvm 1    | Loading native library failed: wrapper-windows-x86-32.dll  Cause:
java.lang.UnsatisfiedLinkError: no wrapper-windows-x86-32 in
java.library.path
jvm 1    | Loaded native library: wrapper.dll
jvm 1    | Calling native initialization method.
jvm 1    | Initializing WrapperManager native library.
jvm 1    | Java Executable: c:\WINDOWS\system32\java.exe
jvm 1    | Windows version: 5.1.2600
jvm 1    | Java Version   : 1.5.0_06-b05 Java HotSpot(TM) Client VM
jvm 1    | Java VM Vendor : Sun Microsystems Inc.
jvm 1    |
jvm 1    | WrapperManager.start(
org.tanukisoftware.wrapper.WrapperSimpleApp@c5c3ac, args[]) called by
thread: main
jvm 1    | Open socket to wrapper...Wrapper-Connection
jvm 1    | Opened Socket from 31000 to 32000
jvm 1    | Send a packet KEY : E6uyLkDxlffbFLn5
jvm 1    | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31000])
wrapperp | accepted a socket from 127.0.0.1 on port 31000
wrapperp | read a packet KEY : E6uyLkDxlffbFLn5
wrapper  | Got key from JVM: E6uyLkDxlffbFLn5
wrapperp | send a packet LOW_LOG_LEVEL : 1
wrapperp | send a packet PING_TIMEOUT : 30
wrapperp | send a packet PROPERTIES : (Property Values)
wrapper  | Start Application.
wrapperp | send a packet START : start
jvm 1    | Received a packet LOW_LOG_LEVEL : 1
jvm 1    | Wrapper Manager: LowLogLevel from Wrapper is 1
jvm 1    | Received a packet PING_TIMEOUT : 30
jvm 1    | Wrapper Manager: PingTimeout from Wrapper is 30000
jvm 1    | Received a packet PROPERTIES : (Property Values)
jvm 1    | Monitoring of the JVM thread count will be delayed for 1 seconds.
jvm 1    | Received a packet START : start
jvm 1    | calling listener.start()
jvm 1    | WrapperSimpleApp: start(args) Will wait up to 2 seconds for the
main method to complete.
jvm 1    | WrapperSimpleApp: invoking main method
jvm 1    | Send a packet START_PENDING : 5000
wrapperp | read a packet START_PENDING : 5000
wrapper  | JVM signalled a start pending with waitHint of 5000 millis.
jvm 1    | Send a packet START_PENDING : 5000
jvm 1    | WrapperSimpleApp: start(args) end.  Main Completed=false,
exitCode=null
jvm 1    | returned from listener.start()
jvm 1    | Send a packet STARTED :
wrapperp | read a packet START_PENDING : 5000
wrapper  | JVM signalled a start pending with waitHint of 5000 millis.
wrapperp | read a packet STARTED :
wrapper  | JVM signalled that it was started.
wrapperp | send a packet PING : ping
jvm 1    | Received a packet PING : ping
jvm 1    | Send a packet PING : ok
jvm 1    | Non-daemon thread count = 4 - 1(system) = 3
wrapperp | read a packet PING : ok
wrapper  | Got ping response from JVM
jvm 1    | Got Control Signal 2->201
jvm 1    | Handled signal
jvm 1    | Processing control event(WRAPPER_CTRL_CLOSE_EVENT)
jvm 1    | WrapperSimpleApp: controlEvent(201) Stopping
jvm 1    | WrapperManager.stop(0) called by thread:
Wrapper-Control-Event-Monitor
jvm 1    | Send a packet STOP : 0
wrapperp | read a packet STOP : 0
wrapper  | JVM requested a shutdown. (0)
wrapper  | wrapperStopProcess(0) called.
wrapper  | Sending stop signal to JVM
wrapperp | send a packet STOP : NULL
jvm 1    | Received a packet STOP :
jvm 1    | Non-daemon thread count = 4 - 1(system) = 3
jvm 1    | Thread, Wrapper-Control-Event-Monitor, handling the shutdown
process.
jvm 1    | calling listener.stop()
jvm 1    | WrapperSimpleApp: stop(0)
jvm 1    | returned from listener.stop()
jvm 1    | Send a packet STOPPED : 0
wrapperp | read a packet STOPPED : 0
wrapper  | JVM signalled that it was stopped.
jvm 1    | Closing socket.
jvm 1    | Closed socket: java.net.SocketException: socket closed
wrapperp | socket read no code (closed?).
wrapperp | server listening on port 32001.
jvm 1    | Server daemon shut down
jvm 1    | calling System.exit(0)
wrapper  | JVM process exited with a code of 0, leaving the wrapper exit
code set to 0.
wrapper  | JVM exited normally.
wrapper  | <-- Wrapper Stopped


There was no file wrapper-windows-x86-32.dll included in the zip file I
downloaded. Am I missing something? There is a wrapper.dll file which I
copied to my native directory.

thanks in advance,
Bill Rees

[Wrapper-user] Unable to lauch application at startup on debian

[jonathan l. <jon...@wa...>]

I'm trying to lauch my java application at the startup of a debian. For the moment my app is only a loading an icone, in the system tray.
It is working properly and I can start and stop it using ./mywrapper start and ./mywrapper stop.
I merely followed the instructions here : http://wrapper.tanukisoftware.org/doc/english/launch-nix-boot-debian.html
Creating the symbolic link in /etc/init.d
ln -s /usr/lib/myapp/bin/myapp /etc/init.d/myapp
The link is working.
Then configuring the rc*.d
update-rc.d myapp start 99 5 . stop 99 0 1 6 .
This also working because as you can see below the wrapper is called and runned.
However, it has a problem running the JVM. I even set the JAVA_HOME in the conf file but it's not working.
 
If someone could help me, it would be great, thanks.

This is my config file :

# Java Application
set.default.JAVA_HOME=/usr/lib/j2sdk1.5-sun
set.JAVA_HOME=/usr/lib/j2sdk1.5-sun
export JAVA_HOME
wrapper.java.command=%JAVA_HOME%/bin/java

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

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=TestTray.jar
wrapper.java.classpath.2=../lib/wrapper.jar
wrapper.java.classpath.3=jdic.jar

# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
#wrapper.java.library.path.2=lib/libwrapper-linux-x86-32.so
# Java Additional Parameters
#wrapper.java.additional.1=


This is the wrapper.log after the startup 

DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[0] : /usr/lib/j2sdk1.5-sun/bin/java
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[1] : -Djava.library.path=../lib
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[2] : -classpath
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[3] : TestTray.jar:../lib/wrapper.jar:jdic.jar
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[4] : -Dwrapper.key=SyGk9qLsm4ALr7Bs
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[5] : -Dwrapper.port=32000
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[6] : -Dwrapper.jvm.port.min=31000
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[7] : -Dwrapper.jvm.port.max=31999
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[8] : -Dwrapper.debug=TRUE
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[9] : -Dwrapper.pid=3005
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[10] : -Dwrapper.version=3.2.0
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[11] : -Dwrapper.native_library=wrapper
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[12] : -Dwrapper.service=TRUE
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[13] : -Dwrapper.cpu.timeout=10
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[14] : -Dwrapper.jvmid=4
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[15] : Main
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[16] : --id
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[17] : 51
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[18] : --address
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[19] : bachibouzouk
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[20] : --home
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[21] : ./
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Command[22] : netmon-conf.xml
STATUS | wrapper  | 2006/05/25 17:27:58 | Launching a JVM...
INFO   | jvm 4    | 2006/05/25 17:27:58 | WrapperManager class initialized by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@198dfaf
INFO   | jvm 4    | 2006/05/25 17:27:58 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
INFO   | jvm 4    | 2006/05/25 17:27:58 |
INFO   | jvm 4    | 2006/05/25 17:27:58 | Wrapper Manager: JVM #4
INFO   | jvm 4    | 2006/05/25 17:27:58 | Running a 32-bit JVM.
INFO   | jvm 4    | 2006/05/25 17:27:58 | Wrapper Manager: Registering shutdown hook
INFO   | jvm 4    | 2006/05/25 17:27:58 | Wrapper Manager: Using wrapper
INFO   | jvm 4    | 2006/05/25 17:27:58 | Load native library.  One or more attempts may fail if platform specific libraries do not exist.
INFO   | jvm 4    | 2006/05/25 17:27:58 | Loaded native library: libwrapper-linux-x86-32.so
INFO   | jvm 4    | 2006/05/25 17:27:58 | Calling native initialization method.
INFO   | jvm 4    | 2006/05/25 17:27:58 | Inside native WrapperManager initialization method
INFO   | jvm 4    | 2006/05/25 17:27:58 | Java Version   : 1.5.0_06-b05 Java HotSpot(TM) Client VM
INFO   | jvm 4    | 2006/05/25 17:27:58 | Java VM Vendor : Sun Microsystems Inc.
INFO   | jvm 4    | 2006/05/25 17:27:58 |
INFO   | jvm 4    | 2006/05/25 17:27:58 | WrapperManager.start(Main@12a54f9, args["--id", "51", "--address", "bachibouzouk", "--home", "./", "netmon-conf.xml"]) called by thread: main
INFO   | jvm 4    | 2006/05/25 17:27:58 | Open socket to wrapper...Wrapper-Connection
INFO   | jvm 4    | 2006/05/25 17:27:58 | Failed attempt to bind using local port 31000
INFO   | jvm 4    | 2006/05/25 17:27:58 | Failed attempt to bind using local port 31001
INFO   | jvm 4    | 2006/05/25 17:27:58 | Failed attempt to bind using local port 31002
INFO   | jvm 4    | 2006/05/25 17:27:58 | Opened Socket from 31003 to 32000
INFO   | jvm 4    | 2006/05/25 17:27:58 | Send a packet KEY : SyGk9qLsm4ALr7Bs
INFO   | jvm 4    | 2006/05/25 17:27:58 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=31003])
DEBUG  | wrapperp | 2006/05/25 17:27:58 | accepted a socket from 127.0.0.1 on port 31003
DEBUG  | wrapperp | 2006/05/25 17:27:58 | read a packet KEY : SyGk9qLsm4ALr7Bs
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Got key from JVM: SyGk9qLsm4ALr7Bs
DEBUG  | wrapperp | 2006/05/25 17:27:58 | send a packet LOW_LOG_LEVEL : 1
DEBUG  | wrapperp | 2006/05/25 17:27:58 | send a packet PING_TIMEOUT : 30
DEBUG  | wrapperp | 2006/05/25 17:27:58 | send a packet PROPERTIES : (Property Values)
DEBUG  | wrapper  | 2006/05/25 17:27:58 | Start Application.
DEBUG  | wrapperp | 2006/05/25 17:27:58 | send a packet START : start
INFO   | jvm 4    | 2006/05/25 17:27:59 | Received a packet LOW_LOG_LEVEL : 1
INFO   | jvm 4    | 2006/05/25 17:27:59 | Wrapper Manager: LowLogLevel from Wrapper is 1
INFO   | jvm 4    | 2006/05/25 17:27:59 | Received a packet PING_TIMEOUT : 30
INFO   | jvm 4    | 2006/05/25 17:27:59 | Wrapper Manager: PingTimeout from Wrapper is 30000
INFO   | jvm 4    | 2006/05/25 17:27:59 | Received a packet PROPERTIES : (Property Values)
INFO   | jvm 4    | 2006/05/25 17:27:59 | Monitoring of the JVM thread count will be delayed for 1 seconds.
INFO   | jvm 4    | 2006/05/25 17:27:59 | Received a packet START : start
INFO   | jvm 4    | 2006/05/25 17:27:59 | calling listener.start()
INFO   | jvm 4    | 2006/05/25 17:27:59 | start
DEBUG  | wrapper  | 2006/05/25 17:27:59 | Signal trapped.  Details:
DEBUG  | wrapper  | 2006/05/25 17:27:59 |   signal number=17 (SIGCHLD), source="unknown"
DEBUG  | wrapper  | 2006/05/25 17:27:59 | Received SIGCHLD, calling wait().
DEBUG  | wrapper  | 2006/05/25 17:27:59 | wait() returned, child process should be gone.
DEBUG  | wrapperp | 2006/05/25 17:27:59 | socket read no code (closed?).
DEBUG  | wrapper  | 2006/05/25 17:27:59 | JVM process is gone.
ERROR  | wrapper  | 2006/05/25 17:27:59 | JVM exited while starting the application.
DEBUG  | wrapperp | 2006/05/25 17:27:59 | server listening on port 32000.
DEBUG  | wrapper  | 2006/05/25 17:27:59 | JVM was only running for 0 seconds leading to a failed restart count of 4

Re: [Wrapper-user] Wrapper Configuration

[Franck T. <fta...@gm...>]

Hi David,
You were right,
I set the classpath to ../classes and parameter to monitor.Ping and
everything is wotking fine. Thank you
Franck


On 5/25/06, David Hayes <da...@sm...> wrote:
>
>   If you run:
>
>
>
> java =96classpath=3D../classes/monitor ping
>
>
>
> from the directory where PingMonitor.bat is located, what is your result?
> This should cause Java to attempt to load the ping class the same way tha=
t
> the wrapper will. If you are returning the same error as in the wrapper,
> then your problem lies not directly within the Wrapper itself.
>
>
>
> My guess, is that ping is a member of the package monitor. As such, you
> shouldn't be setting your classpath to ../classes/monitor, but instead to
> simply ../classes, and setting the wrapper.app.parameter.1=3Dmonitor.ping=
.
>
>
>
> Hope this helps Franck,
>
>
>
> David
>
>
>  ------------------------------
>
> *From:* wra...@li... [mailto:
> wra...@li...] *On Behalf Of *Franck TAPSOBA
> *Sent:* 25 May 2006 16:26
> *To:* wra...@li...
> *Subject:* [Wrapper-user] Wrapper Configuration
>
>
>
> Hi guys,
>
> I have a problem configuring my wrapper.conf file.
>
> Here is the message i got :
>
>
> *C:\winSer\Monitor\bin>PingMonitor.bat**
> wrapper  | --> Wrapper Started as Console
> wrapper  | Launching a JVM...
> jvm 1    | Wrapper (Version 3.2.0) **http://wrapper.tanukisoftware.org*<h=
ttp://wrapper.tanukisoftware.org/>
> *jvm 1    |**
> jvm 1    | WrapperSimpleApp: Unable to locate the class ping.class:
> java.lang.ClassNotFoundException: ping.class
> jvm 1    |
> jvm 1    | WrapperSimpleApp Usage:
> jvm 1    |   java org.tanukisoftware.wrapper.WrapperSimpleApp {app_class}
> [app_parameters]
> jvm 1    |
> jvm 1    | Where:
> jvm 1    |   app_class:      The fully qualified class name of the
> application to run.
> jvm 1    |   app_parameters: The parameters that would normally be passed
> to the
> jvm 1    |                   application.
> wrapper  | <-- Wrapper Stopped
> Press any key to continue . . .*
>
>
> Here is my wrapper.conf file:
>
> *#**********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=3Djava *
>
> *# 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.WrapperSimpleApp*
>
> *# Java Classpath (include wrapper.jar)  Add class path elements as**
> #  needed starting from 1
> wrapper.java.classpath.1=3D../lib/wrapper.jar
> wrapper.java.classpath.2 =3D../classes/monitor*
>
>
> *# Java Library Path (location of Wrapper.DLL or libwrapper.so)**
> wrapper.java.library.path.1=3D../lib*
>
> *# Java Additional Parameters**
> #wrapper.java.additional.1=3D*
>
> *# 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**
> wrapper.app.parameter.1=3Dping.class*
>
> *#**********************************************************************
> # 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=3DINFO*
>
> *# 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=3DPing Monitor*
>
> *#**********************************************************************
> # 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=3DPing Monitor*
>
> *# Display name of the service**
> wrapper.ntservice.displayname=3DPing Monitor*
>
> *# Description of the service**
> wrapper.ntservice.description=3DPing Monitor monitors given IP addresses =
by
> pinging them to check if they are up*
>
> *# 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**
> wrapper.ntservice.starttype=3DAUTO_START*
>
> *# Allow the service to interact with the desktop.**
> wrapper.ntservice.interactive=3Dfalse*
>
>  When i launch my app.bat (PingMonitor.bat) I always got the exception
> ClassnotFoundException due to the fact the wrapper can not get my
> application class.  My application directory is as follow :
>
> *Monitor**
> *  ||
>   ||=3D=3D=3D>*classes**
> *  ||               ||
>   ||               ||=3D=3D=3D>*monitor* (contains ping.class)
>   ||
>   ||=3D=3D=3D>*bin* (contains wrapper.exe and and all .bat files)
>   ||
>   ||=3D=3D=3D>*conf* (contains wrapper.conf)
>
> Thank you for your help
>
> Franck
>
>
>
>
>
>
>

RE: [Wrapper-user] Wrapper Configuration

[David H. <da...@sm...>]

If you run:

 

java -classpath=../classes/monitor ping

 

from the directory where PingMonitor.bat is located, what is your result?
This should cause Java to attempt to load the ping class the same way that
the wrapper will. If you are returning the same error as in the wrapper,
then your problem lies not directly within the Wrapper itself.

 

My guess, is that ping is a member of the package monitor. As such, you
shouldn't be setting your classpath to ../classes/monitor, but instead to
simply ../classes, and setting the wrapper.app.parameter.1=monitor.ping.

 

Hope this helps Franck,

 

David

 

  _____  

From: wra...@li...
[mailto:wra...@li...] On Behalf Of Franck
TAPSOBA
Sent: 25 May 2006 16:26
To: wra...@li...
Subject: [Wrapper-user] Wrapper Configuration

 

Hi guys,

I have a problem configuring my wrapper.conf file.

Here is the message i got :


C:\winSer\Monitor\bin>PingMonitor.bat
wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
jvm 1    | Wrapper (Version 3.2.0)  <http://wrapper.tanukisoftware.org/>
http://wrapper.tanukisoftware.org
jvm 1    |
jvm 1    | WrapperSimpleApp: Unable to locate the class ping.class:
java.lang.ClassNotFoundException: ping.class
jvm 1    |
jvm 1    | WrapperSimpleApp Usage: 
jvm 1    |   java org.tanukisoftware.wrapper.WrapperSimpleApp {app_class}
[app_parameters]
jvm 1    |
jvm 1    | Where:
jvm 1    |   app_class:      The fully qualified class name of the
application to run.
jvm 1    |   app_parameters: The parameters that would normally be passed to
the
jvm 1    |                   application.
wrapper  | <-- Wrapper Stopped
Press any key to continue . . .


Here is my wrapper.conf file:

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

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

# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2 =../classes/monitor


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

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

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

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

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

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

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

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

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

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

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

#********************************************************************
# Wrapper Windows Properties
#********************************************************************
# Title to use when running as a console 
wrapper.console.title=Ping Monitor

#********************************************************************
# 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=Ping Monitor

# Display name of the service
wrapper.ntservice.displayname=Ping Monitor

# Description of the service
wrapper.ntservice.description=Ping Monitor monitors given IP addresses by
pinging them to check if they are up

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

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

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

 When i launch my app.bat (PingMonitor.bat) I always got the exception
ClassnotFoundException due to the fact the wrapper can not get my
application class.  My application directory is as follow :

Monitor
  ||
  ||===>classes
  ||               ||
  ||               ||===>monitor (contains ping.class)
  ||
  ||===>bin (contains wrapper.exe and and all .bat files)
  ||
  ||===>conf (contains wrapper.conf)

Thank you for your help

Franck



 

 

Re: [Wrapper-user] Wrapper Configuration

[Franck T. <fta...@gm...>]

HI Leif,
I tried that but I'm always getting  a classNotFoundException with this
message  *monitor/ping (wrong name: monitor/Ping)*
Thanks for your help
Franck


On 5/25/06, Leif Mortenson <le...@ta...> wrote:
>
> Franck,
> Most likely,
> wrapper.app.parameter.1=3Dping.class
> should be
> wrapper.app.parameter.1=3Dping
>
> Cheers,
> Leif
>

Re: [Wrapper-user] Wrapper Configuration

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

Franck,
Most likely,
wrapper.app.parameter.1=ping.class
should be
wrapper.app.parameter.1=ping

Cheers,
Leif

Franck TAPSOBA wrote:
> Hi guys,
> I have a problem configuring my wrapper.conf file.
> Here is the message i got :
>
>
> *C:\winSer\Monitor\bin>PingMonitor.bat
> wrapper  | --> Wrapper Started as Console
> wrapper  | Launching a JVM...
> jvm 1    | Wrapper (Version 3.2.0) * 
> *http://wrapper.tanukisoftware.org* <http://wrapper.tanukisoftware.org/>
> *jvm 1    |
> jvm 1    | WrapperSimpleApp: Unable to locate the class ping.class: 
> java.lang.ClassNotFoundException: ping.class
> jvm 1    |
> jvm 1    | WrapperSimpleApp Usage:
> jvm 1    |   java org.tanukisoftware.wrapper.WrapperSimpleApp 
> {app_class} [app_parameters]
> jvm 1    |
> jvm 1    | Where:
> jvm 1    |   app_class:      The fully qualified class name of the 
> application to run.
> jvm 1    |   app_parameters: The parameters that would normally be 
> passed to the
> jvm 1    |                   application.
> wrapper  | <-- Wrapper Stopped
> Press any key to continue . . .*
>
>
> Here is my wrapper.conf file:
>
> *#********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=java *
>
> *# Java Main class.  This class must implement the WrapperListener 
> interface
> #  or guarantee that the WrapperManager class is initialized.  Helper
> #  classes are provided to do this for you.  See the Integration section
> #  of the documentation for details.
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp*
>
> *# Java Classpath (include wrapper.jar)  Add class path elements as
> #  needed starting from 1
> wrapper.java.classpath.1=../lib/wrapper.jar
> wrapper.java.classpath.2 =../classes/monitor*
>
>
> *# Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=../lib*
>
> *# 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=64*
>
> *# Application parameters.  Add parameters as needed starting from 1
> wrapper.app.parameter.1=ping.class*
>
> *#********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=PM*
>
> *# Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=INFO*
>
> *# Log file to use for wrapper output logging.
> wrapper.logfile=../logs/wrapper.log*
>
> *# Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=LPTM*
>
> *# Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=INFO*
>
> *# Maximum size that the log file will be allowed to grow to before
> #  the log is rolled. Size is specified in bytes.  The default value
> #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
> #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
> wrapper.logfile.maxsize=0*
>
> *# Maximum number of rolled log files which will be allowed before old
> #  files are deleted.  The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=0*
>
> *# Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=NONE*
>
> *#********************************************************************
> # Wrapper Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Ping Monitor*
>
> *#********************************************************************
> # 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=Ping Monitor*
>
> *# Display name of the service
> wrapper.ntservice.displayname=Ping Monitor*
>
> *# Description of the service
> wrapper.ntservice.description=Ping Monitor monitors given IP addresses 
> by pinging them to check if they are up*
>
> *# Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=*
>
> *# Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START*
>
> *# Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false*
>
>  When i launch my app.bat (PingMonitor.bat) I always got the exception 
> ClassnotFoundException due to the fact the wrapper can not get my 
> application class.  My application directory is as follow :
>
> *Monitor
> *  ||
>   ||===>*classes
> *  ||               ||
>   ||               ||===>*monitor* (contains ping.class)
>   ||
>   ||===>*bin* (contains wrapper.exe and and all .bat files)
>   ||
>   ||===>*conf* (contains wrapper.conf)
>
> Thank you for your help
>
> Franck
>
>
>
>  
>
>  
>

[Wrapper-user] Wrapper Configuration

[Franck T. <fta...@gm...>]

Hi guys,
I have a problem configuring my wrapper.conf file.
Here is the message i got :


*C:\winSer\Monitor\bin>PingMonitor.bat
wrapper  | --> Wrapper Started as Console
wrapper  | Launching a JVM...
jvm 1    | Wrapper (Version 3.2.0)
**http://wrapper.tanukisoftware.org*<http://wrapper.tanukisoftware.org/>
*jvm 1    |
jvm 1    | WrapperSimpleApp: Unable to locate the class ping.class:
java.lang.ClassNotFoundException: ping.class
jvm 1    |
jvm 1    | WrapperSimpleApp Usage:
jvm 1    |   java org.tanukisoftware.wrapper.WrapperSimpleApp {app_class}
[app_parameters]
jvm 1    |
jvm 1    | Where:
jvm 1    |   app_class:      The fully qualified class name of the
application to run.
jvm 1    |   app_parameters: The parameters that would normally be passed t=
o
the
jvm 1    |                   application.
wrapper  | <-- Wrapper Stopped
Press any key to continue . . .*


Here is my wrapper.conf file:

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

*# Java Main class.  This class must implement the WrapperListener interfac=
e
#  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.WrapperSimpleApp*

*# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=3D../lib/wrapper.jar
wrapper.java.classpath.2 =3D../classes/monitor*


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

*# Java Additional Parameters
#wrapper.java.additional.1=3D*

*# 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
wrapper.app.parameter.1=3Dping.class*

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

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

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

*# Display name of the service
wrapper.ntservice.displayname=3DPing Monitor*

*# Description of the service
wrapper.ntservice.description=3DPing Monitor monitors given IP addresses by
pinging them to check if they are up*

*# 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
wrapper.ntservice.starttype=3DAUTO_START*

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

 When i launch my app.bat (PingMonitor.bat) I always got the exception
ClassnotFoundException due to the fact the wrapper can not get my
application class.  My application directory is as follow :

*Monitor
*  ||
  ||=3D=3D=3D>*classes
*  ||               ||
  ||               ||=3D=3D=3D>*monitor* (contains ping.class)
  ||
  ||=3D=3D=3D>*bin* (contains wrapper.exe and and all .bat files)
  ||
  ||=3D=3D=3D>*conf* (contains wrapper.conf)

Thank you for your help

Franck

Re: [Wrapper-user] windows 64bit wrapper dll

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

Richard,
    That is correct.  I don't have any 64-bit machines yet and need a 
volunteer to help get
the build working so I can make it possible.  I started to make the 
makefiles that are
included in the release, but they will not work as is.

Cheers,
Leif

Richard Emberson wrote:
> Am I correct that there is currently not a windows
> 64bit wrapper dll on the download site?
>
> Richard
>

[Wrapper-user] windows 64bit wrapper dll

[Richard E. <rem...@ed...>]

Am I correct that there is currently not a windows
64bit wrapper dll on the download site?

Richard

-- 
This email message is for the sole use of the intended recipient(s) and
may contain confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.

Re: [Wrapper-user] Athlon Processor

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

Patrick,
    Thanks for the note.  I fixed it for the 3.2.1 release.

Cheers,
Leif

Patrick Kimber wrote:
> Hi
> We have just deployed our application to a linux server which has an
> athlon processor.  The default "testwrapper" script fails.
>
> To solve this issue, we amended line 162 in the "testwrapper" script
> to check for the athlon processor:
>
> 162c162
> <     'amd64' | 'ia32' | 'ia64' | 'i386' | 'i486' | 'i586' | 'i686' | 
> 'x86_64')
> ---
>>     'amd64' | 'athlon' | 'ia32' | 'ia64' | 'i386' | 'i486' | 'i586' | 
>> 'i686' | 'x86_64')
>
> Patrick

[Wrapper-user] Athlon Processor

[Patrick K. <mai...@gm...>]

Hi
We have just deployed our application to a linux server which has an
athlon processor.  The default "testwrapper" script fails.

To solve this issue, we amended line 162 in the "testwrapper" script
to check for the athlon processor:

162c162
<     'amd64' | 'ia32' | 'ia64' | 'i386' | 'i486' | 'i586' | 'i686' | 'x86_=
64')
---
>     'amd64' | 'athlon' | 'ia32' | 'ia64' | 'i386' | 'i486' | 'i586' | 'i6=
86' | 'x86_64')

Patrick

Re: [Wrapper-user] getting hardware arch using just java

[Richard E. <rem...@ed...>]

Thanks - works great.

Richard


Leif Mortenson wrote:
> Richard,
>    The wrapper binary itself can always be 32 bit.  It is an independent 
> process and
> the 32-bit version works fine on 64-bit platforms.  the libwrapper.so 
> file is another
> story.   3.2.0 supports platform specific naming.   If you download the 
> delta pack
> release, you will find that it contains all of the currently supported 
> platforms in a
> single release.   The files have been named in such a way as to make 
> sure the
> correct wrapper binary and libwrapper.so file are used for the current 
> platform
> and JVM.
>    In the case of a 32-bit linux JVM, libwrapper-linux-x86-32.so will be 
> loaded.
> 64-bit would be libwrapper-linux-x86-84.so.   The WrapperManager class 
> takes
> care of this by trying to first load a platform specific JNI library and 
> then falling back
> to the default libwrapper.so name.
> 
>    This method works great for the wrapper's JNI library.  But most java 
> classes do
> not contain support for attempting to load platform specific native 
> libraries based on
> their names.
>    To work around this, 3.2.1 will contain a series of 3 new environment 
> variables
> that will be set on wrapper invocation and be available within the 
> wrapper.conf file:
> 
> wrapper.java.library.path.1=../lib/%WRAPPER_OS%-%WRAPPER_ARCH%-%WRAPPER_BITS% 
> 
> 
>    This makes it possible to create a library path as follows so that 
> each platform
> specific directory contains the native libraries for that platform.  
> This method will
> work with any java class requiring a native library without requiring 
> any code
> modifications.
> 
> Cheers,
> Leif
> 
> Richard Emberson wrote:
>> Leif,
>>
>> The native libraries are one of the issues. On a 64 bit machine if
>> I install the 64 bit wrapper and libwrapper.so can I run a 32 bit
>> jvm or must I run a 64 bit jvm?
>> Thanks.
>>
>> Richard
>>
>>
>> Leif Mortenson wrote:
>>> Richard,
>>>    Oh.  To do that you are going to need to use Runtime.exec to
>>> run "uname -a" or some variant.  Note that if you are worried about
>>> native libraries within Java though, it is the bit depth of the JVM, not
>>> that of the hardware that is going to matter to you.
>>>
>>> Cheers,
>>> Leif
>>>
>>> Richard Emberson wrote:
>>>> On my 64 linux workstation when I run java 1.4.2_11,
>>>> a 32 bit version of Java, sun.arch.data.model == 32;
>>>> but when I run java 1.5.0_06 amd64, a 64 bit version
>>>> of Java, sun.arch.data.model == 64.
>>>> I was not clear. I wish to know the underlying
>>>> hardware machine bits, 32 or 64, if possible from
>>>> within java.
>>>>
>>>> Richard
>>>>
>>>> Leif Mortenson wrote:
>>>>> Richard,
>>>>>    Download the source distribution and take a look at the 
>>>>> build.xml in the root
>>>>> directory.  It does exactly this.   If you want to see an example 
>>>>> of it being done
>>>>> in Java, then take a look at the source of the WrapperManager class 
>>>>> in the
>>>>> generateDetailedNativeLibraryBaseName method.  The JVM bits are 
>>>>> accessed
>>>>> as follows:
>>>>>        m_jvmBits = Integer.getInteger( "sun.arch.data.model", -1 
>>>>> ).intValue();
>>>>>    Note that the property does not exist on all JVMs.
>>>>>
>>>>> Cheers,
>>>>> Leif
>>>>>
>>>>> Richard Emberson wrote:
>>>>>> I have to support solaris, linux and windows on
>>>>>> 32 and 64 bit machines.
>>>>>> The wrapper executable and native library comes in
>>>>>> 32 and 64 bit versions for those OSs.
>>>>>> What I need is the ability during an installation
>>>>>> to know what the machine (the hardware) architecture
>>>>>> is, 32 or 64 bit. I need to be able to know this
>>>>>> from within a java process (actually an Ant task).
>>>>>> I discovered today on my 64 bit workstation that if
>>>>>> I run java 1.4.x, a 32 bit java, then the system
>>>>>> property os.arch has the value i386 but if I run java
>>>>>> 1.5.x the os.arch has the value amd64 --- os.arch
>>>>>> does not give the hardware architecture but rather
>>>>>> the java vm architecture. In order to install the
>>>>>> correct version of the wrapper executable and
>>>>>> native libaray I need the true hardware architecture
>>>>>> independent of what jvm I will be running.
>>>>>> Any thoughts as to how to get this information
>>>>>> using just java?
>>>>>>
>>>>>> Richard
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> Using Tomcat but need to do more? Need to support web services, 
>>>>> security?
>>>>> Get stuff done quickly with pre-integrated technology to make your 
>>>>> job easier
>>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>>>> Geronimo
>>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
>>>>>
>>>>> _______________________________________________
>>>>> Wrapper-user mailing list
>>>>> Wra...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services, 
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your 
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>
>>
> 
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


-- 
This email message is for the sole use of the intended recipient(s) and
may contain confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.

RE: [Wrapper-user] Debugging with wrapper

[David H. <da...@sm...>]

I love the sound of that Leif!

You would never really want to roll out an application in Debug mode (in =
my
mind at least), so you wouldn't care as much about the restarting of the
application. You would though care if it would have been restarted, this
will do the job nicely!

Cheers Leif,
David

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...] On Behalf Of Leif
Mortenson
Sent: 17 May 2006 03:47
To: wra...@li...
Subject: Re: [Wrapper-user] Debugging with wrapper

Chandra, David,
    I made some changes for the 3.2.1 release.

    The wrapper will now enter a "DebugJVM" mode if the=20
wrapper.java.command ends
in "jdb" or "jdb.exe", or the "-Xdebug" argument is passed to the JVM.

    When operating in the "DebugJVM" mode, a warning will be displayed=20
on JVM launch
if any of the timeouts are not set to 0.  The warning warns that the=20
ability to detect and
restart a frozen JVM will be disabled.

    Then if a timeout does occur, it will be ignored.  But the first=20
such timeout will cause
another warning to be displayed to the user stating which timeout was=20
encountered and
saying that it may be caused by a debugger having suspended the JVM.

    Does this make everyone happy?

Cheers,
Leif

  =20

Chandra Patni wrote:
> I see how your proposal is more compliant and semantically correct=20
> than mine which is in the spirit of 'benevolent dictatorship'. Either=20
> way, it would be nice to have nice debugging experience.
>
>
>
> da...@sm... wrote:
>> I agree and disagree. I don't think the wrapper should set its ping=20
>> to  0 if debug is set, but I do think it should not restart when=20
>> debug is  set. Maybe record in in the log file that it timed out, but =

>> due to  debug existing, the application won't be restarted, unless=20
>> there is  some super-sexy way of finding out from the debugged=20
>> application that  the wrapper thread (and others depending upon the=20
>> debugger that  connects to it) has been debug paused.
>>
>> My thoughts at least!
>>
>> Cheers again Leif!
>>
>> Quoting Chandra Patni <cp...@ig...>:
>>
>>> I think wrapper should set ping timeout to zero if -Xdebug and
>>> -Xrunjdwp .... option is set  for JVMDI supporting VMs. And print =
out
>>> this as warning. It should also do the same when -agentlib:jdwp...
>>> option is set for newer JVMTI supporting VMs. Otherwise, it will =
always
>>> result in surprised user.
>>>
>>>
>>>
>>> Leif Mortenson wrote:
>>>
>>>> Chandra,
>>>> I'm not sure of any way to let the Wrapper know that the JVM is  =20
>>>> paused due to
>>>> debug mode.  You would not want to disable the ping timeout simply=20
>>>> because
>>>> debug was enabled.    I should add a note about this or maybe=20
>>>> make   the Wrapper
>>>> provide some additional info if the command line contains -Xdebug.  =

>>>> Setting
>>>> wrapper.ping.timeout to 0 should solve the problem for you however.
>>>>
>>>> Cheers,
>>>> Leif
>>>>
>>>> Chandra Patni wrote:
>>>>
>>>>> I started my JVM with
>>>>> -Xdebug -Xnoagent -Djava.compiler=3DNONE  =20
>>>>> =
-Xrunjdwp:transport=3Ddt_socket,server=3Dy,suspend=3Dn,address=3D5005
>>>>>
>>>>> and attached IDE debugger. Blocked a JSP thread on a breakpoint.   =

>>>>> The wrapper restarts/shuts down (depending on  =20
>>>>> wrapper.disable_restarts=3DTRUE) the VM.
>>>>>
>>>>>
>>>>> ERROR  | wrapper  | 2006/05/09 16:35:02 | JVM appears hung:=20
>>>>> Timed   out waiting for signal from JVM.
>>>>> ERROR  | wrapper  | 2006/05/09 16:35:02 | JVM did not exit on  =20
>>>>> request, terminated
>>>>> STATUS | wrapper  | 2006/05/09 16:35:03 | JVM Restarts disabled.   =

>>>>> Shutting down.
>>>>> STATUS | wrapper  | 2006/05/09 16:35:03 | <-- Wrapper Stopped
>>>>>
>>>>> I can set the wrapper.ping.timeout to zero to avoid this.  =20
>>>>> Shouldn't wrapper should detect debug mode?
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> Using Tomcat but need to do more? Need to support web services,=20
>>>>> security?
>>>>> Get stuff done quickly with pre-integrated technology to make=20
>>>>> your   job easier
>>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache=20
>>>>> Geronimo
>>>>>
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642=20
>>>>>
>>>>> _______________________________________________
>>>>> Wrapper-user mailing list
>>>>> Wra...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> Using Tomcat but need to do more? Need to support web services,=20
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make=20
>>>> your   job easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache=20
>>>> Geronimo
>>>>
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642=20
>>>>
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services,=20
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your=20
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache=20
>>> Geronimo
>>> =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642

>>>
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services,=20
>> security?
>> Get stuff done quickly with pre-integrated technology to make your=20
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache=20
>> Geronimo
>> =
http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=120709&bid&3057&dat=121642
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, =
security?
> Get stuff done quickly with pre-integrated technology to make your job =

> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache=20
> Geronimo
> =
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, =
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache =
Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Debugging with wrapper

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

Chandra, David,
    I made some changes for the 3.2.1 release.

    The wrapper will now enter a "DebugJVM" mode if the 
wrapper.java.command ends
in "jdb" or "jdb.exe", or the "-Xdebug" argument is passed to the JVM.

    When operating in the "DebugJVM" mode, a warning will be displayed 
on JVM launch
if any of the timeouts are not set to 0.  The warning warns that the 
ability to detect and
restart a frozen JVM will be disabled.

    Then if a timeout does occur, it will be ignored.  But the first 
such timeout will cause
another warning to be displayed to the user stating which timeout was 
encountered and
saying that it may be caused by a debugger having suspended the JVM.

    Does this make everyone happy?

Cheers,
Leif

   

Chandra Patni wrote:
> I see how your proposal is more compliant and semantically correct 
> than mine which is in the spirit of 'benevolent dictatorship'. Either 
> way, it would be nice to have nice debugging experience.
>
>
>
> da...@sm... wrote:
>> I agree and disagree. I don't think the wrapper should set its ping 
>> to  0 if debug is set, but I do think it should not restart when 
>> debug is  set. Maybe record in in the log file that it timed out, but 
>> due to  debug existing, the application won't be restarted, unless 
>> there is  some super-sexy way of finding out from the debugged 
>> application that  the wrapper thread (and others depending upon the 
>> debugger that  connects to it) has been debug paused.
>>
>> My thoughts at least!
>>
>> Cheers again Leif!
>>
>> Quoting Chandra Patni <cp...@ig...>:
>>
>>> I think wrapper should set ping timeout to zero if -Xdebug and
>>> -Xrunjdwp .... option is set  for JVMDI supporting VMs. And print out
>>> this as warning. It should also do the same when -agentlib:jdwp...
>>> option is set for newer JVMTI supporting VMs. Otherwise, it will always
>>> result in surprised user.
>>>
>>>
>>>
>>> Leif Mortenson wrote:
>>>
>>>> Chandra,
>>>> I'm not sure of any way to let the Wrapper know that the JVM is   
>>>> paused due to
>>>> debug mode.  You would not want to disable the ping timeout simply 
>>>> because
>>>> debug was enabled.    I should add a note about this or maybe 
>>>> make   the Wrapper
>>>> provide some additional info if the command line contains -Xdebug.  
>>>> Setting
>>>> wrapper.ping.timeout to 0 should solve the problem for you however.
>>>>
>>>> Cheers,
>>>> Leif
>>>>
>>>> Chandra Patni wrote:
>>>>
>>>>> I started my JVM with
>>>>> -Xdebug -Xnoagent -Djava.compiler=NONE   
>>>>> -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005
>>>>>
>>>>> and attached IDE debugger. Blocked a JSP thread on a breakpoint.   
>>>>> The wrapper restarts/shuts down (depending on   
>>>>> wrapper.disable_restarts=TRUE) the VM.
>>>>>
>>>>>
>>>>> ERROR  | wrapper  | 2006/05/09 16:35:02 | JVM appears hung: 
>>>>> Timed   out waiting for signal from JVM.
>>>>> ERROR  | wrapper  | 2006/05/09 16:35:02 | JVM did not exit on   
>>>>> request, terminated
>>>>> STATUS | wrapper  | 2006/05/09 16:35:03 | JVM Restarts disabled.   
>>>>> Shutting down.
>>>>> STATUS | wrapper  | 2006/05/09 16:35:03 | <-- Wrapper Stopped
>>>>>
>>>>> I can set the wrapper.ping.timeout to zero to avoid this.   
>>>>> Shouldn't wrapper should detect debug mode?
>>>>>
>>>>>
>>>>>
>>>>> -------------------------------------------------------
>>>>> Using Tomcat but need to do more? Need to support web services, 
>>>>> security?
>>>>> Get stuff done quickly with pre-integrated technology to make 
>>>>> your   job easier
>>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>>>> Geronimo
>>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
>>>>>
>>>>> _______________________________________________
>>>>> Wrapper-user mailing list
>>>>> Wra...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> Using Tomcat but need to do more? Need to support web services, 
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make 
>>>> your   job easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>>> Geronimo
>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
>>>>
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services, 
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your 
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
>>>
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>>
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, 
>> security?
>> Get stuff done quickly with pre-integrated technology to make your 
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=k&kid0709&bid&3057&dat1642
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

Re: [Wrapper-user] Wrapper console vs service problems

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

Gary,
    As David mentioned, the system account does not have access to 
network drives.  But
it sounds like you are using another account.   Is that the same account 
as you are logged
in as?

    I had a problem a couple years ago where a customer's 2000 machine 
would not start
my service correctly after a reboot because the service was referencing 
mapped network
drives.  If I start the service after the machine was up, it would work 
fine.  But on restart,
the network drives would sometimes not be available at the time the 
wrapper service was
started.  They would then never become available to that particular 
service.   The solution
was to use UNC paths to reference the network drives.   But it doesn't 
sound like that is
and option for you.

Cheers,
Leif

Parker, Gary wrote:
>
> Hi Everyone,
>
> I'm running snipsnap (http://snipsnap.org/space/start) and placing the 
> posted content on a network drive and wanted to make this a Windows 
> service for availability. I'm using integration Method1 
> (WrapperSimpleApp) In service mode I get the following in the browser:
>
> http://myserver:myport/space
>
>
> *HTTP ERROR: 404 %2Fspace+Not+Found*
> RequestURI=/space
> _/Powered by Jetty:// <http://jetty.mortbay.org>/_
>
> In console mode everything works fine, and everything works fine on 
> the local file system both in console mode and in service mode.
>
> I can't use UNC syntax because SnipSnap seems unhappy with this, so 
> have a mapped drive whic is active at the time of these observations.  
> I'm not running the service under the system account, and am using the 
> same account for both the service mode and console mode.  I've also 
> tried setting debug on, and working directory with no appreciable effect.
>
> Any ideas?
>
> Here's my wrapper.conf:
>
> #********************************************************************
> # Wrapper Properties
> #********************************************************************
> # Java Application
> wrapper.java.command=%JAVA_HOME%\bin\java
>
> wrapper.working.dir=C:\snipsnap\snipsnap-1.0b3-uttoxeter
> wrapper.debug=TRUE
>
>
> # 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=%JAVA_HOME%/lib/tools.jar
> wrapper.java.classpath.3=lib/snipsnap.jar
>
> # Java Library Path (location of Wrapper.DLL or libwrapper.so)
> wrapper.java.library.path.1=lib
>
> # Java Additional Parameters
> #wrapper.java.additional.1=-Dprogram.name=run.bat
>
> # 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=org.snipsnap.server.SnipSnapLauncher
> #wrapper.app.parameter.2=-root 
> "//myfileshareserver/Share/Technology/DCMTS/Documentation/Projects/Next/NextSnipSnapWiki/content"
>
> #wrapper.app.parameter.2=-root "c:\snipsnap\content"
> wrapper.app.parameter.2=-root 
> "S:\Technology\DCMTS\Documentation\Projects\Next\NextSnipSnapWiki\content" 
>
>
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console.  (See docs for formats)
> wrapper.console.format=PM
>
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=INFO
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=logs/wrapper.log
>
> # Format of output for the log file.  (See docs for formats)
> wrapper.logfile.format=LPTM
>
> # Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=INFO
>
> # Maximum size that the log file will be allowed to grow to before
> #  the log is rolled. Size is specified in bytes.  The default value
> #  of 0, disables log rolling.  May abbreviate with the 'k' (kb) or
> #  'm' (mb) suffix.  For example: 10m = 10 megabytes.
> wrapper.logfile.maxsize=0
>
> # Maximum number of rolled log files which will be allowed before old
> #  files are deleted.  The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=0
>
> # Log Level for sys/event log output.  (See docs for log levels)
> wrapper.syslog.loglevel=NONE
>
> #********************************************************************
> # Wrapper Windows Properties
> #********************************************************************
> # Title to use when running as a console
> wrapper.console.title=Next SnipSnap Wiki
>
> #********************************************************************
> # 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=Next SnipSnap Wiki
>
> # Display name of the service
> wrapper.ntservice.displayname=Next SnipSnap Wiki
>
> # Description of the service
> wrapper.ntservice.description=Next SnipSnap Wiki
>
> # Service dependencies.  Add dependencies as needed starting from 1
> wrapper.ntservice.dependency.1=
>
> # Mode in which the service is installed.  AUTO_START or DEMAND_START
> wrapper.ntservice.starttype=AUTO_START
>
> # Allow the service to interact with the desktop.
> wrapper.ntservice.interactive=false
>
>
> Parkie
>
>  

Re: [Wrapper-user] jvm profiler usage

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

Xavier,
    Want to make sure that the "x" in both the properties below is 
actually an
integer.  If not then the property will not be seen.

    Make sure that the Java command being generated by the wrapper is what
you are expecting.   Set the following and run it again.
wrapper.java.command.loglevel=INFO

Cheers,
Leif

Xavier Toth wrote:
> I'm trying to configure a profiler agent for use with my wrapped
> service but the agents share library isn't being found. I added :
>
> wrapper.java.library.path.x=/opt/jprofiler4/bin/linux_x64
>
> which contains libjprofilerti.so and
>
> wrapper.java.additional.x=-agentlib:jprofilerti
>
> to my wrapper config file. However when I try and start my service it
> fail because it can't find the shared library. I'm doing this on Linux
> and I've tried setting the environment var LD_LIBRARY_PATH and running
> ldconfig /opt/jprofiler4/bin/linux_x64 to make sure that the library
> can be found but nothing has worked. Any suggestions?
>

Re: [Wrapper-user] getting hardware arch using just java

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

Richard,
    The wrapper binary itself can always be 32 bit.  It is an 
independent process and
the 32-bit version works fine on 64-bit platforms.  the libwrapper.so 
file is another
story.   3.2.0 supports platform specific naming.   If you download the 
delta pack
release, you will find that it contains all of the currently supported 
platforms in a
single release.   The files have been named in such a way as to make 
sure the
correct wrapper binary and libwrapper.so file are used for the current 
platform
and JVM.
    In the case of a 32-bit linux JVM, libwrapper-linux-x86-32.so will 
be loaded.
64-bit would be libwrapper-linux-x86-84.so.   The WrapperManager class takes
care of this by trying to first load a platform specific JNI library and 
then falling back
to the default libwrapper.so name.

    This method works great for the wrapper's JNI library.  But most 
java classes do
not contain support for attempting to load platform specific native 
libraries based on
their names.
    To work around this, 3.2.1 will contain a series of 3 new 
environment variables
that will be set on wrapper invocation and be available within the 
wrapper.conf file:

wrapper.java.library.path.1=../lib/%WRAPPER_OS%-%WRAPPER_ARCH%-%WRAPPER_BITS%

    This makes it possible to create a library path as follows so that 
each platform
specific directory contains the native libraries for that platform.  
This method will
work with any java class requiring a native library without requiring 
any code
modifications.

Cheers,
Leif

Richard Emberson wrote:
> Leif,
>
> The native libraries are one of the issues. On a 64 bit machine if
> I install the 64 bit wrapper and libwrapper.so can I run a 32 bit
> jvm or must I run a 64 bit jvm?
> Thanks.
>
> Richard
>
>
> Leif Mortenson wrote:
>> Richard,
>>    Oh.  To do that you are going to need to use Runtime.exec to
>> run "uname -a" or some variant.  Note that if you are worried about
>> native libraries within Java though, it is the bit depth of the JVM, not
>> that of the hardware that is going to matter to you.
>>
>> Cheers,
>> Leif
>>
>> Richard Emberson wrote:
>>> On my 64 linux workstation when I run java 1.4.2_11,
>>> a 32 bit version of Java, sun.arch.data.model == 32;
>>> but when I run java 1.5.0_06 amd64, a 64 bit version
>>> of Java, sun.arch.data.model == 64.
>>> I was not clear. I wish to know the underlying
>>> hardware machine bits, 32 or 64, if possible from
>>> within java.
>>>
>>> Richard
>>>
>>> Leif Mortenson wrote:
>>>> Richard,
>>>>    Download the source distribution and take a look at the 
>>>> build.xml in the root
>>>> directory.  It does exactly this.   If you want to see an example 
>>>> of it being done
>>>> in Java, then take a look at the source of the WrapperManager class 
>>>> in the
>>>> generateDetailedNativeLibraryBaseName method.  The JVM bits are 
>>>> accessed
>>>> as follows:
>>>>        m_jvmBits = Integer.getInteger( "sun.arch.data.model", -1 
>>>> ).intValue();
>>>>    Note that the property does not exist on all JVMs.
>>>>
>>>> Cheers,
>>>> Leif
>>>>
>>>> Richard Emberson wrote:
>>>>> I have to support solaris, linux and windows on
>>>>> 32 and 64 bit machines.
>>>>> The wrapper executable and native library comes in
>>>>> 32 and 64 bit versions for those OSs.
>>>>> What I need is the ability during an installation
>>>>> to know what the machine (the hardware) architecture
>>>>> is, 32 or 64 bit. I need to be able to know this
>>>>> from within a java process (actually an Ant task).
>>>>> I discovered today on my 64 bit workstation that if
>>>>> I run java 1.4.x, a 32 bit java, then the system
>>>>> property os.arch has the value i386 but if I run java
>>>>> 1.5.x the os.arch has the value amd64 --- os.arch
>>>>> does not give the hardware architecture but rather
>>>>> the java vm architecture. In order to install the
>>>>> correct version of the wrapper executable and
>>>>> native libaray I need the true hardware architecture
>>>>> independent of what jvm I will be running.
>>>>> Any thoughts as to how to get this information
>>>>> using just java?
>>>>>
>>>>> Richard
>>>>>
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------
>>>> Using Tomcat but need to do more? Need to support web services, 
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make your 
>>>> job easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>>> Geronimo
>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 
>>>>
>>>> _______________________________________________
>>>> Wrapper-user mailing list
>>>> Wra...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>>
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, 
>> security?
>> Get stuff done quickly with pre-integrated technology to make your 
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
>

Re: [Wrapper-user] getting hardware arch using just java

[Richard E. <rem...@ed...>]

Leif,

The native libraries are one of the issues. On a 64 bit machine if
I install the 64 bit wrapper and libwrapper.so can I run a 32 bit
jvm or must I run a 64 bit jvm?
Thanks.

Richard


Leif Mortenson wrote:
> Richard,
>    Oh.  To do that you are going to need to use Runtime.exec to
> run "uname -a" or some variant.  Note that if you are worried about
> native libraries within Java though, it is the bit depth of the JVM, not
> that of the hardware that is going to matter to you.
> 
> Cheers,
> Leif
> 
> Richard Emberson wrote:
>> On my 64 linux workstation when I run java 1.4.2_11,
>> a 32 bit version of Java, sun.arch.data.model == 32;
>> but when I run java 1.5.0_06 amd64, a 64 bit version
>> of Java, sun.arch.data.model == 64.
>> I was not clear. I wish to know the underlying
>> hardware machine bits, 32 or 64, if possible from
>> within java.
>>
>> Richard
>>
>> Leif Mortenson wrote:
>>> Richard,
>>>    Download the source distribution and take a look at the build.xml 
>>> in the root
>>> directory.  It does exactly this.   If you want to see an example of 
>>> it being done
>>> in Java, then take a look at the source of the WrapperManager class 
>>> in the
>>> generateDetailedNativeLibraryBaseName method.  The JVM bits are accessed
>>> as follows:
>>>        m_jvmBits = Integer.getInteger( "sun.arch.data.model", -1 
>>> ).intValue();
>>>    Note that the property does not exist on all JVMs.
>>>
>>> Cheers,
>>> Leif
>>>
>>> Richard Emberson wrote:
>>>> I have to support solaris, linux and windows on
>>>> 32 and 64 bit machines.
>>>> The wrapper executable and native library comes in
>>>> 32 and 64 bit versions for those OSs.
>>>> What I need is the ability during an installation
>>>> to know what the machine (the hardware) architecture
>>>> is, 32 or 64 bit. I need to be able to know this
>>>> from within a java process (actually an Ant task).
>>>> I discovered today on my 64 bit workstation that if
>>>> I run java 1.4.x, a 32 bit java, then the system
>>>> property os.arch has the value i386 but if I run java
>>>> 1.5.x the os.arch has the value amd64 --- os.arch
>>>> does not give the hardware architecture but rather
>>>> the java vm architecture. In order to install the
>>>> correct version of the wrapper executable and
>>>> native libaray I need the true hardware architecture
>>>> independent of what jvm I will be running.
>>>> Any thoughts as to how to get this information
>>>> using just java?
>>>>
>>>> Richard
>>>>
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services, 
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your 
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> Wrapper-user mailing list
>>> Wra...@li...
>>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>>
>>
>>
> 
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


-- 
This email message is for the sole use of the intended recipient(s) and
may contain confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.

Re: [Wrapper-user] getting hardware arch using just java

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

Richard,
    Oh.  To do that you are going to need to use Runtime.exec to
run "uname -a" or some variant.  Note that if you are worried about
native libraries within Java though, it is the bit depth of the JVM, not
that of the hardware that is going to matter to you.

Cheers,
Leif

Richard Emberson wrote:
> On my 64 linux workstation when I run java 1.4.2_11,
> a 32 bit version of Java, sun.arch.data.model == 32;
> but when I run java 1.5.0_06 amd64, a 64 bit version
> of Java, sun.arch.data.model == 64.
> I was not clear. I wish to know the underlying
> hardware machine bits, 32 or 64, if possible from
> within java.
>
> Richard
>
> Leif Mortenson wrote:
>> Richard,
>>    Download the source distribution and take a look at the build.xml 
>> in the root
>> directory.  It does exactly this.   If you want to see an example of 
>> it being done
>> in Java, then take a look at the source of the WrapperManager class 
>> in the
>> generateDetailedNativeLibraryBaseName method.  The JVM bits are accessed
>> as follows:
>>        m_jvmBits = Integer.getInteger( "sun.arch.data.model", -1 
>> ).intValue();
>>    Note that the property does not exist on all JVMs.
>>
>> Cheers,
>> Leif
>>
>> Richard Emberson wrote:
>>> I have to support solaris, linux and windows on
>>> 32 and 64 bit machines.
>>> The wrapper executable and native library comes in
>>> 32 and 64 bit versions for those OSs.
>>> What I need is the ability during an installation
>>> to know what the machine (the hardware) architecture
>>> is, 32 or 64 bit. I need to be able to know this
>>> from within a java process (actually an Ant task).
>>> I discovered today on my 64 bit workstation that if
>>> I run java 1.4.x, a 32 bit java, then the system
>>> property os.arch has the value i386 but if I run java
>>> 1.5.x the os.arch has the value amd64 --- os.arch
>>> does not give the hardware architecture but rather
>>> the java vm architecture. In order to install the
>>> correct version of the wrapper executable and
>>> native libaray I need the true hardware architecture
>>> independent of what jvm I will be running.
>>> Any thoughts as to how to get this information
>>> using just java?
>>>
>>> Richard
>>>
>>
>>
>>
>> -------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, 
>> security?
>> Get stuff done quickly with pre-integrated technology to make your 
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> Wrapper-user mailing list
>> Wra...@li...
>> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>
>

Re: [Wrapper-user] getting hardware arch using just java

[Richard E. <rem...@ed...>]

On my 64 linux workstation when I run java 1.4.2_11,
a 32 bit version of Java, sun.arch.data.model == 32;
but when I run java 1.5.0_06 amd64, a 64 bit version
of Java, sun.arch.data.model == 64.
I was not clear. I wish to know the underlying
hardware machine bits, 32 or 64, if possible from
within java.

Richard

Leif Mortenson wrote:
> Richard,
>    Download the source distribution and take a look at the build.xml in 
> the root
> directory.  It does exactly this.   If you want to see an example of it 
> being done
> in Java, then take a look at the source of the WrapperManager class in the
> generateDetailedNativeLibraryBaseName method.  The JVM bits are accessed
> as follows:
>        m_jvmBits = Integer.getInteger( "sun.arch.data.model", -1 
> ).intValue();
>    Note that the property does not exist on all JVMs.
> 
> Cheers,
> Leif
> 
> Richard Emberson wrote:
>> I have to support solaris, linux and windows on
>> 32 and 64 bit machines.
>> The wrapper executable and native library comes in
>> 32 and 64 bit versions for those OSs.
>> What I need is the ability during an installation
>> to know what the machine (the hardware) architecture
>> is, 32 or 64 bit. I need to be able to know this
>> from within a java process (actually an Ant task).
>> I discovered today on my 64 bit workstation that if
>> I run java 1.4.x, a 32 bit java, then the system
>> property os.arch has the value i386 but if I run java
>> 1.5.x the os.arch has the value amd64 --- os.arch
>> does not give the hardware architecture but rather
>> the java vm architecture. In order to install the
>> correct version of the wrapper executable and
>> native libaray I need the true hardware architecture
>> independent of what jvm I will be running.
>> Any thoughts as to how to get this information
>> using just java?
>>
>> Richard
>>
> 
> 
> 
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
> 


-- 
This email message is for the sole use of the intended recipient(s) and
may contain confidential information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply email and destroy all
copies of the original message.

Re: [Wrapper-user] getting hardware arch using just java

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

Richard,
    Download the source distribution and take a look at the build.xml in 
the root
directory.  It does exactly this.   If you want to see an example of it 
being done
in Java, then take a look at the source of the WrapperManager class in the
generateDetailedNativeLibraryBaseName method.  The JVM bits are accessed
as follows:
        m_jvmBits = Integer.getInteger( "sun.arch.data.model", -1 
).intValue();
    Note that the property does not exist on all JVMs.

Cheers,
Leif

Richard Emberson wrote:
> I have to support solaris, linux and windows on
> 32 and 64 bit machines.
> The wrapper executable and native library comes in
> 32 and 64 bit versions for those OSs.
> What I need is the ability during an installation
> to know what the machine (the hardware) architecture
> is, 32 or 64 bit. I need to be able to know this
> from within a java process (actually an Ant task).
> I discovered today on my 64 bit workstation that if
> I run java 1.4.x, a 32 bit java, then the system
> property os.arch has the value i386 but if I run java
> 1.5.x the os.arch has the value amd64 --- os.arch
> does not give the hardware architecture but rather
> the java vm architecture. In order to install the
> correct version of the wrapper executable and
> native libaray I need the true hardware architecture
> independent of what jvm I will be running.
> Any thoughts as to how to get this information
> using just java?
>
> Richard
>