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

Re: [Wrapper-user] custom action on wrapper.filter.action

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

Ben,
There is already an open feature request on this.
https://sourceforge.net/tracker/index.php?func=detail&aid=926800&group_id=39428&atid=425190

Please take a look at it and add any additional comments that describe 
exactly what
you would like to be able to do.

Note that 3.1.0 also added the ability to trigger off of JVM exit codes.
http://wrapper.tanukisoftware.org/doc/english/prop-on-exit-n.html

Cheers,
Leif

Ben David, Tomer wrote:

>Hi
>
>Regarding
>
>wrapper.filter.action.<n> 
>wrapper.filter.trigger.<n> 
>
>How can I tell the action to perform my own code?
>
>since currently my only possibilities are : Possible actions are RESTART, SHUTDOWN, and NONE.  And I want some more actions so I though I can plug in some class of mine that will perform the action, is that possible?
>  
>

Re: [Wrapper-user] How to Use vbj for the Java wrapper.

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

Prasad,
I am not familiar with what "vbj" is..

I did a google and found the following:
http://archives.java.sun.com/cgi-bin/wa?A2=ind0011&L=ejb-interest&F=&S=&P=22193

It sounds like VBJ simple sets up some environment variables and then
launches a JVM instance. To use the Wrapper, you will need to find out
what those "environment variables" are. From the above page it sounds
like you can do so by running something like the following:

vbj -VBJdebug -Duser.region=US -Dvbroker.agent.port=14000
com.server.transform.Server

Whatever the result, please post back. A description of how to do this
would be useful for other future users trying to do the same thing.

Cheers,
Leif


Prasad Tirumareddi wrote:

> Hi
>
> I am trying to use the Java Wrapper. It works fine with the normal
> classes or jar files. I would like to use the following one. Can
> anyone suggest how to use this.
>
> vbj -Duser.region=US -Dvbroker.agent.port=14000
> com.server.transform.Server
>
> Can i register this as a service.
>
> Thanks,
> Prasad.

Re: [Wrapper-user] blocking in WrapperManager.stopInner()

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

Sergey,
    This works the same way that calls to System.exit does.  Such calls 
are not
expected to be returning by the calling code.

    What are the case(s) where you are running into problems?

Cheers,
Leif

Sergey Samokhodkin wrote:

>Hello wrapper-user,
>
>What is the purpose of blocking non-first threads in
>WrapperManager.stopInner()?
>I mean, why not to let them off?
>This seem to cause the Wrapper to hang
>instead of exiting in certain cases.
>  
>

Re: [Wrapper-user] java service wrapper on redhat 8.0

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

Samar,
    The Wrapper should be usable on RedHat.  I do not have any RedHat 
servers
available personally to test this out for you.

    If someone RedHat 8 could try this out, I would appreciate it.

    There was a change made in 3.1.0 to start linking dynamically rather 
than statically.
I am interested to know the version that you are using and whether this 
was a new
problem with 3.1.0.

Cheers,
Leif

samar gupta wrote:

> is service wrapper support redhat 8.o
> while running as a console it is showing libcj.*.so not found
>  
>  
> samar
>
> ------------------------------------------------------------------------
> Do you Yahoo!?
> Win a $20,000 Career Makeover at Yahoo! HotJobs 
> <http://pa.yahoo.com/*http://us.rd.yahoo.com/hotjobs/hotjobs_mail_signature_footer_textlink/evt=23983/*http://hotjobs.sweepstakes.yahoo.com/careermakeover> 

[Wrapper-user] what is the memory and cpu footprint of the wrapper itself?

[Jennifer K. <jk...@si...>]

For wrapper 3.1.0 and 3.0.5 under Windows 2000-- using sun's JVM 1.4.2  
what amount of memory do I need to allocate for the
wrapper itself?
Should I expect this number to be higher under 3.1.0?

what about CPU usage. what % of CPU usage should I expect w/ default 
configuration parameters?
I am finding that the CPU load from 3.1.0 is about 20% higher from the 
wrapper  than with 3.0.5.

I am running multiple instances of processes wrapped with the wrapper 
and thus can't just allocate a huge amount of memory to each process.

Thanks,
Jennifer

[Wrapper-user] process not restarting when cpu at 100%

[Jennifer K. <jk...@si...>]

I have processes running under servicewrapper 3.1.0 that are regularly 
becoming CPU bound.. which is a separate problem in and of itself that 
I am addressing..

However, I would expect the servicewrapper to restart those 
services.... (I have seen this same problem under 3.0.5 by the way)


What I see is that the processes just stop running- cpu is at 100% (4 
cpu machine- all pegged).. no errors, no messages from the wrapper.
Any ideas?

How is it that  wrapper code has the cpu cycles to run and know to 
restart the process if the CPU is at 100%?

here are the settings in my properties files that would have any 
relationship to this at all.

# How long to wait [seconds] between when the JVM says it has stopped
# and seeing if the JVM has actually terminated.
# A value of <0 means no timeout will be enforced.
wrapper.jvm_exit.timeout=30

# How long to wait for the cpu [seconds] before declaring it timed-out
# a value of <0 means no timeout will be enforced.
wrapper.cpu.timeout=10

# How long [seconds] to allow between pings before considering the VM 
timed-out
# Max allowed time is 3600 sec or 1 hour.
# Must be atleast 5 seconds longer than the ping interval.
# Must be longer than the CPU timeout.
# A value of <0 means no timeout will be enforced.
wrapper.ping.timeout=300

# How often [seconds] to send pings to the JVM to see if it is alive
# Must be atleast 1 second.
wrapper.ping.interval=5

# How long [seconds] to wait before issuing reset of JVM- only applies
# to resets, not to initial start.
wrapper.restart.delay=10

# Max number of times to restart(or start) invocation of JVM
# must be atleast 1
# Note- this only applies to startup attempts, not anything else
# best to make atleast 2...
wrapper.max_failed_invocations=3

# How long [seconds] an application has to run to be considered 
successfully invoked.
# don't leave too long- since if we restart between processing and have 
been
# running less than this time we will only be allowed 
"max_failed_invocations"
# to restart.. and not the usual unlimited number.
wrapper.successful_invocation_time=2

# How long [seconds] to allow for startup before declaring it timed-out
# and restarting
# Must be longer than the CPU timeout.
# A value of <0 means no timeout will be enforced.
wrapper.startup.timeout=30

#whether to use system time or the internal tick timer
# set to false to use new experimental tick timer
# version 3.1.0 and later
wrapper.use_system_time=FALSE

# Whether you want a thread dump if the JVM failed to exit nicely
wrapper.request_thread_dump_on_failed_jvm_exit=FALSE

#Whether or not system signals should be ignored
# If set to TRUE, CTRL-C will NOT stop the process....
# Only System.exit (if shutdown hooks are not disabled) and internal
# programatic stop commands will stop the service. (and of course 
through
# the service control panel)
wrapper.ignore_signals=TRUE

#whether or not shutdown hooks should be ignored
# Setting this to TRUE means System.exit will result in
# a restart. Setting it to FALSE means System.exit will be treated
# as a purposeful shutdown and actually exit.
wrapper.disable_shutdown_hook=TRUE


Thanks,
  Jennifer

[Wrapper-user] Starting application with pribileged port under Linux/Unix

[Thorsten K. <Th...@pl...>]

Hello  Mailinglist,

I want to start the Tomcat-Server 5.0.x with the current Wrapper.
With the Commons-Demon Package I can start the Tomcat with one of the
privileged ports (< 1024) without runnung it with root-privileges like e.g.
Apache.

Can I configure the wrapper to achieve the same behaviour?

Best regards
Thorsten

-- 
Thorsten Kamann
Email: tho...@pl...
ICQ: 40746578
Yahoo: ThorQue

Re: [Wrapper-user] JBoss ping timeout, shuts down but doesn't restart

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

Eoin,
    I was able to reproduce your problem.   This is a bug in the Wrapper 
that I just got
fixed in CVS.  It will be in the next (3.1.1) release of the Wrapper.

    If the Wrapper process does not get any CPU for some reason for an 
extended
period of time then it will fail to ping the JVM.   Normally this will 
only happen if the
system is under extremely heavy load.  However in such cases, the JVM 
will also
experience the same problem and compensate.  It appears that in your 
case, the
JVM had been getting at least a little CPU.

    The JVM is designed to shut itself down in the event that the 
Wrapper process
is ever killed.   Thus the message that it is attempting to shut itself 
down and then
let the JVM restart it.  Once the JVM decides to shut itself down this 
will happen
very quickly.

    The problem is that when the JVM decided to shut itself down, the 
Wrapper
process was thinking that the JVM wanted to exit cleanly and was 
shutting itself
down as well.   The Wrapper should have been launching a new JVM.

    I had reworked the state engine in 3.1.0 and it looks like I broke 
this.  3.0.5
had been working correctly.

    For now, the best option for you is to set the ping timeout to a 
high enough
value that you do not encounter this.  Read the docs for the property so you
understand the issues involved.
http://wrapper.tanukisoftware.org/doc/english/prop-ping-timeout.html

    I'll try and get a release out soon.  There are
a few other 3.1.0 problems that I want to get fixed first however.

Cheers,
Leif


Eoin Curran wrote:

> I'm using wrapper 3.10 on linux, using:
>
> wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
> wrapper.app.parameter.1=org.jboss.Main
>
> I got the following in my logs:
> INFO   | jvm 1    | 2004/05/13 21:14:59 | Wrapper Manager: The Wrapper 
> code did not ping the JVM for 60 seconds.  Quit and let the Wrapper 
> resynch.
> INFO   | jvm 1    | 2004/05/13 21:14:59 | 21:14:59,954 INFO  [Server] 
> JBoss SHUTDOWN: Undeploying all packages
>
> the server shut down and was not started up. I don't see anything in 
> the logs that might explain why the ping failed, and there was nothing 
> special happening at that time that I know of. I don't have debug 
> output from wrapper, but am enabling it in case this happens again.
>
> I'm wondering how the ping could fail, but the wrapper was able to 
> tell jboss to shut down so quickly (<1 second later). Also, should the 
> wrapper not restart the server if it kills it as a result of timed out 
> ping?
>
> regards,
> eoin.

[Wrapper-user] Converting RMID into a NT/2000 service

[<zge...@ex...>]

I need to convert the Java RMID process into a windows service. 



Using integration method 3 I did the following:

1) Create a WrapperListener implementation that uses java.lang.Runtime.exec(...) to launch "rmid.exe". The implementation's "stop" method similarly launches "rmid.exe -stop" to stop the previously launched rmid process.

2) Install the WrapperListener implementation as an NT service.



On installing the service and starting it and after 

activating a remote object in a separate Activatable Server (that rmid process takes care of launching), I see the following processes (among others) in the "Windows Task Manager". 

#a) wrapper.exe

#b) java.exe (the WrapperListener implemenation)

#c) rmid.exe (launched by #b)

#d) java.exe (activated by rmid.exe in #c).



On stopping the service all of these processes come down cleanly. 



Here's the problem:

After launching the service - if I logoff, rmid.exe (#c) and the java.exe (#d) process seem to shutdown. When I login again, all four processes are gone. 



In the WrapperListener implementation I do get the Service Control Event indicating that a logoff has happened - The current behavior is to let the native WrapperManager handle all service control events. 



Are processes launched from the WrapperListener implementation under the control of the service - i.e. live and die with the life of the service?



Has anyone successfully implemented rmid as a service (especially including its activation features) not just as a registry? 



Can JSW be used for a case like this to first launch rmid.exe which  can then internally launch multiple JVMs that can survive login/logoffs.



Thanks for all your help in advance.

Zac George

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!

[ RE:[Wrapper-user] does wrapper depend on JAVA_HOME? ]

[Ben D. T. <to...@xm...>]

Hi

Im using a hardcoded JAVA_HOME different than the PATH'ed java home and its working perfect.

Original Message:
From: "Cocalea, Eugen"  Co...@sy... 
To: "'wra...@li...'"  wra...@li... 
Subject: [Wrapper-user] does wrapper depend on JAVA_HOME?
Date: Fri May 21 14:56:40 GMT 2004

Hello,
 
This is a bit tricky, because not even me know what the question is about.
 
I have a java application that I want to run as a windows service and I use
wrapper to do this.
 
My app wrapper.conf used to have
 
wrapper.java.command=%JAVA_HOME%/bin/java
 
The problem is that I have to run different versions of the application,
that are certified against different JREs.
 
So, my question is: if I hardcode the path to the JRE I need in
wrapper.java.command, do I need to check anything else to see if the
application really uses that JRE?
 
Example:
 
- JAVA_HOME points to JRE 1.3
- I need to run the app with JRE 1.4
- wrapper.java.command is /bin/java
 
I should be safe, correct? Assuming my application doesn't use JAVA_HOME.

[ RE:Re: [Wrapper-user] CTRL-C not trapped in sercice console mode! ]

[Ben D. T. <to...@xm...>]

Hi

Thanks for the reply.

The point is:

1. I want my app/web server to start up as a service.
2. I sure want the users of that app/web server on windows server to see its console!

I want the CTRL-C either to be trapped, either to be ignored.  Any ways?

Thanks

Original Message:
From: Andreas Wendt <and...@em...>
To: <wra...@li...>
Subject: Re: [Wrapper-user] CTRL-C not trapped in sercice console mode!
Date: Fri May 21 10:31:52 GMT 2004

Tomer,

when running as service, the recommended way to stop the application is via the Service control panel. This is by design, since services should not be started and stopped by itself.

Cheers,
Andreas

> 
> Hi
> 
> When I'm running wrapper in regular console mode ( -c ) then it trapps perfectly the CTRL-C and I see on console:
> 
> wrapper  | CTRL-C trapped.  Shutting down.
> 
> However if I'm running in a service mode with console enabled, then I dont see this line on screen, and my application donesn't shut down properly :(
> 
> Anyone knows why?
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user





-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] does wrapper depend on JAVA_HOME?

[Cocalea, E. <Co...@sy...>]

Hello,
 
This is a bit tricky, because not even me know what the question is about.
 
I have a java application that I want to run as a windows service and I use
wrapper to do this.
 
My app wrapper.conf used to have
 
wrapper.java.command=%JAVA_HOME%/bin/java
 
The problem is that I have to run different versions of the application,
that are certified against different JREs.
 
So, my question is: if I hardcode the path to the JRE I need in
wrapper.java.command, do I need to check anything else to see if the
application really uses that JRE?
 
Example:
 
- JAVA_HOME points to JRE 1.3
- I need to run the app with JRE 1.4
- wrapper.java.command is <JRE1.4_install_path>/bin/java
 
I should be safe, correct? Assuming my application doesn't use JAVA_HOME.

Re: [Wrapper-user] CTRL-C not trapped in sercice console mode!

[Andreas W. <and...@em...>]

Tomer,

when running as service, the recommended way to stop the application is via the Service control panel. This is by design, since services should not be started and stopped by itself.

Cheers,
Andreas

> 
> Hi
> 
> When I'm running wrapper in regular console mode ( -c ) then it trapps perfectly the CTRL-C and I see on console:
> 
> wrapper  | CTRL-C trapped.  Shutting down.
> 
> However if I'm running in a service mode with console enabled, then I dont see this line on screen, and my application donesn't shut down properly :(
> 
> Anyone knows why?
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] reboot on linux

[chris o. <chr...@ya...>]

Hi -- I am running the wrapper on redhat 9.0 w jdk 1.4.2 -- i get 
occasional reboots of my jvm by the wrapper during high load. is there a 
way to configure the wrapper that it ** never **  automatically restarts 
the jvm due to timeouts, but will do so via command (app restart) or 
using jmx.

Thank you,

Chris

[Wrapper-user] CTRL-C not trapped in sercice console mode!

[Ben D. T. <to...@xm...>]

Hi

When I'm running wrapper in regular console mode ( -c ) then it trapps perfectly the CTRL-C and I see on console:

wrapper  | CTRL-C trapped.  Shutting down.

However if I'm running in a service mode with console enabled, then I dont see this line on screen, and my application donesn't shut down properly :(

Anyone knows why?

[Wrapper-user] Filters: triggering on things other than strings

[Wrapper U. <wr...@co...>]

As I understand it now, the wrapper can only trigger on an output string.

Is there any way (or near-future plans) to trigger on something other than
output. For example, if the program throws an Exception, or trigger on the
exit code of the application?

In my specific case, I'm having an application "service1" (which I'm under
the assumption can't be changed to display different output) tries to
connect to a (naming) server "service0". Note that service0 will also be
launched by a wrapper. So, basically, service0 should be started before
service1. But I'm starting them with the init.d services in Linux, so that
can't be guaranteed. The way service1 works is that, upon starting up, it
will try to connect to service0. If service0 is not running, service1 will
retry to connect a number of times before giving up and exiting with exit
code 1.

When it can't connect to service0, service1 prints the following:
----------------------------------------------------------
jvm 1    | [ Retrying to connect to 127.0.0.1:1234 ]
...number of times...
jvm 1    | [ Retrying to connect to 127.0.0.1:1234 ]
jvm 1    | [ Retrying to connect to 127.0.0.1:1234 ]
wrapper  | <-- Wrapper Stopped
----------------------------------------------------------

So as you see, there's really no unique string it prints out that I can
trigger on after it failed n times. I found it exits with exit code 1 by
running the wrapper with logging set to debug.
Anyway, in theory, at the same time, a different wrapper instance could (in
my case should) be off starting service0, so I'd like service1's wrapper to
restart service1 with the hope that service0 will eventually be up to
connect to. Allowing the wrapper to trigger on service1's exit code would
help.
As a workaround (kluge?) , I could just trigger on the "Retrying to connect"
string, but that would restart after each failed connect, as opposed to
after the program exits in failure.

Another (totally separate) solution would be (and I'm just brainstorming
here) putting some dependencies on different wrapper applications. Something
like writing a totally separate script that somehow checks if service0 is
running (service0 status) before it launches service1...

Any ideas?

Thanks,
Aiman

[Wrapper-user] custom action on wrapper.filter.action

[Ben D. T. <to...@xm...>]

Hi

Regarding

wrapper.filter.action.<n> 
wrapper.filter.trigger.<n> 

How can I tell the action to perform my own code?

since currently my only possibilities are : Possible actions are RESTART, SHUTDOWN, and NONE.  And I want some more actions so I though I can plug in some class of mine that will perform the action, is that possible?

[Wrapper-user] How to Use vbj for the Java wrapper.

[Prasad T. <tir...@ho...>]

Hi

I am trying to use the Java Wrapper. It works fine with the normal classes 
or jar files. I would like to use the following one. Can anyone suggest how 
to use this.

vbj -Duser.region=US -Dvbroker.agent.port=14000 com.server.transform.Server

Can i register this as a service.



Thanks,
Prasad.

_________________________________________________________________
Win a Gillette MACH3 Razor. http://go.msnserver.com/IN/48723.asp Click Here.

[Wrapper-user] JBoss ping timeout, shuts down but doesn't restart

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

I'm using wrapper 3.10 on linux, using:

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
wrapper.app.parameter.1=org.jboss.Main

I got the following in my logs:
INFO   | jvm 1    | 2004/05/13 21:14:59 | Wrapper Manager: The Wrapper 
code did not ping the JVM for 60 seconds.  Quit and let the Wrapper 
resynch.
INFO   | jvm 1    | 2004/05/13 21:14:59 | 21:14:59,954 INFO  [Server] 
JBoss SHUTDOWN: Undeploying all packages

the server shut down and was not started up. I don't see anything in the 
logs that might explain why the ping failed, and there was nothing 
special happening at that time that I know of. I don't have debug output 
from wrapper, but am enabling it in case this happens again.

I'm wondering how the ping could fail, but the wrapper was able to tell 
jboss to shut down so quickly (<1 second later). Also, should the 
wrapper not restart the server if it kills it as a result of timed out 
ping?


regards,

eoin.

[Wrapper-user] blocking in WrapperManager.stopInner()

[Sergey S. <se...@zo...>]

Hello wrapper-user,

What is the purpose of blocking non-first threads in
WrapperManager.stopInner()?
I mean, why not to let them off?
This seem to cause the Wrapper to hang
instead of exiting in certain cases.

-- 
Best regards,
 Sergey                          mailto:se...@zo...

RE: [Wrapper-user] Graceful shutdown problem.

[Oded B. <Ode...@in...>]

Leif,
Because it looked like the service wrapper won't work, I turned to look =
at weblogic documentation, for how to install weblogic as a NT Service.
It seems that they have a solution that should work with the Service =
Wrapper as well, and that is to create a simple Static Java Class that =
will shutdown the server, connecting through JMX, more can be found at =
http://e-docs.bea.com/wls/docs81/adminguide/winservice.html
I haven't had the time to try that, but when I will do that, I will =
write again to this mailing list.
Thanks for your responses.
Cheers,
Oded


-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Leif
Mortenson
Sent: Thu, May 13, 2004 10:08 PM
To: wra...@li...
Subject: Re: [Wrapper-user] Graceful shutdown problem.


Oded,
    Just got back from a week backpacking in the Grand Canyon, so sorry=20
for the
slow response. (Not too sorry though.  I needed the time away :-)

    Thanks for the debug log.  It looks like everything is working=20
correctly as far
as the Wrapper is concerned.  The Wrapper process is sending a stop =
command
to the JVM which causes all registered shutdown hooks to be executed.

    The only place that that security error could be coming from is a=20
shutdown
hook registered by your application or WebLogic.   The Wrapper would not
be calling it directly so I don't think the special permissions are even =

necessary.

    There is a permission that make sure that only privileged code calls =

System.exit.
But the individual shutdown hooks are called by the JVM which is =
privileged.

    That message does not look like a standard security exception=20
however so you
may have to ask the WebLogic guys for some ideas.   I am interested in=20
finding
out the end solution as I am sure you are not the only one wanting to=20
use WebLogic
with the Wrapper.

Cheers,
Leif


Oded Blayer wrote:

>Leif,
>Thanks for your response.
>I tried to grant the wrapper jar permissions, by simply granting all =
permisions to everybody, my weblogic.policy file looks like that:
>grant {
>  permission java.security.AllPermission;
>};
>
>The result was the same, and the wrapper log with DEBUG looks like =
that:
>
>DEBUG  | wrapperp | 2004/05/02 11:41:31 | send a packet PING : ping
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Received a packet PING : ping
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Send a packet PING : ok
>DEBUG  | wrapperp | 2004/05/02 11:41:31 | read a packet PING : ok
>DEBUG  | wrapper  | 2004/05/02 11:41:31 | Got ping response from JVM
>STATUS | wrapper  | 2004/05/02 11:41:31 | CTRL-C trapped.  Shutting =
down.
>DEBUG  | wrapper  | 2004/05/02 11:41:31 | wrapperStopProcess(0) called.
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Got Control Signal 0->200
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Handled signal
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Processing control =
event(WRAPPER_CTRL_C_EVENT)
>INFO   | jvm 1    | 2004/05/02 11:41:31 | WrapperStartStopApp: =
controlEvent(200) Stopping
>INFO   | jvm 1    | 2004/05/02 11:41:31 | WrapperManager.stop(0) called =
by thread: Wrapper-Control-Event-Monitor
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Send a packet STOP : 0
>DEBUG  | wrapperp | 2004/05/02 11:41:31 | read a packet STOP : 0
>DEBUG  | wrapper  | 2004/05/02 11:41:31 | JVM requested a shutdown. (0)
>DEBUG  | wrapper  | 2004/05/02 11:41:31 | wrapperStopProcess(0) called. =
 (IGNORED)
>DEBUG  | wrapper  | 2004/05/02 11:41:31 | Sending stop signal to JVM
>DEBUG  | wrapperp | 2004/05/02 11:41:31 | send a packet STOP : NULL
>INFO   | jvm 1    | 2004/05/02 11:41:31 | Received a packet STOP :=20
>INFO   | jvm 1    | 2004/05/02 11:41:32 | Thread, =
Wrapper-Control-Event-Monitor, handling the shutdown process.
>INFO   | jvm 1    | 2004/05/02 11:41:32 | calling listener.stop()
>INFO   | jvm 1    | 2004/05/02 11:41:32 | WrapperStartStopApp: stop(0)
>INFO   | jvm 1    | 2004/05/02 11:41:32 | WrapperStartStopApp: invoking =
stop main method
>INFO   | jvm 1    | 2004/05/02 11:41:32 |=20
>INFO   | jvm 1    | 2004/05/02 11:41:32 | Graceful shutdown command =
issued to the server "EMSServer". This command might take time since the =
server waits for inflight work to finish before shutdown. If you wish to =
ignore inflight work please use FORCESHUTDOWN command to override =
inflight work and shutdown the server ...
>INFO   | jvm 1    | 2004/05/02 11:41:32 | Error: Access not allowed for =
subject: principals=3D[], on ResourceType: ServerRuntime Action: =
execute, Target: shutdown.
>INFO   | jvm 1    | 2004/05/02 11:41:32 | Wrapper Manager: ShutdownHook =
started
>INFO   | jvm 1    | 2004/05/02 11:41:32 | WrapperManager.stop(0) called =
by thread: Wrapper-Shutdown-Hook
>ERROR  | wrapper  | 2004/05/02 11:41:34 | JVM exited unexpectedly while =
stopping the application.
>STATUS | wrapper  | 2004/05/02 11:41:34 | <-- Wrapper Stopped
>
>About the weblogic calling halt, this is very possible, since weblogic =
should wait for all of the resources to be closed.
>Do the wrapper have problems with halt calls?
>Do you have any other idea of what can be the problem?
>
>Thanks,
>Oded.
>
>-----Original Message-----
>From: wra...@li...
>[mailto:wra...@li...]On Behalf Of Leif
>Mortenson
>Sent: Thu, April 29, 2004 7:04 PM
>To: wra...@li...
>Subject: Re: [Wrapper-user] Graceful shutdown problem.
>
>
>Oded,
>The access violation is probably being caused by a SecurityManager(??)  =

>If that is the
>case then you will need to give wrapper.jar full privileges in your=20
>policy file.
>
>The only reason I could think why you would be getting the unexpected=20
>exit was if
>the JVM called Runtime.halt(), or if you have the Wrapper's shutdown =
hook
>disabled.  Is it possible that BEA is calling halt after that access=20
>violation?
>
>You can try turning on wrapper.debug, but I am not sure if that will=20
>give you
>any more info in this case.
>
>Cheers,
>Leif
>
>Oded Blayer wrote:
>
> =20
>
>>Hi, I have a problem using the Service Wrapper version 3.1 to wrap BEA =

>>Weblogic 8.1 on Windows 2K.
>>When I hit ^C in order to test the shutdown I get the following lines=20
>>in the wrapper log:
>>=20
>>STATUS | wrapper  | 2004/04/29 16:42:15 | CTRL-C trapped.  Shutting =
down.
>>INFO   | jvm 1    | 2004/04/29 16:42:16 |
>>INFO   | jvm 1    | 2004/04/29 16:42:16 | Graceful shutdown command=20
>>issued to the server "EMSServer". This command might take time since=20
>>the server waits for inflight work to finish before shutdown. If you=20
>>wish to ignore inflight work please use FORCESHUTDOWN command to=20
>>override inflight work and shutdown the server ...
>>INFO   | jvm 1    | 2004/04/29 16:42:16 | Error: Access not allowed=20
>>for subject: principals=3D[], on ResourceType: ServerRuntime Action:=20
>>execute, Target: shutdown.
>>ERROR  | wrapper  | 2004/04/29 16:42:18 | JVM exited unexpectedly=20
>>while stopping the application.
>>STATUS | wrapper  | 2004/04/29 16:42:18 | <-- Wrapper Stopped
>>The shutdown part of the wrapper.conf is :
>># The first application parameter is the name of the class whose main
>># method is to be called when the application is launched.  The class
>># name is followed by the number of parameters to be passed to its =
main
>># method.  Then comes the actual parameters.
>>wrapper.app.parameter.1=3Dweblogic.Server
>>wrapper.app.parameter.2=3D0
>>=20
>># The start parameters are followed by the name of the class whose =
main
>># method is to be called to stop the application.  The stop class name
>># is followed by a flag which controls whether or not the Wrapper =
should
>># wait for all non daemon threads to complete before exiting the JVM.
>># The flag is followed by the number of parameters to be passed to the
>># stop class's main method.  Finally comes the actual parameters.
>>wrapper.app.parameter.3=3Dweblogic.Admin
>>wrapper.app.parameter.4=3Dtrue
>>wrapper.app.parameter.5=3D7
>>wrapper.app.parameter.6=3D-url t3://localhost:80
>>wrapper.app.parameter.7=3D-username system
>>wrapper.app.parameter.8=3D-password password
>>wrapper.app.parameter.9=3DSHUTDOWN
>>Have you any idea as to what causes this problem?
>>Thanks
>>=20
>>Oded Blayer
>>od...@in... <mailto:od...@in...>
>>=20
>>



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=3D2562&alloc_id=3D6184&op=3Dclick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] How to set arguments containing "/" and how to span multiple lines?

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

Marcel,

> 1.How can i use "/" in argument values, for example:
>
>     wrapper.java.additional.2=-Dtest="BLA/BLU"
>     wrapper.app.parameter.2="BLA/BLU"
>
>   cuts the tail and delivers only "BLA".
>   Is this a bug?

What version and platform are you using?  I just tested this out using 
3.1.0 on both
Windows and Linux and it is working correctly.  Tried both '/' and '\'

Try setting wrapper.debug=true to make sure that the command used to 
launch the
JVM is correct.  Then try printing out args[1] and System.getProperty( 
"test" ).

> 2. How to use multiple lines for one argument, example:
>
>   wrapper.app.parameter.3="JdbcQueueCommonTablePlugin,\
>                   
> url=jdbc:microsoft:sqlserver://localhost:1433;DatabaseName=xmlBlaster,\
>                   user=sa,\
>                   password=secret,\
>                   dbAdmin=true"
>
>   using '\' does not work, is there another way?

The Wrapper does not support properties that are broken up into multiple 
lines.
Do you want to do this in the conf file or do you want to set app 
parameters that
contain line feeds.  I don't think that is possible with standalone java 
either though.

Cheers,
Leif

Re: [Wrapper-user] running as NT service. where is the logfile?

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

Alphonse,
    The wrapper logfile's location is controlled by the wrapper.logfile 
property
and its log level is controlled by the wrapper.logfile.loglevel 
property.  If the
logfile log level is too high then no logging will be made to the log file.

    The log file will be written relative to the location of the 
wrapper.exe file
so it should be working if it was working when run as a console application.
If it fails to be written for any reason then it will fall back to the 
location of
the wrapper.exe.  If that fails as well then it will write to the 
current directory.
When run as an NT service, this will be the windows system32 directory.

    The directory that you have specified looks correct so I doubt it is 
a path
problem.   Another reason that I have seen is a permission problem.   When
running as an NT service the Wrapper will by default run as the System user.
Make sure that you have not configured the wrapper's log directory is such
a way that that user does not have write access.

Cheers,
Leif

Alphonse Bendt wrote:

> hello all,
>
> when running my app as a NT service i can't find the logfile.
>
> if i start the application in the console the logfile is written as 
> expected therefor i think my configuration is correct.
>
> [...]
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=INFO
>
>
> # Log file to use for wrapper output logging.
> wrapper.logfile=../NotifyService-Wrapper.log
> [...]
>
> then i delete the logfile and start the app as NT service.
>
> the service starts successfully. unfortunately the logfile does not 
> appear in the location where i expect it.
>
> i did search the diskdrive for the logfile but was unable to find it.
>
> Did i miss some configuration option?
>
> OS: Win XP
> Wrapper version: 3.1.0
> JDK: 1.4.2_03
>
> best regards,
>     alphonse
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] running as NT service. where is the logfile?

[<cyb...@t-...>]

hello all,

when running my app as a NT service i can't find the logfile.

if i start the application in the console the logfile is written as 
expected therefor i think my configuration is correct.

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

# Log file to use for wrapper output logging.
wrapper.logfile=../NotifyService-Wrapper.log
[...]

then i delete the logfile and start the app as NT service.

the service starts successfully. unfortunately the logfile does not 
appear in the location where i expect it.

i did search the diskdrive for the logfile but was unable to find it.

Did i miss some configuration option?

OS: Win XP
Wrapper version: 3.1.0
JDK: 1.4.2_03

best regards,
	alphonse

Re: [Wrapper-user] Wrapper 3.1.0 on HP-UX

[Andreas W. <and...@em...>]

Leif,

I am current working on a "generic" Makefile for all platforms.
This new Makefile is actually a merger of all current platform-specific 
Makefiles.
It makes use of both standard make variables like CC, CFLAGS, etc. and 
the GCC for compiling and linking.
Escpecially the mixture of using gcc for compiling and sometimes using 
the system's linker (mostly ld) for linking, is probably the cause for 
the problems. When using gcc for linking, it takes care of passing the 
proper arguments to the underlying linker.
I got the Makefile running on the systems I have access to (AIX, 
Solaris, OSF1, Irix, Linux), but did not succeed on HP-UX, since the 
binutils are broken on my boxes (but I hope Ashish can help on this).
I will also test it on my home box (Mac OS X 10.3) next week.
I will then send the Makefile around, and would appreciate your 
feedback.

Cheers,
Andreas

> Ashish, Andreas,
>
> Ashish Gawarikar wrote:
>
>> Andreas Wendt wrote:
>>
>>> When using the native compiler (HP's cc) on my boxes, these errors 
>>> do not occur.
>>>
>> We should make that change in the Makefile(s) and rebuild..
>
> I will be very happy to commit a fix for this and get it into the next 
> release.  This has
> been an issue for 64 bit HP-UX users for quite some time and is not 
> something that
> I can track down myself due to a lack of hardware.   Awaiting a tested 
> patch.
>
> Cheers,
> Leif
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>