Menu
▾
▴
wrapper-user — User issues for Wrapper. (Support questions, etc.)
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
(13) |
Nov
(16) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(38) |
Feb
(51) |
Mar
(51) |
Apr
(115) |
May
(82) |
Jun
(30) |
Jul
(50) |
Aug
(68) |
Sep
(57) |
Oct
(160) |
Nov
(80) |
Dec
(78) |
| 2004 |
Jan
(71) |
Feb
(75) |
Mar
(108) |
Apr
(87) |
May
(79) |
Jun
(70) |
Jul
(69) |
Aug
(39) |
Sep
(52) |
Oct
(47) |
Nov
(50) |
Dec
(32) |
| 2005 |
Jan
(22) |
Feb
(122) |
Mar
(46) |
Apr
(76) |
May
(31) |
Jun
(51) |
Jul
(61) |
Aug
(70) |
Sep
(37) |
Oct
(46) |
Nov
(57) |
Dec
(83) |
| 2006 |
Jan
(55) |
Feb
(81) |
Mar
(51) |
Apr
(67) |
May
(77) |
Jun
(43) |
Jul
(106) |
Aug
(64) |
Sep
(47) |
Oct
(64) |
Nov
(60) |
Dec
(12) |
| 2007 |
Jan
(50) |
Feb
(93) |
Mar
(49) |
Apr
(56) |
May
(40) |
Jun
(63) |
Jul
(40) |
Aug
(47) |
Sep
(54) |
Oct
(37) |
Nov
(54) |
Dec
(37) |
| 2008 |
Jan
(35) |
Feb
(39) |
Mar
(26) |
Apr
(14) |
May
(23) |
Jun
(51) |
Jul
(43) |
Aug
(26) |
Sep
(29) |
Oct
(31) |
Nov
(24) |
Dec
(16) |
| 2009 |
Jan
(21) |
Feb
(30) |
Mar
(74) |
Apr
(26) |
May
(26) |
Jun
(43) |
Jul
(23) |
Aug
(23) |
Sep
(15) |
Oct
(27) |
Nov
(37) |
Dec
(10) |
| 2010 |
Jan
(16) |
Feb
(28) |
Mar
(16) |
Apr
(45) |
May
(8) |
Jun
(68) |
Jul
(45) |
Aug
(44) |
Sep
(51) |
Oct
(7) |
Nov
(20) |
Dec
(21) |
| 2011 |
Jan
(14) |
Feb
(17) |
Mar
(7) |
Apr
(7) |
May
(48) |
Jun
(23) |
Jul
(5) |
Aug
(33) |
Sep
(22) |
Oct
(14) |
Nov
(14) |
Dec
(5) |
| 2012 |
Jan
|
Feb
(10) |
Mar
(12) |
Apr
(51) |
May
(10) |
Jun
(8) |
Jul
(14) |
Aug
(22) |
Sep
(9) |
Oct
(24) |
Nov
(14) |
Dec
(13) |
| 2013 |
Jan
(12) |
Feb
(4) |
Mar
(14) |
Apr
(19) |
May
(2) |
Jun
(5) |
Jul
(13) |
Aug
(10) |
Sep
(4) |
Oct
(11) |
Nov
(13) |
Dec
(2) |
| 2014 |
Jan
(3) |
Feb
(14) |
Mar
(5) |
Apr
(10) |
May
(10) |
Jun
(11) |
Jul
(10) |
Aug
(3) |
Sep
(13) |
Oct
(22) |
Nov
(14) |
Dec
(32) |
| 2015 |
Jan
(8) |
Feb
(2) |
Mar
(17) |
Apr
(1) |
May
(24) |
Jun
|
Jul
(4) |
Aug
|
Sep
(9) |
Oct
(9) |
Nov
(5) |
Dec
(2) |
| 2016 |
Jan
(8) |
Feb
(6) |
Mar
(6) |
Apr
(9) |
May
(3) |
Jun
(2) |
Jul
(7) |
Aug
(6) |
Sep
|
Oct
|
Nov
(1) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(8) |
Mar
(6) |
Apr
|
May
|
Jun
(3) |
Jul
(13) |
Aug
(10) |
Sep
(8) |
Oct
|
Nov
(6) |
Dec
|
| 2018 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
(2) |
May
|
Jun
|
Jul
(3) |
Aug
(2) |
Sep
(9) |
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2019 |
Jan
(9) |
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
|
Jul
(7) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2020 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2021 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2023 |
Jan
(3) |
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2026 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Pauwels S. <Ste...@si...> - 2003-04-10 07:54:40
|
Hallo, I tested out version 3.0.2 of the service wrapper (downloaded today). Does anybody know what's wrong with this output ? STATUS | wrapper | 2003/04/10 09:48:28 | --> Wrapper Started as Console STATUS | wrapper | 2003/04/10 09:48:29 | Launching a JVM... INFO | jvm 1 | 2003/04/10 09:48:39 | Wrapper (Version 3.0.1) INFO | jvm 1 | 2003/04/10 09:48:39 | INFO | jvm 1 | 2003/04/10 09:48:39 | Wrapper code received an unknown packet type: 113 Kind regards, Stefan |
|
From: Leif M. <le...@ta...> - 2003-04-09 09:37:37
|
For those not monitoring the support section, there was a bug found recently which would cause the Wrapper to crash when run as an NT Service on some systems. This was caused by another program setting an invalid environment variable into the system registry. Nasty, but considering the culprit appears to be Oracle, the Wrapper needed to handle that case correctly. Please see the following issue for the full thread. http://sourceforge.net/tracker/index.php?func=detail&aid=714107&group_id=39428&atid=425188 This will be fixed in version 3.0.2. See the issue for a patch you can download if you can't wait a few more days. 2.2.x users were not affected. Cheers, Leif |
|
From: Moulin, N. <nic...@cg...> - 2003-04-09 07:47:00
|
Hi Leif,
Thanks for your very quick answer (can't imagine a quicker one!).
I have pasted the new "wrapper.log" (using the modified wrapper.jar) at the
end the text.
Regarding Problem 1: we have done a test after changing the permissions on
the file "libwrapper.so" to 777, but it produces exactly the same output as
with default permisions (644).
Question: how could we check if the "libwrapper.so" file is corrupted?
FYI, a checksum on the file gives:
26458 32 libwrapper.so
"DEBUG | wrapper | 2003/04/09 15:28:01 | Spawning intermediate process...
DEBUG | wrapper | 2003/04/09 15:28:02 | Spawning daemon process...
STATUS | wrapper | 2003/04/09 15:28:02 | --> Wrapper Started as Console
INFO | wrapperp | 2003/04/09 15:28:02 | port 1777 already in use, using
port 1781 instead.
DEBUG | wrapperp | 2003/04/09 15:28:02 | server listening on port 1781.
DEBUG | wrapperp | 2003/04/09 15:28:02 | socket creation failed. (11)
DEBUG | wrapperp | 2003/04/09 15:28:02 | socket creation failed. (11)
DEBUG | wrapperp | 2003/04/09 15:28:02 | socket creation failed. (11)
DEBUG | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[0] : /opt/java1.3/bin/java
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[1] : -Xms3m
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[2] : -Xmx64m
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[3] :
-Djava.library.path=/home/vccdev/VCCInt/deploy/lib
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[4] : -classpath
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[5] :
/home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[6] :
-Dwrapper.key=NZop9_KQY_q7viil
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[7] : -Dwrapper.port=1781
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[8] : -Dwrapper.debug=TRUE
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[9] :
-Dwrapper.cpu.timeout=10
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[10] : -Dwrapper.jvmid=1
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[11] :
org.tanukisoftware.wrapper.WrapperSimpleApp
DEBUG | wrapper | 2003/04/09 15:28:03 | Command[12] :
com.spower.vcc.intf.client.VCCRxClient
STATUS | wrapper | 2003/04/09 15:28:03 | Launching a JVM...
DEBUG | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG | wrapperp | 2003/04/09 15:28:03 | socket creation failed. (11)
DEBUG | wrapperp | 2003/04/09 15:28:04 | socket creation failed. (11)
INFO | jvm 1 | 2003/04/09 15:28:04 | Wrapper Manager: JVM #1
INFO | jvm 1 | 2003/04/09 15:28:04 | Wrapper Manager: Registering
shutdown hook
INFO | jvm 1 | 2003/04/09 15:28:04 | Wrapper Manager: Using wrapper
INFO | jvm 1 | 2003/04/09 15:28:04 | java.lang.UnsatisfiedLinkError: no
wrapper in java.library.path
INFO | jvm 1 | 2003/04/09 15:28:04 | at
java.lang.ClassLoader.loadLibrary(Unknown Source)
INFO | jvm 1 | 2003/04/09 15:28:04 | at
java.lang.Runtime.loadLibrary0(Unknown Source)
INFO | jvm 1 | 2003/04/09 15:28:04 | at
java.lang.System.loadLibrary(Unknown Source)
INFO | jvm 1 | 2003/04/09 15:28:04 | at
org.tanukisoftware.wrapper.WrapperManager.<clinit>(WrapperManager.java:393)
INFO | jvm 1 | 2003/04/09 15:28:04 | at
org.tanukisoftware.wrapper.WrapperSimpleApp.main(WrapperSimpleApp.java:366)
INFO | jvm 1 | 2003/04/09 15:28:04 |
INFO | jvm 1 | 2003/04/09 15:28:04 | WARNING - Unable to load native
library 'libwrapper.so'. The file
INFO | jvm 1 | 2003/04/09 15:28:04 | is located on the path
at the following location but could
INFO | jvm 1 | 2003/04/09 15:28:04 | be loaded:
INFO | jvm 1 | 2003/04/09 15:28:04 |
/home/vccdev/VCCInt/deploy/lib/libwrapper.so
INFO | jvm 1 | 2003/04/09 15:28:04 | Please verify that the
file is readable by the current user
INFO | jvm 1 | 2003/04/09 15:28:04 | and that the file has
not been corrupted in any way.
INFO | jvm 1 | 2003/04/09 15:28:04 | System signals will not
be handled correctly.
INFO | jvm 1 | 2003/04/09 15:28:04 |
INFO | jvm 1 | 2003/04/09 15:28:04 | Java Version :
1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM
INFO | jvm 1 | 2003/04/09 15:28:04 | Java VM Vendor : Hewlett-Packard
Company
INFO | jvm 1 | 2003/04/09 15:28:04 |
INFO | jvm 1 | 2003/04/09 15:28:04 | Wrapper (Version 3.0.2a)
INFO | jvm 1 | 2003/04/09 15:28:04 |
INFO | jvm 1 | 2003/04/09 15:28:04 | Open socket to wrapper...
INFO | jvm 1 | 2003/04/09 15:28:04 | Opened Socket
INFO | jvm 1 | 2003/04/09 15:28:04 | Send a packet 110 :
NZop9_KQY_q7viil
INFO | jvm 1 | 2003/04/09 15:28:04 |
handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=60260])
DEBUG | wrapperp | 2003/04/09 15:28:04 | accepted a socket from 127.0.0.1
on port 60260
DEBUG | wrapperp | 2003/04/09 15:28:04 | read a packet 110 :
NZop9_KQY_q7viil
DEBUG | wrapper | 2003/04/09 15:28:04 | Got key from JVM: NZop9_KQY_q7viil
DEBUG | wrapperp | 2003/04/09 15:28:04 | send a packet 112 : 1
DEBUG | wrapperp | 2003/04/09 15:28:04 | socket read failed. (11)
DEBUG | wrapper | 2003/04/09 15:28:04 | Start Application.
DEBUG | wrapperp | 2003/04/09 15:28:04 | socket creation failed. (11)
ERROR | wrapper | 2003/04/09 15:28:04 | Unable to send the start command
to the JVM.
ERROR | wrapper | 2003/04/09 15:28:04 | JVM did not exit on request,
terminated
INFO | jvm 1 | 2003/04/09 15:28:05 | Received a packet 112 : 1
INFO | jvm 1 | 2003/04/09 15:28:05 | Wrapper Manager: LowLogLevel from
Wrapper is 1
INFO | jvm 1 | 2003/04/09 15:28:05 | java.io.EOFException
INFO | jvm 1 | 2003/04/09 15:28:05 | java.io.EOFException
INFO | jvm 1 | 2003/04/09 15:28:05 | at
java.io.DataInputStream.readByte(Unknown Source)
INFO | jvm 1 | 2003/04/09 15:28:05 | at
org.tanukisoftware.wrapper.WrapperManager.handleSocket(WrapperManager.java:1
434)
INFO | jvm 1 | 2003/04/09 15:28:05 | at
org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:1750)
INFO | jvm 1 | 2003/04/09 15:28:05 | at
java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2003/04/09 15:28:05 | Dump the stack so I can see how we
got here.
INFO | jvm 1 | 2003/04/09 15:28:05 | java.lang.Exception: Stack trace
INFO | jvm 1 | 2003/04/09 15:28:05 | at
java.lang.Thread.dumpStack(Unknown Source)
INFO | jvm 1 | 2003/04/09 15:28:05 | at
org.tanukisoftware.wrapper.WrapperManager.closeSocket(WrapperManager.java:13
30)
INFO | jvm 1 | 2003/04/09 15:28:05 | at
org.tanukisoftware.wrapper.WrapperManager.run(WrapperManager.java:1767)
DEBUG | wrapperp | 2003/04/09 15:28:05 | socket creation failed. (11)
DEBUG | wrapper | 2003/04/09 15:28:05 | JVM was only running for 2 seconds
leading to a failed restart count of 1."
Thanks again for the great support.
Best Regards,
Nicolas
-----Original Message-----
From: Leif Mortenson
To: wra...@li...
Sent: 4/9/2003 2:37 PM
Subject: Re: [Wrapper-user] socket creation failed and libwrapper.so
Nicolas,
Thanks for the detailed report. I do not have access to an HP-UX
machine but others have been using it on that platform without problems as
far as I know. If any HP-UX users out there could chime in, I would
appreciate it.
Problem 1: The library not being loaded. Looking at the ls and
wrapper.log output that you provided, the only ideas that I have here are
permission problems reading the file or maybe that the library file is
corrupted. In the wrapper.jar file that I am sending you, I have added code
to test for this case. This will be in the 3.0.2 release as well.
Problem 2: Socket disconnect problem. This one is puzzling. The
Java side successfully connects to the native code and sends back the
authorization key. The Wrapper then responds by sending the Log Level to the
JVM. The JVM is successfully reading this Log Level and displaying a
message. The problem is that at this point, it appears that the JVM is
closing the socket for some reason.
Looking at the code, the only thing that I can find that would cause
this is if an IOException was being thrown. I am currently not displaying
this stack trace because up until now, it is only thrown in the event of the
socket being closed on shutdown. This may not be correct.
I have temporarily added some stack dumps to the code and have build you
a special wrapper.jar file to test this. (I will send it to you directly as
everyone else on the list does not need it. Please respond to
the list though.)
If you could send me the new wrapper.log just as you did this time, it
might give me the info I need to get this fixed for you. I only need a
single run of the Wrapper output. You don't need to send all 5 attempts at
launching the JVM.
Cheers,
Leif
Moulin, Nicolas wrote:
>Hi All,
>
>We are having an issue when running the wrapper 3.0.1 on HP-UX11i.
>
>It seems that there is a socket problem and also the file
"libwrapper.so"
>can't be found, ALTHOUGH it is existing in the directory where the
wrapper
>is trying to find it (see log below)...
>
>Please find below the content of the "wrapper.log" file:
>
>
<snip>
>Note:
>$ ls -lrt /home/vccdev/VCCInt/deploy/lib/libwrapper.so
>
>-rw-r--r-- 1 vccdev dev 16384 Apr 8 17:51
>/home/vccdev/VCCInt/deploy/lib/libwrapper.so
>
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
____________________________________________________
This message contains information that may be privileged or confidential and
is the property of the Cap Gemini Ernst & Young Group. It is intended only
for the person to whom it is addressed. If you are not the intended
recipient, you are not authorised to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all copies
of this message.
|
|
From: Leif M. <le...@ta...> - 2003-04-09 06:37:57
|
Nicolas,
Thanks for the detailed report. I do not have access to an HP-UX
machine but
others have been using it on that platform without problems as far as I
know.
If any HP-UX users out there could chime in, I would appreciate it.
Problem 1: The library not being loaded. Looking at the ls and
wrapper.log
output that you provided, the only ideas that I have here are permission
problems
reading the file or maybe that the library file is corrupted. In the
wrapper.jar file
that I am sending you, I have added code to test for this case. This
will be in the
3.0.2 release as well.
Problem 2: Socket disconnect problem. This one is puzzling. The
Java side
successfully connects to the native code and sends back the
authorization key.
The Wrapper then responds by sending the Log Level to the JVM. The JVM is
successfully reading this Log Level and displaying a message. The
problem is
that at this point, it appears that the JVM is closing the socket for
some reason.
Looking at the code, the only thing that I can find that would cause
this is if an
IOException was being thrown. I am currently not displaying this stack
trace
because up until now, it is only thrown in the event of the socket being
closed on
shutdown. This may not be correct. I have temporarily added some
stack dumps
to the code and have build you a special wrapper.jar file to test this.
(I will send it
to you directly as everyone else on the list does not need it. Please
respond to
the list though.) If you could send me the new wrapper.log just as you
did this
time, it might give me the info I need to get this fixed for you. I
only need a single
run of the Wrapper output. You don't need to send all 5 attempts at
launching the
JVM.
Cheers,
Leif
Moulin, Nicolas wrote:
>Hi All,
>
>We are having an issue when running the wrapper 3.0.1 on HP-UX11i.
>
>It seems that there is a socket problem and also the file "libwrapper.so"
>can't be found, ALTHOUGH it is existing in the directory where the wrapper
>is trying to find it (see log below)...
>
>Please find below the content of the "wrapper.log" file:
>
>
<snip>
>Note:
>$ ls -lrt /home/vccdev/VCCInt/deploy/lib/libwrapper.so
>
>-rw-r--r-- 1 vccdev dev 16384 Apr 8 17:51
>/home/vccdev/VCCInt/deploy/lib/libwrapper.so
>
|
|
From: Moulin, N. <nic...@cg...> - 2003-04-09 04:21:04
|
Hi All, We are having an issue when running the wrapper 3.0.1 on HP-UX11i. It seems that there is a socket problem and also the file "libwrapper.so" can't be found, ALTHOUGH it is existing in the directory where the wrapper is trying to find it (see log below)... Please find below the content of the "wrapper.log" file: "DEBUG | wrapper | 2003/04/09 12:14:28 | Spawning intermediate process... DEBUG | wrapper | 2003/04/09 12:14:28 | Spawning daemon process... STATUS | wrapper | 2003/04/09 12:14:28 | --> Wrapper Started as Console INFO | wrapperp | 2003/04/09 12:14:28 | port 1777 already in use, using port 1781 instead. DEBUG | wrapperp | 2003/04/09 12:14:28 | server listening on port 1781. DEBUG | wrapperp | 2003/04/09 12:14:28 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:29 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:29 | Command[0] : /opt/java1.3/bin/java DEBUG | wrapper | 2003/04/09 12:14:29 | Command[1] : -Xms3m DEBUG | wrapper | 2003/04/09 12:14:29 | Command[2] : -Xmx64m DEBUG | wrapper | 2003/04/09 12:14:29 | Command[3] : -Djava.library.path=/home/vccdev/VCCInt/deploy/lib DEBUG | wrapper | 2003/04/09 12:14:29 | Command[4] : -classpath DEBUG | wrapper | 2003/04/09 12:14:29 | Command[5] : /home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar DEBUG | wrapper | 2003/04/09 12:14:29 | Command[6] : -Dwrapper.key=BFJFSSp_bRtvKh_W DEBUG | wrapper | 2003/04/09 12:14:29 | Command[7] : -Dwrapper.port=1781 DEBUG | wrapper | 2003/04/09 12:14:29 | Command[8] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2003/04/09 12:14:29 | Command[9] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2003/04/09 12:14:29 | Command[10] : -Dwrapper.jvmid=1 DEBUG | wrapper | 2003/04/09 12:14:29 | Command[11] : org.tanukisoftware.wrapper.WrapperSimpleApp DEBUG | wrapper | 2003/04/09 12:14:29 | Command[12] : com.spower.vcc.intf.client.VCCRxClient STATUS | wrapper | 2003/04/09 12:14:29 | Launching a JVM... DEBUG | wrapperp | 2003/04/09 12:14:29 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:29 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:29 | socket creation failed. (11) INFO | jvm 1 | 2003/04/09 12:14:30 | Wrapper Manager: JVM #1 INFO | jvm 1 | 2003/04/09 12:14:30 | Wrapper Manager: Registering shutdown hook INFO | jvm 1 | 2003/04/09 12:14:30 | Wrapper Manager: Using wrapper INFO | jvm 1 | 2003/04/09 12:14:30 | INFO | jvm 1 | 2003/04/09 12:14:30 | WARNING - Unable to load native library 'wrapper' because the INFO | jvm 1 | 2003/04/09 12:14:30 | file 'libwrapper.so' could not be located in the following INFO | jvm 1 | 2003/04/09 12:14:30 | java.library.path: INFO | jvm 1 | 2003/04/09 12:14:30 | /home/vccdev/VCCInt/deploy/lib INFO | jvm 1 | 2003/04/09 12:14:30 | Please see the documentation for the wrapper.java.library.path INFO | jvm 1 | 2003/04/09 12:14:30 | configuration property. INFO | jvm 1 | 2003/04/09 12:14:30 | System signals will not be handled correctly. INFO | jvm 1 | 2003/04/09 12:14:30 | INFO | jvm 1 | 2003/04/09 12:14:30 | Java Version : 1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM INFO | jvm 1 | 2003/04/09 12:14:30 | Java VM Vendor : Hewlett-Packard Company INFO | jvm 1 | 2003/04/09 12:14:30 | INFO | jvm 1 | 2003/04/09 12:14:30 | Wrapper (Version 3.0.1) INFO | jvm 1 | 2003/04/09 12:14:30 | DEBUG | wrapperp | 2003/04/09 12:14:30 | socket creation failed. (11) INFO | jvm 1 | 2003/04/09 12:14:30 | Open socket to wrapper... INFO | jvm 1 | 2003/04/09 12:14:30 | Opened Socket INFO | jvm 1 | 2003/04/09 12:14:30 | Send a packet 110 : BFJFSSp_bRtvKh_W INFO | jvm 1 | 2003/04/09 12:14:30 | handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=52333]) DEBUG | wrapperp | 2003/04/09 12:14:30 | accepted a socket from 127.0.0.1 on port 52333 DEBUG | wrapperp | 2003/04/09 12:14:30 | read a packet 110 : BFJFSSp_bRtvKh_W DEBUG | wrapper | 2003/04/09 12:14:30 | Got key from JVM: BFJFSSp_bRtvKh_W DEBUG | wrapperp | 2003/04/09 12:14:30 | send a packet 112 : 1 DEBUG | wrapperp | 2003/04/09 12:14:30 | socket read failed. (11) DEBUG | wrapper | 2003/04/09 12:14:30 | Start Application. DEBUG | wrapperp | 2003/04/09 12:14:30 | socket creation failed. (11) ERROR | wrapper | 2003/04/09 12:14:30 | Unable to send the start command to the JVM. ERROR | wrapper | 2003/04/09 12:14:30 | JVM did not exit on request, terminated INFO | jvm 1 | 2003/04/09 12:14:31 | Received a packet 112 : 1 INFO | jvm 1 | 2003/04/09 12:14:31 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 1 | 2003/04/09 12:14:31 | Closing socket. DEBUG | wrapperp | 2003/04/09 12:14:31 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:31 | JVM was only running for 2 seconds leading to a failed restart count of 1. DEBUG | wrapperp | 2003/04/09 12:14:31 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:31 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:31 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:32 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:32 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:32 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:32 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:33 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:33 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:33 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:33 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:34 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:34 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:34 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:35 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:35 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:35 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:35 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:36 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:36 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:36 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:36 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:37 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:37 | Command[0] : /opt/java1.3/bin/java DEBUG | wrapper | 2003/04/09 12:14:37 | Command[1] : -Xms3m DEBUG | wrapper | 2003/04/09 12:14:37 | Command[2] : -Xmx64m DEBUG | wrapper | 2003/04/09 12:14:37 | Command[3] : -Djava.library.path=/home/vccdev/VCCInt/deploy/lib DEBUG | wrapper | 2003/04/09 12:14:37 | Command[4] : -classpath DEBUG | wrapper | 2003/04/09 12:14:37 | Command[5] : /home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar DEBUG | wrapper | 2003/04/09 12:14:37 | Command[6] : -Dwrapper.key=xKR_k1luLtoU4jmT DEBUG | wrapper | 2003/04/09 12:14:37 | Command[7] : -Dwrapper.port=1781 DEBUG | wrapper | 2003/04/09 12:14:37 | Command[8] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2003/04/09 12:14:37 | Command[9] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2003/04/09 12:14:37 | Command[10] : -Dwrapper.jvmid=2 DEBUG | wrapper | 2003/04/09 12:14:37 | Command[11] : org.tanukisoftware.wrapper.WrapperSimpleApp DEBUG | wrapper | 2003/04/09 12:14:37 | Command[12] : com.spower.vcc.intf.client.VCCRxClient STATUS | wrapper | 2003/04/09 12:14:37 | Launching a JVM... DEBUG | wrapperp | 2003/04/09 12:14:37 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:37 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:37 | socket creation failed. (11) INFO | jvm 2 | 2003/04/09 12:14:38 | Wrapper Manager: JVM #2 INFO | jvm 2 | 2003/04/09 12:14:38 | Wrapper Manager: Registering shutdown hook INFO | jvm 2 | 2003/04/09 12:14:38 | Wrapper Manager: Using wrapper INFO | jvm 2 | 2003/04/09 12:14:38 | INFO | jvm 2 | 2003/04/09 12:14:38 | WARNING - Unable to load native library 'wrapper' because the INFO | jvm 2 | 2003/04/09 12:14:38 | file 'libwrapper.so' could not be located in the following INFO | jvm 2 | 2003/04/09 12:14:38 | java.library.path: INFO | jvm 2 | 2003/04/09 12:14:38 | /home/vccdev/VCCInt/deploy/lib INFO | jvm 2 | 2003/04/09 12:14:38 | Please see the documentation for the wrapper.java.library.path INFO | jvm 2 | 2003/04/09 12:14:38 | configuration property. INFO | jvm 2 | 2003/04/09 12:14:38 | System signals will not be handled correctly. INFO | jvm 2 | 2003/04/09 12:14:38 | INFO | jvm 2 | 2003/04/09 12:14:38 | Java Version : 1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM INFO | jvm 2 | 2003/04/09 12:14:38 | Java VM Vendor : Hewlett-Packard Company INFO | jvm 2 | 2003/04/09 12:14:38 | DEBUG | wrapperp | 2003/04/09 12:14:38 | socket creation failed. (11) INFO | jvm 2 | 2003/04/09 12:14:38 | Wrapper (Version 3.0.1) INFO | jvm 2 | 2003/04/09 12:14:38 | INFO | jvm 2 | 2003/04/09 12:14:38 | Open socket to wrapper... INFO | jvm 2 | 2003/04/09 12:14:38 | Opened Socket INFO | jvm 2 | 2003/04/09 12:14:38 | Send a packet 110 : xKR_k1luLtoU4jmT INFO | jvm 2 | 2003/04/09 12:14:38 | handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=52337]) DEBUG | wrapperp | 2003/04/09 12:14:38 | accepted a socket from 127.0.0.1 on port 52337 DEBUG | wrapperp | 2003/04/09 12:14:38 | read a packet 110 : xKR_k1luLtoU4jmT DEBUG | wrapper | 2003/04/09 12:14:38 | Got key from JVM: xKR_k1luLtoU4jmT DEBUG | wrapperp | 2003/04/09 12:14:38 | send a packet 112 : 1 DEBUG | wrapperp | 2003/04/09 12:14:38 | socket read failed. (11) DEBUG | wrapper | 2003/04/09 12:14:38 | Start Application. DEBUG | wrapperp | 2003/04/09 12:14:38 | socket creation failed. (11) ERROR | wrapper | 2003/04/09 12:14:38 | Unable to send the start command to the JVM. ERROR | wrapper | 2003/04/09 12:14:38 | JVM did not exit on request, terminated INFO | jvm 2 | 2003/04/09 12:14:39 | Received a packet 112 : 1 INFO | jvm 2 | 2003/04/09 12:14:39 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 2 | 2003/04/09 12:14:39 | Closing socket. DEBUG | wrapperp | 2003/04/09 12:14:39 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:39 | JVM was only running for 2 seconds leading to a failed restart count of 2. DEBUG | wrapperp | 2003/04/09 12:14:39 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:39 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:39 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:40 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:40 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:40 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:41 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:41 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:41 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:41 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:42 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:42 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:42 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:42 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:43 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:43 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:43 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:43 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:44 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:44 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:44 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:44 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:45 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:45 | Command[0] : /opt/java1.3/bin/java DEBUG | wrapper | 2003/04/09 12:14:45 | Command[1] : -Xms3m DEBUG | wrapper | 2003/04/09 12:14:45 | Command[2] : -Xmx64m DEBUG | wrapper | 2003/04/09 12:14:45 | Command[3] : -Djava.library.path=/home/vccdev/VCCInt/deploy/lib DEBUG | wrapper | 2003/04/09 12:14:45 | Command[4] : -classpath DEBUG | wrapper | 2003/04/09 12:14:45 | Command[5] : /home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar DEBUG | wrapper | 2003/04/09 12:14:45 | Command[6] : -Dwrapper.key=FVZMfucKwepBPvP6 DEBUG | wrapper | 2003/04/09 12:14:45 | Command[7] : -Dwrapper.port=1781 DEBUG | wrapper | 2003/04/09 12:14:45 | Command[8] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2003/04/09 12:14:45 | Command[9] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2003/04/09 12:14:45 | Command[10] : -Dwrapper.jvmid=3 DEBUG | wrapper | 2003/04/09 12:14:45 | Command[11] : org.tanukisoftware.wrapper.WrapperSimpleApp DEBUG | wrapper | 2003/04/09 12:14:45 | Command[12] : com.spower.vcc.intf.client.VCCRxClient STATUS | wrapper | 2003/04/09 12:14:45 | Launching a JVM... DEBUG | wrapperp | 2003/04/09 12:14:45 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:45 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:45 | socket creation failed. (11) INFO | jvm 3 | 2003/04/09 12:14:46 | Wrapper Manager: JVM #3 INFO | jvm 3 | 2003/04/09 12:14:46 | Wrapper Manager: Registering shutdown hook INFO | jvm 3 | 2003/04/09 12:14:46 | Wrapper Manager: Using wrapper INFO | jvm 3 | 2003/04/09 12:14:46 | INFO | jvm 3 | 2003/04/09 12:14:46 | WARNING - Unable to load native library 'wrapper' because the INFO | jvm 3 | 2003/04/09 12:14:46 | file 'libwrapper.so' could not be located in the following INFO | jvm 3 | 2003/04/09 12:14:46 | java.library.path: INFO | jvm 3 | 2003/04/09 12:14:46 | /home/vccdev/VCCInt/deploy/lib INFO | jvm 3 | 2003/04/09 12:14:46 | Please see the documentation for the wrapper.java.library.path INFO | jvm 3 | 2003/04/09 12:14:46 | configuration property. INFO | jvm 3 | 2003/04/09 12:14:46 | System signals will not be handled correctly. INFO | jvm 3 | 2003/04/09 12:14:46 | INFO | jvm 3 | 2003/04/09 12:14:46 | Java Version : 1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM INFO | jvm 3 | 2003/04/09 12:14:46 | Java VM Vendor : Hewlett-Packard Company INFO | jvm 3 | 2003/04/09 12:14:46 | DEBUG | wrapperp | 2003/04/09 12:14:46 | socket creation failed. (11) INFO | jvm 3 | 2003/04/09 12:14:46 | Wrapper (Version 3.0.1) INFO | jvm 3 | 2003/04/09 12:14:46 | INFO | jvm 3 | 2003/04/09 12:14:46 | Open socket to wrapper... INFO | jvm 3 | 2003/04/09 12:14:46 | Opened Socket INFO | jvm 3 | 2003/04/09 12:14:46 | Send a packet 110 : FVZMfucKwepBPvP6 INFO | jvm 3 | 2003/04/09 12:14:46 | handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=52341]) DEBUG | wrapperp | 2003/04/09 12:14:46 | accepted a socket from 127.0.0.1 on port 52341 DEBUG | wrapperp | 2003/04/09 12:14:46 | read a packet 110 : FVZMfucKwepBPvP6 DEBUG | wrapper | 2003/04/09 12:14:46 | Got key from JVM: FVZMfucKwepBPvP6 DEBUG | wrapperp | 2003/04/09 12:14:46 | send a packet 112 : 1 DEBUG | wrapperp | 2003/04/09 12:14:46 | socket read failed. (11) DEBUG | wrapper | 2003/04/09 12:14:46 | Start Application. DEBUG | wrapperp | 2003/04/09 12:14:46 | socket creation failed. (11) ERROR | wrapper | 2003/04/09 12:14:46 | Unable to send the start command to the JVM. ERROR | wrapper | 2003/04/09 12:14:46 | JVM did not exit on request, terminated INFO | jvm 3 | 2003/04/09 12:14:47 | Received a packet 112 : 1 INFO | jvm 3 | 2003/04/09 12:14:47 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 3 | 2003/04/09 12:14:47 | Closing socket. DEBUG | wrapperp | 2003/04/09 12:14:47 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:47 | JVM was only running for 2 seconds leading to a failed restart count of 3. DEBUG | wrapperp | 2003/04/09 12:14:47 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:47 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:48 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:48 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:48 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:48 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:49 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:49 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:49 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:49 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:50 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:50 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:50 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:50 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:51 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:51 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:51 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:51 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:52 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:52 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:52 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:53 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:53 | Command[0] : /opt/java1.3/bin/java DEBUG | wrapper | 2003/04/09 12:14:53 | Command[1] : -Xms3m DEBUG | wrapper | 2003/04/09 12:14:53 | Command[2] : -Xmx64m DEBUG | wrapper | 2003/04/09 12:14:53 | Command[3] : -Djava.library.path=/home/vccdev/VCCInt/deploy/lib DEBUG | wrapper | 2003/04/09 12:14:53 | Command[4] : -classpath DEBUG | wrapper | 2003/04/09 12:14:53 | Command[5] : /home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar DEBUG | wrapper | 2003/04/09 12:14:53 | Command[6] : -Dwrapper.key=DeURD13ZvAbAKXIL DEBUG | wrapper | 2003/04/09 12:14:53 | Command[7] : -Dwrapper.port=1781 DEBUG | wrapper | 2003/04/09 12:14:53 | Command[8] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2003/04/09 12:14:53 | Command[9] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2003/04/09 12:14:53 | Command[10] : -Dwrapper.jvmid=4 DEBUG | wrapper | 2003/04/09 12:14:53 | Command[11] : org.tanukisoftware.wrapper.WrapperSimpleApp DEBUG | wrapper | 2003/04/09 12:14:53 | Command[12] : com.spower.vcc.intf.client.VCCRxClient STATUS | wrapper | 2003/04/09 12:14:53 | Launching a JVM... DEBUG | wrapperp | 2003/04/09 12:14:53 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:53 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:53 | socket creation failed. (11) INFO | jvm 4 | 2003/04/09 12:14:54 | Wrapper Manager: JVM #4 INFO | jvm 4 | 2003/04/09 12:14:54 | Wrapper Manager: Registering shutdown hook INFO | jvm 4 | 2003/04/09 12:14:54 | Wrapper Manager: Using wrapper INFO | jvm 4 | 2003/04/09 12:14:54 | INFO | jvm 4 | 2003/04/09 12:14:54 | WARNING - Unable to load native library 'wrapper' because the INFO | jvm 4 | 2003/04/09 12:14:54 | file 'libwrapper.so' could not be located in the following INFO | jvm 4 | 2003/04/09 12:14:54 | java.library.path: INFO | jvm 4 | 2003/04/09 12:14:54 | /home/vccdev/VCCInt/deploy/lib INFO | jvm 4 | 2003/04/09 12:14:54 | Please see the documentation for the wrapper.java.library.path INFO | jvm 4 | 2003/04/09 12:14:54 | configuration property. INFO | jvm 4 | 2003/04/09 12:14:54 | System signals will not be handled correctly. INFO | jvm 4 | 2003/04/09 12:14:54 | INFO | jvm 4 | 2003/04/09 12:14:54 | Java Version : 1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM INFO | jvm 4 | 2003/04/09 12:14:54 | Java VM Vendor : Hewlett-Packard Company INFO | jvm 4 | 2003/04/09 12:14:54 | INFO | jvm 4 | 2003/04/09 12:14:54 | Wrapper (Version 3.0.1) INFO | jvm 4 | 2003/04/09 12:14:54 | DEBUG | wrapperp | 2003/04/09 12:14:54 | socket creation failed. (11) INFO | jvm 4 | 2003/04/09 12:14:54 | Open socket to wrapper... INFO | jvm 4 | 2003/04/09 12:14:54 | Opened Socket INFO | jvm 4 | 2003/04/09 12:14:54 | Send a packet 110 : DeURD13ZvAbAKXIL INFO | jvm 4 | 2003/04/09 12:14:54 | handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=52349]) DEBUG | wrapperp | 2003/04/09 12:14:54 | accepted a socket from 127.0.0.1 on port 52349 DEBUG | wrapperp | 2003/04/09 12:14:54 | read a packet 110 : DeURD13ZvAbAKXIL DEBUG | wrapper | 2003/04/09 12:14:54 | Got key from JVM: DeURD13ZvAbAKXIL DEBUG | wrapperp | 2003/04/09 12:14:54 | send a packet 112 : 1 DEBUG | wrapperp | 2003/04/09 12:14:54 | socket read failed. (11) DEBUG | wrapper | 2003/04/09 12:14:54 | Start Application. DEBUG | wrapperp | 2003/04/09 12:14:54 | socket creation failed. (11) ERROR | wrapper | 2003/04/09 12:14:54 | Unable to send the start command to the JVM. ERROR | wrapper | 2003/04/09 12:14:54 | JVM did not exit on request, terminated INFO | jvm 4 | 2003/04/09 12:14:55 | Received a packet 112 : 1 INFO | jvm 4 | 2003/04/09 12:14:55 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 4 | 2003/04/09 12:14:55 | Closing socket. DEBUG | wrapperp | 2003/04/09 12:14:55 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:14:55 | JVM was only running for 2 seconds leading to a failed restart count of 4. DEBUG | wrapperp | 2003/04/09 12:14:55 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:55 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:55 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:56 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:56 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:56 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:56 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:57 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:57 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:57 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:57 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:58 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:58 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:58 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:59 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:59 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:59 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:14:59 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:00 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:00 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:00 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:00 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:01 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:15:01 | Command[0] : /opt/java1.3/bin/java DEBUG | wrapper | 2003/04/09 12:15:01 | Command[1] : -Xms3m DEBUG | wrapper | 2003/04/09 12:15:01 | Command[2] : -Xmx64m DEBUG | wrapper | 2003/04/09 12:15:01 | Command[3] : -Djava.library.path=/home/vccdev/VCCInt/deploy/lib DEBUG | wrapper | 2003/04/09 12:15:01 | Command[4] : -classpath DEBUG | wrapper | 2003/04/09 12:15:01 | Command[5] : /home/vccdev/VCCInt/deploy/lib/wrapper.jar:/home/vccdev/VCCInt/deploy/rx.jar DEBUG | wrapper | 2003/04/09 12:15:01 | Command[6] : -Dwrapper.key=8Ye518pRPd9M9tEv DEBUG | wrapper | 2003/04/09 12:15:01 | Command[7] : -Dwrapper.port=1781 DEBUG | wrapper | 2003/04/09 12:15:01 | Command[8] : -Dwrapper.debug=TRUE DEBUG | wrapper | 2003/04/09 12:15:01 | Command[9] : -Dwrapper.cpu.timeout=10 DEBUG | wrapper | 2003/04/09 12:15:01 | Command[10] : -Dwrapper.jvmid=5 DEBUG | wrapper | 2003/04/09 12:15:01 | Command[11] : org.tanukisoftware.wrapper.WrapperSimpleApp DEBUG | wrapper | 2003/04/09 12:15:01 | Command[12] : com.spower.vcc.intf.client.VCCRxClient STATUS | wrapper | 2003/04/09 12:15:01 | Launching a JVM... DEBUG | wrapperp | 2003/04/09 12:15:01 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:01 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:01 | socket creation failed. (11) DEBUG | wrapperp | 2003/04/09 12:15:02 | socket creation failed. (11) INFO | jvm 5 | 2003/04/09 12:15:02 | Wrapper Manager: JVM #5 INFO | jvm 5 | 2003/04/09 12:15:02 | Wrapper Manager: Registering shutdown hook INFO | jvm 5 | 2003/04/09 12:15:02 | Wrapper Manager: Using wrapper INFO | jvm 5 | 2003/04/09 12:15:02 | INFO | jvm 5 | 2003/04/09 12:15:02 | WARNING - Unable to load native library 'wrapper' because the INFO | jvm 5 | 2003/04/09 12:15:02 | file 'libwrapper.so' could not be located in the following INFO | jvm 5 | 2003/04/09 12:15:02 | java.library.path: INFO | jvm 5 | 2003/04/09 12:15:02 | /home/vccdev/VCCInt/deploy/lib INFO | jvm 5 | 2003/04/09 12:15:02 | Please see the documentation for the wrapper.java.library.path INFO | jvm 5 | 2003/04/09 12:15:02 | configuration property. INFO | jvm 5 | 2003/04/09 12:15:02 | System signals will not be handled correctly. INFO | jvm 5 | 2003/04/09 12:15:02 | INFO | jvm 5 | 2003/04/09 12:15:02 | Java Version : 1.3.1.02-011206-02:17 Java HotSpot(TM) Server VM INFO | jvm 5 | 2003/04/09 12:15:02 | Java VM Vendor : Hewlett-Packard Company INFO | jvm 5 | 2003/04/09 12:15:02 | INFO | jvm 5 | 2003/04/09 12:15:02 | Wrapper (Version 3.0.1) INFO | jvm 5 | 2003/04/09 12:15:02 | INFO | jvm 5 | 2003/04/09 12:15:02 | Open socket to wrapper... INFO | jvm 5 | 2003/04/09 12:15:02 | Opened Socket INFO | jvm 5 | 2003/04/09 12:15:02 | Send a packet 110 : 8Ye518pRPd9M9tEv INFO | jvm 5 | 2003/04/09 12:15:02 | handleSocket(Socket[addr=localhost/127.0.0.1,port=1781,localport=52357]) DEBUG | wrapperp | 2003/04/09 12:15:02 | accepted a socket from 127.0.0.1 on port 52357 DEBUG | wrapperp | 2003/04/09 12:15:02 | read a packet 110 : 8Ye518pRPd9M9tEv DEBUG | wrapper | 2003/04/09 12:15:02 | Got key from JVM: 8Ye518pRPd9M9tEv DEBUG | wrapperp | 2003/04/09 12:15:02 | send a packet 112 : 1 DEBUG | wrapperp | 2003/04/09 12:15:02 | socket read failed. (11) DEBUG | wrapper | 2003/04/09 12:15:02 | Start Application. DEBUG | wrapperp | 2003/04/09 12:15:02 | socket creation failed. (11) ERROR | wrapper | 2003/04/09 12:15:02 | Unable to send the start command to the JVM. ERROR | wrapper | 2003/04/09 12:15:02 | JVM did not exit on request, terminated INFO | jvm 5 | 2003/04/09 12:15:03 | Received a packet 112 : 1 INFO | jvm 5 | 2003/04/09 12:15:03 | Wrapper Manager: LowLogLevel from Wrapper is 1 INFO | jvm 5 | 2003/04/09 12:15:03 | Closing socket. DEBUG | wrapperp | 2003/04/09 12:15:03 | socket creation failed. (11) DEBUG | wrapper | 2003/04/09 12:15:03 | JVM was only running for 2 seconds leading to a failed restart count of 5. FATAL | wrapper | 2003/04/09 12:15:03 | There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up. FATAL | wrapper | 2003/04/09 12:15:03 | There may be a configuration problem: please check the logs. DEBUG | wrapperp | 2003/04/09 12:15:03 | socket creation failed. (11) STATUS | wrapper | 2003/04/09 12:15:03 | <-- Wrapper Stopped" Note: $ ls -lrt /home/vccdev/VCCInt/deploy/lib/libwrapper.so -rw-r--r-- 1 vccdev dev 16384 Apr 8 17:51 /home/vccdev/VCCInt/deploy/lib/libwrapper.so Any help/suggestion would be greatly appreciated, Best Regards, Nicolas ____________________________________________________ This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorised to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. |
|
From: Leif M. <le...@ta...> - 2003-04-08 10:51:53
|
I am unable to tell the exact problem unless you post the debug output of a single run but if you have integrated with the Wrapper by implementing the WrapperListener method then the problem is most likely that your implementation of the start method is not returning. But like I said, that is just a guess without being able to see the debug output. To enable debug output, set the following property: wrapper.logfile.loglevel=DEBUG Also review the documentation for the integration method you are using. See the following: http://wrapper.tanukisoftware.org/doc/english/integrate.html Also before trying to get the application running as an NT service, verify that things are working correctly as a console application. Cheers, Leif San...@DM... wrote: >I have a service that it doesn't start in a Windows NT 4.0 server. > >It try to start it but, after a time, it crashes. > >I get next log info: > >ERROR | wrapper | 2003/04/08 10:07:33 | Startup failed: Timed out waiting >for signal from JVM. >ERROR | wrapper | 2003/04/08 10:07:33 | Java Virtual Machine did not exit >on request, terminated >STATUS | wrapper | 2003/04/08 10:07:39 | Launching a JVM... >INFO | jvm 2 | 2003/04/08 10:07:40 | Wrapper (Version 2.2.9) >INFO | jvm 2 | 2003/04/08 10:07:40 | >INFO | jvm 2 | 2003/04/08 10:07:40 | Running TelnetEventPublisher as a >service. >INFO | jvm 2 | 2003/04/08 10:07:40 | Creating thread... > >It try to start five times and wrapper dies. > >In the Windos NT event viewer I get the message below. > >The description for Event ID ( 100 ) in Source ( V-CHAIN Telnet listener ) >cannot be found. The local computer may not have the necessary registry >information or message DLL files to display messages from a remote >computer. The following information is part of the event: wrapper; There >were 5 failed launches in a row, each lasting less than 300 seconds. >Giving up.. > >Thanks in advance. > > |
|
From: <San...@DM...> - 2003-04-08 09:36:20
|
I have a service that it doesn't start in a Windows NT 4.0 server. It try to start it but, after a time, it crashes. I get next log info: ERROR | wrapper | 2003/04/08 10:07:33 | Startup failed: Timed out waiting for signal from JVM. ERROR | wrapper | 2003/04/08 10:07:33 | Java Virtual Machine did not exit on request, terminated STATUS | wrapper | 2003/04/08 10:07:39 | Launching a JVM... INFO | jvm 2 | 2003/04/08 10:07:40 | Wrapper (Version 2.2.9) INFO | jvm 2 | 2003/04/08 10:07:40 | INFO | jvm 2 | 2003/04/08 10:07:40 | Running TelnetEventPublisher as a service. INFO | jvm 2 | 2003/04/08 10:07:40 | Creating thread... It try to start five times and wrapper dies. In the Windos NT event viewer I get the message below. The description for Event ID ( 100 ) in Source ( V-CHAIN Telnet listener ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: wrapper; There were 5 failed launches in a row, each lasting less than 300 seconds. Giving up.. Thanks in advance. |
|
From: <da...@ix...> - 2003-04-05 06:50:42
|
In article <3E8...@ta...>,
Leif Mortenson <wra...@li...> wrote:
>Mike Castle wrote:
>>nt -> NT ?
>Could not find this one.
Oops. Think that one was from the copy of the batch file in the docs.
>>JRockit -> JRocket
In that case, JRocket -> JRockit :->
mrc
--
Mike Castle da...@ix... www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
|
|
From: David O. J. <da...@da...> - 2003-04-05 03:48:15
|
Ah.. That was the one page I had missed in the links I went through. Sorry. I'll go RTFWP now. And thank you Leif. You've written an excellent tool. On Friday, April 04, 2003 6:26 PM, Leif Mortenson <le...@ta...> wrote: > David, > Please read over the following page of the documentation. It describes the > process in great detail. In most cases you will not need to do any coding. > Reading over the integration 3 methods of the documentation all should > become clear. If after reading the documentation you still have questions > then come back and ask, > > http://wrapper.tanukisoftware.org/english/integrate.html > > Cheers, > Leif > > David Orriss Jr wrote: > >> Am I correct in understanding that in order to use the Java Service Wrapper I >> need to write some sort of 'management' class that will 'talk' back to the >> service wrapper to tell it that my program (in this case, WebLogic Server) is >> running OK, etc? If so, are there any simple examples of how to provide this >> service? >> >> Thanks.. >> >> >> > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user -- David Orriss Jr. Please email me if you want my ICQ/AIM/IM ID's. |
|
From: Leif M. <le...@ta...> - 2003-04-05 02:26:46
|
David, Please read over the following page of the documentation. It describes the process in great detail. In most cases you will not need to do any coding. Reading over the integration 3 methods of the documentation all should become clear. If after reading the documentation you still have questions then come back and ask, http://wrapper.tanukisoftware.org/english/integrate.html Cheers, Leif David Orriss Jr wrote: >Am I correct in understanding that in order to use the Java Service Wrapper I >need to write some sort of 'management' class that will 'talk' back to the >service wrapper to tell it that my program (in this case, WebLogic Server) is >running OK, etc? If so, are there any simple examples of how to provide this >service? > >Thanks.. > > > |
|
From: David O. Jr <da...@da...> - 2003-04-05 02:05:45
|
Am I correct in understanding that in order to use the Java Service Wrapp= er I=20 need to write some sort of 'management' class that will 'talk' back to th= e=20 service wrapper to tell it that my program (in this case, WebLogic Server= ) is=20 running OK, etc? If so, are there any simple examples of how to provide = this=20 service? Thanks.. --=20 David Orriss Jr ICQ/AIM/MSN Id's available upon request |
|
From: Pauwels S. <Ste...@si...> - 2003-04-04 05:44:07
|
Hi, Thanks for your fast response, This is exactly the problem I have. I gave the example with CLASSPATH vars, but actually I will use this feature for other variables to. This feature is easy to maintain a lot of setting of my application in just one file which runs as a service on Windows and as a daemon on Solaris. At this moment (version 2.2.5), I replace every env var in the conf files with the env vars defined in one general file. But it is a lot of extra work. Thanks again, and I hope the fixed release 3.0.2 comes out soon. regards, Stefan ---------------------------------------------------------------------------- ------------------- Stefan, Well there is a good reason why you can't get this to work. You found a bug. :-/ This actually has nothing to do with the use of cascading configuration files. I was setting new environment variables before doing any expansion of their values so in this case, JARS variable was being set to the value "%JAR1%;%JAR2%" rather than "test1.jar;test2.jar". Was this the problem that you were seeing? I have committed a fix to CVS and this will be in the 3.0.2 release. I am waiting for other users to test a couple other fixes, but it should be released soon. For now, you will need to avoid setting environment variables which reference other variables themselves. Change to the following: set.JAR1=test1.jar set.JAR2=test2.jar set.JARS=test1.jar;test2.jar As a side note, though while building up a classpath like this will technically work on windows platforms, the resulting config files will not be platform dependent. A better solution would be to actually set the wrapper.java.classpath properties in the include file. Set common values first in the main class and then include other values in your cascading include file. wrapper.conf: --- wrapper.java.classpath.1=../lib/wrapper.jar wrapper.java.classpath.2=../lib/common.jar wrapper.java.classpath.3=../lib/default.jar #include myconf.conf --- myconf.conf: --- wrapper.java.classpath.3=../lib/alt.jar --- The 3rd classpath element would then be overridden if the myconf.conf file exists. Thanks for finding this. Cheers, Leif Pauwels Stefan wrote: >Hello, > >I want to use the cascading of configuration files. >But there's is something that did not work: > >If I put in my vonfig file this: > >... ># include ../conf/myconf > >... > >wrapper.java.classpath.1=%JARS% > >... > >And in my cascaded conf file (myconf): >set.JAR1=test1.jar >set.JAR2=test2.jar >set.JARS=%JAR1%;%JAR2% >... > > >This won't work. >Can someone help me please, > >Kind regards, > > Stefan Pauwels > E-mail: * Stefan.Pauwels@si... > > |
|
From: David O. Jr <da...@da...> - 2003-04-03 23:13:36
|
I appreciate the response. WebLogic has a way of operating that is prett= y=20 different from any other application server I've seen. I guess I'll just= =20 dive in and take a shot at it.. Thanks for the input. On Thursday 03 April 2003 14:56, Richard Emberson wrote: > David, > > I've wrapped JBoss (and a bunch of other apps). No problems that a coup= le > of days of hands on learning > did not resolve. > > Richard > > David Orriss Jr wrote: > > Hello, > > > > I just discovered through a coworker the Java Service Wrapper project= =2E=20 > > This looks like it could be just what I need on my project. I'm runn= ing > > WebLogic 7.0 here in a managed server configuration. A managed serve= r > > configuration consists of two JVM's - one for each weblogic instance= =2E=20 > > And the second instance relies on the first one to be already running > > before the second one starts. I have written startup scripts in Linu= x to > > handle this, however I'd like something a bit more robust and somethi= ng > > that will *also* move over to Solaris. So, my questions are: > > > > - Has anyone used wrapper with WLS 7? > > - Have you used a managed server configuration with wrapper? > > - Did you run into any serious issues that kept wrapper from being a > > solution for your needs? > > - Do you have any tips/advice/config files you can share? > > > > Thanks in advance.... > > > > -- > > > > David Orriss Jr > > ICQ/AIM/MSN Id's available upon request > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ValueWeb: > > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > > No other company gives more support or power for your dedicated serve= r > > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > > _______________________________________________ > > Wrapper-user mailing list > > Wra...@li... > > https://lists.sourceforge.net/lists/listinfo/wrapper-user > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user --=20 David Orriss Jr ICQ/AIM/MSN Id's available upon request |
|
From: Richard E. <rem...@ou...> - 2003-04-03 22:56:47
|
David, I've wrapped JBoss (and a bunch of other apps). No problems that a couple of days of hands on learning did not resolve. Richard David Orriss Jr wrote: > Hello, > > I just discovered through a coworker the Java Service Wrapper project. This > looks like it could be just what I need on my project. I'm running WebLogic > 7.0 here in a managed server configuration. A managed server configuration > consists of two JVM's - one for each weblogic instance. And the second > instance relies on the first one to be already running before the second one > starts. I have written startup scripts in Linux to handle this, however I'd > like something a bit more robust and something that will *also* move over to > Solaris. So, my questions are: > > - Has anyone used wrapper with WLS 7? > - Have you used a managed server configuration with wrapper? > - Did you run into any serious issues that kept wrapper from being a solution > for your needs? > - Do you have any tips/advice/config files you can share? > > Thanks in advance.... > > -- > > David Orriss Jr > ICQ/AIM/MSN Id's available upon request > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user |
|
From: David O. Jr <da...@da...> - 2003-04-03 22:32:42
|
Hello, I just discovered through a coworker the Java Service Wrapper project. T= his=20 looks like it could be just what I need on my project. I'm running WebLo= gic=20 7.0 here in a managed server configuration. A managed server configurati= on=20 consists of two JVM's - one for each weblogic instance. And the second=20 instance relies on the first one to be already running before the second = one=20 starts. I have written startup scripts in Linux to handle this, however = I'd=20 like something a bit more robust and something that will *also* move over= to=20 Solaris. So, my questions are: - Has anyone used wrapper with WLS 7? - Have you used a managed server configuration with wrapper? - Did you run into any serious issues that kept wrapper from being a solu= tion=20 for your needs? - Do you have any tips/advice/config files you can share? Thanks in advance.... --=20 David Orriss Jr ICQ/AIM/MSN Id's available upon request |
|
From: Leif M. <le...@ta...> - 2003-04-03 16:25:27
|
Stefan,
Well there is a good reason why you can't get this to work. You
found a bug. :-/
This actually has nothing to do with the use of cascading configuration
files. I was
setting new environment variables before doing any expansion of their
values so
in this case, JARS variable was being set to the value "%JAR1%;%JAR2%"
rather than "test1.jar;test2.jar".
Was this the problem that you were seeing?
I have committed a fix to CVS and this will be in the 3.0.2 release.
I am waiting
for other users to test a couple other fixes, but it should be released
soon.
For now, you will need to avoid setting environment variables which
reference
other variables themselves. Change to the following:
set.JAR1=test1.jar
set.JAR2=test2.jar
set.JARS=test1.jar;test2.jar
As a side note, though while building up a classpath like this will
technically
work on windows platforms, the resulting config files will not be platform
dependent. A better solution would be to actually set the
wrapper.java.classpath properties in the include file. Set common
values first
in the main class and then include other values in your cascading
include file.
wrapper.conf:
---
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/common.jar
wrapper.java.classpath.3=../lib/default.jar
#include myconf.conf
---
myconf.conf:
---
wrapper.java.classpath.3=../lib/alt.jar
---
The 3rd classpath element would then be overridden if the myconf.conf
file exists.
Thanks for finding this.
Cheers,
Leif
Pauwels Stefan wrote:
>Hello,
>
>I want to use the cascading of configuration files.
>But there's is something that did not work:
>
>If I put in my vonfig file this:
>
>...
># include ../conf/myconf
>
>...
>
>wrapper.java.classpath.1=%JARS%
>
>...
>
>And in my cascaded conf file (myconf):
>set.JAR1=test1.jar
>set.JAR2=test2.jar
>set.JARS=%JAR1%;%JAR2%
>...
>
>
>This won't work.
>Can someone help me please,
>
>Kind regards,
>
> Stefan Pauwels
> E-mail: * Ste...@si...
>
>
|
|
From: Pauwels S. <Ste...@si...> - 2003-04-03 14:27:53
|
Hello, I want to use the cascading of configuration files. But there's is something that did not work: If I put in my vonfig file this: ... # include ../conf/myconf ... wrapper.java.classpath.1=%JARS% ... And in my cascaded conf file (myconf): set.JAR1=test1.jar set.JAR2=test2.jar set.JARS=%JAR1%;%JAR2% ... This won't work. Can someone help me please, Kind regards, Stefan Pauwels E-mail: * Ste...@si... |
|
From: Leif M. <le...@ta...> - 2003-04-03 08:30:40
|
Clement,
I also just noticed from the generated Java command line, that you
appear
to have the following two properties set in your configuration file:
wrapper.java.initmemory=256
wrapper.java.maxmemory=256
The max memory setting is fine, but is there a reason to set the
init memory
so high? The JVM will have to allocate all of that memory on start up.
This
could be part of the reason why your application is so slow on that machine.
The machine I am currently working on has 768Mb of actual memory, so I was
tried setting the above settings to 900 each. The test apps are indeed
quite
a bit slower on startup. But I was was still not seeing the problem you are
having.
How much memory does that machine have available. If you give Java more
memory than the amount of actual memory available then the OS has to start
swapping memory to make the requested memory available. In my experience
Java does not perform very well under these circumstances. Depending on the
amount of disk swapping that is required to let the JVM access its required
memory, the application can be slowed down by a couple orders of magnitude.
So can you tell me how much actual and virtual memory is available
before you
launch the JVM?
Can you also perform your test and send me the resulting log file
when the
wrapper.java.initmemory=16
Thanks,
Leif
Leif Mortenson wrote:
> Clement,
> Thanks for the log files they were very helpful. I think that the
> problem is
> most likely that the Wrapper is not getting hardly any CPU at all. I
> see cases
> where the time stamps from the JVM are outputting a hundred or so
> lines of
> output all with the exact same time stamp, but the time stamps from
> the Wrapper
> show that it is taking well over a minute to output all of them.
> Because it was
> outputting around 1 line per second, it was taking over 50 seconds to
> output 50
> lines of output from the JVM. Thus, in the severe case you are
> seeing, my fix
> did not work correctly.
>
> I made another attempt at fixing this by making the function that
> processes
> JVM output yield CPU to the event loop after 250ms rather than 50
> lines of
> output. Originally I had thought that counting to 50 would be a
> lighter operation
> than getting the time so many times. This new fix should work even in
> the
> severe loading situation that you appear to be seeing.
>
> I have checked this fix into CVS and will email you an 3.0.2a
> release off list.
> Could you please test this new version on the problematic machine and
> let me
> know the results? Whether it works or not, I would like to get at
> least two runs
> with debug output enabled and the log format set to LPTM so I can take
> a look
> and make sure it is behaving as I expect.
>
> Could you also verify that the system CPU is indeed pegged at 100%
> while
> the application is starting up? I want to make sure it is not some
> other problem
> that I have not thought of.
>
> That is turning out to be a good test machine. :-)
>
> Cheers,
> Leif
>
>
>
> Clement, Nathan wrote:
>
>> Lief,
>>
>> We set the log level as requested and the problem did not occur. We
>> then
>> tried various combinations of the log parameters with the results below:
>>
>> M+INFO=FAIL
>> LPTM+DEBUG=WORK
>> LPTM+INFO=FAIL
>> M+DEBUG=FAIL
>>
>> PTM+DEBUG=FAIL
>> LM+DEBUG=FAIL
>>
>> I'm not sure why this occurs. The log file for this is attached. I
>> think
>> you can tell which part of the log corresponds to which parameter
>> combination based on what the log contains.
>>
>> Regards,
>>
>> Nathan
>>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for
> just $79/mo with 500 GB of bandwidth! No other company gives more
> support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
|
|
From: Leif M. <le...@ta...> - 2003-04-03 08:12:24
|
Clement,
Thanks for the log files they were very helpful. I think that the
problem is
most likely that the Wrapper is not getting hardly any CPU at all. I
see cases
where the time stamps from the JVM are outputting a hundred or so lines of
output all with the exact same time stamp, but the time stamps from the
Wrapper
show that it is taking well over a minute to output all of them.
Because it was
outputting around 1 line per second, it was taking over 50 seconds to
output 50
lines of output from the JVM. Thus, in the severe case you are seeing,
my fix
did not work correctly.
I made another attempt at fixing this by making the function that
processes
JVM output yield CPU to the event loop after 250ms rather than 50 lines of
output. Originally I had thought that counting to 50 would be a lighter
operation
than getting the time so many times. This new fix should work even in the
severe loading situation that you appear to be seeing.
I have checked this fix into CVS and will email you an 3.0.2a
release off list.
Could you please test this new version on the problematic machine and let me
know the results? Whether it works or not, I would like to get at least
two runs
with debug output enabled and the log format set to LPTM so I can take a
look
and make sure it is behaving as I expect.
Could you also verify that the system CPU is indeed pegged at 100% while
the application is starting up? I want to make sure it is not some
other problem
that I have not thought of.
That is turning out to be a good test machine. :-)
Cheers,
Leif
Clement, Nathan wrote:
>Lief,
>
>We set the log level as requested and the problem did not occur. We then
>tried various combinations of the log parameters with the results below:
>
>M+INFO=FAIL
>LPTM+DEBUG=WORK
>LPTM+INFO=FAIL
>M+DEBUG=FAIL
>
>PTM+DEBUG=FAIL
>LM+DEBUG=FAIL
>
>I'm not sure why this occurs. The log file for this is attached. I think
>you can tell which part of the log corresponds to which parameter
>combination based on what the log contains.
>
>Regards,
>
>Nathan
>
|
|
From: Leif M. <le...@ta...> - 2003-04-03 04:05:36
|
Mike Castle wrote: >Ok.. I caught one then got bored and busy with aspell. > Ouch. That long list was embarrassing. I just home my kids never find this in the list archives when I just got chewing them out for not studying... :-) Thanks for the help. I have been accused of many things over the years, but "knowing how to spell" was never one of them :-) Most of these are fixed. See below: >nt -> NT ? > Could not find this one. >JRockit -> JRocket > The name of this JVM is "BEA WebLogic JRockit" I thought it was strange the first time I saw it as well. Please let me know if you find any others. Cheers, Leif |
|
From: Leif M. <le...@ta...> - 2003-04-03 02:58:30
|
Clement,
The messages about extending timeouts are being caused by either the
Wrapper or JVM process not receiving CPU for an extended period of time.
This can happen for a number of reasons including one or more applications
on the system consuming all the CPU. The messages about extending
timeouts are not a problem, they are merely telling you that that other
timeouts like the ping timeout are being extended.
The log that you sent contains lots of information about your
application,
but unfortunately, it doesn't tell me very much about what is going on with
the Wrapper. I know it is a pain as this is at a customer site, but
could you
set the following properties and then send me the resulting log file? Go
ahead and post the reply message to the list, but only send the log file
to me
off list, no reason to post the whole thing to the list as it is a bit
large.
Send me the full log file without any trimming. Include two failed startups
as a service and one as a console so I can compare them.
wrapper.logfile.format=LPTM
wrapper.logfile.loglevel=DEBUG
Cheers,
Leif
Clement, Nathan wrote:
>Leif,
>
>The new configurable Java side timeout sounds like a good idea. We haven't
>had any problems with the application in question overnight, which is
>obviously a good start.
>
>However, we have had a similar problem with another application in a
>customer's environment. This environment seems unique in some way, because
>we can't replicate the problem in any of our test environments. I have
>attached the log of the wrapper trying to start the JVM. The key lines I
>saw are as follows:
>
>Wrapper Process has not received any CPU time for 52 seconds. Extending
>timeouts.
>
>The Wrapper code did not ping the JVM for 40 seconds. Quit and let the
>wrapper resynch.
>
>The problem occurs continually on startup - the wrapper starts the JVM, then
>the application almost starts up, and finally quits because it has not been
>pinged for 30 seconds. The restarts occur repeatedly until the wrapper
>gives up. I don't know why the wrapper process is not getting any CPU for
>this long - the logging on startup is not what I'd call excessive (only
>about 60k per start-up).
>
>The interesting thing is that if the wrapper is run interactively (not as a
>service), the application starts fine and continues to work without
>problems.
>
>Since this is a customer's environment, any suggestions you can provide
>would be welcome.
>
>Thanks again,
>
>Nathan
>
>
|
|
From: Leif M. <le...@ta...> - 2003-04-03 01:56:20
|
Jindong, > you guys did a great job!! > Thanks :-) > · The WrapperManager detects if there's any non-daemon threads > other than the current thread and system thread running after the > application is launched, in my case since all my threads are daemon > threads, I had to start another thread in my listener code to run > indefinitely until it receives the stop control from the service > panel...otherwise, the service will be stopped right after it was > started, any other way to get around that ? > The Wrapper should be following the same rules as the regular Java executable when run without the Wrapper. The Wrapper has to do its own thread counting because it starts its own non-daemon thread. If the Wrapper did not do any special counting of the threads, then the JVM would never shutdown. By waiting until there is only one non-daemon thread running, the Wrapper is able to work around this. What happens when you run your application without the Wrapper or its helper classes. If you truly do not have any non-daemon threads running then Java should assume that your application is stopped and exit. That is the difference between daemon and non-daemon threads. What JVM are you running? This may be an issue with a JVM I have not seen before? > · When I use the command line command "net start/stop" to start > / stop the service I installed using wrapper.exe, starting is always > successful without any issue but stopping, on the other hand, I often > get "... service could not be stopped." even though the service has > been stopped indeed...any idea? This problem does not appear to exist > if stopping from the GUI. > I will need more info to tell you the problem without guessing. Could you enable debug output and then post the wrapper.log file that contains both the startup and shutdown of a single run of your application. Delete any existing log file first so you don't send the log of multiple invocations. Cheers, Leif P.S. There is no need to cc the wrapper-cvs list as that just gets me 2 copies of your mail. :-) |
|
From: <da...@ix...> - 2003-04-03 00:55:50
|
Ok.. I caught one then got bored and busy with aspell.
instalation -> installation
backgroud -> background
demonstratehow -> demonstrate how
lowlevel -> low level (or low-level... being picky here :-)
Wrapepr -> Wrapper
interresting -> interesting
simmilar -> similar
lifecycle -> life-cycle (again, picky)
concidered -> considered
concered -> concerned
shutsdown -> shuts down (if logs out is 2 words, so should shuts down)
<tt>dum</tt>p -> <tt>dump</tt>
logouts -> log outs
broser -> browser
assumtions -> assumptions
sublicense -> sub-license
NONINFRINGEMENT -> NON-INFRINGEMENT
extenstion -> extension
avoind -> avoid
config -> configuration (bit more polished?)
appplication -> application
bugfixes -> bug fixes
HPUX -> HP-UX (or the other way around)
linux -> Linux
thier -> their
ablility -> ability
launchine -> launching
applicaiton -> application
indeffinately -> indefinitely
Sorlen -> Sorlin (or vice-versa)
nt -> NT ?
JRockit -> JRocket
--
Mike Castle da...@ix... www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
|
|
From: Clement, N. <ncl...@qv...> - 2003-04-03 00:21:48
|
Here's the message again with the log trimmed more -----Original Message----- From: Clement, Nathan Sent: Thursday, 3 April 2003 10:13 To: 'wra...@li...' Subject: RE: Disabling JVM ping Leif, The new configurable Java side timeout sounds like a good idea. We haven't had any problems with the application in question overnight, which is obviously a good start. However, we have had a similar problem with another application in a customer's environment. This environment seems unique in some way, because we can't replicate the problem in any of our test environments. I have attached the log of the wrapper trying to start the JVM. The key lines I saw are as follows: Wrapper Process has not received any CPU time for 52 seconds. Extending timeouts. The Wrapper code did not ping the JVM for 40 seconds. Quit and let the wrapper resynch. The problem occurs continually on startup - the wrapper starts the JVM, then the application almost starts up, and finally quits because it has not been pinged for 30 seconds. The restarts occur repeatedly until the wrapper gives up. I don't know why the wrapper process is not getting any CPU for this long - the logging on startup is not what I'd call excessive (only about 60k per start-up). The interesting thing is that if the wrapper is run interactively (not as a service), the application starts fine and continues to work without problems. Since this is a customer's environment, any suggestions you can provide would be welcome. Thanks again, Nathan From: Leif Mortenson <leif@ta...> Re: RE: Disabling JVM ping 2003-04-02 02:08 Wow, you want to disable the feature that led me to create the Wrapper in the first place... Having just had problems with restarting I can understand your concern. But in general, the Wrapper is quite good about only restarting the JVM when it is really necessary. The ability to sleep well at night and put the old pager in the bottom drawer where it belongs should be viewed as a good thing :-) The wrapper.ping.timeout property controls how long the Wrapper will allow to pass without the JVM responding to a ping. The problem was inverted in your case. The Wrapper process was busy and failed to ping the JVM. The JVM side of the Wrapper has a feature that will cause it to exit and let the Wrapper restart it if it ever fails to be pinged for a long period of time. The thinking there was to avoid the JVM turning into a zombie process if the Wrapper process ever died abnormally. The fact that this Java side timeout is hard coded at 30 seconds was an oversight. It should have been the same as the ping timeout on the Wrapper side. A fix is now in CVS and will be in the 3.0.2 release. I don't want to do a release just for this as it is not a critical problem. Unless you really need this immediately for some reason, I'll wait until there are more things needing to be released. You can also do a build from CVS to get it sooner. Cheers, Leif |
|
From: Jindong Li <Jin...@so...> - 2003-04-02 16:05:48
|
Hi there, I'm currently exploring the possibility of using Java Service Wrapper to run our Java application as an NT service (Windows 2000 professional), everything is going well so far...you guys did a great job!! I do have couple of questions: * The WrapperManager detects if there's any non-daemon threads other than the current thread and system thread running after the application is launched, in my case since all my threads are daemon threads, I had to start another thread in my listener code to run indefinitely until it receives the stop control from the service panel...otherwise, the service will be stopped right after it was started, any other way to get around that ? * When I use the command line command "net start/stop" to start / stop the service I installed using wrapper.exe, starting is always successful without any issue but stopping, on the other hand, I often get "... service could not be stopped." even though the service has been stopped indeed...any idea? This problem does not appear to exist if stopping from the GUI. Thanks and really appreciate your help... Jindong. ##################################################################################### This e-mail message has been scanned for Viruses and Content and cleared by MailMarshal ##################################################################################### |
165 messages has been excluded from this view by a project administrator.
