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: Haig E. <ha...@ca...> - 2004-11-26 16:43:35
|
Hello, I've noticed in a couple of places that you have a .stripquotes wrapper.java.additional.1=-Xrs wrapper.java.additional.2=-Dprop=TRUE wrapper.java.additional.3=-Dmyapp.data="../data" wrapper.java.additional.3.stripquotes=TRUE Would this work in the following scenario? wrapper.java.library.path.1=../lib1 wrapper.java.library.path.2=../lib2 wrapper.java.library.path.3=../lib3 wrapper.java.library.path.append_system_path=true wrapper.java.library.path.stripquotes=true Some applications installed on certain Win32 machines put quotes in the PATH. This, in turn, prevents my application from running. Haig Ehramdjian, B. Comp. Sci. Developer - Engineering Support Group http://esg.cae.ca/esg > Military Simulation and Training > CAE Inc. > Tel: 514-341-2000, ext: 2017 > ha...@ca... > > PROPRIETARY NOTICE: The information contained herein is confidential > and/or proprietary to CAE Inc., and shall not be reproduced or disclosed > in whole or in part, or used for any purpose whatsoever unless authorized > in writing by CAE Inc > |
|
From: Love, E. <EB...@ic...> - 2004-11-26 11:28:29
|
Thanks, Leif! I will give that a shot and let you know how it works =
out.
-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Leif
Mortenson
Sent: Wednesday, November 24, 2004 7:12 PM
To: wra...@li...
Subject: Re: [Wrapper-user] <DEFUNCT> java processes on Solaris
Erik,
This looks like the same problem that had me stumped for about a=20
month. One of my
customers was experiencing this same problem.
After much debugging, the problem was being caused by the usleep()=20
system function.
Solaris appears to have a problem where the usleep function will not=20
always return if the
process receives a signal while sleeping. The fix was to switch from=20
using usleep() to
using nanosleep. This fix was implemented in version 3.1.2.
My customer had been experiencing the problem on a single machine=20
about once
every 72 hours. Since the fix was made it has been running for a=20
couple months without
any further problems.
Please try upgrading to 3.1.2 and giving it a try. You should not=20
need any other
configuration changes.
As a note, it appears that the usleep function would hang up until=20
the process received
another signal. At which point it would immediately start working=20
correctly again. The
problem is that the main event loop of the Wrapper was hung. It is=20
responsible for pinging
the JVM, processing JVM output etc.
In your log file, you see that log output stopped at '2004/11/22=20
13:02:14' and then
resumed at '2004/11/24 09:20:42' when the Wrapper received a signal. =20
The problem is
that at this point, the JVM had long given up and quit to let its=20
backend socket be
resynched by the Wrapper process. All related output from the JVM had=20
been queued
up in the Wrapper's pipe buffers for a couple days. This makes the JVM=20
appear to have
shutdown when the signal was received when in reality it had actualy=20
shutdown a couple
days earlier.
The only difference between your case and what I had seen was that=20
in your case,
the Wrapper is exiting. In my case, the Wrapper was launching a new=20
JVM after
recovering. This may have something to do with your WrapperListener=20
implementation.
I had been using the WrapperSimpleApp class.
Cheer,
Leif
Love, Erik wrote:
>Hi,
>
>I am using Wrapper 3.1.1 on a Sun Solaris 8 platform and using java =
1.4.2_04-b05. The wrapper kicks off a scheduling program which runs =
great for a period of time and then without any warning or apparent =
cause goes into a defunct state. Most recently, it shut down the =
afternoon of the 22nd and didn't recover until the process was manually =
killed today by the unix admin. After the admin killed the process, the =
wrapper wrote the Wrapper Process has not received any CPU time for =
159507 seconds message to the log...
>
>I have looked at the info regarding the new tick timer, but it doesn't =
seem to be the same issue. Any ideas would be greatly appreciated. I =
have included an excerpt from the log (with the debug option turned =
on)... A side note, we have another wrapper-based application that runs =
as an NT service. This application has been running since December 2003 =
and has never experienced this issue.
>
>2004/11/22 13:02:14 | send a packet PING : ping
>2004/11/22 13:02:14 | Received a packet PING : ping
>2004/11/22 13:02:14 | Send a packet PING : ok
>2004/11/22 13:02:14 | read a packet PING : ok
>2004/11/22 13:02:14 | Got ping response from JVM
>2004/11/24 09:20:42 | Signal trapped. Details:
>2004/11/24 09:20:42 | signal number=3D15, source=3D"kill, sigsend or =
raise"
>2004/11/24 09:20:42 | signal generated by PID: 22857 (Session PID: =
22813), UID: 0 (root)
>2004/11/24 09:20:42 | TERM trapped. Shutting down.
>2004/11/24 09:20:42 | wrapperStopProcess(0) called.
>2004/11/24 09:20:42 | Read Timed out. (Last Ping was 30000 milliseconds =
ago)
>2004/11/24 09:20:42 | Still alive
>2004/11/24 09:20:42 | Read Timed out. (Last Ping was 60000 milliseconds =
ago)
>2004/11/24 09:20:42 | Wrapper Manager: The Wrapper code did not ping =
the JVM for 60 seconds. Quit and let the Wrapper resynch.
>2004/11/24 09:20:42 | Send a packet RESTART : restart
>2004/11/24 09:20:42 | Thread, Wrapper-Connection, handling the shutdown =
process.
>2004/11/24 09:20:42 | calling listener.stop()
>2004/11/24 09:20:42 | Stopping the RC Scheduler Application
>2004/11/24 09:20:42 | returned from listener.stop()
>2004/11/24 09:20:42 | Send a packet STOPPED : 0
>2004/11/24 09:20:42 | Closing socket.
>2004/11/24 09:20:42 | calling System.exit(1)
>2004/11/24 09:20:42 | read a packet RESTART : restart
>2004/11/24 09:20:42 | JVM requested a restart.
>2004/11/24 09:20:42 | wrapperRestartProcess() called. (IGNORED)
>2004/11/24 09:20:42 | read a packet STOPPED : 0
>2004/11/24 09:20:42 | JVM signalled that it was stopped.
>2004/11/24 09:20:42 | socket read no code (closed?).
>2004/11/24 09:20:42 | Wrapper Process has not received any CPU time for =
159507 seconds. Extending timeouts.
>2004/11/24 09:20:42 | JVM process exited with a code of 1, setting the =
wrapper exit code to 1.
>2004/11/24 09:20:42 | JVM exited normally.
>2004/11/24 09:20:42 | <-- Wrapper Stopped
>2004/11/24 09:20:45 | Spawning intermediate process...
>2004/11/24 09:20:45 | Spawning daemon process...
>2004/11/24 09:20:45 | --> Wrapper Started as Daemon
>2004/11/24 09:20:45 | Using system timer.
>2004/11/24 09:20:45 | server listening on port 32000.
>2004/11/24 09:20:45 | Classpath element, wrapper.java.classpath.11, =
does not exist: /apps/java/ira.jar
>2004/11/24 09:20:45 | Classpath element, wrapper.java.classpath.24, =
does not exist: /apps/java/output.txt
>2004/11/24 09:20:45 | Command[0] : java
>2004/11/24 09:20:45 | Command[1] : -Xms256m
>2004/11/24 09:20:45 | Command[2] : -Xmx768m
>2004/11/24 09:20:45 | Command[3] : =
-Djava.library.path=3D/apps/RCScheduler/lib
>2004/11/24 09:20:45 | Command[4] : -classpath
>2004/11/24 09:20:45 | Command[5] : =
../lib/wrapper.jar:/apps/java/rcscheduler.jar:/apps/java/vantage.jar:/app=
s/java/vantageadmin.jar:/apps/java/rcmailings.jar:/apps/java/acme.jar:/ap=
ps/java/activation.jar:/apps/java/avalon.jar:/apps/java/batik.jar:/apps/j=
ava/fop.jar:/apps/java/ira.jar:/apps/java/itext.jar:/apps/java/j2ee.jar:/=
apps/java/jai_codec.jar:/apps/java/jakarta-oro-2.0.7.jar:/apps/java/jdom.=
jar:/apps/java/jlink.jar:/apps/java/log4j.jar:/apps/java/mail.jar:/apps/j=
ava/netcharts.jar:/apps/java/NetComponents-1_3_8.jar:/apps/java/ojdbc14.j=
ar:/apps/java/oreilly.jar:/apps/java/output.txt:/apps/java/pja.jar:/apps/=
java/pjatools.jar:/apps/java/Tidy.jar:/apps/java/wrapper.jar:/apps/java/x=
alan.jar:/apps/java/xerces.jar:/apps/java/xml-apis.jar:/apps/java/xp-asse=
ts.jar:/apps/java/weblogic.jar
>2004/11/24 09:20:45 | Command[6] : -Dwrapper.key=3D4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:45 | Command[7] : -Dwrapper.port=3D32000
>2004/11/24 09:20:45 | Command[8] : -Dwrapper.debug=3DTRUE
>2004/11/24 09:20:45 | Command[9] : -Dwrapper.use_system_time=3DTRUE
>2004/11/24 09:20:45 | Command[10] : -Dwrapper.version=3D3.1.1
>2004/11/24 09:20:45 | Command[11] : -Dwrapper.native_library=3Dwrapper
>2004/11/24 09:20:45 | Command[12] : -Dwrapper.service=3DTRUE
>2004/11/24 09:20:45 | Command[13] : -Dwrapper.cpu.timeout=3D10
>2004/11/24 09:20:45 | Command[14] : -Dwrapper.jvmid=3D1
>2004/11/24 09:20:45 | Command[15] : =
org.icmarc.scheduler.application.Scheduler
>2004/11/24 09:20:45 | Command[16] : ./RCScheduler.cfg
>2004/11/24 09:20:45 | Launching a JVM...
>2004/11/24 09:20:46 | WrapperManager class initialized by thread: main =
Using classloader: sun.misc.Launcher$AppClassLoader@67ac19
>2004/11/24 09:20:46 | Wrapper Manager: JVM #1
>2004/11/24 09:20:46 | Wrapper Manager: Registering shutdown hook
>2004/11/24 09:20:46 | Wrapper Manager: Using wrapper
>2004/11/24 09:20:47 | Loaded native library: libwrapper.so
>2004/11/24 09:20:47 | Calling native initialization method.
>2004/11/24 09:20:47 | Inside native WrapperManager initialization =
method
>2004/11/24 09:20:47 | Java Version : 1.4.2_04-b05 Java HotSpot(TM) =
Client VM
>2004/11/24 09:20:47 | Java VM Vendor : Sun Microsystems Inc.
>2004/11/24 09:20:47 |=20
>2004/11/24 09:20:47 | Wrapper (Version 3.1.1) =
http://wrapper.tanukisoftware.org
>2004/11/24 09:20:47 |=20
>2004/11/24 09:20:47 | =
WrapperManager.start(org.icmarc.scheduler.application.Scheduler@e102dc, =
args["./RCScheduler.cfg"]) called by thread: main
>2004/11/24 09:20:47 | Open socket to wrapper...
>2004/11/24 09:20:47 | Opened Socket
>2004/11/24 09:20:47 | Send a packet KEY : 4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:47 | =
handleSocket(Socket[addr=3D/127.0.0.1,port=3D32000,localport=3D36727])
>2004/11/24 09:20:47 | accepted a socket from 127.0.0.1 on port 36727
>2004/11/24 09:20:47 | read a packet KEY : 4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:47 | Got key from JVM: 4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:47 | send a packet LOW_LOG_LEVEL : 1
>2004/11/24 09:20:47 | send a packet PING_TIMEOUT : 30
>2004/11/24 09:20:47 | Start Application.
>2004/11/24 09:20:47 | send a packet START : start
>2004/11/24 09:20:47 | Received a packet LOW_LOG_LEVEL : 1
>2004/11/24 09:20:47 | Wrapper Manager: LowLogLevel from Wrapper is 1
>2004/11/24 09:20:47 | Received a packet PING_TIMEOUT : 30
>2004/11/24 09:20:47 | Wrapper Manager: PingTimeout from Wrapper is =
30000
>2004/11/24 09:20:47 | Received a packet START : start
>2004/11/24 09:20:47 | calling listener.start()
>2004/11/24 09:20:48 | Initializing the RC Scheduler Application
>
>
>-------------------------------------------------------
>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.=20
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
> =20
>
-------------------------------------------------------
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.=20
http://productguide.itmanagersjournal.com/
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: <ste...@ce...> - 2004-11-26 09:09:12
|
The user is the same (sure).
The directory tree is :
serviceroot
|
---bin
| |
| ---wrapper
| |
| ---sh.script
|
---conf
| |
| ---wrapper.conf
|
---lib
|
---logs
In the wrapper.conf : wrapper.working.dir="../"
In sh.script : PIDDIR="."
When i start the service (with user "steff"), the MYAPP.pid file is in
the "serviceroot" directory.
When i want to stop (with user "steff"), the sh.script complains that
"service not running". but
if i print $PIDFILE in the sh.script, it display : "./MYAPP.pid" : seems
good if the working directory
is really set to "serviceroot"
Maybe i missunderstood about working dir but if someone can points me to
the right solution.....
Thanks to answerers
Leif Mortenson wrote:
> Stephane,
> My first guess here is a permission problem. Are you starting the
> wrapper as the same
> user that you are later attempting stop it with? I may have some
> problems there but I have
> not heard of any to date. Give me a little more info and I'll go back
> and look over the
> script some more.
>
> Cheers,
> Leif
>
> Stéphane RIFF wrote:
>
>> I have problem with the pid file :
>> in sh.script.in i have PIDDIR=".", the 'start ' command seems to
>> place pidfile in the right location.
>> but when i try to launch a 'stop' command the script tell me that the
>> daemon isn't running .
>>
>> I also echo some variable and the $PIDFILE is : "./MYAPPNAME.pid" so
>> i don't understand why the line : "if [ -f $PIDFILE ]" is not true
>>
>> I don't know if i'm understandable but i suspect there a problem with
>> the sh.script.in and the wrapper.working.dir.
>>
>> any hints are welcome
>> Thanks
>>
>>
>> -------------------------------------------------------
>> 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
>>
>
>
>
> -------------------------------------------------------
> 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
>
|
|
From: Leif M. <le...@ta...> - 2004-11-26 08:55:08
|
Hi all, In version 3.1.0 of the Wrapper, I added a new experimental tick based timer to replace the timing mechanism that had existed in all previous versions of the product. It can be enabled by setting the following property: wrapper.use_system_time=false Version 3.1.0 turned out to have a couple bugs, but 3.1.1 and 3.1.2 have proved to be much more reliable than the old system time based timer. I have been using this new timer for a few months now on all of my customer applications without any problems. It appears to be much more stable when the system is under heavy loads. This means that you are much less likely to get unwanted restarts etc. I never got much feedback from anyone on how this new timer has been working. :-/ Unless I hear any negative feedback, I am planning to make this new timer the default in the next release of the Wrapper. The old system based timer will still be available by setting the above property to true: wrapper.use_system_time=true The next release is still a ways off, but I would not mind hearing some feedback one way or another. Timing is extremely critical to the inner workings of the Wrapper so it would be good make sure this feature gets as much testing as possible. Especially under high load / low resource environments. Cheers, Leif |
|
From: Leif M. <le...@ta...> - 2004-11-26 08:09:11
|
Stephane,
My first guess here is a permission problem. Are you starting the
wrapper as the same
user that you are later attempting stop it with? I may have some
problems there but I have
not heard of any to date. Give me a little more info and I'll go back
and look over the
script some more.
Cheers,
Leif
Stéphane RIFF wrote:
> I have problem with the pid file :
> in sh.script.in i have PIDDIR=".", the 'start ' command seems to
> place pidfile in the right location.
> but when i try to launch a 'stop' command the script tell me that the
> daemon isn't running .
>
> I also echo some variable and the $PIDFILE is : "./MYAPPNAME.pid" so
> i don't understand why the line : "if [ -f $PIDFILE ]" is not true
>
> I don't know if i'm understandable but i suspect there a problem with
> the sh.script.in and the wrapper.working.dir.
>
> any hints are welcome
> Thanks
>
>
> -------------------------------------------------------
> 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
>
|
|
From: Leif M. <le...@ta...> - 2004-11-26 08:06:53
|
Haig,
This has not been possible in any released versions of the Wrapper
simply because I had
not been able to figure out how to get it working correctly in a
reliable way.
I gave it a try again today and was finally able to figure out how
to resolve my previous
problems. So good news. This will be implemented in the next release.
Bad news, for now at least. Is that the Wrapper is undergoing
several other feature
improvements at the moment. Unless there are any bad bugs found, I was
not planning
on doing another release until after new years some time. You are
welcome to build
your own version from source if you like, but I do not want to do a
release until I have
gotten some of the new APIs worked out.
Cheers,
Leif
Haig Ehramdjian wrote:
>Hello,
>
>I am new to the mailing list.
>I am currently trying to wrap my command line driven application. Wehn I try
>to run it, I get the following warning:
>
>WARNING - System.in can not be used when the JVM is being controlled by the
>Java Service Wrapper. Calls will block indefinitely.
>
>>From a thread on this list from the month of March, it seems this is a
>functionality, not a limitation.
>http://sourceforge.net/mailarchive/forum.php?thread_id=4088388&forum_id=1194
>8
>
>Unfortunately, my application is really requires System.in to get input from
>users.
>One of the reasons for using the wrapper is to avoid ugly classpath
>limitations on Win32 systems.
>
>Is there any known workaround to allow my application input without using
>System.in?
>
>
|
|
From: Leif M. <le...@ta...> - 2004-11-26 03:40:49
|
Jason,
What you asking is not currently possible with the Wrapper. The
closest thing you
could do would be to pass the environment variable to the JVM using a system
property as follows:
wrapper.java.additional.1=-Denvironment.MYENV=%MYENV%
You can then access it as System.getProperty( "environment.MYENV" );
I'm not sure the exact reasons why Java deprecated the System.getenv()
method. That was a Sun decision and nothing to do with the Wrapper.
Now, as to whether or not this would be possible to add to the
Wrapper...
The thing is that the Wrapper process will be given an Environment by
the system
at the time it is created. It then passes on that Environment to the
Java process
when it is launched.
If the user makes any changes to the environment after the processes
are created
they would not be visible until the process is restarted.
As a workaround, the environment variables can be accessed directly
from the
registry. The Wrapper does that to make it possible to run as an NT
service without
requiring a system restart to get the latest environment variables.
Normally the NT
service manager does not update its Environment after it has been
launched at startup.
Any changes to the Environment variables in the System control panel
will therefor
not be visible until the system has been restarted.
A better way to approach this might be to tell me exactly what you
are trying to
do. There may be other ways to accomplish this. As a rule, you should
assume
that environment variables will not be changed during the life of a
given process.
Cheers,
Leif
Jas...@sc... wrote:
>
> Hi,
>
> First off, kudos for such a useful library!
>
> I have a service which handles requests (jobs) from other machines - a
> distributed build process.
>
> My problem is that it needs to know what "tools" (compilers, SDKs) are
> installed locally, which requires the service to check for the
> existence (say) of %SDK_HOME%/sdk.h or %APP%/bin/app.exe
>
> System.getenv() is causing a java.lang.Error in the service, but not
> as an application. Checking the docs it seems to imply that getenv is
> deprecated, but this does not appear to be true going by the javadoc:
> http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#getenv(java.lang.String)
>
> These variables may not be known at run-time and are subject to change
> and so I would rather not have them hardwired into each client via
> properties...
>
> Any thoughts?
>
>
> Jason Chown
> Head Programmer
> SCEE Studio Liverpool
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> pos...@sc...
>
> This footnote also confirms that this email message has been checked
> for all known viruses.
>
> **********************************************************************
> Sony Computer Entertainment Europe
|
|
From: Haig E. <ha...@ca...> - 2004-11-25 17:48:45
|
Hello, I am new to the mailing list. I am currently trying to wrap my command line driven application. Wehn I try to run it, I get the following warning: WARNING - System.in can not be used when the JVM is being controlled by the Java Service Wrapper. Calls will block indefinitely. From a thread on this list from the month of March, it seems this is a functionality, not a limitation. http://sourceforge.net/mailarchive/forum.php?thread_id=4088388&forum_id=1194 8 Unfortunately, my application is really requires System.in to get input from users. One of the reasons for using the wrapper is to avoid ugly classpath limitations on Win32 systems. Is there any known workaround to allow my application input without using System.in? Haig Ehramdjian, B. Comp. Sci. Developer - Engineering Support Group http://esg.cae.ca/esg > Military Simulation and Training > CAE Inc. > Tel: 514-341-2000, ext: 2017 > ha...@ca... > > PROPRIETARY NOTICE: The information contained herein is confidential > and/or proprietary to CAE Inc., and shall not be reproduced or disclosed > in whole or in part, or used for any purpose whatsoever unless authorized > in writing by CAE Inc > |
|
From: Stuijt, J. <JS...@gt...> - 2004-11-25 07:31:57
|
Christophe,
1) you should print the stacktrace (e.printStackTrace()) in your code,
because now, if there is an exception I think the JVM just exits silently,
and this could be happening 5 times in a row.
2) You are using integration method 3 (see website of the java service
wrapper), and for this method to work, your start(args) method must return.
At the moment, it stays in its while-loop forever..
Maybe you need yet another thread that watches over your mailing thread:
public Integer start(String[] args) {
try{
Mailing mailing = new Mailing();
mailing.setDaemon(true);
mailing.start();
MailingWatcher watcher = new MailingWatcher(mailing);
Watcher.start();
}
catch(Exception e){
System.exit(1);
}
return null;
}
/**
* Inner class for watching the Mailing thread.
*/
class MailingWatcher extends Thread
{
private Mailing mailing;
public MailingWatcher(Mailing mailing)
{
this.mailing = mailing;
}
public void run()
{
while (mailing.isAlive()){
System.out.println("Thread encore vivant !");
Thread.sleep(6000);
}
}
}
Johan
Met vriendelijke groet,
Johan Stuijt
Application Engineer
MES Expert Center
Doorkiesnummer: 075 612 79 34
GTI Industrie Noordwest bv
Industrial Automation
Houthavenkade 44 1506 PD Zaandam
Postbus 1377 1500 AJ Zaandam
tel.: 075 612 76 00 fax: 075 612 30 60
www.gti-group.com/ia
-----Oorspronkelijk bericht-----
Van: Christophe Leroux [mailto:ler...@ho...]
Verzonden: woensdag 24 november 2004 13:55
Aan: wra...@li...
Onderwerp: [Wrapper-user] Please help me ... service was launched, but
failed to start.
Dear all,
First of all, I would like to say that sourceforge is a very huge knowledge
source for me. I like your work and hope your success will continue growing.
Ohterwise, I'm really disapointed about the way to execute my app as a
service with the wrapper.
Here is the content of my wrapper.conf :
Starting the SendLogByMail service...
--> Wrapper Started as Service
Using system timer.
server listening on port 32000.
Launching a JVM...
command: "C:\J2EE\SDK1.4\jdk\bin\java.exe" -Djava.library.path="classes/lib"
-classpath "classes/" -Dwrapper.key="Rfv8sZ_PcoRLht4W" -Dwrapper.port=32000
-Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE"
-Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper"
-Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
com.cleroux.Main
JVM started (PID=3392)
WrapperManager class initialized by thread: main Using classloader:
sun.misc.Launcher$AppClassLoader@e80a59
Wrapper Manager: JVM #1
Wrapper Manager: Registering shutdown hook
Wrapper Manager: Using wrapper
Loaded native library: wrapper.dll
Calling native initialization method.
Initializing WrapperManager native library.
Java Executable: C:\J2EE\SDK1.4\jdk\bin\java.exe
Windows version: 5.1.2600
Java Version : 1.4.2_04-b04 Java HotSpot(TM) Client VM
Java VM Vendor : Sun Microsystems Inc.
Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org
WrapperManager.start(com.cleroux.Main@14b7453, args[]) called by thread:
main
Open socket to wrapper...
Opened Socket
Send a packet KEY : Rfv8sZ_PcoRLht4W
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=2313])
accepted a socket from 127.0.0.1 on port 2313
read a packet KEY : Rfv8sZ_PcoRLht4W
Got key from JVM: Rfv8sZ_PcoRLht4W
send a packet LOW_LOG_LEVEL : 1
send a packet PING_TIMEOUT : 30
Start Application.
send a packet START : start
Received a packet LOW_LOG_LEVEL : 1
Wrapper Manager: LowLogLevel from Wrapper is 1
Received a packet PING_TIMEOUT : 30
Wrapper Manager: PingTimeout from Wrapper is 30000
Received a packet START : start
calling listener.start()
Waiting to start...
Waiting to start...
Waiting to start...
Waiting to start...
Waiting to start...
Startup failed: Timed out waiting for signal from JVM.
As you can see, the wrapper try 5 times to launch the service
unsuccessfully.
I really ask my self why it does not !
If any one had an idea, I would be really happy !
Here is an extract of my main class :
public class Main implements WrapperListener{
public Integer start(String[] arg0) {
boolean flag=true;
try{
Mailing mailing = new Mailing();
mailing.setDaemon(true);
mailing.start();
while (mailing.isAlive()){
System.out.println("Thread encore vivant
!");
Thread.sleep(6000);
}
}
catch(Exception e){
System.exit(1);
}
return null;
}
public static void main(String[] args) {
WrapperManager.start(new Main(), args);
}
}
Thanks for your help !
Bye,
Christophe (please excuse me for the quality of my english !)
-------------------------------------------------------
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
================================================
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en
is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken en
de afzender direct te informeren door het bericht te retourneren.
================================================
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the contents
herein and notify the sender immediately by return e-mail.
================================================
|
|
From: Leif M. <le...@ta...> - 2004-11-25 04:37:55
|
Christophe,
The problem here is that your WrapperListener.start method is not
returning.
It is described in the javadocs, but that method must return. The
Wrapper is timing
out waiting for it.
From your source code, I don't see anything that you are doing that
warrants you
going to the extra work of using integration method #3. I would
suggest using method
#1. It will work out of the box and requires no special coding.
If you do want to keep using this integration method, you should be
able to simply
remove the loop in your start method. My guess is that your
application was quitting
because "All non-daemon threads had completed." You can fix that
original problem
by making it your mailing thread into a non-daemon. Try the following:
private Mailing m_mailing;
public Integer start(String[] arg0) {
m_mailing = new Mailing();
m_mailing.start();
return null;
}
public int stop(int exitCode) {
m_mailing.stop();
return exitCode;
}
I changed your Mailing class from a Thread(??) to an object that can be
started and
stopped. Then made stop method stop your class cleanly. Internally,
the Mailing.start()
method should create a runner thread that is NOT A DAEMON. Then start
it. It should
look something like the following. This is based on working code that
I took from one
of my base classes.
public class Mailing implements Runnable {
private Thread m_runner;
private boolean m_runnerStop = false;
public void start() throws Exception {
m_runner = new Thread( this, "Mailing_runner" );
m_runner.start();
}
public void stop() throws Exception {
Thread runner = m_runner;
m_runnerStop = true;
if ( runner != null ) {
runner.interrupt();
}
// Give the user code a change to stop cleanly.
try {
stopRunner();
} catch ( Throwable t ) {
System.out.println( "Encountered a problem while stopping
the component." );
t.printStackTrace();
}
// Waiting for runner thread to stop.
synchronized ( this ) {
while ( m_runner != null ) {
try {
// Wait to be notified that the thread has exited.
this.wait();
} catch ( InterruptedException e ) {
// Ignore
}
}
}
}
public void run() {
if ( Thread.currentThread() != m_runner ) {
throw new IllegalStateException( "Private method." );
}
try {
try {
runner();
} catch ( Throwable t ) {
System.out.println( "The runner method threw an uncaught
exception, runner is terminating," );
t.printStackTrace();
}
} finally {
synchronized ( this ) {
m_runner = null;
// Wake up the stop method if it is waiting for the
runner to stop.
this.notify();
}
}
}
protected void stopRunner() throws Exception
{
// Do anything you need to do to stop cleanly.
}
protected void runner() {
while ( !isStopping() ) {
try {
// ******
// Your user code would go here for each cycle of the
main loop.
// ******
} catch ( Throwable t ) {
System.out.println( "Unexpected error in runner." );
t.printStackTrace();
// Avoid thrashing.
if ( !isStopping() ) {
try {
Thread.sleep( 5000 );
} catch ( InterruptedException e ) {
// Ignore
}
}
}
}
}
public boolean isStopping() {
return m_runnerStop;
}
}
Your code also did this:
catch(Exception e){
System.exit(1);
}
That is BAD BAD BAD. You will will regret that programming style at
some point as your
application will just suddenly exit for no reason. ALWAYS do something
with a caught
exception. If you "know" it will never happen anyway then it will no
hurt to print the
stack trace.
Cheers,
Leif
Christophe Leroux wrote:
> Dear all,
>
> First of all, I would like to say that sourceforge is a very huge
> knowledge source for me. I like your work and hope your success will
> continue growing.
>
> Ohterwise, I'm really disapointed about the way to execute my app as a
> service with the wrapper.
>
> Here is the content of my wrapper.conf :
>
> Starting the SendLogByMail service...
> --> Wrapper Started as Service
> Using system timer.
> server listening on port 32000.
> Launching a JVM...
> command: "C:\J2EE\SDK1.4\jdk\bin\java.exe"
> -Djava.library.path="classes/lib" -classpath "classes/"
> -Dwrapper.key="Rfv8sZ_PcoRLht4W" -Dwrapper.port=32000
> -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE"
> -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper"
> -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
> com.cleroux.Main
> JVM started (PID=3392)
> WrapperManager class initialized by thread: main Using classloader:
> sun.misc.Launcher$AppClassLoader@e80a59
> Wrapper Manager: JVM #1
> Wrapper Manager: Registering shutdown hook
> Wrapper Manager: Using wrapper
> Loaded native library: wrapper.dll
> Calling native initialization method.
> Initializing WrapperManager native library.
> Java Executable: C:\J2EE\SDK1.4\jdk\bin\java.exe
> Windows version: 5.1.2600
> Java Version : 1.4.2_04-b04 Java HotSpot(TM) Client VM
> Java VM Vendor : Sun Microsystems Inc.
>
> Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org
>
> WrapperManager.start(com.cleroux.Main@14b7453, args[]) called by
> thread: main
> Open socket to wrapper...
> Opened Socket
> Send a packet KEY : Rfv8sZ_PcoRLht4W
> handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=2313])
> accepted a socket from 127.0.0.1 on port 2313
> read a packet KEY : Rfv8sZ_PcoRLht4W
> Got key from JVM: Rfv8sZ_PcoRLht4W
> send a packet LOW_LOG_LEVEL : 1
> send a packet PING_TIMEOUT : 30
> Start Application.
> send a packet START : start
> Received a packet LOW_LOG_LEVEL : 1
> Wrapper Manager: LowLogLevel from Wrapper is 1
> Received a packet PING_TIMEOUT : 30
> Wrapper Manager: PingTimeout from Wrapper is 30000
> Received a packet START : start
> calling listener.start()
> Waiting to start...
> Waiting to start...
> Waiting to start...
> Waiting to start...
> Waiting to start...
> Startup failed: Timed out waiting for signal from JVM.
>
> As you can see, the wrapper try 5 times to launch the service
> unsuccessfully.
>
> I really ask my self why it does not !
>
> If any one had an idea, I would be really happy !
>
> Here is an extract of my main class :
>
> public class Main implements WrapperListener{
>
> public Integer start(String[] arg0) {
> boolean flag=true;
>
> try{
> Mailing mailing = new Mailing();
> mailing.setDaemon(true);
> mailing.start();
> while (mailing.isAlive()){
> System.out.println("Thread encore vivant !");
> Thread.sleep(6000);
> }
> }
> catch(Exception e){
> System.exit(1);
> }
> return null;
> }
>
> public static void main(String[] args) {
> WrapperManager.start(new Main(), args);
> }
> }
>
> Thanks for your help !
>
> Bye,
>
> Christophe (please excuse me for the quality of my english !)
|
|
From: Paul C. <cas...@au...> - 2004-11-25 03:39:37
|
Hi Christophe,
The Wrapper really is a fantastic tool, so let's get it working for you.
Could you please include your wrapper.conf file? (the log was included
before - not the conf file).
I assume your class runs fine when executed from the command line - could
you please also include the complete command used to execute it from the
command line?
Regards,
Paul Casanova
"Christophe
Leroux"
<lerouxtof@hotmai To
l.com> wra...@li...
Sent by: cc
wrapper-user-admi
n...@li... Subject
ge.net [Wrapper-user] Please help me ...
service was launched, but failed to
start.
24/11/2004 11:54
PM
Please respond to
wrapper-user
Dear all,
First of all, I would like to say that sourceforge is a very huge knowledge
source for me. I like your work and hope your success will continue
growing.
Ohterwise, I'm really disapointed about the way to execute my app as a
service with the wrapper.
Here is the content of my wrapper.conf :
Starting the SendLogByMail service...
--> Wrapper Started as Service
Using system timer.
server listening on port 32000.
Launching a JVM...
command: "C:\J2EE\SDK1.4\jdk\bin\java.exe"
-Djava.library.path="classes/lib"
-classpath "classes/" -Dwrapper.key="Rfv8sZ_PcoRLht4W" -Dwrapper.port=32000
-Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE"
-Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper"
-Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1
com.cleroux.Main
JVM started (PID=3392)
WrapperManager class initialized by thread: main Using classloader:
sun.misc.Launcher$AppClassLoader@e80a59
Wrapper Manager: JVM #1
Wrapper Manager: Registering shutdown hook
Wrapper Manager: Using wrapper
Loaded native library: wrapper.dll
Calling native initialization method.
Initializing WrapperManager native library.
Java Executable: C:\J2EE\SDK1.4\jdk\bin\java.exe
Windows version: 5.1.2600
Java Version : 1.4.2_04-b04 Java HotSpot(TM) Client VM
Java VM Vendor : Sun Microsystems Inc.
Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org
WrapperManager.start(com.cleroux.Main@14b7453, args[]) called by thread:
main
Open socket to wrapper...
Opened Socket
Send a packet KEY : Rfv8sZ_PcoRLht4W
handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=2313])
accepted a socket from 127.0.0.1 on port 2313
read a packet KEY : Rfv8sZ_PcoRLht4W
Got key from JVM: Rfv8sZ_PcoRLht4W
send a packet LOW_LOG_LEVEL : 1
send a packet PING_TIMEOUT : 30
Start Application.
send a packet START : start
Received a packet LOW_LOG_LEVEL : 1
Wrapper Manager: LowLogLevel from Wrapper is 1
Received a packet PING_TIMEOUT : 30
Wrapper Manager: PingTimeout from Wrapper is 30000
Received a packet START : start
calling listener.start()
Waiting to start...
Waiting to start...
Waiting to start...
Waiting to start...
Waiting to start...
Startup failed: Timed out waiting for signal from JVM.
As you can see, the wrapper try 5 times to launch the service
unsuccessfully.
I really ask my self why it does not !
If any one had an idea, I would be really happy !
Here is an extract of my main class :
public class Main implements WrapperListener{
public Integer start(String[] arg0) {
boolean flag=true;
try{
Mailing mailing = new Mailing();
mailing.setDaemon(true);
mailing.start();
while (mailing.isAlive()){
System.out.println("Thread
encore vivant !");
Thread.sleep(6000);
}
}
catch(Exception e){
System.exit(1);
}
return null;
}
public static void main(String[] args) {
WrapperManager.start(new Main(), args);
}
}
Thanks for your help !
Bye,
Christophe (please excuse me for the quality of my english !)
-------------------------------------------------------
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
|
|
From: Leif M. <le...@ta...> - 2004-11-25 00:12:41
|
Erik,
This looks like the same problem that had me stumped for about a
month. One of my
customers was experiencing this same problem.
After much debugging, the problem was being caused by the usleep()
system function.
Solaris appears to have a problem where the usleep function will not
always return if the
process receives a signal while sleeping. The fix was to switch from
using usleep() to
using nanosleep. This fix was implemented in version 3.1.2.
My customer had been experiencing the problem on a single machine
about once
every 72 hours. Since the fix was made it has been running for a
couple months without
any further problems.
Please try upgrading to 3.1.2 and giving it a try. You should not
need any other
configuration changes.
As a note, it appears that the usleep function would hang up until
the process received
another signal. At which point it would immediately start working
correctly again. The
problem is that the main event loop of the Wrapper was hung. It is
responsible for pinging
the JVM, processing JVM output etc.
In your log file, you see that log output stopped at '2004/11/22
13:02:14' and then
resumed at '2004/11/24 09:20:42' when the Wrapper received a signal.
The problem is
that at this point, the JVM had long given up and quit to let its
backend socket be
resynched by the Wrapper process. All related output from the JVM had
been queued
up in the Wrapper's pipe buffers for a couple days. This makes the JVM
appear to have
shutdown when the signal was received when in reality it had actualy
shutdown a couple
days earlier.
The only difference between your case and what I had seen was that
in your case,
the Wrapper is exiting. In my case, the Wrapper was launching a new
JVM after
recovering. This may have something to do with your WrapperListener
implementation.
I had been using the WrapperSimpleApp class.
Cheer,
Leif
Love, Erik wrote:
>Hi,
>
>I am using Wrapper 3.1.1 on a Sun Solaris 8 platform and using java 1.4.2_04-b05. The wrapper kicks off a scheduling program which runs great for a period of time and then without any warning or apparent cause goes into a defunct state. Most recently, it shut down the afternoon of the 22nd and didn't recover until the process was manually killed today by the unix admin. After the admin killed the process, the wrapper wrote the Wrapper Process has not received any CPU time for 159507 seconds message to the log...
>
>I have looked at the info regarding the new tick timer, but it doesn't seem to be the same issue. Any ideas would be greatly appreciated. I have included an excerpt from the log (with the debug option turned on)... A side note, we have another wrapper-based application that runs as an NT service. This application has been running since December 2003 and has never experienced this issue.
>
>2004/11/22 13:02:14 | send a packet PING : ping
>2004/11/22 13:02:14 | Received a packet PING : ping
>2004/11/22 13:02:14 | Send a packet PING : ok
>2004/11/22 13:02:14 | read a packet PING : ok
>2004/11/22 13:02:14 | Got ping response from JVM
>2004/11/24 09:20:42 | Signal trapped. Details:
>2004/11/24 09:20:42 | signal number=15, source="kill, sigsend or raise"
>2004/11/24 09:20:42 | signal generated by PID: 22857 (Session PID: 22813), UID: 0 (root)
>2004/11/24 09:20:42 | TERM trapped. Shutting down.
>2004/11/24 09:20:42 | wrapperStopProcess(0) called.
>2004/11/24 09:20:42 | Read Timed out. (Last Ping was 30000 milliseconds ago)
>2004/11/24 09:20:42 | Still alive
>2004/11/24 09:20:42 | Read Timed out. (Last Ping was 60000 milliseconds ago)
>2004/11/24 09:20:42 | Wrapper Manager: The Wrapper code did not ping the JVM for 60 seconds. Quit and let the Wrapper resynch.
>2004/11/24 09:20:42 | Send a packet RESTART : restart
>2004/11/24 09:20:42 | Thread, Wrapper-Connection, handling the shutdown process.
>2004/11/24 09:20:42 | calling listener.stop()
>2004/11/24 09:20:42 | Stopping the RC Scheduler Application
>2004/11/24 09:20:42 | returned from listener.stop()
>2004/11/24 09:20:42 | Send a packet STOPPED : 0
>2004/11/24 09:20:42 | Closing socket.
>2004/11/24 09:20:42 | calling System.exit(1)
>2004/11/24 09:20:42 | read a packet RESTART : restart
>2004/11/24 09:20:42 | JVM requested a restart.
>2004/11/24 09:20:42 | wrapperRestartProcess() called. (IGNORED)
>2004/11/24 09:20:42 | read a packet STOPPED : 0
>2004/11/24 09:20:42 | JVM signalled that it was stopped.
>2004/11/24 09:20:42 | socket read no code (closed?).
>2004/11/24 09:20:42 | Wrapper Process has not received any CPU time for 159507 seconds. Extending timeouts.
>2004/11/24 09:20:42 | JVM process exited with a code of 1, setting the wrapper exit code to 1.
>2004/11/24 09:20:42 | JVM exited normally.
>2004/11/24 09:20:42 | <-- Wrapper Stopped
>2004/11/24 09:20:45 | Spawning intermediate process...
>2004/11/24 09:20:45 | Spawning daemon process...
>2004/11/24 09:20:45 | --> Wrapper Started as Daemon
>2004/11/24 09:20:45 | Using system timer.
>2004/11/24 09:20:45 | server listening on port 32000.
>2004/11/24 09:20:45 | Classpath element, wrapper.java.classpath.11, does not exist: /apps/java/ira.jar
>2004/11/24 09:20:45 | Classpath element, wrapper.java.classpath.24, does not exist: /apps/java/output.txt
>2004/11/24 09:20:45 | Command[0] : java
>2004/11/24 09:20:45 | Command[1] : -Xms256m
>2004/11/24 09:20:45 | Command[2] : -Xmx768m
>2004/11/24 09:20:45 | Command[3] : -Djava.library.path=/apps/RCScheduler/lib
>2004/11/24 09:20:45 | Command[4] : -classpath
>2004/11/24 09:20:45 | Command[5] : ../lib/wrapper.jar:/apps/java/rcscheduler.jar:/apps/java/vantage.jar:/apps/java/vantageadmin.jar:/apps/java/rcmailings.jar:/apps/java/acme.jar:/apps/java/activation.jar:/apps/java/avalon.jar:/apps/java/batik.jar:/apps/java/fop.jar:/apps/java/ira.jar:/apps/java/itext.jar:/apps/java/j2ee.jar:/apps/java/jai_codec.jar:/apps/java/jakarta-oro-2.0.7.jar:/apps/java/jdom.jar:/apps/java/jlink.jar:/apps/java/log4j.jar:/apps/java/mail.jar:/apps/java/netcharts.jar:/apps/java/NetComponents-1_3_8.jar:/apps/java/ojdbc14.jar:/apps/java/oreilly.jar:/apps/java/output.txt:/apps/java/pja.jar:/apps/java/pjatools.jar:/apps/java/Tidy.jar:/apps/java/wrapper.jar:/apps/java/xalan.jar:/apps/java/xerces.jar:/apps/java/xml-apis.jar:/apps/java/xp-assets.jar:/apps/java/weblogic.jar
>2004/11/24 09:20:45 | Command[6] : -Dwrapper.key=4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:45 | Command[7] : -Dwrapper.port=32000
>2004/11/24 09:20:45 | Command[8] : -Dwrapper.debug=TRUE
>2004/11/24 09:20:45 | Command[9] : -Dwrapper.use_system_time=TRUE
>2004/11/24 09:20:45 | Command[10] : -Dwrapper.version=3.1.1
>2004/11/24 09:20:45 | Command[11] : -Dwrapper.native_library=wrapper
>2004/11/24 09:20:45 | Command[12] : -Dwrapper.service=TRUE
>2004/11/24 09:20:45 | Command[13] : -Dwrapper.cpu.timeout=10
>2004/11/24 09:20:45 | Command[14] : -Dwrapper.jvmid=1
>2004/11/24 09:20:45 | Command[15] : org.icmarc.scheduler.application.Scheduler
>2004/11/24 09:20:45 | Command[16] : ./RCScheduler.cfg
>2004/11/24 09:20:45 | Launching a JVM...
>2004/11/24 09:20:46 | WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@67ac19
>2004/11/24 09:20:46 | Wrapper Manager: JVM #1
>2004/11/24 09:20:46 | Wrapper Manager: Registering shutdown hook
>2004/11/24 09:20:46 | Wrapper Manager: Using wrapper
>2004/11/24 09:20:47 | Loaded native library: libwrapper.so
>2004/11/24 09:20:47 | Calling native initialization method.
>2004/11/24 09:20:47 | Inside native WrapperManager initialization method
>2004/11/24 09:20:47 | Java Version : 1.4.2_04-b05 Java HotSpot(TM) Client VM
>2004/11/24 09:20:47 | Java VM Vendor : Sun Microsystems Inc.
>2004/11/24 09:20:47 |
>2004/11/24 09:20:47 | Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org
>2004/11/24 09:20:47 |
>2004/11/24 09:20:47 | WrapperManager.start(org.icmarc.scheduler.application.Scheduler@e102dc, args["./RCScheduler.cfg"]) called by thread: main
>2004/11/24 09:20:47 | Open socket to wrapper...
>2004/11/24 09:20:47 | Opened Socket
>2004/11/24 09:20:47 | Send a packet KEY : 4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:47 | handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=36727])
>2004/11/24 09:20:47 | accepted a socket from 127.0.0.1 on port 36727
>2004/11/24 09:20:47 | read a packet KEY : 4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:47 | Got key from JVM: 4Nq8kvz4U0jqZd7N
>2004/11/24 09:20:47 | send a packet LOW_LOG_LEVEL : 1
>2004/11/24 09:20:47 | send a packet PING_TIMEOUT : 30
>2004/11/24 09:20:47 | Start Application.
>2004/11/24 09:20:47 | send a packet START : start
>2004/11/24 09:20:47 | Received a packet LOW_LOG_LEVEL : 1
>2004/11/24 09:20:47 | Wrapper Manager: LowLogLevel from Wrapper is 1
>2004/11/24 09:20:47 | Received a packet PING_TIMEOUT : 30
>2004/11/24 09:20:47 | Wrapper Manager: PingTimeout from Wrapper is 30000
>2004/11/24 09:20:47 | Received a packet START : start
>2004/11/24 09:20:47 | calling listener.start()
>2004/11/24 09:20:48 | Initializing the RC Scheduler Application
>
>
>-------------------------------------------------------
>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
>
>
>
|
|
From: Love, E. <EB...@ic...> - 2004-11-24 16:38:52
|
Hi, I am using Wrapper 3.1.1 on a Sun Solaris 8 platform and using java = 1.4.2_04-b05. The wrapper kicks off a scheduling program which runs = great for a period of time and then without any warning or apparent = cause goes into a defunct state. Most recently, it shut down the = afternoon of the 22nd and didn't recover until the process was manually = killed today by the unix admin. After the admin killed the process, the = wrapper wrote the Wrapper Process has not received any CPU time for = 159507 seconds message to the log... I have looked at the info regarding the new tick timer, but it doesn't = seem to be the same issue. Any ideas would be greatly appreciated. I = have included an excerpt from the log (with the debug option turned = on)... A side note, we have another wrapper-based application that runs = as an NT service. This application has been running since December 2003 = and has never experienced this issue. 2004/11/22 13:02:14 | send a packet PING : ping 2004/11/22 13:02:14 | Received a packet PING : ping 2004/11/22 13:02:14 | Send a packet PING : ok 2004/11/22 13:02:14 | read a packet PING : ok 2004/11/22 13:02:14 | Got ping response from JVM 2004/11/24 09:20:42 | Signal trapped. Details: 2004/11/24 09:20:42 | signal number=3D15, source=3D"kill, sigsend or = raise" 2004/11/24 09:20:42 | signal generated by PID: 22857 (Session PID: = 22813), UID: 0 (root) 2004/11/24 09:20:42 | TERM trapped. Shutting down. 2004/11/24 09:20:42 | wrapperStopProcess(0) called. 2004/11/24 09:20:42 | Read Timed out. (Last Ping was 30000 milliseconds = ago) 2004/11/24 09:20:42 | Still alive 2004/11/24 09:20:42 | Read Timed out. (Last Ping was 60000 milliseconds = ago) 2004/11/24 09:20:42 | Wrapper Manager: The Wrapper code did not ping the = JVM for 60 seconds. Quit and let the Wrapper resynch. 2004/11/24 09:20:42 | Send a packet RESTART : restart 2004/11/24 09:20:42 | Thread, Wrapper-Connection, handling the shutdown = process. 2004/11/24 09:20:42 | calling listener.stop() 2004/11/24 09:20:42 | Stopping the RC Scheduler Application 2004/11/24 09:20:42 | returned from listener.stop() 2004/11/24 09:20:42 | Send a packet STOPPED : 0 2004/11/24 09:20:42 | Closing socket. 2004/11/24 09:20:42 | calling System.exit(1) 2004/11/24 09:20:42 | read a packet RESTART : restart 2004/11/24 09:20:42 | JVM requested a restart. 2004/11/24 09:20:42 | wrapperRestartProcess() called. (IGNORED) 2004/11/24 09:20:42 | read a packet STOPPED : 0 2004/11/24 09:20:42 | JVM signalled that it was stopped. 2004/11/24 09:20:42 | socket read no code (closed?). 2004/11/24 09:20:42 | Wrapper Process has not received any CPU time for = 159507 seconds. Extending timeouts. 2004/11/24 09:20:42 | JVM process exited with a code of 1, setting the = wrapper exit code to 1. 2004/11/24 09:20:42 | JVM exited normally. 2004/11/24 09:20:42 | <-- Wrapper Stopped 2004/11/24 09:20:45 | Spawning intermediate process... 2004/11/24 09:20:45 | Spawning daemon process... 2004/11/24 09:20:45 | --> Wrapper Started as Daemon 2004/11/24 09:20:45 | Using system timer. 2004/11/24 09:20:45 | server listening on port 32000. 2004/11/24 09:20:45 | Classpath element, wrapper.java.classpath.11, does = not exist: /apps/java/ira.jar 2004/11/24 09:20:45 | Classpath element, wrapper.java.classpath.24, does = not exist: /apps/java/output.txt 2004/11/24 09:20:45 | Command[0] : java 2004/11/24 09:20:45 | Command[1] : -Xms256m 2004/11/24 09:20:45 | Command[2] : -Xmx768m 2004/11/24 09:20:45 | Command[3] : = -Djava.library.path=3D/apps/RCScheduler/lib 2004/11/24 09:20:45 | Command[4] : -classpath 2004/11/24 09:20:45 | Command[5] : = ../lib/wrapper.jar:/apps/java/rcscheduler.jar:/apps/java/vantage.jar:/app= s/java/vantageadmin.jar:/apps/java/rcmailings.jar:/apps/java/acme.jar:/ap= ps/java/activation.jar:/apps/java/avalon.jar:/apps/java/batik.jar:/apps/j= ava/fop.jar:/apps/java/ira.jar:/apps/java/itext.jar:/apps/java/j2ee.jar:/= apps/java/jai_codec.jar:/apps/java/jakarta-oro-2.0.7.jar:/apps/java/jdom.= jar:/apps/java/jlink.jar:/apps/java/log4j.jar:/apps/java/mail.jar:/apps/j= ava/netcharts.jar:/apps/java/NetComponents-1_3_8.jar:/apps/java/ojdbc14.j= ar:/apps/java/oreilly.jar:/apps/java/output.txt:/apps/java/pja.jar:/apps/= java/pjatools.jar:/apps/java/Tidy.jar:/apps/java/wrapper.jar:/apps/java/x= alan.jar:/apps/java/xerces.jar:/apps/java/xml-apis.jar:/apps/java/xp-asse= ts.jar:/apps/java/weblogic.jar 2004/11/24 09:20:45 | Command[6] : -Dwrapper.key=3D4Nq8kvz4U0jqZd7N 2004/11/24 09:20:45 | Command[7] : -Dwrapper.port=3D32000 2004/11/24 09:20:45 | Command[8] : -Dwrapper.debug=3DTRUE 2004/11/24 09:20:45 | Command[9] : -Dwrapper.use_system_time=3DTRUE 2004/11/24 09:20:45 | Command[10] : -Dwrapper.version=3D3.1.1 2004/11/24 09:20:45 | Command[11] : -Dwrapper.native_library=3Dwrapper 2004/11/24 09:20:45 | Command[12] : -Dwrapper.service=3DTRUE 2004/11/24 09:20:45 | Command[13] : -Dwrapper.cpu.timeout=3D10 2004/11/24 09:20:45 | Command[14] : -Dwrapper.jvmid=3D1 2004/11/24 09:20:45 | Command[15] : = org.icmarc.scheduler.application.Scheduler 2004/11/24 09:20:45 | Command[16] : ./RCScheduler.cfg 2004/11/24 09:20:45 | Launching a JVM... 2004/11/24 09:20:46 | WrapperManager class initialized by thread: main = Using classloader: sun.misc.Launcher$AppClassLoader@67ac19 2004/11/24 09:20:46 | Wrapper Manager: JVM #1 2004/11/24 09:20:46 | Wrapper Manager: Registering shutdown hook 2004/11/24 09:20:46 | Wrapper Manager: Using wrapper 2004/11/24 09:20:47 | Loaded native library: libwrapper.so 2004/11/24 09:20:47 | Calling native initialization method. 2004/11/24 09:20:47 | Inside native WrapperManager initialization method 2004/11/24 09:20:47 | Java Version : 1.4.2_04-b05 Java HotSpot(TM) = Client VM 2004/11/24 09:20:47 | Java VM Vendor : Sun Microsystems Inc. 2004/11/24 09:20:47 |=20 2004/11/24 09:20:47 | Wrapper (Version 3.1.1) = http://wrapper.tanukisoftware.org 2004/11/24 09:20:47 |=20 2004/11/24 09:20:47 | = WrapperManager.start(org.icmarc.scheduler.application.Scheduler@e102dc, = args["./RCScheduler.cfg"]) called by thread: main 2004/11/24 09:20:47 | Open socket to wrapper... 2004/11/24 09:20:47 | Opened Socket 2004/11/24 09:20:47 | Send a packet KEY : 4Nq8kvz4U0jqZd7N 2004/11/24 09:20:47 | = handleSocket(Socket[addr=3D/127.0.0.1,port=3D32000,localport=3D36727]) 2004/11/24 09:20:47 | accepted a socket from 127.0.0.1 on port 36727 2004/11/24 09:20:47 | read a packet KEY : 4Nq8kvz4U0jqZd7N 2004/11/24 09:20:47 | Got key from JVM: 4Nq8kvz4U0jqZd7N 2004/11/24 09:20:47 | send a packet LOW_LOG_LEVEL : 1 2004/11/24 09:20:47 | send a packet PING_TIMEOUT : 30 2004/11/24 09:20:47 | Start Application. 2004/11/24 09:20:47 | send a packet START : start 2004/11/24 09:20:47 | Received a packet LOW_LOG_LEVEL : 1 2004/11/24 09:20:47 | Wrapper Manager: LowLogLevel from Wrapper is 1 2004/11/24 09:20:47 | Received a packet PING_TIMEOUT : 30 2004/11/24 09:20:47 | Wrapper Manager: PingTimeout from Wrapper is 30000 2004/11/24 09:20:47 | Received a packet START : start 2004/11/24 09:20:47 | calling listener.start() 2004/11/24 09:20:48 | Initializing the RC Scheduler Application |
|
From: <ste...@ce...> - 2004-11-24 16:19:30
|
I have problem with the pid file : in sh.script.in i have PIDDIR=".", the 'start ' command seems to place pidfile in the right location. but when i try to launch a 'stop' command the script tell me that the daemon isn't running . I also echo some variable and the $PIDFILE is : "./MYAPPNAME.pid" so i don't understand why the line : "if [ -f $PIDFILE ]" is not true I don't know if i'm understandable but i suspect there a problem with the sh.script.in and the wrapper.working.dir. any hints are welcome Thanks |
|
From: Filippo L. <liv...@we...> - 2004-11-24 13:41:54
|
Hi, I've changed the javax.swing.Timer object based structure with a TimerTask from java.utils based structure and everything works. I'd still like to know if there's a compatibility issue between Service Wrapper and the javax.swing.Timer class; it seems the javax.swing.Timer,if wrapped, doesn't generate correctly its action events anymore. Filippo Liverani liv...@we... |
|
From: Christophe L. <ler...@ho...> - 2004-11-24 12:55:47
|
Dear all, First of all, I would like to say that sourceforge is a very huge knowledge source for me. I like your work and hope your success will continue growing. Ohterwise, I'm really disapointed about the way to execute my app as a service with the wrapper. Here is the content of my wrapper.conf : Starting the SendLogByMail service... --> Wrapper Started as Service Using system timer. server listening on port 32000. Launching a JVM... command: "C:\J2EE\SDK1.4\jdk\bin\java.exe" -Djava.library.path="classes/lib" -classpath "classes/" -Dwrapper.key="Rfv8sZ_PcoRLht4W" -Dwrapper.port=32000 -Dwrapper.debug="TRUE" -Dwrapper.use_system_time="TRUE" -Dwrapper.version="3.1.2" -Dwrapper.native_library="wrapper" -Dwrapper.service="TRUE" -Dwrapper.cpu.timeout="10" -Dwrapper.jvmid=1 com.cleroux.Main JVM started (PID=3392) WrapperManager class initialized by thread: main Using classloader: sun.misc.Launcher$AppClassLoader@e80a59 Wrapper Manager: JVM #1 Wrapper Manager: Registering shutdown hook Wrapper Manager: Using wrapper Loaded native library: wrapper.dll Calling native initialization method. Initializing WrapperManager native library. Java Executable: C:\J2EE\SDK1.4\jdk\bin\java.exe Windows version: 5.1.2600 Java Version : 1.4.2_04-b04 Java HotSpot(TM) Client VM Java VM Vendor : Sun Microsystems Inc. Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org WrapperManager.start(com.cleroux.Main@14b7453, args[]) called by thread: main Open socket to wrapper... Opened Socket Send a packet KEY : Rfv8sZ_PcoRLht4W handleSocket(Socket[addr=/127.0.0.1,port=32000,localport=2313]) accepted a socket from 127.0.0.1 on port 2313 read a packet KEY : Rfv8sZ_PcoRLht4W Got key from JVM: Rfv8sZ_PcoRLht4W send a packet LOW_LOG_LEVEL : 1 send a packet PING_TIMEOUT : 30 Start Application. send a packet START : start Received a packet LOW_LOG_LEVEL : 1 Wrapper Manager: LowLogLevel from Wrapper is 1 Received a packet PING_TIMEOUT : 30 Wrapper Manager: PingTimeout from Wrapper is 30000 Received a packet START : start calling listener.start() Waiting to start... Waiting to start... Waiting to start... Waiting to start... Waiting to start... Startup failed: Timed out waiting for signal from JVM. As you can see, the wrapper try 5 times to launch the service unsuccessfully. I really ask my self why it does not ! If any one had an idea, I would be really happy ! Here is an extract of my main class : public class Main implements WrapperListener{ public Integer start(String[] arg0) { boolean flag=true; try{ Mailing mailing = new Mailing(); mailing.setDaemon(true); mailing.start(); while (mailing.isAlive()){ System.out.println("Thread encore vivant !"); Thread.sleep(6000); } } catch(Exception e){ System.exit(1); } return null; } public static void main(String[] args) { WrapperManager.start(new Main(), args); } } Thanks for your help ! Bye, Christophe (please excuse me for the quality of my english !) |
|
From: <Jas...@sc...> - 2004-11-24 12:03:52
|
Hi, First off, kudos for such a useful library! I have a service which handles requests (jobs) from other machines - a distributed build process. My problem is that it needs to know what "tools" (compilers, SDKs) are installed locally, which requires the service to check for the existence (say) of %SDK_HOME%/sdk.h or %APP%/bin/app.exe System.getenv() is causing a java.lang.Error in the service, but not as an application. Checking the docs it seems to imply that getenv is deprecated, but this does not appear to be true going by the javadoc: http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#getenv(java.lang.String) These variables may not be known at run-time and are subject to change and so I would rather not have them hardwired into each client via properties... Any thoughts? Jason Chown Head Programmer SCEE Studio Liverpool ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify pos...@sc... This footnote also confirms that this email message has been checked for all known viruses. ********************************************************************** Sony Computer Entertainment Europe |
|
From: Filippo L. <liv...@we...> - 2004-11-24 10:00:34
|
Hi,
I'm using Service Wrapper to install and start a networking
multi-threaded Java application and I've a serious problem while running
from server side a background timer thread that keeps calling a RMI ping
method to verify clients status. If start my server application without
Service Wrapper it works correctly, my thread keeps doing its job at
prefixed timeouts, while if I start my application using Service Wrapper
the thread doesn't even start and doesn't execute any ping. Any other
thread is working fine. This is the significant portion of my property
configuration:
wrapper.java.additional.1=-server
wrapper.java.additional.2=-Djava.awt.headless=true
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp
wrapper.app.parameter.1=srvLayer.server.SimServer
wrapper.app.parameter.2=1
wrapper.app.parameter.3=..\..\conf\properties.xml
wrapper.app.parameter.4=srvLayer.server.HaltServer
wrapper.app.parameter.5=true
wrapper.app.parameter.6=2
wrapper.app.parameter.7=localhost
wrapper.app.parameter.8=4010
wrapper.max_failed_invocations=2
wrapper.jvm_exit.timeout=15
wrapper.startup.timeout=60
wrapper.shutdown.timeout=10
wrapper.cpu.timeout=0
wrapper.ping.interval=60
wrapper.ping.timeout=120
wrapper.use_system_time=FALSE
wrapper.single_invocation=TRUE
This is the way I create and call the ping thread:
pingTimer = new javax.swing.Timer(PropConst.PING_DELAY, this);
...
pingTimer.start();
...
In the run method I start another thread to execute the RMI ping:
Thread pingTr = new Thread(rmiPing);
pingTr.start();
try{
pingTr.join(timeout);
}catch(InterruptedException iEx){
log.error("Error trying to join Ping Thread: ",iEx);
}
in the run method it simply calls a remote isAlive() method on the
client.
Thanks for your help,
Filippo Liverani
liv...@we...
|
|
From: Ajay K. <Aja...@sa...> - 2004-11-23 07:25:10
|
Hi,
Following are the steps to create an executable wrapper file for solaris
intel (x/86) platform.
Steps:
1. Download wrapper source code. i.e. /wrapper_3.1.1_src
2. Download ant tool ver 1.6. i.e. apache-ant-1.6alpha build
3. Copy ant.jar, optional.jar from apache-ant-1.6alpha folder and
paste/overwrite them into wrapper_3.1.1_src/tools/lib folder.
4. Change directory to /wrapper_3.1.1_src and run command sh build.sh from
terminal window.
5. If you get FileNotFoundException for 'make' then add entry for 'make'
command into enviornment variable
OR
Edit Build.xml file and change line number 72:
<property name="make.name" value="make"/>
To
<property name="make.name" value="/usr/ccs/bin/make"/>
Where '/usr/ccs/bin/make' is absolute path for make command.
6. Again run command sh build.sh.
7. If you get error for 'gcc' It means you don't have C compiler installed
on your machine.
so download and install gcc-2.95.2-sol8-intel-local package.
Add entry for 'gcc' command into enviornment variable
OR
Edit wrapper_3.1.1_src/src/c/MakeFile.solaris file and change first
line:
'COMPILE = gcc -O3 -Wall --pedantic -DSOLARIS'
To
'COMPILE = /usr/local/bin/gcc -O3 -Wall --pedantic -DSOLARIS'
Where '/usr/local/bin/gcc' is absolute path for gcc command
6. Again run command sh build.sh.
7. On successful compilation of build you will get executable wrapper file
into /wrapper_3.1.1_src/bin folder. also you will get libwrapper.so,
wrapper.jar into /wrapper_3.1.1_src/lib folder.
Thanks.
Regards,
Ajay
----- Original Message -----
From: "Leif Mortenson" <le...@ta...>
To: <wra...@li...>
Sent: Friday, November 19, 2004 7:18 PM
Subject: Re: [Wrapper-user] Solaris Intel (X/86)
> Ajay,
> Great, glad you got it working. Did it require any changes? If
> so, please post what you did.
> I would like to make it work out of the box for people if possible.
>
> Cheers,
> Leif
>
> Ajay Khairnar wrote:
>
> >Hi Leif,
> > Thanks for such a helpful information. Today we have generated a
> >executable wrapper for solaris intel (x/86) by using build.sh. Now our
> >program is running fine with wrapper. if any user wants wrapper for
solaris
> >intel (x/86) then please contact me on aja...@sa...
> >email-id.
> >
> >Thanks again.
> >
> >Regards,
> >Ajay
|
|
From: Leif M. <le...@ta...> - 2004-11-19 13:48:59
|
Ajay,
Great, glad you got it working. Did it require any changes? If
so, please post what you did.
I would like to make it work out of the box for people if possible.
Cheers,
Leif
Ajay Khairnar wrote:
>Hi Leif,
> Thanks for such a helpful information. Today we have generated a
>executable wrapper for solaris intel (x/86) by using build.sh. Now our
>program is running fine with wrapper. if any user wants wrapper for solaris
>intel (x/86) then please contact me on aja...@sa...
>email-id.
>
>Thanks again.
>
>Regards,
>Ajay
>----- Original Message -----
>From: "Leif Mortenson" <le...@ta...>
>To: "Wrapper User List" <wra...@li...>
>Cc: "Ajay Khairnar" <Aja...@sa...>
>Sent: Tuesday, November 09, 2004 7:53 PM
>Subject: [Wrapper-user] Solaris Intel (X/86)
>
>
>
>
>>Ajay,
>> There are not currently any binaries available for that platform.
>>This does not mean that
>>the Wrapper can not be run on that platform, simply that I do not have
>>access to such a
>>machine in order to generate the build.
>>
>> Please download the source distribution and give it a try. You
>>will most likely have a few
>>questions, but I should be able to walk you through it. The Wrapper's
>>build system uses
>>an included copy of Ant. Depending on the value of the os.name
>>property, it decides on a
>>Makefile to use for the current platform. Most likely you will need to
>>copy the current
>>Makefile.solaris file and make a few changes for your platform. I
>>suggest just running
>>./build.sh in the root of the src directory and see how far you get out
>>of the box.
>>
>> I am able to support many of the platforms listed below because
>>several Wrapper users
>>are willing to donate a little bit of time and CPU a few times a year to
>>help out with releases
>>and testing. If I find someone for the Solaris Intel x86 platform to
>>help out then we can start
>>supporting that platform as well. (hint hint)
>>
>>Cheers,
>>Leif
>>
>>Ajay Khairnar wrote:
>>
>>
>>
>>>Hi,
>>> I am using Java Service Wrapper for windows platform and it's
>>>
>>>
>working
>
>
>>>excellent. Thanks to tanukisoftware for development of this wrapper. I
>>>wish
>>>to know whether wrapper is available for Solaris Intel (X/86) platform
>>>
>>>
>or
>
>
>>>not. Because we are having Solaris Intel (X/86) machine and we want
>>>to test
>>>our program on this machine. I have not seen binaries download of
>>>
>>>
>wrapper
>
>
>>>for Solaris Intel (X/86) platform. Binaries downloads are available for
>>>following platform only:
>>>
>>>wrapper_aix_3.1.1.tar.gz -> Other
>>>wrapper_freebsd_3.1.1.tar.gz -> i386
>>>wrapper_hpux_3.1.1.tar.gz -> Other
>>>wrapper_hpux64_3.1.1.tar.gz -> Other
>>>wrapper_irix_3.1.1.tar.gz -> Other
>>>wrapper_linux_3.1.1.tar.gz -> i386
>>>wrapper_macosx_3.1.1.tar.gz -> PPC
>>>wrapper_osf1_3.1.1.tar.gz -> Alpha
>>>wrapper_solaris_3.1.1.tar.gz -> UltraSparc
>>>wrapper_win32_3.1.1.zip -> i386
>>>
>>>Please let me know from above which one i can use for Solaris Intel
>>>
>>>
>(X/86)
>
>
>>>platform.
>>>Please reply.
>>>
>>>Thanks in Advance.
>>>
>>>Regards,
>>>Ajay Khairnar
>>>
>>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by:
>>Sybase ASE Linux Express Edition - download now for FREE
>>LinuxWorld Reader's Choice Award Winner for best database on Linux.
>>http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
>>_______________________________________________
>>Wrapper-user mailing list
>>Wra...@li...
>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>
>>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: InterSystems CACHE
>FREE OODBMS DOWNLOAD - A multidimensional database that combines
>robust object and relational technologies, making it a perfect match
>for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>
|
|
From: Ajay K. <Aja...@sa...> - 2004-11-19 10:36:50
|
Hi Leif,
Thanks for such a helpful information. Today we have generated a
executable wrapper for solaris intel (x/86) by using build.sh. Now our
program is running fine with wrapper. if any user wants wrapper for solaris
intel (x/86) then please contact me on aja...@sa...
email-id.
Thanks again.
Regards,
Ajay
----- Original Message -----
From: "Leif Mortenson" <le...@ta...>
To: "Wrapper User List" <wra...@li...>
Cc: "Ajay Khairnar" <Aja...@sa...>
Sent: Tuesday, November 09, 2004 7:53 PM
Subject: [Wrapper-user] Solaris Intel (X/86)
> Ajay,
> There are not currently any binaries available for that platform.
> This does not mean that
> the Wrapper can not be run on that platform, simply that I do not have
> access to such a
> machine in order to generate the build.
>
> Please download the source distribution and give it a try. You
> will most likely have a few
> questions, but I should be able to walk you through it. The Wrapper's
> build system uses
> an included copy of Ant. Depending on the value of the os.name
> property, it decides on a
> Makefile to use for the current platform. Most likely you will need to
> copy the current
> Makefile.solaris file and make a few changes for your platform. I
> suggest just running
> ./build.sh in the root of the src directory and see how far you get out
> of the box.
>
> I am able to support many of the platforms listed below because
> several Wrapper users
> are willing to donate a little bit of time and CPU a few times a year to
> help out with releases
> and testing. If I find someone for the Solaris Intel x86 platform to
> help out then we can start
> supporting that platform as well. (hint hint)
>
> Cheers,
> Leif
>
> Ajay Khairnar wrote:
>
> > Hi,
> > I am using Java Service Wrapper for windows platform and it's
working
> > excellent. Thanks to tanukisoftware for development of this wrapper. I
> > wish
> > to know whether wrapper is available for Solaris Intel (X/86) platform
or
> > not. Because we are having Solaris Intel (X/86) machine and we want
> > to test
> > our program on this machine. I have not seen binaries download of
wrapper
> > for Solaris Intel (X/86) platform. Binaries downloads are available for
> > following platform only:
> >
> > wrapper_aix_3.1.1.tar.gz -> Other
> > wrapper_freebsd_3.1.1.tar.gz -> i386
> > wrapper_hpux_3.1.1.tar.gz -> Other
> > wrapper_hpux64_3.1.1.tar.gz -> Other
> > wrapper_irix_3.1.1.tar.gz -> Other
> > wrapper_linux_3.1.1.tar.gz -> i386
> > wrapper_macosx_3.1.1.tar.gz -> PPC
> > wrapper_osf1_3.1.1.tar.gz -> Alpha
> > wrapper_solaris_3.1.1.tar.gz -> UltraSparc
> > wrapper_win32_3.1.1.zip -> i386
> >
> > Please let me know from above which one i can use for Solaris Intel
(X/86)
> > platform.
> > Please reply.
> >
> > Thanks in Advance.
> >
> > Regards,
> > Ajay Khairnar
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
|
|
From: Leif M. <le...@ta...> - 2004-11-19 04:54:31
|
Nathalie, Unfortunately this is not currently possible with the Wrapper. The controlEvent method of the WrapperListener receives system signals received by the JVM process. These are different from the signals sent by the ServiceManager, or in your case another service. Those signals are only received by the Wrapper process. It currently is ignoring any unknown signals. I don't have any suggested workarounds for you at the moment, sorry. I am currently working on a new Event system in the Wrapper which will allow this kind of thing to be done. It is still going to take a little bit of time before that API has been finalized however. But the goal is to have it in the next release. I will plan on making Service events amongst those reported to listeners. Cheers, Leif Vancaudenberg Nathalie wrote: > Hi, > > I am using wrapper 3.1.1 (integration method 3) and wrote a small > program that is incorporated as a service in a large program > (developed at another location). This large program uses a specific > service control event to inform others about changes. When receiving > such an event certain actions need to be taken. > > My problem now is that JSW does not forward user defined service > control events to the WrapperListener. The other party does not want > to change their code so I need to find a solution. > > Is it possible for the JSW to forward service control events different > from stop, shutdown and interrogate to controlEvent(int) of the > WrapperListener? > > > Kind regards, > Nathalie Vancaudenberg. > |
|
From: Leif M. <le...@ta...> - 2004-11-19 02:33:42
|
Jindong Li wrote: > I'm just thinking...when Wrapper pings the JVM, if there's any issue > with the ping itself (for example, there isn't any socket available, > would that be considered JVM not responding as well? > The Wrapper process opens a port that will listen for a single client connection from localhost. It allocates the port dynamically so it is very unlikely that you will ever run into a problem where a port can not be allocated. When the JVM is launched, it is provided with a wrapper.key that it used to identify the JVM. On initialization, the WrapperManager class immediately opens up a socket back to the Wrapper process for backend communication. The key is used so that the Wrapper can verify that the correct JVM is connecting. The Socket will then stay open for the life of the JVM. Because it is a localhost socket, there is no reason that the socket would ever drop. Just in case however there is code to reestablish the connection, to my knowledge however it has never been needed. In response to your question. If a socket could not be established then yes, the JVM would fail to start up. But that would happen either before the JVM is launched, when the server port is being opened. Or immediately after the JVM is launched, when it opens up the backend socket. Once the JVM is up and running, you will not have any problems caused by the socket itself. Cheers, Leif |
|
From: Jindong Li <Jin...@so...> - 2004-11-19 01:43:36
|
Thanks Leif for your prompt response... I'm just thinking...when Wrapper pings the JVM, if there's any issue with the ping itself (for example, there isn't any socket available, would that be considered JVM not responding as well? Jindong. -----Original Message----- From: Leif Mortenson [mailto:le...@ta...] Sent: Wednesday, November 17, 2004 5:52 PM To: Jindong Li Subject: Re: JVM appears hung in Wrapper log file for RMI registry service Jindong, In the future PLEASE post to the mailing list and not to me directly. The log is showing that both the Wrapper and Java processes are failing to get enough CPU. The Wrapper is continuing to function correctly, but it is designed to display warnings when that happens. Since both processes are failing to get CPU, this means that something else on the system is consuming all available CPU in a way that is failing to share that CPU with other processes. Version 3.1.2 functions much better on systems under high load. Try upgrading to 3.1.2 and then setting the following property: wrapper.use_system_time=false 3.1.2 has a new optional timing method which has been in since 3.1.0. It is now quite stable and will be the new default in the next release. This change should make your application behave a little better, but you should figure out what is using all of the CPU? The occasional startup failures you are seeing are because the Wrapper is not getting enough CPU to launch the JVM. I don't think this is a problem with your application or RMI. Cheers, Leif Jindong Li wrote: > Hi Leif, > > How are you doing? > > I have an urgent question, I'm using wrapper to start RMI registry > service as windows service and all is good. Recently however, we've > getting error messages in the wrapper log file suggesting the JVM the > RMI registry is started in appears hung and thus restarted by the > wrapper automatically. > > However the restarted registry service does not have any previously > bound RMI servers and causing RMI lookup throwing NotBoundException. > > Any idea and suggestions would be greatly appreciated!!! > > Thanks, > > Jindong. > > I'm attaching the source code for the RMI registry service code and > the log file as well. > > ------------------------------------------------------------------------ > This e-mail message has been scanned for Viruses and Content and > cleared by *NetIQ MailMarshal * > ------------------------------------------------------------------------ ############################################################## This e-mail message has been scanned for Viruses and Contents ############################################################## ############################################################## This e-mail message has been scanned for Viruses and Contents ############################################################## |
|
From: <WLi...@ci...> - 2004-11-17 17:25:18
|
<<From: Ori Argov <oa...@me...> <<To: "'wra...@li...'" <<<wra...@li...> <<Subject: RE: [Wrapper-user] jintegra and JBoss <<Date: Wed, 17 Nov 2004 10:13:28 +0200 <<Reply-To: wra...@li... <<This is a long shot but try checking permission issues, the windows services <<run by default on the system account which might not have sufficient <<permissions on the COM component. <<Maybe a more detailed exception from COM could help. <<Ori You were correct Ori. I created a local system account for running JBoss via Wrapper and it has no problem resolving COM. Thanks |
165 messages has been excluded from this view by a project administrator.
