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

[Wrapper-user] Issues with WebSphere ASS 4.0.x Windows Service terminating

[<IPi...@Xe...>]

Hi,
 
Hopefully this isn't a duplicate.
 
I have WebSphere Advanced Single Server Edition 4.0.x installed on Windows
2000 Server. I've set-up Wrapper to stop and start the server using
WrapperStartStopApp and I am able to start and stop successfully. However,
when I start-up the server and the start-up of WebSphere is complete, the
shutdown sequence begins.
 
My thoughts are that the start-up script for WebSphere starts WebSphere as a
server and then the JVM that created the server exits. This may then trigger
the shutdown sequence. I also wonder if the fact that I'm using the IBM JDK
1.3 has any bearing on the situation. Has anyone any experience of using
Wrapper for WebSphere?
 
I have also configured WrapperSimpleApp to work, which is successful, but
the wrapper terminates after a successful start-up, which means that the
although WebSphere runs it doesn't show as a started application in Windows
Services. This is acceptable for now, but if we ever run monitoring software
that looks for the status of services it will report a false negative.
 
Cheers,
 
Ian
 
Here's my configuration file:
 
#********************************************************************
# Wrapper Properties
#********************************************************************
# Java Application
wrapper.java.command=C:\appserver\WebSphere\AppServer\java\bin\java
 
# Java Main class.  This class must implement the WrapperListener interface
#  or guarantee that the WrapperManager class is initialized.  Helper
#  classes are provided to do this for you.  See the Integration section
#  of the documentation for details.
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp
 
# Java Classpath (include wrapper.jar)  Add class path elements as
#  needed starting from 1
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=c:\appserver\WebSphere\AppServer\properties
wrapper.java.classpath.3=c:\appserver\WebSphere\AppServer\lib\bootstrap.jar
 
# Java Library Path (location of Wrapper.DLL or libwrapper.so)
wrapper.java.library.path.1=../lib
wrapper.java.library.path.2=.
 
# Java Additional Parameters
wrapper.java.additional.1=-Dws.output.encoding=console 
wrapper.java.additional.2=-Dserver.root=c:\appserver\WebSphere\AppServer  
wrapper.java.additional.3=-Dws.def.olt.host=localhost 
wrapper.java.additional.4=-Dws.def.olt.port=2102 
wrapper.java.additional.5=-Dws.def.jdwp.port=7777 
wrapper.java.additional.6=-Dws.ext.dirs=c:\appserver\WebSphere\AppServer\jav
a\lib;c:\appserver\WebSphere\AppServer\classes;c:\appserver\WebSphere\AppSer
ver\lib;c:\appserver\WebSphere\AppServer\lib\ext;c:\appserver\WebSphere\AppS
erver\web\help;
wrapper.java.additional.7=-Dcom.ibm.CORBA.ConfigURL=file:/c:/appserver/WebSp
here/AppServer/properties/sas.server.props
 
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=3
 
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=64
 
# Application parameters.  Add parameters as needed starting from 1
 
# The first application parameter is the name of the class whose main
# method is to be called when the application is launched.  The class
# name is followed by the number of parameters to be passed to its main
# method.  Then comes the actual parameters.
wrapper.app.parameter.1=com.ibm.ws.bootstrap.WSLauncher
wrapper.app.parameter.2=1
wrapper.app.parameter.3=com.ibm.websphere.install.commands.ProcessLauncherTe
st
 
# The start parameters are followed by the name of the class whose main
# method is to be called to stop the application.  The stop class name
# is followed by a flag which controls whether or not the Wrapper should
# wait for all non daemon threads to complete before exiting the JVM.
# The flag is followed by the number of parameters to be passed to the
# stop class's main method.  Finally comes the actual parameters.
wrapper.app.parameter.4=com.ibm.ws.bootstrap.WSLauncher
wrapper.app.parameter.5=true
wrapper.app.parameter.6=4
wrapper.app.parameter.7=com.ibm.ejs.sm.util.debug.DrAdmin
wrapper.app.parameter.8=-configurationFile
wrapper.app.parameter.9=c:\appserver\WebSphere\AppServer\config\server-cfg.x
ml
wrapper.app.parameter.10=-stopServer
 
#********************************************************************
# 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
wra...@ap...@
 
#********************************************************************
# 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=WebSphere
 
# Display name of the service
wrapper.ntservice.displayname=WebSphere Application Server
 
# Description of the service
wrapper.ntservice.description=WebSphere Application Server service running
under Java Wrapper
 
# 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's my wrapper log:
 
STATUS | wrapper  | 2005/01/26 15:59:30 | --> Wrapper Started as Service
STATUS | wrapper  | 2005/01/26 15:59:31 | Launching a JVM...
INFO   | jvm 1    | 2005/01/26 15:59:31 | 
INFO   | jvm 1    | 2005/01/26 15:59:31 | Wrapper (Version 3.1.2)
http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2005/01/26 15:59:31 | 
INFO   | jvm 1    | 2005/01/26 15:59:32 | 
INFO   | jvm 1    | 2005/01/26 15:59:32 | WebSphere Application Server,
Advanced Single Server Edition V4.0
INFO   | jvm 1    | 2005/01/26 15:59:32 | Application Server Launcher
INFO   | jvm 1    | 2005/01/26 15:59:32 | Copyright (C) IBM Corporation,
2001
INFO   | jvm 1    | 2005/01/26 15:59:32 | 
INFO   | jvm 1    | 2005/01/26 15:59:32 | The configuration file was
defaulted to:
INFO   | jvm 1    | 2005/01/26 15:59:32 |
c:\WebSphere\AppServer\config\server-cfg.xml
INFO   | jvm 1    | 2005/01/26 15:59:32 | Using the single available node or
the localhost node.
INFO   | jvm 1    | 2005/01/26 15:59:32 | Using the single available server.
INFO   | jvm 1    | 2005/01/26 15:59:32 | Initiating server launch.
INFO   | jvm 1    | 2005/01/26 15:59:34 | Loaded domain "WebSphere
Administrative Domain".
INFO   | jvm 1    | 2005/01/26 15:59:34 | Selected node "uklab02".
INFO   | jvm 1    | 2005/01/26 15:59:34 | Selected server "Default Server".
INFO   | jvm 1    | 2005/01/26 15:59:34 | WSPL0065I: Initiated server launch
with process id 2296.
INFO   | jvm 1    | 2005/01/26 15:59:38 | Time mark: 26 January 2005
15:59:38 o'clock GMT
INFO   | jvm 1    | 2005/01/26 15:59:38 | Waiting for the server to be
initialized.
INFO   | jvm 1    | 2005/01/26 15:59:40 | Time mark: 26 January 2005
15:59:40 o'clock GMT
INFO   | jvm 1    | 2005/01/26 15:59:40 | Initialized server.
INFO   | jvm 1    | 2005/01/26 15:59:40 | Waiting for applications to be
started.
INFO   | jvm 1    | 2005/01/26 15:59:56 | Time mark: 26 January 2005
15:59:56 o'clock GMT
INFO   | jvm 1    | 2005/01/26 15:59:56 | Started applications.
INFO   | jvm 1    | 2005/01/26 15:59:56 | WSPL0057I: The server Default
Server is open for e-business.
INFO   | jvm 1    | 2005/01/26 15:59:56 | Please review the server log files
for additional information.
INFO   | jvm 1    | 2005/01/26 15:59:56 | Standard output:
C:\WebSphere\AppServer/logs/default_server_stdout.log
INFO   | jvm 1    | 2005/01/26 15:59:56 | Standard error:
C:\WebSphere\AppServer/logs/default_server_stderr.log
INFO   | jvm 1    | 2005/01/26 15:59:57 | 
INFO   | jvm 1    | 2005/01/26 15:59:57 | WebSphere Application Server,
Advanced Single Server Edition V4.0
INFO   | jvm 1    | 2005/01/26 15:59:57 | WebSphere Application Server,
Advanced Developer Edition V4.0
INFO   | jvm 1    | 2005/01/26 15:59:57 | WebSphere Application Server,
Advanced Edition V4.0
INFO   | jvm 1    | 2005/01/26 15:59:57 | Runtime Utility Program
INFO   | jvm 1    | 2005/01/26 15:59:57 | Copyright (C) IBM Corporation,
1997-2001
INFO   | jvm 1    | 2005/01/26 15:59:57 | 
INFO   | jvm 1    | 2005/01/26 15:59:57 | WSRU0025I: Loading configuration
from file.
INFO   | jvm 1    | 2005/01/26 15:59:57 | WSRU0028I: Using the specified
configuration file:
INFO   | jvm 1    | 2005/01/26 15:59:57 |
c:\WebSphere\AppServer\config\server-cfg.xml
INFO   | jvm 1    | 2005/01/26 15:59:57 | WSRU0029I: The diagnostic host
name read as localhost.
INFO   | jvm 1    | 2005/01/26 15:59:57 | WSRU0030I: The diagnostic port was
read as 7000.
INFO   | jvm 1    | 2005/01/26 15:59:57 | Stopping server.
INFO   | jvm 1    | 2005/01/26 15:59:57 | The server was successfully
stopped.
ERROR  | wrapper  | 2005/01/26 16:00:30 | Shutdown failed: Timed out waiting
for signal from JVM.
ERROR  | wrapper  | 2005/01/26 16:00:30 | JVM did not exit on request,
terminated
STATUS | wrapper  | 2005/01/26 16:00:31 | <-- Wrapper Stopped
 
 
Ian Pilborough
Integration Consultant
 
xenos | the data to e-content company(tm)
Direct: +44 (0) 1932 236 912
Mobile: +44 (0) 7812 193 208
Main: +44 (0) 1932 252 299
Fax: +44 (0) 1932 252 288
Email: mailto:ipi...@xe... <mailto:ipi...@xe...> 
Web: http://www.xenos.com/ <http://www.xenos.com/> 
 
*****************************************************************
For Xenos Helpdesk support contact +44 (0)1932 236900 or e-mail
su...@xe...
*****************************************************************
 

[Wrapper-user] Anchor file mysteriously getting deleted immediately

[John M. <joh...@jb...>]

OK, so I have more information on this and know the problem - it is a
bug that I will write up.

When I press the "start" button on MSWindows's Services GUI, the JBoss
instance starts up fine.

Its only when I issue a wrapper.exe -t will the anchor file come and go
quickly.

Looking at the code, wrapper_win.c lines 2745-2751, I see the anchor
file gets created when -c is used.  Lines  2777-2785 create the anchor
file with -s (this is why pressing the start button in the Windows
Services GUI works).

However, look at the -t - there is no code to write that anchor file.
This is probably intentional - since I think when you start the wrapper,
it ends up starting up with "-s" (in other words, the wrapper process
that starts with -t is a short-lived process - just issues the start
command and exits - it isn't the "true" wrapper so it should not create
the anchor).

However, -t still goes through the same exit routine - which means
appExit() is called (last line in main()).  In appExit(), there is the
unlink to remove the anchor file.

Since -s and -c never return, that appExit() isn't called until the
appropriate time.  However, -t exits immediately and thus deletes the
anchor file (the anchor file is created when the service is started
(with the -s)).

It's a race condition - the -s wrapper service starts, creates the
anchor then the -t process, seeing that the service started, exits.  But
it then immediately deletes the anchor file.

I'll write this up as a bug.  Somehow, there needs to be a global flag
to say, "wrapper.exe is exiting, but don't delete the anchor or pid
files".  And appExit() needs to only delete the files if that flag tells
it to.

Work around is probably to pass in on the command line to wrapper.exe a
bogus setting for anchorfile (one different than the real anchorfile
setting in .conf).  The -t process should try to delete that bogus file
(and fail) leaving the real anchor file alone.

> -----Original Message-----
> From: John Mazzitelli=20
> Sent: Monday, January 24, 2005 10:13 AM
> To: 'wra...@li...'
> Subject: Anchor file mysteriously getting deleted immediately=20
> upon startup
>=20
> [sorry for dup - originally sent this to Help forum; just now=20
> found out that is old and that I should be sending to this=20
> mailing list]
>=20
> I am seeing some weird behavior dealing with the anchorfile.=20
> I have my anchorfile set. And under certain conditions, I=20
> have seen it work. For example, if I start in -c console=20
> mode, it works (anchorfile is created and the JVM will die=20
> when I specifically delete it).=20
> =20
> I can see this work when I install the wrapper as an NT=20
> service BUT ONLY if i start the service using the Windows GUI=20
> utility (the Services GUI from Administration tools). If,=20
> however, I start the Windows service via the -t wrapper=20
> option, the JVM starts up fine, but immediately the=20
> anchorfile gets deleted and the wrapper immediately shuts the=20
> JVM down. It is very weird- I have no idea why or who is=20
> deleting that anchor file - but as soon as it gets created=20
> (no more than a second or two delay) that anchor file gets deleted.=20
> =20
> And this only happens if i start the service using the -t.=20
> Again, if I start the service using the Winows Services GUI,=20
> it all works fine.=20
> =20
> See below for my debug log - note the time stamps and see=20
> that the anchorfile gets deleted rather quickly after startup.=20
> =20
> Has anyone seen this behavior, or more importantly, how to fix it?=20
> =20
> ----=20
> INFO | jvm 1 | 2005/01/22 00:53:38 | 00:53:38,567 INFO=20
> [NamingService] Started jnpPort=3D1099, rmiPort=3D1098,=20
> backlog=3D50, bindAddress=3D/0.0.0.0, Client SocketFactory=3Dnull,=20
> Server=20
> SocketFactory=3Dorg.jboss.net.sockets.DefaultSocketFactory@ad093076=20
> STATUS | wrapper | 2005/01/22 00:53:38 | JBoss [abc-dpl] started.=20
> INFO | jvm 1 | 2005/01/22 00:53:40 | 00:53:40,120 INFO=20
> [Server] JBoss (MX MicroKernel) [4.0.0 (build:=20
> CVSTag=3DJBoss_4_0_0 date=3D200412201046)] Started in 2s:604ms=20
> STATUS | wrapper | 2005/01/22 00:53:41 | Anchor file deleted.=20
> Shutting down.=20
> DEBUG | wrapper | 2005/01/22 00:53:41 | wrapperStopProcess(0) called.=20
> DEBUG | wrapper | 2005/01/22 00:53:41 | Sending stop signal to JVM
>=20
> FWIW: I set wrapper.anchor.poll_interval to something higher=20
> (15 seconds) and it still behaves as I describe in my first=20
> post. If I start with -t, the JVM stays up for 15 seconds,=20
> but the anchor file is gone almost immediately. So, after the=20
> 15 seconds are up, since the file is gone, the JVM is=20
> shutdown. It looks like as soon as the wrapper spits out the=20
> log "wrapper | <my service name> started.", that's when the=20
> anchor file gets deleted.=20
> =20
> Don't know if any of this helps. I looked at the C code but=20
> nothing jumped out at me as to a possible problem. Should I=20
> write this up as a bug or am I missing something obvious?
>=20

[Wrapper-user] Anchor file mysteriously getting deleted immediately upon startup

[John M. <joh...@jb...>]

[sorry for dup - originally sent this to Help forum; just now found out
that is old and that I should be sending to this mailing list]

I am seeing some weird behavior dealing with the anchorfile. I have my
anchorfile set. And under certain conditions, I have seen it work. For
example, if I start in -c console mode, it works (anchorfile is created
and the JVM will die when I specifically delete it).=20
=20
I can see this work when I install the wrapper as an NT service BUT ONLY
if i start the service using the Windows GUI utility (the Services GUI
from Administration tools). If, however, I start the Windows service via
the -t wrapper option, the JVM starts up fine, but immediately the
anchorfile gets deleted and the wrapper immediately shuts the JVM down.
It is very weird- I have no idea why or who is deleting that anchor file
- but as soon as it gets created (no more than a second or two delay)
that anchor file gets deleted.=20
=20
And this only happens if i start the service using the -t. Again, if I
start the service using the Winows Services GUI, it all works fine.=20
=20
See below for my debug log - note the time stamps and see that the
anchorfile gets deleted rather quickly after startup.=20
=20
Has anyone seen this behavior, or more importantly, how to fix it?=20
=20
----=20
INFO | jvm 1 | 2005/01/22 00:53:38 | 00:53:38,567 INFO [NamingService]
Started jnpPort=3D1099, rmiPort=3D1098, backlog=3D50, =
bindAddress=3D/0.0.0.0,
Client SocketFactory=3Dnull, Server
SocketFactory=3Dorg.jboss.net.sockets.DefaultSocketFactory@ad093076=20
STATUS | wrapper | 2005/01/22 00:53:38 | JBoss [abc-dpl] started.=20
INFO | jvm 1 | 2005/01/22 00:53:40 | 00:53:40,120 INFO [Server] JBoss
(MX MicroKernel) [4.0.0 (build: CVSTag=3DJBoss_4_0_0 =
date=3D200412201046)]
Started in 2s:604ms=20
STATUS | wrapper | 2005/01/22 00:53:41 | Anchor file deleted. Shutting
down.=20
DEBUG | wrapper | 2005/01/22 00:53:41 | wrapperStopProcess(0) called.=20
DEBUG | wrapper | 2005/01/22 00:53:41 | Sending stop signal to JVM

FWIW: I set wrapper.anchor.poll_interval to something higher (15
seconds) and it still behaves as I describe in my first post. If I start
with -t, the JVM stays up for 15 seconds, but the anchor file is gone
almost immediately. So, after the 15 seconds are up, since the file is
gone, the JVM is shutdown. It looks like as soon as the wrapper spits
out the log "wrapper | <my service name> started.", that's when the
anchor file gets deleted.=20
=20
Don't know if any of this helps. I looked at the C code but nothing
jumped out at me as to a possible problem. Should I write this up as a
bug or am I missing something obvious?

[Wrapper-user] Long starting up Java process

[Jindong Li <Jin...@so...>]

I have a Java process that takes a few minutes to start up (it has to talk
to a back end server to populate a fair amount of data).  With the
WrapperStartStopApp class, is there any way to specify the startWaitHint and
it will call WrapperManager.signalStarting() method so the Windows service
manager will wait for that period of time?
Also, is there a setting to indicate to WrapperStartStopApp that it should
wait until the main method returns?

Thanks,

Jindong.

#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared 
by NetIQ MailMarshal
#####################################################################################

RE: [Wrapper-user] Error while starting wrapper on HP-UX 64bit

[Venkatesh S. <Ven...@lc...>]

++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please read the disclaimer at the bottom of this e-mail.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Could you be a bit more explicit as to how you started the wrapper and your=
 configuration, i am running the wrapper on HP-Ux64 bit and do not have thi=
s problem.
=20
=20

-----Original Message-----
From: wra...@li... [mailto:wrapper-user-admin@l=
ists.sourceforge.net]On Behalf Of mit...@bo...
Sent: 14 January 2005 18:51
To: wra...@li...
Subject: [Wrapper-user] Error while starting wrapper on HP-UX 64bit



I'm attempting to start version 3.1.2 on HP-UX 11i, 64bit and I'm getting t=
his error:=20

 FATAL  | wrapper  | 2005/01/14 19:31:54 | Unable to create a timer thread:=
 251, Error 0=20


I'm not sure what this error means exactly...any ideas?=20

Mitch=20



**********************************************************************
This email is intended for the named recipient(s) only. Its contents
are  confidential and may only be retained by the named recipient(s)
and may only be copied or  disclosed  with the consent of=20
LCH.Clearnet Limited.   If you are not an intended recipient please
delete this e-mail and notify pos...@lc....

The contents  of this  email are  subject to  contract in all cases,=20
and LCH.Clearnet Limited makes no contractual commitment save where
confirmed by hard copy.  LCH.Clearnet Limited accepts no liability,=20
including liability for negligence, in respect of any statement in=20
this email.

LCH.Clearnet Limited, Registered Office: Aldgate House,=20
33 Aldgate High Street, London EC3N 1EA.    Recognised as a Clearing=20
House under the Financial Services & Markets Act 2000. Reg in England No.25=
932=20
Telephone: +44 20 7426 7000              Internet: http://www.lchclearnet.c=
om
**********************************************************************

[Wrapper-user] Error while starting wrapper on HP-UX 64bit

[<mit...@bo...>]

I'm attempting to start version 3.1.2 on HP-UX 11i, 64bit and I'm getting
this error:

 FATAL  | wrapper  | 2005/01/14 19:31:54 | Unable to create a timer thread:
251, Error 0


I'm not sure what this error means exactly...any ideas?

Mitch

[Wrapper-user] RUN_AS_USER

[<nic...@uk...>]

Hi,

With respect to the RUN_AS_USER variable in the scripts;

1) Would it make sense for this to be obeyed when running with "console"
(so you can test, running with the correct privs)
2) Would it be make sense to also use this when stopping the wrapper? (you
cant kill a process you dont own...)

-Nick




This message and any attachments (the "message") is 
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet 
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised 
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.

BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the 
United Kingdom.
  
BNP Paribas Fund Services UK Limited is authorised and 
regulated by the Financial Services Authority.

Re: [Wrapper-user] Linux wrapper fails to start JVM on reboot

[Eoin C. <eo...@pe...>]

maybe 'java' isn't on the path during startup, but is on the path when 
you log in and start it manually?

try setting the absolute path to the java executable in your 
wrapper.conf to see if this is the problem.

eoin.


Sascha Monteiro wrote:

> Linux wrapper fails to start JVM on reboot, but is successful when 
> started manual!
> This is the log from reboot (in runlevel 3):
> DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning intermediate process...
> DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning daemon process...
> STATUS | wrapper | 2005/01/13 22:29:03 | --> Wrapper Started as Daemon
> DEBUG | wrapper | 2005/01/13 22:29:03 | Using system timer.
> DEBUG | wrapperp | 2005/01/13 22:29:03 | server listening on port 32000.
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[0] : java
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[1] : 
> -Djava.library.path=./lib
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[2] : -classpath
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[3] : 
> ./lib/wrapper.jar:./lib/mail.jar:./lib/activation.jar:./cdrc.jar
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[4] : 
> -Dwrapper.key=5bWn9AdgITKTHYsU
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[5] : -Dwrapper.port=32000
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[6] : -Dwrapper.debug=TRUE
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[7] : 
> -Dwrapper.use_system_time=TRUE
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[8] : 
> -Dwrapper.version=3.1.2
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[9] : 
> -Dwrapper.native_library=wrapper
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[10] : 
> -Dwrapper.service=TRUE
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[11] : 
> -Dwrapper.cpu.timeout=10
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[12] : -Dwrapper.jvmid=1
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[13] : 
> org.tanukisoftware.wrapper.WrapperSimpleApp
> DEBUG | wrapper | 2005/01/13 22:29:03 | Command[14] : 
> com.yourcdr.collector.CdrcD
> STATUS | wrapper | 2005/01/13 22:29:03 | Launching a JVM...
> ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start JVM: No such 
> file or directory (2)
> ERROR | wrapper | 2005/01/13 22:29:03 | Critical error: wait for JVM 
> process failed (No child processes)
> DEBUG | wrapper | 2005/01/13 22:29:03 | JVM process exited with a code 
> of 1, setting the wrapper exit code to 1.
> ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start a JVM
> STATUS | wrapper | 2005/01/13 22:29:03 | <-- Wrapper Stopped
>
> I have put the shell script in my apps directory,
> then an symbolic link in /etc/init.d/
> and have put a link to that in /etc/rc3.d/S98yourcdr
>
> but if I do /etc/rc3.d/S98yourcdr start it works fine!
>
> I looks like the shell script terminates before everything is started, 
> but how can I change it to wait for my app to be started?
> (I am using the WrapperSimpleApp as main class)
>
> thanks a lot!
>
> oh, these are the lines from a manual start:
> DEBUG  | wrapper  | 2005/01/13 22:49:04 | Command[14] : 
> com.yourcdr.collector.CdrcD
> STATUS | wrapper  | 2005/01/13 22:49:04 | Launching a JVM...
> INFO   | jvm 1    | 2005/01/13 22:49:10 | WrapperManager class 
> initialized by thread: main  Using classloader: 
> sun.misc.Launcher$AppClassLoader@7b7072
> INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: JVM #1
> INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Registering 
> shutdown hook
> INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Using wrapper
> INFO   | jvm 1    | 2005/01/13 22:49:10 | Loaded native library: 
> libwrapper.so
>
> _________________________________________________________________
> Play online games with your friends with MSN Messenger 
> http://messenger.msn.nl/
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Linux wrapper fails to start JVM on reboot

[<nic...@uk...>]

>> but if I do /etc/rc3.d/S98yourcdr start it works fine!

Just making sure...

Which dir are you running that script from?
Are you running it from /etc/rc3.d/S98yourcdr ?

-Nick





Internet
sas...@ho...@lists.sourceforge.net - 13/01/2005 10:16


Please respond to wra...@li...

Sent by:    wra...@li...



To:    wrapper-user

cc:


Subject:    [Wrapper-user] Linux wrapper fails to start JVM on reboot


Linux wrapper fails to start JVM on reboot, but is successful when started
manual!
This is the log from reboot (in runlevel 3):
DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning intermediate process...
DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning daemon process...
STATUS | wrapper | 2005/01/13 22:29:03 | --> Wrapper Started as Daemon
DEBUG | wrapper | 2005/01/13 22:29:03 | Using system timer.
DEBUG | wrapperp | 2005/01/13 22:29:03 | server listening on port 32000.
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[0] : java
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[1] :
-Djava.library.path=./lib
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[2] : -classpath
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[3] :
./lib/wrapper.jar:./lib/mail.jar:./lib/activation.jar:./cdrc.jar
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[4] :
-Dwrapper.key=5bWn9AdgITKTHYsU
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[5] : -Dwrapper.port=32000
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[6] : -Dwrapper.debug=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[7] :
-Dwrapper.use_system_time=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[8] :
-Dwrapper.version=3.1.2
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[9] :
-Dwrapper.native_library=wrapper
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[10] :
-Dwrapper.service=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[11] :
-Dwrapper.cpu.timeout=10
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[12] : -Dwrapper.jvmid=1
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[13] :
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[14] :
com.yourcdr.collector.CdrcD
STATUS | wrapper | 2005/01/13 22:29:03 | Launching a JVM...
ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start JVM: No such file
or
directory (2)
ERROR | wrapper | 2005/01/13 22:29:03 | Critical error: wait for JVM
process
failed (No child processes)
DEBUG | wrapper | 2005/01/13 22:29:03 | JVM process exited with a code of
1,
setting the wrapper exit code to 1.
ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start a JVM
STATUS | wrapper | 2005/01/13 22:29:03 | <-- Wrapper Stopped

I have put the shell script in my apps directory,
then an symbolic link in /etc/init.d/
and have put a link to that in /etc/rc3.d/S98yourcdr

but if I do /etc/rc3.d/S98yourcdr start it works fine!

I looks like the shell script terminates before everything is started, but
how can I change it to wait for my app to be started?
(I am using the WrapperSimpleApp as main class)

thanks a lot!

oh, these are the lines from a manual start:
DEBUG  | wrapper  | 2005/01/13 22:49:04 | Command[14] :
com.yourcdr.collector.CdrcD
STATUS | wrapper  | 2005/01/13 22:49:04 | Launching a JVM...
INFO   | jvm 1    | 2005/01/13 22:49:10 | WrapperManager class initialized
by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@7b7072
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Registering
shutdown hook
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2005/01/13 22:49:10 | Loaded native library:
libwrapper.so

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Wrapper-user mailing list
Wra...@li...
 https://lists.sourceforge.net/lists/listinfo/wrapper-user



This message and any attachments (the "message") is 
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet 
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 

**********************************************************************************************

BNP Paribas Private Bank London Branch is authorised 
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the
United Kingdom.

BNP Paribas Securities Services London Branch is authorised
by CECEI & AMF and is regulated by the Financial Services
Authority for the conduct of its investment business in the 
United Kingdom.
  
BNP Paribas Fund Services UK Limited is authorised and 
regulated by the Financial Services Authority.

[Wrapper-user] Linux wrapper fails to start JVM on reboot

[Sascha M. <sas...@ho...>]

Linux wrapper fails to start JVM on reboot, but is successful when started 
manual!
This is the log from reboot (in runlevel 3):
DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning intermediate process...
DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning daemon process...
STATUS | wrapper | 2005/01/13 22:29:03 | --> Wrapper Started as Daemon
DEBUG | wrapper | 2005/01/13 22:29:03 | Using system timer.
DEBUG | wrapperp | 2005/01/13 22:29:03 | server listening on port 32000.
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[0] : java
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[1] : 
-Djava.library.path=./lib
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[2] : -classpath
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[3] : 
./lib/wrapper.jar:./lib/mail.jar:./lib/activation.jar:./cdrc.jar
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[4] : 
-Dwrapper.key=5bWn9AdgITKTHYsU
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[5] : -Dwrapper.port=32000
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[6] : -Dwrapper.debug=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[7] : 
-Dwrapper.use_system_time=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[8] : -Dwrapper.version=3.1.2
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[9] : 
-Dwrapper.native_library=wrapper
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[10] : -Dwrapper.service=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[11] : 
-Dwrapper.cpu.timeout=10
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[12] : -Dwrapper.jvmid=1
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[13] : 
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[14] : 
com.yourcdr.collector.CdrcD
STATUS | wrapper | 2005/01/13 22:29:03 | Launching a JVM...
ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start JVM: No such file or 
directory (2)
ERROR | wrapper | 2005/01/13 22:29:03 | Critical error: wait for JVM process 
failed (No child processes)
DEBUG | wrapper | 2005/01/13 22:29:03 | JVM process exited with a code of 1, 
setting the wrapper exit code to 1.
ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start a JVM
STATUS | wrapper | 2005/01/13 22:29:03 | <-- Wrapper Stopped

I have put the shell script in my apps directory,
then an symbolic link in /etc/init.d/
and have put a link to that in /etc/rc3.d/S98yourcdr

but if I do /etc/rc3.d/S98yourcdr start it works fine!

I looks like the shell script terminates before everything is started, but 
how can I change it to wait for my app to be started?
(I am using the WrapperSimpleApp as main class)

thanks a lot!

oh, these are the lines from a manual start:
DEBUG  | wrapper  | 2005/01/13 22:49:04 | Command[14] : 
com.yourcdr.collector.CdrcD
STATUS | wrapper  | 2005/01/13 22:49:04 | Launching a JVM...
INFO   | jvm 1    | 2005/01/13 22:49:10 | WrapperManager class initialized 
by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@7b7072
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Registering 
shutdown hook
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2005/01/13 22:49:10 | Loaded native library: 
libwrapper.so

_________________________________________________________________
Play online games with your friends with MSN Messenger 
http://messenger.msn.nl/

[Wrapper-user] Linux wrapper fails to start JVM on reboot

[Sascha M. <sas...@ho...>]

Linux wrapper fails to start JVM on reboot, but is successful when started 
manual!
This is the log from reboot (in runlevel 3):
DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning intermediate process...
DEBUG | wrapper | 2005/01/13 22:29:03 | Spawning daemon process...
STATUS | wrapper | 2005/01/13 22:29:03 | --> Wrapper Started as Daemon
DEBUG | wrapper | 2005/01/13 22:29:03 | Using system timer.
DEBUG | wrapperp | 2005/01/13 22:29:03 | server listening on port 32000.
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[0] : java
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[1] : 
-Djava.library.path=./lib
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[2] : -classpath
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[3] : 
./lib/wrapper.jar:./lib/mail.jar:./lib/activation.jar:./cdrc.jar
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[4] : 
-Dwrapper.key=5bWn9AdgITKTHYsU
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[5] : -Dwrapper.port=32000
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[6] : -Dwrapper.debug=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[7] : 
-Dwrapper.use_system_time=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[8] : -Dwrapper.version=3.1.2
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[9] : 
-Dwrapper.native_library=wrapper
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[10] : -Dwrapper.service=TRUE
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[11] : 
-Dwrapper.cpu.timeout=10
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[12] : -Dwrapper.jvmid=1
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[13] : 
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG | wrapper | 2005/01/13 22:29:03 | Command[14] : 
com.yourcdr.collector.CdrcD
STATUS | wrapper | 2005/01/13 22:29:03 | Launching a JVM...
ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start JVM: No such file or 
directory (2)
ERROR | wrapper | 2005/01/13 22:29:03 | Critical error: wait for JVM process 
failed (No child processes)
DEBUG | wrapper | 2005/01/13 22:29:03 | JVM process exited with a code of 1, 
setting the wrapper exit code to 1.
ERROR | wrapper | 2005/01/13 22:29:03 | Unable to start a JVM
STATUS | wrapper | 2005/01/13 22:29:03 | <-- Wrapper Stopped

I have put the shell script in my apps directory,
then an symbolic link in /etc/init.d/
and have put a link to that in /etc/rc3.d/S98yourcdr

but if I do /etc/rc3.d/S98yourcdr start it works fine!

I looks like the shell script terminates before everything is started, but 
how can I change it to wait for my app to be started?
(I am using the WrapperSimpleApp as main class)

thanks a lot!

oh, these are the lines from a manual start:
DEBUG  | wrapper  | 2005/01/13 22:49:04 | Command[14] : 
com.yourcdr.collector.CdrcD
STATUS | wrapper  | 2005/01/13 22:49:04 | Launching a JVM...
INFO   | jvm 1    | 2005/01/13 22:49:10 | WrapperManager class initialized 
by thread: main  Using classloader: sun.misc.Launcher$AppClassLoader@7b7072
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: JVM #1
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Registering 
shutdown hook
INFO   | jvm 1    | 2005/01/13 22:49:10 | Wrapper Manager: Using wrapper
INFO   | jvm 1    | 2005/01/13 22:49:10 | Loaded native library: 
libwrapper.so

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

[Wrapper-user] Error Dialog in Win2K Services Applet

[Justo C. <jca...@cf...>]

Hi,
=20
I am using version 3.1.2 of the wrapper. Whenever I right-click on my
service on the Win2K services applet and click on the "properties" menu
item, I get this error in a popup window:
=20
    Microsoft Management Console
    Configuration Manager: a general internal error occured
=20
Afterward the service properties dialog appears and everything works
fine. There is no output in wrapper.log to coincide with this error
message. There are also no corresponding messages in the Win2K Event
Viewer. Any ideas, anyone ? Is the error harmless (it appears to be...)
?
=20
Thanks,
=20
Justo M. Casablanca

[Wrapper-user] Wait until JBoss finished

[Guofeng Z. <gu...@ra...>]

Hi,

=20

We use Method 1 to install JBoss as a Windows service.

=20

When I start the service from Windows' Services window, the status of
the service in the Services window displayed "Started", I cannot access
my web application this time because JBoss has not finished to deploy my
web application.

=20

Could let the Wrapper do not return the control to Windows' service
window until JBoss has finished to deploy my web application, so that
when I see the "Started" status, I can access my web application
immediately.

=20

Thank you very much.

=20

Guofeng

=20

[Wrapper-user] RE: Problem running as a service, but ok in the console

[Huang, Y. (M. R. Interface) <yuf...@ml...>]

Leif,

Thank you. It works after I set wrapper.ntservice.account/password,
assign Log on as a service and Create global objects from system's Local
Policies' User Rights Assignment.

Yufu

-----Original Message-----
From: Leif Mortenson [mailto:le...@ta...]=20
Sent: Friday, December 31, 2004 8:23 PM
To: Huang, Yufu (MLCI Real Interface); Wrapper User List
Subject: Re: Problem running as a service, but ok in the console

Huang,
    Probable just a mistake, but please send messages to the list rather

than the
admin address.  wra...@li...

    Looking over the log below, it looks like you are getting a class=20
not found
exception when running as an NT service.

    It was working correctly when running as a Console app.  But you had
shut it down by pressing CTRL-C 5-6 times.  This tells the Wrapper that
you
don't want to wait for the JVM to shutdown cleanly, thus the Wrapper=20
correctly
killed the JVM process immediately.

    Next, there is no log, but you said that copying the generated java=20
command to
a batch file and then running that works correctly.

    When running in the console either under the Wrapper or in a batch=20
file, the
JVM is run using the current user that you are logged in as.   When=20
running as
a Service however, the Wrapper and its JVM will by default run as the
SYSTEM
user.   This can be changed using the wrapper.ntservice.account=20
property, but
it does not look like you are doing so.

    In your case, the Wrapper is finding the wrapper's classes and your=20
mail class
com.realinterface.wef.WEF with no problems.  But it is failing to find
com.realinterface.extraction.RecordSetCache.  Do you know what jar file=20
that class
is located in?  I am guessing .\lib\commons-realinterface-1.0.jar  The=20
generated
classpaths for the service and console are both identical, which is
correct.
    Because of the way this is failing, my first guess would be a file=20
permission problem.
Your account can read that jar, but the SYSTEM user is not able to.  =20
usually when I
have seen this problem it is a whole directory that is misconfigured and

not just a single
jar file however.

    Because of the package names, I am wondering if=20
com.realinterface.wef.WEF and
com.realinterface.extraction.RecordSetCache are in the same jar?  If=20
that is the case
then the real source of the problem is most likely a super class of
com.realinterface.extraction.RecordSetCache which can not be found. =20
Java can
sometimes be confusing in cases like that.

    I may have missed something else in that log.  All the extra=20
wrapping and inserted
tokens made it a bit difficult to read :-)

Cheers,
Leif

Huang, Yufu (MLCI Real Interface) wrote:

>Hi,
>
>Happy New Year!
>The log file when running as a service is as the following. If I copy
>the command to a batch file and delete
>'-Dwrapper.key=3D3D3D"JBTFY1DZk2Bq_MEW"', then it works ok in the
console.
>Any help? Thanks a lot.
>
>
>Yufu
> =20
>
>>>=3D20
>>>STATUS | wrapper  | 2004/12/31 14:53:58 | --> Wrapper Started as
>>>     =20
>>>
>>Service
>>   =20
>>
>>>DEBUG  | wrapper  | 2004/12/31 14:53:58 | Using system timer.
>>>DEBUG  | wrapperp | 2004/12/31 14:53:58 | server listening on port
>>>32001.
>>>STATUS | wrapper  | 2004/12/31 14:53:58 | Launching a JVM...
>>>DEBUG  | wrapper  | 2004/12/31 14:53:58 | command:
>>>"C:\j2sdk1.4.2_03\bin\java" -Djava.library.path=3D3D3D".\lib"
>>>     =20
>>>
>-classpath
> =20
>
>".\lib\wrapper.jar;.\PROPERTIES;.\lib\wef-1.0.jar;.\lib\datasources-1.1
.
> =20
>
>jar;.\lib\activation-1.4.jar;.\lib\classes-1.2.jar;.\lib\commons-beanut
i
> =20
>
>ls-1.6.1.jar;.\lib\commons-cli-1.0.jar;.\lib\commons-collections-3.1.ja
r
> =20
>
>;.\lib\commons-dbcp-1.2.1.jar;.\lib\commons-dbutils-1.0.jar;.\lib\commo
n
> =20
>
>s-httpclient-3.0-alpha2.jar;.\lib\commons-lang-2.0.jar;.\lib\commons-lo
g
> =20
>
>ging-1.0.3.jar;.\lib\commons-net-1.2.2.jar;.\lib\commons-pool-1.2.jar;.
\
> =20
>
>lib\commons-realinterface-1.0.jar;.\lib\coroutine4java-1.0.jar;.\lib\j2
e
> =20
>
>e-1.4.jar;.\lib\javadde-1.0.jar;.\lib\jpedal-1.0.jar;.\lib\jtidy-r8.jar
;
> =20
>
>.\lib\junit-3.8.jar;.\lib\jxl-1.0.jar;.\lib\mail-1.4.jar;.\lib\msbase-1
.
> =20
>
>0.jar;.\lib\mssqlserver-1.0.jar;.\lib\msutil-1.0.jar;.\lib\ostermilleru
t
> =20
>
>ils-1.0.jar;C:\j2sdk1.4.2_03\lib\tools.jar;.\lib\poi-2.0-final-20040126
.
> =20
>
>jar;.\lib\weblogic-6.1.jar;.\lib\jbossall-client-4.0.0.jar;.\lib\common
s
> =20
>
>>>-codec-1.3.jar" -Dwrapper.key=3D3D3D"JBTFY1DZk2Bq_MEW" =3D3D
>>>-Dwrapper.port=3D3D3D32001
>>>-Dwrapper.debug=3D3D3D"TRUE" -Dwrapper.use_system_time=3D3D3D"TRUE"
>>>-Dwrapper.version=3D3D3D"3.1.2" =
-Dwrapper.native_library=3D3D3D"wrapper"
>>>-Dwrapper.service=3D3D3D"TRUE" -Dwrapper.cpu.timeout=3D3D3D"10" =3D3D
>>>-Dwrapper.jvmid=3D3D3D1
>>>org.tanukisoftware.wrapper.WrapperSimpleApp
>>>     =20
>>>
>com.realinterface.wef.WEF
> =20
>
>>>-config C:\wef\config\wefconfig.xml
>>>DEBUG  | wrapper  | 2004/12/31 14:53:58 | JVM started
>>>     =20
>>>
>(PID=3D3D3D221312)
> =20
>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperManager class
>>>initialized by thread: main  Using classloader:
>>>sun.misc.Launcher$AppClassLoader@1ff5ea7
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager: JVM #1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager:
>>>     =20
>>>
>Registering
> =20
>
>>>shutdown hook
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager: Using
>>>     =20
>>>
>>wrapper
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Loaded native library:
>>>wrapper.dll
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Calling native
>>>     =20
>>>
>>initialization
>>   =20
>>
>>>method.
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Initializing
>>>     =20
>>>
>WrapperManager
> =20
>
>>>native library.
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Java Executable:
>>>C:\j2sdk1.4.2_03\bin\java.exe
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Windows version: 5.2.3790
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Java Version   :
>>>     =20
>>>
>>1.4.2_03-b02
>>   =20
>>
>>>Java HotSpot(TM) Client VM
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Java VM Vendor : Sun
>>>Microsystems Inc.
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |=3D3D20
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper (Version 3.1.2)
>>>http://wrapper.tanukisoftware.org
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |=3D3D20
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |
>>>
>>>     =20
>>>
>WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1430b5
c
> =20
>
>>>, args["-config", "C:\wef\config\wefconfig.xml"]) called by thread:
>>>     =20
>>>
>>main
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Open socket to wrapper...
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Opened Socket
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Send a packet KEY :
>>>JBTFY1DZk2Bq_MEW
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |
>>>=3D
>>>     =20
>>>
>handleSocket(Socket[addr=3D3D3D/127.0.0.1,port=3D3D3D32001,localport=3D3=
D3D48
7
>4=3D
> =20
>
>>])
>>   =20
>>
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | accepted a socket from
>>>127.0.0.1 on port 4874
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | read a packet KEY :
>>>JBTFY1DZk2Bq_MEW
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | Got key from JVM:
>>>JBTFY1DZk2Bq_MEW
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet
>>>     =20
>>>
>LOW_LOG_LEVEL
> =20
>
>>:
>>   =20
>>
>>>1
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet PING_TIMEOUT
>>>     =20
>>>
>:
> =20
>
>>>30
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | Start Application.
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet START :
>>>     =20
>>>
>start
> =20
>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Received a packet
>>>LOW_LOG_LEVEL : 1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager:
>>>     =20
>>>
>LowLogLevel
> =20
>
>>>from Wrapper is 1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Received a packet
>>>     =20
>>>
>>PING_TIMEOUT
>>   =20
>>
>>>: 30
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager:
>>>     =20
>>>
>PingTimeout
> =20
>
>>>from Wrapper is 30000
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Received a packet START :
>>>start
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | calling listener.start()
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp:
>>>     =20
>>>
>>start(args)
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp: invoking
>>>main method
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |=3D3D20
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp:
>>>     =20
>>>
>>Encountered
>>   =20
>>
>>>an error running main: java.lang.NoClassDefFoundError:
>>>com/realinterface/extraction/RecordSetCache
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |
>>>java.lang.NoClassDefFoundError:
>>>com/realinterface/extraction/RecordSetCache
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>com.realinterface.wef.WEF.<init>(WEF.java:18)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>com.realinterface.wef.WEF.main(WEF.java:133)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>
>>>     =20
>>>
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja
v
> =20
>
>>>a:39)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>
>>>     =20
>>>
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso
r
> =20
>
>>>Impl.java:25)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>java.lang.reflect.Method.invoke(Method.java:324)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>
>>>     =20
>>>
>org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:1
3
> =20
>
>>>6)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>java.lang.Thread.run(Thread.java:534)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp:
>>>     =20
>>>
>>start(args)
>>   =20
>>
>>>end.  Main Completed=3D3D3Dtrue, exitCode=3D3D3D1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperManager.stop(1)
>>>     =20
>>>
>>called
>>   =20
>>
>>>by thread: Wrapper-Connection
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Send a packet STOP : 1
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | read a packet STOP : 1
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | JVM requested a shutdown.
>>>     =20
>>>
>>(1)
>>   =20
>>
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | wrapperStopProcess(1)
>>>     =20
>>>
>>called.
>>   =20
>>
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | Sending stop signal to JVM
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet STOP : NULL
>>>INFO   | jvm 1    | 2004/12/31 14:54:00 | Thread,
>>>     =20
>>>
>Wrapper-Connection,
> =20
>
>>>handling the shutdown process.
>>>INFO   | jvm 1    | 2004/12/31 14:54:00 | Send a packet STOPPED : 0
>>>DEBUG  | wrapperp | 2004/12/31 14:54:00 | read a packet STOPPED : 0
>>>DEBUG  | wrapper  | 2004/12/31 14:54:00 | JVM signalled that it was
>>>stopped.
>>>INFO   | jvm 1    | 2004/12/31 14:54:00 | Closing socket.
>>>DEBUG  | wrapperp | 2004/12/31 14:54:00 | socket read no code
>>>     =20
>>>
>>(closed?).
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 14:54:01 | calling System.exit(1)
>>>DEBUG  | wrapper  | 2004/12/31 14:54:01 | JVM process exited with a
>>>     =20
>>>
>>code
>>   =20
>>
>>>of 1, however the wrapper exit code was already 1.
>>>DEBUG  | wrapper  | 2004/12/31 14:54:01 | JVM exited normally.
>>>STATUS | wrapper  | 2004/12/31 14:54:01 | <-- Wrapper Stopped
>>>STATUS | wrapper  | 2004/12/31 15:11:51 | --> Wrapper Started as
>>>     =20
>>>
>>Console
>>   =20
>>
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | Using system timer.
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | server listening on port
>>>32001.
>>>STATUS | wrapper  | 2004/12/31 15:11:51 | Launching a JVM...
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | command:
>>>"C:\j2sdk1.4.2_03\bin\java" -Djava.library.path=3D3D3D".\lib"
>>>     =20
>>>
>-classpath
> =20
>
>".\lib\wrapper.jar;.\PROPERTIES;.\lib\wef-1.0.jar;.\lib\datasources-1.1
.
> =20
>
>jar;.\lib\activation-1.4.jar;.\lib\classes-1.2.jar;.\lib\commons-beanut
i
> =20
>
>ls-1.6.1.jar;.\lib\commons-cli-1.0.jar;.\lib\commons-collections-3.1.ja
r
> =20
>
>;.\lib\commons-dbcp-1.2.1.jar;.\lib\commons-dbutils-1.0.jar;.\lib\commo
n
> =20
>
>s-httpclient-3.0-alpha2.jar;.\lib\commons-lang-2.0.jar;.\lib\commons-lo
g
> =20
>
>ging-1.0.3.jar;.\lib\commons-net-1.2.2.jar;.\lib\commons-pool-1.2.jar;.
\
> =20
>
>lib\commons-realinterface-1.0.jar;.\lib\coroutine4java-1.0.jar;.\lib\j2
e
> =20
>
>e-1.4.jar;.\lib\javadde-1.0.jar;.\lib\jpedal-1.0.jar;.\lib\jtidy-r8.jar
;
> =20
>
>.\lib\junit-3.8.jar;.\lib\jxl-1.0.jar;.\lib\mail-1.4.jar;.\lib\msbase-1
.
> =20
>
>0.jar;.\lib\mssqlserver-1.0.jar;.\lib\msutil-1.0.jar;.\lib\ostermilleru
t
> =20
>
>ils-1.0.jar;C:\j2sdk1.4.2_03\lib\tools.jar;.\lib\poi-2.0-final-20040126
.
> =20
>
>jar;.\lib\weblogic-6.1.jar;.\lib\jbossall-client-4.0.0.jar;.\lib\common
s
> =20
>
>>>-codec-1.3.jar" -Dwrapper.key=3D3D3D"UXP_MXiGv9mWdiV3" =3D3D
>>>-Dwrapper.port=3D3D3D32001
>>>-Dwrapper.debug=3D3D3D"TRUE" -Dwrapper.use_system_time=3D3D3D"TRUE"
>>>-Dwrapper.version=3D3D3D"3.1.2" =
-Dwrapper.native_library=3D3D3D"wrapper"
>>>-Dwrapper.cpu.timeout=3D3D3D"10" -Dwrapper.jvmid=3D3D3D1
>>>org.tanukisoftware.wrapper.WrapperSimpleApp
>>>     =20
>>>
>com.realinterface.wef.WEF
> =20
>
>>>-config C:\wef\config\wefconfig.xml
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | JVM started
>>>     =20
>>>
>(PID=3D3D3D222384)
> =20
>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | WrapperManager class
>>>initialized by thread: main  Using classloader:
>>>sun.misc.Launcher$AppClassLoader@1ff5ea7
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager: JVM #1
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager:
>>>     =20
>>>
>Registering
> =20
>
>>>shutdown hook
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager: Using
>>>     =20
>>>
>>wrapper
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Loaded native library:
>>>wrapper.dll
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Calling native
>>>     =20
>>>
>>initialization
>>   =20
>>
>>>method.
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Initializing
>>>     =20
>>>
>WrapperManager
> =20
>
>>>native library.
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Java Executable:
>>>C:\j2sdk1.4.2_03\bin\java.exe
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Windows version: 5.2.3790
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Java Version   :
>>>     =20
>>>
>>1.4.2_03-b02
>>   =20
>>
>>>Java HotSpot(TM) Client VM
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Java VM Vendor : Sun
>>>Microsystems Inc.
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |=3D3D20
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper (Version 3.1.2)
>>>http://wrapper.tanukisoftware.org
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |=3D3D20
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |
>>>
>>>     =20
>>>
>WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1aaa14
a
> =20
>
>>>, args["-config", "C:\wef\config\wefconfig.xml"]) called by thread:
>>>     =20
>>>
>>main
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Open socket to wrapper...
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Opened Socket
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Send a packet KEY :
>>>UXP_MXiGv9mWdiV3
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |
>>>=3D
>>>     =20
>>>
>handleSocket(Socket[addr=3D3D3D/127.0.0.1,port=3D3D3D32001,localport=3D3=
D3D12
5
>2=3D
> =20
>
>>])
>>   =20
>>
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | accepted a socket from
>>>127.0.0.1 on port 1252
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | read a packet KEY :
>>>UXP_MXiGv9mWdiV3
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | Got key from JVM:
>>>UXP_MXiGv9mWdiV3
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | send a packet
>>>     =20
>>>
>LOW_LOG_LEVEL
> =20
>
>>:
>>   =20
>>
>>>1
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | send a packet PING_TIMEOUT
>>>     =20
>>>
>:
> =20
>
>>>30
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | Start Application.
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | send a packet START :
>>>     =20
>>>
>start
> =20
>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Received a packet
>>>LOW_LOG_LEVEL : 1
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager:
>>>     =20
>>>
>LowLogLevel
> =20
>
>>>from Wrapper is 1
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Received a packet
>>>     =20
>>>
>>PING_TIMEOUT
>>   =20
>>
>>>: 30
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager:
>>>     =20
>>>
>PingTimeout
> =20
>
>>>from Wrapper is 30000
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Received a packet START :
>>>start
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | calling listener.start()
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | WrapperSimpleApp:
>>>     =20
>>>
>>start(args)
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | WrapperSimpleApp: invoking
>>>main method
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Shutting
>>>down.
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | wrapperStopProcess(0)
>>>     =20
>>>
>>called.
>>   =20
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Got Control Signal 0->200
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Handled signal
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Processing control
>>>event(WRAPPER_CTRL_C_EVENT)
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | WrapperSimpleApp:
>>>controlEvent(200) Stopping
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | WrapperManager.stop(0)
>>>     =20
>>>
>>called
>>   =20
>>
>>>by thread: Wrapper-Control-Event-Monitor
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Send a packet STOP : 0
>>>DEBUG  | wrapperp | 2004/12/31 15:11:53 | read a packet STOP : 0
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | JVM requested a shutdown.
>>>     =20
>>>
>>(0)
>>   =20
>>
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | wrapperStopProcess(0)
>>>     =20
>>>
>>called.
>>   =20
>>
>>>(IGNORED)
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | Sending stop signal to JVM
>>>DEBUG  | wrapperp | 2004/12/31 15:11:53 | send a packet STOP : NULL
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Got Control Signal 0->200
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Handled signal
>>>ERROR  | wrapper  | 2004/12/31 15:11:53 | JVM did not exit on
>>>     =20
>>>
>request,
> =20
>
>>>terminated
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>FATAL  | wrapper  | 2004/12/31 15:11:53 | Critical error: wait for
>>>     =20
>>>
>JVM
> =20
>
>>>process failed
>>>=3D20
>>>=3D20
>>>Here is the config file:
>>>=3D20
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Wrapper Properties
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Java Application
>>>wrapper.java.command=3D3D3DC:\j2sdk1.4.2_03\bin\java
>>>=3D20
>>># Java Main class.  This class must implement the WrapperListener
>>>interface
>>>#  or guarantee that the WrapperManager class is initialized.
>>>     =20
>>>
>Helper
> =20
>
>>>#  classes are provided to do this for you.  See the Integration
>>>     =20
>>>
>>section
>>   =20
>>
>>>#  of the documentation for details.
>>>
>>>     =20
>>>
>wrapper.java.mainclass=3D3D3Dorg.tanukisoftware.wrapper.WrapperSimpleApp=

> =20
>
>>>=3D20
>>># Java Classpath (include wrapper.jar)  Add class path elements as
>>>#  needed starting from 1
>>>wrapper.java.classpath.1=3D3D3D.\lib\wrapper.jar
>>>wrapper.java.classpath.2=3D3D3D.\PROPERTIES
>>>wrapper.java.classpath.3=3D3D3D.\lib\wef-1.0.jar
>>>wrapper.java.classpath.4=3D3D3D.\lib\datasources-1.1.jar
>>>wrapper.java.classpath.5=3D3D3D.\lib\activation-1.4.jar
>>>wrapper.java.classpath.6=3D3D3D.\lib\classes-1.2.jar
>>>wrapper.java.classpath.7=3D3D3D.\lib\commons-beanutils-1.6.1.jar
>>>wrapper.java.classpath.8=3D3D3D.\lib\commons-cli-1.0.jar
>>>wrapper.java.classpath.9=3D3D3D.\lib\commons-collections-3.1.jar
>>>wrapper.java.classpath.10=3D3D3D.\lib\commons-dbcp-1.2.1.jar
>>>wrapper.java.classpath.11=3D3D3D.\lib\commons-dbutils-1.0.jar
>>>
>>>     =20
>>>
>wrapper.java.classpath.12=3D3D3D.\lib\commons-httpclient-3.0-alpha2.jar
> =20
>
>>>wrapper.java.classpath.13=3D3D3D.\lib\commons-lang-2.0.jar
>>>wrapper.java.classpath.14=3D3D3D.\lib\commons-logging-1.0.3.jar
>>>wrapper.java.classpath.15=3D3D3D.\lib\commons-net-1.2.2.jar
>>>wrapper.java.classpath.16=3D3D3D.\lib\commons-pool-1.2.jar
>>>wrapper.java.classpath.17=3D3D3D.\lib\commons-realinterface-1.0.jar
>>>wrapper.java.classpath.18=3D3D3D.\lib\coroutine4java-1.0.jar
>>>wrapper.java.classpath.19=3D3D3D.\lib\j2ee-1.4.jar
>>>wrapper.java.classpath.20=3D3D3D.\lib\javadde-1.0.jar
>>>wrapper.java.classpath.21=3D3D3D.\lib\jpedal-1.0.jar
>>>wrapper.java.classpath.22=3D3D3D.\lib\jtidy-r8.jar
>>>wrapper.java.classpath.23=3D3D3D.\lib\junit-3.8.jar
>>>wrapper.java.classpath.24=3D3D3D.\lib\jxl-1.0.jar
>>>wrapper.java.classpath.25=3D3D3D.\lib\mail-1.4.jar
>>>wrapper.java.classpath.26=3D3D3D.\lib\msbase-1.0.jar
>>>wrapper.java.classpath.27=3D3D3D.\lib\mssqlserver-1.0.jar
>>>wrapper.java.classpath.28=3D3D3D.\lib\msutil-1.0.jar
>>>wrapper.java.classpath.29=3D3D3D.\lib\ostermillerutils-1.0.jar
>>>wrapper.java.classpath.30=3D3D3DC:\j2sdk1.4.2_03\lib\tools.jar
>>>wrapper.java.classpath.31=3D3D3D.\lib\poi-2.0-final-20040126.jar
>>>wrapper.java.classpath.32=3D3D3D.\lib\weblogic-6.1.jar
>>>wrapper.java.classpath.33=3D3D3D.\lib\jbossall-client-4.0.0.jar
>>>wrapper.java.classpath.34=3D3D3D.\lib\commons-codec-1.3.jar
>>>=3D20
>>># Java Library Path (location of Wrapper.DLL or libwrapper.so)
>>>wrapper.java.library.path.1=3D3D3D.\lib
>>>=3D20
>>># Java Additional Parameters
>>>
>>>     =20
>>>
>#wrapper.java.additional.1=3D3D3D-Djava.util.logging.config.file=3D3D3DC=
:\w
e
>f=3D
> =20
>
>>\pr
>>o=3D3D
>>   =20
>>
>>>per
>>>ties\logging.properties
>>>=3D20
>>># Initial Java Heap Size (in MB)
>>>wrapper.java.initmemory=3D3D3D-ms256m
>>>=3D20
>>># Maximum Java Heap Size (in MB)
>>>wrapper.java.maxmemory=3D3D3D-mx512m
>>>=3D20
>>># Application parameters.  Add parameters as needed starting from 1
>>>wrapper.app.parameter.1=3D3D3Dcom.realinterface.wef.WEF
>>>wrapper.app.parameter.2=3D3D3D-config
>>>wrapper.app.parameter.3=3D3D3DC:\wef\config\wefconfig.xml
>>>=3D20
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Wrapper Logging Properties
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Format of output for the console.  (See docs for formats)
>>>wrapper.console.format=3D3D3DPM
>>>=3D20
>>># Log Level for console output.  (See docs for log levels)
>>>wrapper.console.loglevel=3D3D3DINFO
>>>=3D20
>>># Log file to use for wrapper output logging.
>>>wrapper.logfile=3D3D3D./logs/wrapperwef.log
>>>=3D20
>>># Format of output for the log file.  (See docs for formats)
>>>wrapper.logfile.format=3D3D3DLPTM
>>>=3D20
>>># Log Level for log file output.  (See docs for log levels)
>>>wrapper.logfile.loglevel=3D3D3DINFO
>>>=3D20
>>># 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 =3D3D3D 10 megabytes.
>>>wrapper.logfile.maxsize=3D3D3D0
>>>=3D20
>>># Maximum number of rolled log files which will be allowed before
>>>     =20
>>>
>old
> =20
>
>>>#  files are deleted.  The default value of 0 implies no limit.
>>>wrapper.logfile.maxfiles=3D3D3D0
>>>=3D20
>>># Log Level for sys/event log output.  (See docs for log levels)
>>>wrapper.syslog.loglevel=3D3D3DNONE
>>>=3D20
>>>wrapper.debug=3D3D3Dtrue
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Wrapper Windows Properties
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Title to use when running as a console
>>>wrapper.console.title=3D3D3DWEF
>>>=3D20
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># Wrapper Windows NT/2000/XP Service Properties
>>>
>>>     =20
>>>
>#********************************************************************
> =20
>
>>># WARNING - Do not modify any of these properties when an
>>>     =20
>>>
>application
> =20
>
>>>#  using this configuration file has been installed as a service.
>>>#  Please uninstall the service before modifying this section.  The
>>>#  service can then be reinstalled.
>>>=3D20
>>># Name of the service
>>>wrapper.ntservice.name=3D3D3DWEFApp
>>>=3D20
>>># Display name of the service
>>>wrapper.ntservice.displayname=3D3D3DWEFApp
>>>=3D20
>>># Description of the service
>>>wrapper.ntservice.description=3D3D3DWEF Application
>>>=3D20
>>># Service dependencies.  Add dependencies as needed starting from 1
>>>wrapper.ntservice.dependency.1=3D3D3D
>>>=3D20
>>># Mode in which the service is installed.  AUTO_START or
>>>     =20
>>>
>DEMAND_START
> =20
>
>>>wrapper.ntservice.starttype=3D3D3DAUTO_START
>>>=3D20
>>># Allow the service to interact with the desktop.
>>>wrapper.ntservice.interactive=3D3D3Dfalse
>>>--------------------------------------------------------
>>>=3D20
>>>If you are not an intended recipient of this e-mail, please notify
>>>     =20
>>>
>the
> =20
>
>>=3D3D
>>   =20
>>
>>>sender, delete it and do not read, act upon, print, disclose, copy,
>>>     =20
>>>
>=3D
> =20
>
>>=3D3D
>>   =20
>>
>>>retain or redistribute it. Click here for important additional terms
>>>     =20
>>>
>=3D
> =20
>
>>=3D3D
>>   =20
>>
>>>relating to this e-mail.     http://www.ml.com/email_terms/
>>>--------------------------------------------------------
>>>=3D20
>>>
>>>     =20
>>>
>>--------------------------------------------------------
>>
>>If you are not an intended recipient of this e-mail, please notify the
>>   =20
>>
>=3D
> =20
>
>>sender, delete it and do not read, act upon, print, disclose, copy, =
=3D
>>retain or redistribute it. Click here for important additional terms =
=3D
>>relating to this e-mail.     http://www.ml.com/email_terms/
>>--------------------------------------------------------
>>
>>
>>   =20
>>
>--------------------------------------------------------
>
>If you are not an intended recipient of this e-mail, please notify the
sender, delete it and do not read, act upon, print, disclose, copy,
retain or redistribute it. Click here for important additional terms
relating to this e-mail.     http://www.ml.com/email_terms/
>--------------------------------------------------------
>
>
> =20
>

[Wrapper-user] Re: Problem running as a service, but ok in the console

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

Huang,
    Probable just a mistake, but please send messages to the list rather 
than the
admin address.  wra...@li...

    Looking over the log below, it looks like you are getting a class 
not found
exception when running as an NT service.

    It was working correctly when running as a Console app.  But you had
shut it down by pressing CTRL-C 5-6 times.  This tells the Wrapper that you
don't want to wait for the JVM to shutdown cleanly, thus the Wrapper 
correctly
killed the JVM process immediately.

    Next, there is no log, but you said that copying the generated java 
command to
a batch file and then running that works correctly.

    When running in the console either under the Wrapper or in a batch 
file, the
JVM is run using the current user that you are logged in as.   When 
running as
a Service however, the Wrapper and its JVM will by default run as the SYSTEM
user.   This can be changed using the wrapper.ntservice.account 
property, but
it does not look like you are doing so.

    In your case, the Wrapper is finding the wrapper's classes and your 
mail class
com.realinterface.wef.WEF with no problems.  But it is failing to find
com.realinterface.extraction.RecordSetCache.  Do you know what jar file 
that class
is located in?  I am guessing .\lib\commons-realinterface-1.0.jar  The 
generated
classpaths for the service and console are both identical, which is correct.
    Because of the way this is failing, my first guess would be a file 
permission problem.
Your account can read that jar, but the SYSTEM user is not able to.   
usually when I
have seen this problem it is a whole directory that is misconfigured and 
not just a single
jar file however.

    Because of the package names, I am wondering if 
com.realinterface.wef.WEF and
com.realinterface.extraction.RecordSetCache are in the same jar?  If 
that is the case
then the real source of the problem is most likely a super class of
com.realinterface.extraction.RecordSetCache which can not be found.  
Java can
sometimes be confusing in cases like that.

    I may have missed something else in that log.  All the extra 
wrapping and inserted
tokens made it a bit difficult to read :-)

Cheers,
Leif

Huang, Yufu (MLCI Real Interface) wrote:

>Hi,
>
>Happy New Year!
>The log file when running as a service is as the following. If I copy
>the command to a batch file and delete
>'-Dwrapper.key=3D3D"JBTFY1DZk2Bq_MEW"', then it works ok in the console.
>Any help? Thanks a lot.
>
>
>Yufu
>  
>
>>>=20
>>>STATUS | wrapper  | 2004/12/31 14:53:58 | --> Wrapper Started as
>>>      
>>>
>>Service
>>    
>>
>>>DEBUG  | wrapper  | 2004/12/31 14:53:58 | Using system timer.
>>>DEBUG  | wrapperp | 2004/12/31 14:53:58 | server listening on port
>>>32001.
>>>STATUS | wrapper  | 2004/12/31 14:53:58 | Launching a JVM...
>>>DEBUG  | wrapper  | 2004/12/31 14:53:58 | command:
>>>"C:\j2sdk1.4.2_03\bin\java" -Djava.library.path=3D3D".\lib"
>>>      
>>>
>-classpath
>  
>
>".\lib\wrapper.jar;.\PROPERTIES;.\lib\wef-1.0.jar;.\lib\datasources-1.1.
>  
>
>jar;.\lib\activation-1.4.jar;.\lib\classes-1.2.jar;.\lib\commons-beanuti
>  
>
>ls-1.6.1.jar;.\lib\commons-cli-1.0.jar;.\lib\commons-collections-3.1.jar
>  
>
>;.\lib\commons-dbcp-1.2.1.jar;.\lib\commons-dbutils-1.0.jar;.\lib\common
>  
>
>s-httpclient-3.0-alpha2.jar;.\lib\commons-lang-2.0.jar;.\lib\commons-log
>  
>
>ging-1.0.3.jar;.\lib\commons-net-1.2.2.jar;.\lib\commons-pool-1.2.jar;.\
>  
>
>lib\commons-realinterface-1.0.jar;.\lib\coroutine4java-1.0.jar;.\lib\j2e
>  
>
>e-1.4.jar;.\lib\javadde-1.0.jar;.\lib\jpedal-1.0.jar;.\lib\jtidy-r8.jar;
>  
>
>.\lib\junit-3.8.jar;.\lib\jxl-1.0.jar;.\lib\mail-1.4.jar;.\lib\msbase-1.
>  
>
>0.jar;.\lib\mssqlserver-1.0.jar;.\lib\msutil-1.0.jar;.\lib\ostermillerut
>  
>
>ils-1.0.jar;C:\j2sdk1.4.2_03\lib\tools.jar;.\lib\poi-2.0-final-20040126.
>  
>
>jar;.\lib\weblogic-6.1.jar;.\lib\jbossall-client-4.0.0.jar;.\lib\commons
>  
>
>>>-codec-1.3.jar" -Dwrapper.key=3D3D"JBTFY1DZk2Bq_MEW" =3D
>>>-Dwrapper.port=3D3D32001
>>>-Dwrapper.debug=3D3D"TRUE" -Dwrapper.use_system_time=3D3D"TRUE"
>>>-Dwrapper.version=3D3D"3.1.2" -Dwrapper.native_library=3D3D"wrapper"
>>>-Dwrapper.service=3D3D"TRUE" -Dwrapper.cpu.timeout=3D3D"10" =3D
>>>-Dwrapper.jvmid=3D3D1
>>>org.tanukisoftware.wrapper.WrapperSimpleApp
>>>      
>>>
>com.realinterface.wef.WEF
>  
>
>>>-config C:\wef\config\wefconfig.xml
>>>DEBUG  | wrapper  | 2004/12/31 14:53:58 | JVM started
>>>      
>>>
>(PID=3D3D221312)
>  
>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperManager class
>>>initialized by thread: main  Using classloader:
>>>sun.misc.Launcher$AppClassLoader@1ff5ea7
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager: JVM #1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager:
>>>      
>>>
>Registering
>  
>
>>>shutdown hook
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager: Using
>>>      
>>>
>>wrapper
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Loaded native library:
>>>wrapper.dll
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Calling native
>>>      
>>>
>>initialization
>>    
>>
>>>method.
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Initializing
>>>      
>>>
>WrapperManager
>  
>
>>>native library.
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Java Executable:
>>>C:\j2sdk1.4.2_03\bin\java.exe
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Windows version: 5.2.3790
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Java Version   :
>>>      
>>>
>>1.4.2_03-b02
>>    
>>
>>>Java HotSpot(TM) Client VM
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Java VM Vendor : Sun
>>>Microsystems Inc.
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |=3D20
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper (Version 3.1.2)
>>>http://wrapper.tanukisoftware.org
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |=3D20
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |
>>>
>>>      
>>>
>WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1430b5c
>  
>
>>>, args["-config", "C:\wef\config\wefconfig.xml"]) called by thread:
>>>      
>>>
>>main
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Open socket to wrapper...
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Opened Socket
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Send a packet KEY :
>>>JBTFY1DZk2Bq_MEW
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |
>>>=
>>>      
>>>
>handleSocket(Socket[addr=3D3D/127.0.0.1,port=3D3D32001,localport=3D3D487
>4=
>  
>
>>])
>>    
>>
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | accepted a socket from
>>>127.0.0.1 on port 4874
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | read a packet KEY :
>>>JBTFY1DZk2Bq_MEW
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | Got key from JVM:
>>>JBTFY1DZk2Bq_MEW
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet
>>>      
>>>
>LOW_LOG_LEVEL
>  
>
>>:
>>    
>>
>>>1
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet PING_TIMEOUT
>>>      
>>>
>:
>  
>
>>>30
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | Start Application.
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet START :
>>>      
>>>
>start
>  
>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Received a packet
>>>LOW_LOG_LEVEL : 1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager:
>>>      
>>>
>LowLogLevel
>  
>
>>>from Wrapper is 1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Received a packet
>>>      
>>>
>>PING_TIMEOUT
>>    
>>
>>>: 30
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Wrapper Manager:
>>>      
>>>
>PingTimeout
>  
>
>>>from Wrapper is 30000
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Received a packet START :
>>>start
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | calling listener.start()
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp:
>>>      
>>>
>>start(args)
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp: invoking
>>>main method
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |=3D20
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp:
>>>      
>>>
>>Encountered
>>    
>>
>>>an error running main: java.lang.NoClassDefFoundError:
>>>com/realinterface/extraction/RecordSetCache
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 |
>>>java.lang.NoClassDefFoundError:
>>>com/realinterface/extraction/RecordSetCache
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>com.realinterface.wef.WEF.<init>(WEF.java:18)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>com.realinterface.wef.WEF.main(WEF.java:133)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>
>>>      
>>>
>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
>  
>
>>>a:39)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>
>>>      
>>>
>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
>  
>
>>>Impl.java:25)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>java.lang.reflect.Method.invoke(Method.java:324)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>
>>>      
>>>
>org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:13
>  
>
>>>6)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | 	at
>>>java.lang.Thread.run(Thread.java:534)
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperSimpleApp:
>>>      
>>>
>>start(args)
>>    
>>
>>>end.  Main Completed=3D3Dtrue, exitCode=3D3D1
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | WrapperManager.stop(1)
>>>      
>>>
>>called
>>    
>>
>>>by thread: Wrapper-Connection
>>>INFO   | jvm 1    | 2004/12/31 14:53:59 | Send a packet STOP : 1
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | read a packet STOP : 1
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | JVM requested a shutdown.
>>>      
>>>
>>(1)
>>    
>>
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | wrapperStopProcess(1)
>>>      
>>>
>>called.
>>    
>>
>>>DEBUG  | wrapper  | 2004/12/31 14:53:59 | Sending stop signal to JVM
>>>DEBUG  | wrapperp | 2004/12/31 14:53:59 | send a packet STOP : NULL
>>>INFO   | jvm 1    | 2004/12/31 14:54:00 | Thread,
>>>      
>>>
>Wrapper-Connection,
>  
>
>>>handling the shutdown process.
>>>INFO   | jvm 1    | 2004/12/31 14:54:00 | Send a packet STOPPED : 0
>>>DEBUG  | wrapperp | 2004/12/31 14:54:00 | read a packet STOPPED : 0
>>>DEBUG  | wrapper  | 2004/12/31 14:54:00 | JVM signalled that it was
>>>stopped.
>>>INFO   | jvm 1    | 2004/12/31 14:54:00 | Closing socket.
>>>DEBUG  | wrapperp | 2004/12/31 14:54:00 | socket read no code
>>>      
>>>
>>(closed?).
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 14:54:01 | calling System.exit(1)
>>>DEBUG  | wrapper  | 2004/12/31 14:54:01 | JVM process exited with a
>>>      
>>>
>>code
>>    
>>
>>>of 1, however the wrapper exit code was already 1.
>>>DEBUG  | wrapper  | 2004/12/31 14:54:01 | JVM exited normally.
>>>STATUS | wrapper  | 2004/12/31 14:54:01 | <-- Wrapper Stopped
>>>STATUS | wrapper  | 2004/12/31 15:11:51 | --> Wrapper Started as
>>>      
>>>
>>Console
>>    
>>
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | Using system timer.
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | server listening on port
>>>32001.
>>>STATUS | wrapper  | 2004/12/31 15:11:51 | Launching a JVM...
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | command:
>>>"C:\j2sdk1.4.2_03\bin\java" -Djava.library.path=3D3D".\lib"
>>>      
>>>
>-classpath
>  
>
>".\lib\wrapper.jar;.\PROPERTIES;.\lib\wef-1.0.jar;.\lib\datasources-1.1.
>  
>
>jar;.\lib\activation-1.4.jar;.\lib\classes-1.2.jar;.\lib\commons-beanuti
>  
>
>ls-1.6.1.jar;.\lib\commons-cli-1.0.jar;.\lib\commons-collections-3.1.jar
>  
>
>;.\lib\commons-dbcp-1.2.1.jar;.\lib\commons-dbutils-1.0.jar;.\lib\common
>  
>
>s-httpclient-3.0-alpha2.jar;.\lib\commons-lang-2.0.jar;.\lib\commons-log
>  
>
>ging-1.0.3.jar;.\lib\commons-net-1.2.2.jar;.\lib\commons-pool-1.2.jar;.\
>  
>
>lib\commons-realinterface-1.0.jar;.\lib\coroutine4java-1.0.jar;.\lib\j2e
>  
>
>e-1.4.jar;.\lib\javadde-1.0.jar;.\lib\jpedal-1.0.jar;.\lib\jtidy-r8.jar;
>  
>
>.\lib\junit-3.8.jar;.\lib\jxl-1.0.jar;.\lib\mail-1.4.jar;.\lib\msbase-1.
>  
>
>0.jar;.\lib\mssqlserver-1.0.jar;.\lib\msutil-1.0.jar;.\lib\ostermillerut
>  
>
>ils-1.0.jar;C:\j2sdk1.4.2_03\lib\tools.jar;.\lib\poi-2.0-final-20040126.
>  
>
>jar;.\lib\weblogic-6.1.jar;.\lib\jbossall-client-4.0.0.jar;.\lib\commons
>  
>
>>>-codec-1.3.jar" -Dwrapper.key=3D3D"UXP_MXiGv9mWdiV3" =3D
>>>-Dwrapper.port=3D3D32001
>>>-Dwrapper.debug=3D3D"TRUE" -Dwrapper.use_system_time=3D3D"TRUE"
>>>-Dwrapper.version=3D3D"3.1.2" -Dwrapper.native_library=3D3D"wrapper"
>>>-Dwrapper.cpu.timeout=3D3D"10" -Dwrapper.jvmid=3D3D1
>>>org.tanukisoftware.wrapper.WrapperSimpleApp
>>>      
>>>
>com.realinterface.wef.WEF
>  
>
>>>-config C:\wef\config\wefconfig.xml
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | JVM started
>>>      
>>>
>(PID=3D3D222384)
>  
>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | WrapperManager class
>>>initialized by thread: main  Using classloader:
>>>sun.misc.Launcher$AppClassLoader@1ff5ea7
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager: JVM #1
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager:
>>>      
>>>
>Registering
>  
>
>>>shutdown hook
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager: Using
>>>      
>>>
>>wrapper
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Loaded native library:
>>>wrapper.dll
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Calling native
>>>      
>>>
>>initialization
>>    
>>
>>>method.
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Initializing
>>>      
>>>
>WrapperManager
>  
>
>>>native library.
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Java Executable:
>>>C:\j2sdk1.4.2_03\bin\java.exe
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Windows version: 5.2.3790
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Java Version   :
>>>      
>>>
>>1.4.2_03-b02
>>    
>>
>>>Java HotSpot(TM) Client VM
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Java VM Vendor : Sun
>>>Microsystems Inc.
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |=3D20
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper (Version 3.1.2)
>>>http://wrapper.tanukisoftware.org
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |=3D20
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |
>>>
>>>      
>>>
>WrapperManager.start(org.tanukisoftware.wrapper.WrapperSimpleApp@1aaa14a
>  
>
>>>, args["-config", "C:\wef\config\wefconfig.xml"]) called by thread:
>>>      
>>>
>>main
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Open socket to wrapper...
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Opened Socket
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Send a packet KEY :
>>>UXP_MXiGv9mWdiV3
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 |
>>>=
>>>      
>>>
>handleSocket(Socket[addr=3D3D/127.0.0.1,port=3D3D32001,localport=3D3D125
>2=
>  
>
>>])
>>    
>>
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | accepted a socket from
>>>127.0.0.1 on port 1252
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | read a packet KEY :
>>>UXP_MXiGv9mWdiV3
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | Got key from JVM:
>>>UXP_MXiGv9mWdiV3
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | send a packet
>>>      
>>>
>LOW_LOG_LEVEL
>  
>
>>:
>>    
>>
>>>1
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | send a packet PING_TIMEOUT
>>>      
>>>
>:
>  
>
>>>30
>>>DEBUG  | wrapper  | 2004/12/31 15:11:51 | Start Application.
>>>DEBUG  | wrapperp | 2004/12/31 15:11:51 | send a packet START :
>>>      
>>>
>start
>  
>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Received a packet
>>>LOW_LOG_LEVEL : 1
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager:
>>>      
>>>
>LowLogLevel
>  
>
>>>from Wrapper is 1
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Received a packet
>>>      
>>>
>>PING_TIMEOUT
>>    
>>
>>>: 30
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Wrapper Manager:
>>>      
>>>
>PingTimeout
>  
>
>>>from Wrapper is 30000
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | Received a packet START :
>>>start
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | calling listener.start()
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | WrapperSimpleApp:
>>>      
>>>
>>start(args)
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:51 | WrapperSimpleApp: invoking
>>>main method
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Shutting
>>>down.
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | wrapperStopProcess(0)
>>>      
>>>
>>called.
>>    
>>
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Got Control Signal 0->200
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Handled signal
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Processing control
>>>event(WRAPPER_CTRL_C_EVENT)
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | WrapperSimpleApp:
>>>controlEvent(200) Stopping
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | WrapperManager.stop(0)
>>>      
>>>
>>called
>>    
>>
>>>by thread: Wrapper-Control-Event-Monitor
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Send a packet STOP : 0
>>>DEBUG  | wrapperp | 2004/12/31 15:11:53 | read a packet STOP : 0
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | JVM requested a shutdown.
>>>      
>>>
>>(0)
>>    
>>
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | wrapperStopProcess(0)
>>>      
>>>
>>called.
>>    
>>
>>>(IGNORED)
>>>DEBUG  | wrapper  | 2004/12/31 15:11:53 | Sending stop signal to JVM
>>>DEBUG  | wrapperp | 2004/12/31 15:11:53 | send a packet STOP : NULL
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Got Control Signal 0->200
>>>INFO   | jvm 1    | 2004/12/31 15:11:53 | Handled signal
>>>ERROR  | wrapper  | 2004/12/31 15:11:53 | JVM did not exit on
>>>      
>>>
>request,
>  
>
>>>terminated
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>STATUS | wrapper  | 2004/12/31 15:11:53 | CTRL-C trapped.  Forcing
>>>immediate shutdown.
>>>FATAL  | wrapper  | 2004/12/31 15:11:53 | Critical error: wait for
>>>      
>>>
>JVM
>  
>
>>>process failed
>>>=20
>>>=20
>>>Here is the config file:
>>>=20
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># Wrapper Properties
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># Java Application
>>>wrapper.java.command=3D3DC:\j2sdk1.4.2_03\bin\java
>>>=20
>>># 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=3D3Dorg.tanukisoftware.wrapper.WrapperSimpleApp
>  
>
>>>=20
>>># Java Classpath (include wrapper.jar)  Add class path elements as
>>>#  needed starting from 1
>>>wrapper.java.classpath.1=3D3D.\lib\wrapper.jar
>>>wrapper.java.classpath.2=3D3D.\PROPERTIES
>>>wrapper.java.classpath.3=3D3D.\lib\wef-1.0.jar
>>>wrapper.java.classpath.4=3D3D.\lib\datasources-1.1.jar
>>>wrapper.java.classpath.5=3D3D.\lib\activation-1.4.jar
>>>wrapper.java.classpath.6=3D3D.\lib\classes-1.2.jar
>>>wrapper.java.classpath.7=3D3D.\lib\commons-beanutils-1.6.1.jar
>>>wrapper.java.classpath.8=3D3D.\lib\commons-cli-1.0.jar
>>>wrapper.java.classpath.9=3D3D.\lib\commons-collections-3.1.jar
>>>wrapper.java.classpath.10=3D3D.\lib\commons-dbcp-1.2.1.jar
>>>wrapper.java.classpath.11=3D3D.\lib\commons-dbutils-1.0.jar
>>>
>>>      
>>>
>wrapper.java.classpath.12=3D3D.\lib\commons-httpclient-3.0-alpha2.jar
>  
>
>>>wrapper.java.classpath.13=3D3D.\lib\commons-lang-2.0.jar
>>>wrapper.java.classpath.14=3D3D.\lib\commons-logging-1.0.3.jar
>>>wrapper.java.classpath.15=3D3D.\lib\commons-net-1.2.2.jar
>>>wrapper.java.classpath.16=3D3D.\lib\commons-pool-1.2.jar
>>>wrapper.java.classpath.17=3D3D.\lib\commons-realinterface-1.0.jar
>>>wrapper.java.classpath.18=3D3D.\lib\coroutine4java-1.0.jar
>>>wrapper.java.classpath.19=3D3D.\lib\j2ee-1.4.jar
>>>wrapper.java.classpath.20=3D3D.\lib\javadde-1.0.jar
>>>wrapper.java.classpath.21=3D3D.\lib\jpedal-1.0.jar
>>>wrapper.java.classpath.22=3D3D.\lib\jtidy-r8.jar
>>>wrapper.java.classpath.23=3D3D.\lib\junit-3.8.jar
>>>wrapper.java.classpath.24=3D3D.\lib\jxl-1.0.jar
>>>wrapper.java.classpath.25=3D3D.\lib\mail-1.4.jar
>>>wrapper.java.classpath.26=3D3D.\lib\msbase-1.0.jar
>>>wrapper.java.classpath.27=3D3D.\lib\mssqlserver-1.0.jar
>>>wrapper.java.classpath.28=3D3D.\lib\msutil-1.0.jar
>>>wrapper.java.classpath.29=3D3D.\lib\ostermillerutils-1.0.jar
>>>wrapper.java.classpath.30=3D3DC:\j2sdk1.4.2_03\lib\tools.jar
>>>wrapper.java.classpath.31=3D3D.\lib\poi-2.0-final-20040126.jar
>>>wrapper.java.classpath.32=3D3D.\lib\weblogic-6.1.jar
>>>wrapper.java.classpath.33=3D3D.\lib\jbossall-client-4.0.0.jar
>>>wrapper.java.classpath.34=3D3D.\lib\commons-codec-1.3.jar
>>>=20
>>># Java Library Path (location of Wrapper.DLL or libwrapper.so)
>>>wrapper.java.library.path.1=3D3D.\lib
>>>=20
>>># Java Additional Parameters
>>>
>>>      
>>>
>#wrapper.java.additional.1=3D3D-Djava.util.logging.config.file=3D3DC:\we
>f=
>  
>
>>\pr
>>o=3D
>>    
>>
>>>per
>>>ties\logging.properties
>>>=20
>>># Initial Java Heap Size (in MB)
>>>wrapper.java.initmemory=3D3D-ms256m
>>>=20
>>># Maximum Java Heap Size (in MB)
>>>wrapper.java.maxmemory=3D3D-mx512m
>>>=20
>>># Application parameters.  Add parameters as needed starting from 1
>>>wrapper.app.parameter.1=3D3Dcom.realinterface.wef.WEF
>>>wrapper.app.parameter.2=3D3D-config
>>>wrapper.app.parameter.3=3D3DC:\wef\config\wefconfig.xml
>>>=20
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># Wrapper Logging Properties
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># Format of output for the console.  (See docs for formats)
>>>wrapper.console.format=3D3DPM
>>>=20
>>># Log Level for console output.  (See docs for log levels)
>>>wrapper.console.loglevel=3D3DINFO
>>>=20
>>># Log file to use for wrapper output logging.
>>>wrapper.logfile=3D3D./logs/wrapperwef.log
>>>=20
>>># Format of output for the log file.  (See docs for formats)
>>>wrapper.logfile.format=3D3DLPTM
>>>=20
>>># Log Level for log file output.  (See docs for log levels)
>>>wrapper.logfile.loglevel=3D3DINFO
>>>=20
>>># 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 =3D3D 10 megabytes.
>>>wrapper.logfile.maxsize=3D3D0
>>>=20
>>># 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=3D3D0
>>>=20
>>># Log Level for sys/event log output.  (See docs for log levels)
>>>wrapper.syslog.loglevel=3D3DNONE
>>>=20
>>>wrapper.debug=3D3Dtrue
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># Wrapper Windows Properties
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># Title to use when running as a console
>>>wrapper.console.title=3D3DWEF
>>>=20
>>>
>>>      
>>>
>#********************************************************************
>  
>
>>># 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.
>>>=20
>>># Name of the service
>>>wrapper.ntservice.name=3D3DWEFApp
>>>=20
>>># Display name of the service
>>>wrapper.ntservice.displayname=3D3DWEFApp
>>>=20
>>># Description of the service
>>>wrapper.ntservice.description=3D3DWEF Application
>>>=20
>>># Service dependencies.  Add dependencies as needed starting from 1
>>>wrapper.ntservice.dependency.1=3D3D
>>>=20
>>># Mode in which the service is installed.  AUTO_START or
>>>      
>>>
>DEMAND_START
>  
>
>>>wrapper.ntservice.starttype=3D3DAUTO_START
>>>=20
>>># Allow the service to interact with the desktop.
>>>wrapper.ntservice.interactive=3D3Dfalse
>>>--------------------------------------------------------
>>>=20
>>>If you are not an intended recipient of this e-mail, please notify
>>>      
>>>
>the
>  
>
>>=3D
>>    
>>
>>>sender, delete it and do not read, act upon, print, disclose, copy,
>>>      
>>>
>=
>  
>
>>=3D
>>    
>>
>>>retain or redistribute it. Click here for important additional terms
>>>      
>>>
>=
>  
>
>>=3D
>>    
>>
>>>relating to this e-mail.     http://www.ml.com/email_terms/
>>>--------------------------------------------------------
>>>=20
>>>
>>>      
>>>
>>--------------------------------------------------------
>>
>>If you are not an intended recipient of this e-mail, please notify the
>>    
>>
>=
>  
>
>>sender, delete it and do not read, act upon, print, disclose, copy, =
>>retain or redistribute it. Click here for important additional terms =
>>relating to this e-mail.     http://www.ml.com/email_terms/
>>--------------------------------------------------------
>>
>>
>>    
>>
>--------------------------------------------------------
>
>If you are not an intended recipient of this e-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute it. Click here for important additional terms relating to this e-mail.     http://www.ml.com/email_terms/
>--------------------------------------------------------
>
>
>  
>

[Wrapper-user] Weblogic VM crash in debug mode

[Ori A. <oa...@me...>]

Hi,

I'm seeing a problem when trying to run Weblogic 8.1 in debug mode:

wrapper.java.additional.12=-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5412

 

The VM crashes about 2 out of 3 times we try bringing the server up.

I'm guessing this has to do with some signal that the VM gets but can anyone
be more specific and possible have a workaround?

 

Thanks,

 

Here is the crash info:

 

INFO   | jvm 1    | 2004/12/26 17:45:06 | An unexpected exception has been
detected in native code outside the VM.

INFO   | jvm 1    | 2004/12/26 17:45:06 | Unexpected Signal :
EXCEPTION_ILLEGAL_INSTRUCTION occurred at PC=0x510028

INFO   | jvm 1    | 2004/12/26 17:45:06 | Function=[Unknown.]

INFO   | jvm 1    | 2004/12/26 17:45:06 | Library=(N/A)

INFO   | jvm 1    | 2004/12/26 17:45:06 | 

INFO   | jvm 1    | 2004/12/26 17:45:06 | NOTE: We are unable to locate the
function name symbol for the error

INFO   | jvm 1    | 2004/12/26 17:45:06 |       just occurred. Please refer
to release documentation for possible

INFO   | jvm 1    | 2004/12/26 17:45:06 |       reason and solutions.

INFO   | jvm 1    | 2004/12/26 17:45:06 | 

INFO   | jvm 1    | 2004/12/26 17:45:06 | 

INFO   | jvm 1    | 2004/12/26 17:45:06 | Current Java thread:

INFO   | jvm 1    | 2004/12/26 17:45:06 | 

INFO   | jvm 1    | 2004/12/26 17:45:06 | Dynamic libraries:

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x00400000 - 0x00406000
d:\bea812\jdk141_05\bin\java.exe

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x77F50000 - 0x77FF7000
C:\WINDOWS\System32\ntdll.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x77E60000 - 0x77F46000
C:\WINDOWS\system32\kernel32.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x77DD0000 - 0x77E5D000
C:\WINDOWS\system32\ADVAPI32.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x78000000 - 0x78087000
C:\WINDOWS\system32\RPCRT4.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x77C10000 - 0x77C63000
C:\WINDOWS\system32\MSVCRT.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x6D470000 - 0x6D6E1000
d:\bea812\jdk141_05\jre\bin\server\jvm.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x77D40000 - 0x77DCC000
C:\WINDOWS\system32\USER32.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x7E090000 - 0x7E0D1000
C:\WINDOWS\system32\GDI32.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x76B40000 - 0x76B6C000
C:\WINDOWS\System32\WINMM.dll

INFO   | jvm 1    | 2004/12/26 17:45:06 | 0x76390000 - 0x763AC000
C:\WINDOWS\System32\IMM32.DLL

DEBUG  | wrapper  | 2004/12/26 17:45:07 | Pause reading child output to
share cycles.

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x629C0000 - 0x629C8000
C:\WINDOWS\System32\LPK.DLL

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x72FA0000 - 0x72FFA000
C:\WINDOWS\System32\USP10.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D1E0000 - 0x6D1E7000
d:\bea812\jdk141_05\jre\bin\hpi.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D310000 - 0x6D31E000
d:\bea812\jdk141_05\jre\bin\verify.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D220000 - 0x6D239000
d:\bea812\jdk141_05\jre\bin\java.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D330000 - 0x6D33D000
d:\bea812\jdk141_05\jre\bin\zip.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D270000 - 0x6D28C000
d:\bea812\jdk141_05\jre\bin\jdwp.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D180000 - 0x6D185000
d:\bea812\jdk141_05\jre\bin\dt_socket.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x71AB0000 - 0x71AC4000
C:\WINDOWS\System32\ws2_32.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x71AA0000 - 0x71AA8000
C:\WINDOWS\System32\WS2HELP.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x71A50000 - 0x71A8B000
C:\WINDOWS\system32\mswsock.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x71A90000 - 0x71A98000
C:\WINDOWS\System32\wshtcpip.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x4B070000 - 0x4B07E000
C:\Mercury\MAM-V2.4.1\root\ext\dll\Wrapper.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D2E0000 - 0x6D2EE000
D:\bea812\jdk141_05\jre\bin\net.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x71AD0000 - 0x71AD8000
C:\WINDOWS\System32\WSOCK32.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x76F20000 - 0x76F45000
C:\WINDOWS\System32\DNSAPI.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x76FB0000 - 0x76FB7000
C:\WINDOWS\System32\winrnr.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x76F60000 - 0x76F8C000
C:\WINDOWS\system32\WLDAP32.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x76FC0000 - 0x76FC5000
C:\WINDOWS\System32\rasadhlp.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D2F0000 - 0x6D2F8000
D:\bea812\jdk141_05\jre\bin\nio.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D200000 - 0x6D206000
D:\bea812\jdk141_05\jre\bin\ioser12.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x6D000000 - 0x6D106000
D:\bea812\jdk141_05\jre\bin\awt.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x73000000 - 0x73023000
C:\WINDOWS\System32\WINSPOOL.DRV

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x771B0000 - 0x772D4000
C:\WINDOWS\system32\ole32.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x4FBD0000 - 0x4FBD5000
D:\bea812\weblogic81\server\bin\stackdump.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x4FBE0000 - 0x4FBE5000
D:\bea812\weblogic81\server\bin\wlntio.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x76C90000 - 0x76CB2000
C:\WINDOWS\system32\imagehlp.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x51300000 - 0x5137D000
C:\WINDOWS\system32\DBGHELP.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x77C00000 - 0x77C07000
C:\WINDOWS\system32\VERSION.dll

INFO   | jvm 1    | 2004/12/26 17:45:07 | 0x76BF0000 - 0x76BFB000
C:\WINDOWS\System32\PSAPI.DLL

INFO   | jvm 1    | 2004/12/26 17:45:07 | 

INFO   | jvm 1    | 2004/12/26 17:45:07 | Local Time = Sun Dec 26 17:45:06
2004

INFO   | jvm 1    | 2004/12/26 17:45:07 | Elapsed Time = 266

INFO   | jvm 1    | 2004/12/26 17:45:07 | #

INFO   | jvm 1    | 2004/12/26 17:45:07 | # The exception above was detected
in native code outside the VM

INFO   | jvm 1    | 2004/12/26 17:45:07 | #

INFO   | jvm 1    | 2004/12/26 17:45:07 | # Java VM: Java HotSpot(TM) Server
VM (1.4.1_05-b01 mixed mode)

INFO   | jvm 1    | 2004/12/26 17:45:07 | #

INFO   | jvm 1    | 2004/12/26 17:45:07 | # An error report file has been
saved as hs_err_pid4156.log.

INFO   | jvm 1    | 2004/12/26 17:45:07 | # Please refer to the file for
further information.

INFO   | jvm 1    | 2004/12/26 17:45:07 | #

ERROR  | wrapper  | 2004/12/26 17:45:07 | JVM exited while starting the
application.

DEBUG  | wrapper  | 2004/12/26 17:45:07 | JVM was only running for 268
seconds leading to a failed restart count of 1.



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

[Wrapper-user] Re: Windows 2000 issue

[Salman H. <sal...@ho...>]

<html><div style='background-color:'><DIV class=RTE></DIV>
<DIV>Hey Leif,</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks for the response. </DIV>
<DIV>&nbsp;</DIV>
<DIV>Exact same problem can also be found at:<BR><BR><A href="http://www.codecomments.com/archive250-2004-10-278613.html">http://www.codecomments.com/archive250-2004-10-278613.html</A><BR></DIV>
<DIV>Their fix is a hack but it definately proves that it has something to do with the user account and some security permissions which directly relates to the security patches to Direct X 9.0. I tried their solution and it did work. Additional notes that I made are as follows:</DIV>
<DIV><BR>1) If you launch a Java application through the Wrapper service which has a <BR>frame it will never return from the pack() function as described in the link <BR>above. So you cannot load another Java application through the Wrapper service <BR>which has a frame. However, you can run Java Apps through the Wrapper service <BR>that do not have a GUI. <BR><BR>2) If you launch any application with a frame then other Java apps with frames <BR>wont show. Try loading a service with a frame and then going to Control Panel -<BR>&gt; Java Plug-in. If you stop this service and try to load the plugin again it <BR>will show you a window. In both cases the process javaw.exe does start. <BR><BR>3) When you Start Jetty (which is a webserver with no GUI) as a Wrapper Service&nbsp;then Start another application with a GUI, the same behaviour occurs as described in 2. However, <BR>if you load Jetty 
as a service, load the Web app that loads the JApplet, and <BR>then execute an application with a JFrame as a service, everything will work as <BR>normal. As if the applet loads something in memory that the Frame app is unable <BR>to load while executing through the Wrapper. <BR><BR>I also upgraded from Direct X7.0 to 9.0 and everything seems to work fine now.</DIV>
<DIV>&nbsp;</DIV>
<DIV>The scenario with loading an applet seems strange. But upgrading to Direct X9.0 works so I can live with that</DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanks for your help. </DIV></div></html>

Re: [Wrapper-user] Windows 2000 issue

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

Salman,
I think this might be the following bug:
https://sourceforge.net/tracker/?func=detail&aid=812467&group_id=39428&atid=425187

I need to figure out a way for the Wrapper to test and warn about this. But
it appears to be a DirectX problem. Another user was able to resolve the
problem by upgrading from DirectX 7.0 to 9.0b
Let me know what version of DirectX you are running and then whether or not
upgrading resolves the problem for you.

Cheers,
Leif

Salman Hemani wrote:

> Hi,
>
> I am having an issue using the Wrapper Service on Windows 2000. I have
> been trying to track the problem for 2 days now and I've finally
> pinned down that its something to do with wrapper.
>
> Issue: Other java windows will not render
>
> I downloaded the most recent version of the WS and installed the
> testWrapper as a service. I start this service. Then I go to Control
> Panel and double click on Java plug-in. It starts the program but it
> will not show the window for the plugin. If you open the Task Manager
> you can see the process javaw.exe running.
>
> Kill the javaw.exe. Stop the service and go to Control Panel and
> double click on the Java plugin again. This time it will load the window.
>
> This DOES NOT happen on XP. It works fine. Its only reproducable on
> Windows 2000. Service Pack 3 and 4.
>
> This is a simple scenario. I have some more complicated ones.
>
> Any insigts are greatly appreciated.
>
> Thanks
>
> Sal.
>
> ------------------------------------------------------- SF email is
> sponsored by - The IT Product Guide Read honest & candid reviews on
> hundreds of IT Products from real users. Discover which products truly
> live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________ Wrapper-user mailing
> list Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user 

[Wrapper-user] Windows 2000 issue

[Salman H. <sal...@ho...>]

<html><div style='background-color:'><DIV class=RTE></DIV>
<DIV>
<DIV>
<P>Hi,</P>
<P>I am having an issue using the Wrapper Service on Windows 2000. I have been trying to track the problem for 2 days now and I've finally pinned down that its something to do with wrapper. <BR><BR>Issue: Other java windows will not render<BR><BR>I downloaded the most recent version of the WS and installed the testWrapper as&nbsp;a service. I start this service. Then I go to Control Panel and double click on Java plug-in. It starts the program but it will not show the window for the plugin. If you open the Task Manager you can see the process javaw.exe running. </P>
<P>Kill the javaw.exe. Stop the service and go to Control Panel and double click on the Java plugin again. This time it will load the window.</P>
<P>This DOES NOT happen on XP. It works fine. Its only reproducable on Windows 2000. Service Pack 3 and 4. </P>
<P>This is a simple scenario. I have some more complicated ones. </P>
<P>Any insigts are greatly appreciated.</P>
<P>Thanks</P>
<P>Sal.</P></DIV></DIV></div></html>

[Wrapper-user] Compiled wrapper on AMD64

[Stephen S. <scs...@gm...>]

I had to do the following to make wrapper compile on AMD64:

diff -r wrapper_3.1.2_src/build.xml wrapper_3.1.2_src_new/build.xml
205a206
>              source="1.2"
214a216
>              source="1.2"
diff -r wrapper_3.1.2_src/src/c/Makefile.linux
wrapper_3.1.2_src_new/src/c/Makefile.linux
1c1
< COMPILE = gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP
---
> COMPILE = gcc -O3 -Wall --pedantic -pthread -DUSE_NANOSLEEP -lm -fPIC

[Wrapper-user] Wrapper on AMD-64

[Stephen S. <scs...@gm...>]

Has anyone built the wrapper for AMD64?  We have such a machine
running Debian sarge, and would love to use the wrapper pretty soon
(as in.. today..).

Thanks,

Stephen.

[Wrapper-user] boot process of windows prevents wrapper-service startup

[Mattias T. <Mat...@mi...>]

> Hi
>=20
> After a reboot of a  windows 2003 server our application implemented =
as a serice with the service wrapper failed to start. Looking to the =
wrapper log below there are somethings that puzzels me.=20
>=20
> 1. First of all the time sequenze, how can an event 13:36:44 be logged =
after events 14:36:43 (Maybe a bug or could it be that the server on =
boot contacts another server for sync of time?)
> 2. The amount of seconds waiting for CPU time suggest that somehting =
with the system time is wrong (1)
>=20
> My conclusion is that something during the boot process of the server =
prevents CPU time to the wrapper and jvm. How to circumvent this?
> Is it a good idea to set wrapper.use_system_time=3Dfalse to avoid =
problems like mentioned above?
> Would setting  wrapper.startup.delay.service=3D30 cause the wrapper =
waiting 30 seconds after startup of server before launching? Thus maybe =
avoid the conflict during boot on CPU time?
> Any other good suggestions wold be nice...
> //Mattias
>=20
> INFO   | wrapper  | 2004/12/14 13:34:00 | User logged out.  Ignored.
> STATUS | wrapper  | 2004/12/14 13:34:12 | Machine is shutting down.
> STATUS | wrapper  | 2004/12/14 13:34:14 | <-- Wrapper Stopped			=
//reboot
> STATUS | wrapper  | 2004/12/14 14:36:37 | --> Wrapper Started as =
Service
> STATUS | wrapper  | 2004/12/14 14:36:37 | Launching a JVM...
> INFO   | jvm 1    | 2004/12/14 14:36:43 | Wrapper (Version 3.1.0) =
http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2004/12/14 14:36:43 |=20
> INFO   | jvm 1    | 2004/12/14 14:36:44 | Application Alarm Manager =
running.
> INFO   | jvm 1    | 2004/12/14 14:36:44 | Started:Tue Dec 14 14:36:44 =
CET 2004
> INFO   | jvm 1    | 2004/12/14 13:37:52 | JVM Process has not received =
any CPU time for 429493180 seconds.  Extending timeouts.
> INFO   | jvm 1    | 2004/12/14 13:38:51 | Wrapper Manager: The Wrapper =
code did not ping the JVM for 59 seconds.  Quit and let the Wrapper =
resynch.
> STATUS | wrapper  | 2004/12/14 13:38:52 | <-- Wrapper Stopped
>=20
>=20
>=20

Re: [Wrapper-user] boot process of windows prevents wrapper-service startup

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

Mattias,
    There were a couple timing problems in 3.1.0 and 3.1.1 which have 
been fixed in 3.1.2.
Please upgrade to that version and give it a try.  I am pretty sure that 
this problem has
been fixed.  Read over the change log.

Mattias Ternert wrote:

> After a reboot of a  windows 2003 server our application implemented 
> as a serice with the service wrapper failed to start. Looking to the 
> wrapper log below there are somethings that puzzels me.
>
> 1. First of all the time sequenze, how can an event 13:36:44 be logged 
> after events 14:36:43 (Maybe a bug or could it be that the server on 
> boot contacts another server for sync of time?)
>
Yes the system time does appear to be getting adjusted... Not sure what 
would be
causing such a large jump.

> 2. The amount of seconds waiting for CPU time suggest that somehting 
> with the system time is wrong (1)
>
I think that may be the bug I mentioned above.

> My conclusion is that something during the boot process of the server 
> prevents CPU time to the wrapper and jvm. How to circumvent this?
>
> Is it a good idea to set wrapper.use_system_time=false to avoid 
> problems like mentioned above?
> Would setting  wrapper.startup.delay.service=30 cause the wrapper 
> waiting 30 seconds after startup of server before launching? Thus 
> maybe avoid the conflict during boot on CPU time?
>
In 3.1.2, try setting wrapper.use_system_time=false.  This should make 
the wrapper
work correctly even without setting any timeouts or using the startup 
delay.  The
delay is also working off the timer.  So if you are using system time 
then that would
still fail.

The tick timer has proved to be quite reliable.  It will be the default 
for 3.2.0 and
future versions.

Post back with results.

Cheers,
Leif

> Any other good suggestions wold be nice...
> //Mattias
>
> INFO   | wrapper  | 2004/12/14 13:34:00 | User logged out.  Ignored.
> STATUS | wrapper  | 2004/12/14 13:34:12 | Machine is shutting down.
> STATUS | wrapper  | 2004/12/14 13:34:14 | <-- Wrapper Stopped   
>                 //reboot
> STATUS | wrapper  | 2004/12/14 14:36:37 | --> Wrapper Started as Service
> STATUS | wrapper  | 2004/12/14 14:36:37 | Launching a JVM...
> INFO   | jvm 1    | 2004/12/14 14:36:43 | Wrapper (Version 3.1.0) 
> http://wrapper.tanukisoftware.org
> INFO   | jvm 1    | 2004/12/14 14:36:43 |
> INFO   | jvm 1    | 2004/12/14 14:36:44 | Application Alarm Manager 
> running.
> INFO   | jvm 1    | 2004/12/14 14:36:44 | Started:Tue Dec 14 14:36:44 
> CET 2004
> INFO   | jvm 1    | 2004/12/14 13:37:52 | JVM Process has not received 
> any CPU time for 429493180 seconds.  Extending timeouts.
>
> INFO   | jvm 1    | 2004/12/14 13:38:51 | Wrapper Manager: The Wrapper 
> code did not ping the JVM for 59 seconds.  Quit and let the Wrapper 
> resynch.
>
> STATUS | wrapper  | 2004/12/14 13:38:52 | <-- Wrapper Stopped
>
>
>

[Wrapper-user] boot process of windows prevents wrapper-service startup

[Mattias T. <Mat...@mi...>]

Hi

After a reboot of a  windows 2003 server our application implemented as =
a serice with the service wrapper failed to start. Looking to the =
wrapper log below there are somethings that puzzels me.=20

1. First of all the time sequenze, how can an event 13:36:44 be logged =
after events 14:36:43 (Maybe a bug or could it be that the server on =
boot contacts another server for sync of time?)
2. The amount of seconds waiting for CPU time suggest that somehting =
with the system time is wrong (1)

My conclusion is that something during the boot process of the server =
prevents CPU time to the wrapper and jvm. How to circumvent this?
Is it a good idea to set wrapper.use_system_time=3Dfalse to avoid =
problems like mentioned above?
Would setting  wrapper.startup.delay.service=3D30 cause the wrapper =
waiting 30 seconds after startup of server before launching? Thus maybe =
avoid the conflict during boot on CPU time?
Any other good suggestions wold be nice...
//Mattias

INFO   | wrapper  | 2004/12/14 13:34:00 | User logged out.  Ignored.
STATUS | wrapper  | 2004/12/14 13:34:12 | Machine is shutting down.
STATUS | wrapper  | 2004/12/14 13:34:14 | <-- Wrapper Stopped			//reboot
STATUS | wrapper  | 2004/12/14 14:36:37 | --> Wrapper Started as Service
STATUS | wrapper  | 2004/12/14 14:36:37 | Launching a JVM...
INFO   | jvm 1    | 2004/12/14 14:36:43 | Wrapper (Version 3.1.0) =
http://wrapper.tanukisoftware.org
INFO   | jvm 1    | 2004/12/14 14:36:43 |=20
INFO   | jvm 1    | 2004/12/14 14:36:44 | Application Alarm Manager =
running.
INFO   | jvm 1    | 2004/12/14 14:36:44 | Started:Tue Dec 14 14:36:44 =
CET 2004
INFO   | jvm 1    | 2004/12/14 13:37:52 | JVM Process has not received =
any CPU time for 429493180 seconds.  Extending timeouts.
INFO   | jvm 1    | 2004/12/14 13:38:51 | Wrapper Manager: The Wrapper =
code did not ping the JVM for 59 seconds.  Quit and let the Wrapper =
resynch.
STATUS | wrapper  | 2004/12/14 13:38:52 | <-- Wrapper Stopped

[Wrapper-user] Ntservice.process_priority

[Robert D. <rdi...@tr...>]

Is there any way to get this to be AboveNormal? I only see options for
NORMAL, HIGH, and REALTIME.