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

Re: [Wrapper-user] Java service - windows service recovery?

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

Sandeep,
    Sorry, but the Wrapper does not currently exit with the correct exit 
code.  I added
a feature request for this last month and try to get it into the Wrapper 
for a near future
version.  You might want to monitor the feature request so you will get 
notifications
on its progress.
http://sourceforge.net/tracker/index.php?func=detail&aid=852491&group_id=39428&atid=425190

    One alternative for you would be to write a simple utility class 
which you specify
as the main class (Ie the first parameter to WrapperSimpleApp)   It 
would start by
calling the WrapperManager.getJVMId() method to find out which 
invocation number
the JVM was.  If it is < 4 then call you real application's main 
method.  Otherwise
call a method that executes SendMail and then calls System.exit().   
Alternatively you
could make use of the Java Mail API rather than using SendMail.  It is 
quite easy to
use.

    I am also working on another feature that will allow you to run 
arbitrary external
programs in response to various events in the Wrapper life cycles.  Some 
users have
needed this functionality so they could, for example, run an application 
after a JVM
crashes, but before a new one is launched.  I was planning to have 
events for the
startup and shutdown of the Wrapper as well.   This feature is still in 
the design phase
so if you have any requirements you would like me to consider, go ahead 
and post them.
http://sourceforge.net/tracker/index.php?func=detail&aid=837037&group_id=39428&atid=425190

Cheers,
Leif

Sandeep Khanna wrote:

>Hi All,
>
>We have been using Java Service Wrapper for the past several months to
>run a couple of Java programs as Windows services.
>
>Our current requirement needs us to use the Windows "service recovery
>options". In the Properties page of a service one can set 3 different
>actions to take when a service fails to start for 3 consecutive times.
>We needed this to be able to execute a restart the first 2 failures and
>execute a command-line SendMail.exe to send mail to support on the 3rd
>failure.
>
>Unfortunately, my investigation has revealed that the Java Service
>Wrapper does not return an exit code to the Windows Service manager to
>trigger the service recovery settings. I even tried using the 3
>integration technique as mentioned on the website, but to no success!
>
>Can somebody comment if this is possible using Java Service Wrapper and
>it's current feature set and/or I am missing something here?
>
>If YES, please explain how?
>If NO, please suggest alternatives?
>
>Thanks in advance,
>Sandeep Khanna
>  
>

[Wrapper-user] Java service - windows service recovery?

[Sandeep K. <san...@vi...>]

Hi All,

We have been using Java Service Wrapper for the past several months to
run a couple of Java programs as Windows services.

Our current requirement needs us to use the Windows "service recovery
options". In the Properties page of a service one can set 3 different
actions to take when a service fails to start for 3 consecutive times.
We needed this to be able to execute a restart the first 2 failures and
execute a command-line SendMail.exe to send mail to support on the 3rd
failure.

Unfortunately, my investigation has revealed that the Java Service
Wrapper does not return an exit code to the Windows Service manager to
trigger the service recovery settings. I even tried using the 3
integration technique as mentioned on the website, but to no success!

Can somebody comment if this is possible using Java Service Wrapper and
it's current feature set and/or I am missing something here?

If YES, please explain how?
If NO, please suggest alternatives?

Thanks in advance,
Sandeep Khanna

Re: [Wrapper-user] How to catch other system events

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

Richard,
Sorry I never answered you did I.

The Wrapper currently catches system events in the native code,
Wrapper.DLL. It is taking any signal except the CTRL_BREAK_EVENT, which
is used to generate thread dumps.
What is the actual system signal that your card is throwing? Normally
windows does not throw any signals that I know of when a user logs in. I am
interesting in finding out how your card works because I have been looking
for a nice clean way of telling when a user logs on for a while. The next
version of the Wrapper allows you to poll for this information, but there is
no signal that I could find that is fired when a user logs on to a
Windows system.

Here is the native code that parses the signals. Note that I am passing any
unknown signals off to the JVM as well so the controlEvent method of your
WrapperListener should get them if they are thrown.

---
int wrapperConsoleHandler(int key) {
int event;

/* Call the control callback in the java code */
switch(key) {
case CTRL_C_EVENT:
event = org_tanukisoftware_wrapper_WrapperManager_WRAPPER_CTRL_C_EVENT;
break;
case CTRL_BREAK_EVENT:
/* This is a request to do a thread dump. Let the JVM handle this. */
return FALSE;
case CTRL_CLOSE_EVENT:
event = org_tanukisoftware_wrapper_WrapperManager_WRAPPER_CTRL_CLOSE_EVENT;
break;
case CTRL_LOGOFF_EVENT:
event = org_tanukisoftware_wrapper_WrapperManager_WRAPPER_CTRL_LOGOFF_EVENT;
break;
case CTRL_SHUTDOWN_EVENT:
event =
org_tanukisoftware_wrapper_WrapperManager_WRAPPER_CTRL_SHUTDOWN_EVENT;
break;
default:
event = key;
}
if (wrapperJNIDebugging) {
printf("Got Control Signal %d->%d\n", key, event);
flushall();
}

wrapperJNIHandleSignal(event);

if (wrapperJNIDebugging) {
printf("Handled signal\n");
flushall();
}

return TRUE; /* We handled the event. */
}
---

Please most back with as much info as you can make available even if you
get this working.

Cheers,
Leif

Richard Luong wrote:

> I want to hook onto the Windows Login (Gina.dll) so that I can login
> through an ID card. I can do the JNI stuff to talk from Java to the C
> dll. But I would like the C code to be able to talk back to the Java
> code through throwing events to my NT Service.
>
> My question is, does the Java Service Wrapper catch all events and
> pass them on? If that's so, then problem solved.
>
> If not, does it only pass on specific control events such as windows
> logoff, shutdown and ctr+C ?
>
> If so, can I modify the code to pass on all events? I know that I will
> have to use Integration Method #3, which is not a problem for me.
> However, any pointers to the code that is catching and possibly
> ignoring/passing on events would be helpful.
>
> Thanks.
>
> _________________________________________________________________
> Expand your wine savvy ・and get some great new recipes ・at MSN Wine.
> http://wine.msn.com
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] How to catch other system events

[Richard L. <ric...@ms...>]

Hi,

I want to hook onto the Windows Login (Gina.dll) so that I can login through 
an ID card. I can do the JNI stuff to talk from Java to the C dll. But I 
would like the C code to be able to talk back to the Java code through 
throwing events to my NT Service.

My question is, does the Java Service Wrapper catch all events and pass them 
on? If that's so, then problem solved.

If not, does it only pass on specific control events such as windows logoff, 
shutdown and ctr+C ?

If so, can I modify the code to pass on all events? I know that I will have 
to use Integration Method #3, which is not a problem for me. However, any 
pointers to the code that is catching and possibly ignoring/passing on 
events would be helpful.

Thanks.

_________________________________________________________________
Expand your wine savvy — and get some great new recipes — at MSN Wine. 
http://wine.msn.com

[Wrapper-user] Re: Services Performance...

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

Elhanan,
    Please post tot the Wrapper users list rather than to me directly.  
This lets others
answer your questions and makes the mail searchable so others can learn 
from it in the
future.
 
אלחנן מעיין wrote:

> Hi.. after running our java program on it's normal mode and running it 
> as a service we noticed there is a difference in performance between 
> the two (the first takes around 2-3 seconds, and as a service takes 8 
> seconds) any ideas on what's creating the laaag?
>
    I am going to need more information to be able to give you any 
useful answers.
When is the service being run?  At startup?  Is it possible that the 
service is competing for
system resources etc?

    The only difference in performance that I am aware of is actually 
the other way around.
If an application sends large quantities of output to stdout then the 
Wrapper, and a
standalone JVM for that matter, sends all of that information to the 
console.  Windows
is pretty slow in the way it displays text in a command window and 
quickly becomes a
bottle neck as it tries to paint all of the text, in graphics mode, in 
real time.
    When running as a service, there is no console so all of that output 
is just thrown away.
In both cases, writing to a log file is very fast.

    Could you try enabling debug output and run a single run in Console 
mode and then
again as a Service.  By comparing the timestamps in the log files it may 
become obvious
if a particular action is taking a lot of time or if the application is 
in general running slower
as a service.
    I have not seen this behavior but I'll do a few tests to get some 
numbers.

Cheers,
Leif

>
> This mail was scanned and found secure
>
> The contents of this email and any attachments are confidential.
> It is intended for the named recipient(s) only.
> If you have received this email in error please notify the sender 
> immediately through the
> technological support center,email:he...@mi... and do not 
> disclose the contents to any one or make copies.
>
>

Re: [Wrapper-user] cant access main function in parent class

[Aiman Y. <wr...@co...>]

Thanks for the quick response, Leif.

I also hadn't known it was possible that it could work without its own main
function until I started getting that error and investigated.

The reason the child is launched from the command line is because the parent
is an abstract class. The child(ren) statically sets a variable (among other
things, but I didn't look into it very deeply) which is used in the Parent's
main class to identify what kind of child it is. So for different children
objects to be instantiated (they are different types of servers), the
children have to be run to identify themselves.

I would have replied sooner but I was trying to get that dummy class written
and compiled. It became somewhat confusing...as confusing as the above
paragraph, and for the same reasons :)
But its working for now.

And any idea about if/when a new version that can call the parent's main
would be available? I'm not looking for anything specific...just a "next
month" or "within 2 years" type of answer.

Thanks again,
Aiman

----- Original Message ----- 
From: "Leif Mortenson" <le...@ta...>
To: <wra...@li...>
Sent: Tuesday, January 06, 2004 11:19 AM
Subject: Re: [Wrapper-user] cant access main function in parent class


> Aiman,
>     The WrapperSimpleApp and WrapperStartStopApp classes currently only
> look for a
> static main method in the class specified as the main class.  It does
> not recurse up and
> look at the parent classes looking for a main method.    I had not
> actually known that
> was legal.   I'll do some testing here and get this fixed for a future
> version.
>
>     For now, you can work around this by creating a dummy class whose
> main method
> simply calls the main method that you want.
>
>     Thinking about this as I write however, I am confused as to why you
> do not just specify
> BlaParent as your main class?   The main class is static so there is no
> reason to be calling
> the main method using the child class name.
>
>     As for searching the list, go to the following page:
> http://sourceforge.net/mailarchive/forum.php?forum_id=11948
>
>     Use the search box in the upper left of the screen.  It is a bit
> confusing as it is the same
> search box as the SF site.  But if you look closely you will see the
> list box over the field
> says "This Mailing List".
>
> Cheers,
> Leif
>
> Aiman Younis wrote:
>
> >Hi.
> >Just joined the mailing list today (just started using the software last
> >week).
> >
> >I've run into a problem where I get the error:
> >jvm 1    | WrapperSimpleApp: Unable to locate a static main method in
class
> >com.my.class.Bla: java.lang.NoSuchMethodException:
> >com.my.class.Bla.main([Ljava.lang.String;)
> >
> >I looked in the code of Bla (not my code), and there was no main class,
> >however Bla extended BlaParent which does have a main class. So when Bla
is
> >run from the command line, it works.
> >
> >So does anybody know how to have WrapperSimpleApp launch Bla even though
it
> >uses BlaParent's main function to start?
> >
> >And one more (non-related) question. Is there a way to search the mailing
> >list archives? I went through all the subjects of the archives on the web
> >looking for the word "main" hoping to find this question already asked. I
> >didn't find anything though, so I apologize if this is a repeat question.
> >
> >Thanks,
> >Aiman
> >
> >
> >
> >-------------------------------------------------------
> >This SF.net email is sponsored by: IBM Linux Tutorials.
> >Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> >Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> >Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> >_______________________________________________
> >Wrapper-user mailing list
> >Wra...@li...
> >https://lists.sourceforge.net/lists/listinfo/wrapper-user
> >
> >
> >
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] cant access main function in parent class

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

Aiman,
    The WrapperSimpleApp and WrapperStartStopApp classes currently only 
look for a
static main method in the class specified as the main class.  It does 
not recurse up and
look at the parent classes looking for a main method.    I had not 
actually known that
was legal.   I'll do some testing here and get this fixed for a future 
version.

    For now, you can work around this by creating a dummy class whose 
main method
simply calls the main method that you want.

    Thinking about this as I write however, I am confused as to why you 
do not just specify
BlaParent as your main class?   The main class is static so there is no 
reason to be calling
the main method using the child class name.

    As for searching the list, go to the following page:
http://sourceforge.net/mailarchive/forum.php?forum_id=11948

    Use the search box in the upper left of the screen.  It is a bit 
confusing as it is the same
search box as the SF site.  But if you look closely you will see the 
list box over the field
says "This Mailing List".

Cheers,
Leif

Aiman Younis wrote:

>Hi.
>Just joined the mailing list today (just started using the software last
>week).
>
>I've run into a problem where I get the error:
>jvm 1    | WrapperSimpleApp: Unable to locate a static main method in class
>com.my.class.Bla: java.lang.NoSuchMethodException:
>com.my.class.Bla.main([Ljava.lang.String;)
>
>I looked in the code of Bla (not my code), and there was no main class,
>however Bla extended BlaParent which does have a main class. So when Bla is
>run from the command line, it works.
>
>So does anybody know how to have WrapperSimpleApp launch Bla even though it
>uses BlaParent's main function to start?
>
>And one more (non-related) question. Is there a way to search the mailing
>list archives? I went through all the subjects of the archives on the web
>looking for the word "main" hoping to find this question already asked. I
>didn't find anything though, so I apologize if this is a repeat question.
>
>Thanks,
>Aiman
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>

[Wrapper-user] cant access main function in parent class

[Aiman Y. <wr...@co...>]

Hi.
Just joined the mailing list today (just started using the software last
week).

I've run into a problem where I get the error:
jvm 1    | WrapperSimpleApp: Unable to locate a static main method in class
com.my.class.Bla: java.lang.NoSuchMethodException:
com.my.class.Bla.main([Ljava.lang.String;)

I looked in the code of Bla (not my code), and there was no main class,
however Bla extended BlaParent which does have a main class. So when Bla is
run from the command line, it works.

So does anybody know how to have WrapperSimpleApp launch Bla even though it
uses BlaParent's main function to start?

And one more (non-related) question. Is there a way to search the mailing
list archives? I went through all the subjects of the archives on the web
looking for the word "main" hoping to find this question already asked. I
didn't find anything though, so I apologize if this is a repeat question.

Thanks,
Aiman

RE: [Wrapper-user] wrapper executable fails to restart JVM

[Sal I. <sal...@sy...>]

the way i see it the wrapper is a process and the jvm is another.
when the kill signals go around, they go directly to all processes.
that explains why one process dies but not the other.

i'm with you on the second question.  why isn't the wrapper restarting it?
could the intermediate/daemon processes be in an inconsistent state if they
manage the jvm pinging?

that'sall i got

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Robert
DiFalco
Sent: Monday, January 05, 2004 1:04 PM
To: wra...@li...
Subject: RE: [Wrapper-user] wrapper executable fails to restart JVM


I'm not sure how this is related. When the JVM dies, if you *are* using
the wrapper, shouldn't the wrapper restart it?

-----Original Message-----
From: Sal Ingrilli [mailto:sal...@sy...]
Sent: Monday, January 05, 2004 12:00 PM
To: wra...@li...
Subject: RE: [Wrapper-user] wrapper executable fails to restart JVM


at my old job we never ran the wrapper but we did run java/weblogic.

our java process would simply die for no reason, and even simultaneously
across networks!

we had one network in NY running production & one in CA running qa.

servers in both time zones would die simultaneously.

we were going crazy & did a ton of research.

after weeks of dealing with weblogic, we got escalated to a tech who
told us to run the java process with NOHUP.

so instead of running
java MyApp
run
nohup java MyApp

nohup is unix utility that ignores kill signals from the OS.

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Patrick
Woodworth
Sent: Monday, January 05, 2004 11:45 AM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper executable fails to restart JVM



To follow up with a little more info in case it's of any use.  We've
been running duration tests with the debug output on, on a number of
boxes for two weeks, but haven't seen this problem on any of them.  We
recently reinstalled the application on one box but forgot to turn the
debugging output on, and of course 21 hours later the JVM process was
gone.  The log snippet from the previous email is from that failure.
We've now turned debugging on again, but it's not clear whether we can
reproduce the problem with debugging on.


--- Patrick Woodworth <wo...@em...> wrote:
> I'm using the wrapper to run a service and I'm seeing odd behaviour on
> two Solaris 8 boxes.  Basically the java process dies and goes away.
> The wrapper executable is still running but never restarts the JVM.
> This has happened on two different boxes, sometimes after running for
> 2
> weeks and sometimes after only 21 hours or so.  Unfortunately I
> haven't
> been able to reproduce the error with debug flags on, but below is a
> snippet of what does appear in the log file.  Basically the first
> line
> of the snippet is the last thing sent to the log before manual
> intervention.  The rest of the snippet occurs after we noticed the
> JVM
> process no longer existed and we manually told the wrapper to
> restart.
> Any suggestions on what this might be?
>
> INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.
> STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down. INFO | jvm 1 |

> 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper code
> did not ping the JVM for 30 seconds. Quit and let the Wrapper
> resynch.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service
> Tomcat-Standalone
> INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not
> received
> any CPU time for 104525 seconds. Extending timeouts.
> STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
> process...
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
> STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as
> Console
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials. Become an
> expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user


-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=ick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

RE: [Wrapper-user] wrapper executable fails to restart JVM

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

I'm not sure how this is related. When the JVM dies, if you *are* using
the wrapper, shouldn't the wrapper restart it?

-----Original Message-----
From: Sal Ingrilli [mailto:sal...@sy...]=20
Sent: Monday, January 05, 2004 12:00 PM
To: wra...@li...
Subject: RE: [Wrapper-user] wrapper executable fails to restart JVM


at my old job we never ran the wrapper but we did run java/weblogic.

our java process would simply die for no reason, and even simultaneously
across networks!

we had one network in NY running production & one in CA running qa.

servers in both time zones would die simultaneously.

we were going crazy & did a ton of research.

after weeks of dealing with weblogic, we got escalated to a tech who
told us to run the java process with NOHUP.

so instead of running
java MyApp
run
nohup java MyApp

nohup is unix utility that ignores kill signals from the OS.

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Patrick
Woodworth
Sent: Monday, January 05, 2004 11:45 AM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper executable fails to restart JVM



To follow up with a little more info in case it's of any use.  We've
been running duration tests with the debug output on, on a number of
boxes for two weeks, but haven't seen this problem on any of them.  We
recently reinstalled the application on one box but forgot to turn the
debugging output on, and of course 21 hours later the JVM process was
gone.  The log snippet from the previous email is from that failure.
We've now turned debugging on again, but it's not clear whether we can
reproduce the problem with debugging on.


--- Patrick Woodworth <wo...@em...> wrote:
> I'm using the wrapper to run a service and I'm seeing odd behaviour on
> two Solaris 8 boxes.  Basically the java process dies and goes away.
> The wrapper executable is still running but never restarts the JVM.
> This has happened on two different boxes, sometimes after running for
> 2
> weeks and sometimes after only 21 hours or so.  Unfortunately I
> haven't
> been able to reproduce the error with debug flags on, but below is a
> snippet of what does appear in the log file.  Basically the first
> line
> of the snippet is the last thing sent to the log before manual
> intervention.  The rest of the snippet occurs after we noticed the
> JVM
> process no longer existed and we manually told the wrapper to
> restart.
> Any suggestions on what this might be?
>
> INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.=20
> STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down. INFO | jvm 1 |

> 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper code
> did not ping the JVM for 30 seconds. Quit and let the Wrapper
> resynch.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service
> Tomcat-Standalone
> INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not
> received
> any CPU time for 104525 seconds. Extending timeouts.
> STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
> process...
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
> STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as
> Console
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials. Become an=20
> expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys
> admin.
> Click now! =
http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

RE: [Wrapper-user] wrapper executable fails to restart JVM

[Sal I. <sal...@sy...>]

at my old job we never ran the wrapper but we did run java/weblogic.

our java process would simply die for no reason, and even simultaneously
across networks!

we had one network in NY running production & one in CA running qa.

servers in both time zones would die simultaneously.

we were going crazy & did a ton of research.

after weeks of dealing with weblogic, we got escalated to a tech who told us
to run the java process with NOHUP.

so instead of running
java MyApp
run
nohup java MyApp

nohup is unix utility that ignores kill signals from the OS.

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Patrick
Woodworth
Sent: Monday, January 05, 2004 11:45 AM
To: wra...@li...
Subject: Re: [Wrapper-user] wrapper executable fails to restart JVM



To follow up with a little more info in case it's of any use.  We've
been running duration tests with the debug output on, on a number of
boxes for two weeks, but haven't seen this problem on any of them.  We
recently reinstalled the application on one box but forgot to turn the
debugging output on, and of course 21 hours later the JVM process was
gone.  The log snippet from the previous email is from that failure.
We've now turned debugging on again, but it's not clear whether we can
reproduce the problem with debugging on.


--- Patrick Woodworth <wo...@em...> wrote:
> I'm using the wrapper to run a service and I'm seeing odd behaviour
> on
> two Solaris 8 boxes.  Basically the java process dies and goes away.
> The wrapper executable is still running but never restarts the JVM.
> This has happened on two different boxes, sometimes after running for
> 2
> weeks and sometimes after only 21 hours or so.  Unfortunately I
> haven't
> been able to reproduce the error with debug flags on, but below is a
> snippet of what does appear in the log file.  Basically the first
> line
> of the snippet is the last thing sent to the log before manual
> intervention.  The rest of the snippet occurs after we noticed the
> JVM
> process no longer existed and we manually told the wrapper to
> restart.
> Any suggestions on what this might be?
>
> INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.
> STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper
> code
> did not ping the JVM for 30 seconds. Quit and let the Wrapper
> resynch.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service
> Tomcat-Standalone
> INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not
> received
> any CPU time for 104525 seconds. Extending timeouts.
> STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
> process...
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
> STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as
> Console
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

RE: [Wrapper-user] Request for opinions on the API for requesting user information.

[Sal I. <sal...@sy...>]

I like what you're saying.

I will find this new functionality useful for debugging whether the service
is indeed running as we intended it to be: system account or domained user
account (this is a must if you wanna be able to access printers & mount
points).

Additionally this is going to be very useful information to show somewhere
on my UI for a sysadmin to see.

So I will welcome these changes very much.

Since one of the OS requests you're talking about are beefy, consider adding
a separate mbean to display this info.
Then from the existing wrapper mbean you can add a method like this:
ObjectName getUserMBean ()

When you do this, the jmx consoles don't display the mbean ObjectName.
Instead, they show it as a link to the mbean specified by the object name.
This way the beefy domain call you're talking about does not get executed
until you click on the link!

-----Original Message-----
From: wra...@li...
[mailto:wra...@li...]On Behalf Of Leif Mortenson
Sent: Sunday, January 04, 2004 10:09 PM
To: Wrapper User List
Subject: [Wrapper-user] Request for opinions on the API for requesting user
information.


The next version of the Wrapper will include the ability to request
information about the user currently running the Wrapper as well
as the user, if any, that is currently logged in to a Windows box.
This is implemented using the following two calls:

WrapperUser WrapperManager.getUser( boolean groups )
WrapperUser WrapperManager.getInteractiveUser( boolean groups )

Both methods take a parameter that specifies whether or not the returned
WrapperUser object should contain information about which groups the
user belongs to. This is a fairly heavy operation on Windows so I wanted
to give the user the option of not requesting the groups if it is not
needed.

The returned WrapperUser object is actually an instance of a
WrapperWin32User or a WrapperUNIXUser. They each contain additional
platform specific information.

On Windows the getUser call will always return a user. But when the Wrapper
is being run as a service, this will most likely be the SYSTEM user. Which
is not very interesting.

If the getInteractiveUser method is called before a user logs on to the
machine
it will return null. Otherwise it will return the user, if any, which
currently
has interactive status with the Wrapper as a service. If the service is not
interactive then this will always return null.

User code will need to poll these methods manually to detect when a user
logs on. They are not super heavy, but heavy enough that I do not want
the wrapper to be making the calls unless the user code actually needs
the user information.

First of all does anyone have any opinions or concerns about the Windows
implementation?

My next question is what do you think would be best to do on the UNIX
side?

The getUser call will return the user that is currently running the Wrapper.

But what should the getInteractiveUser method return?
Currently I am thinking of having it return null unless a DISPLAY
environment variable is detected. Otherwise it would return null.

Users often ask how to detect when a user has opened an XWindows session
under Linux so they can display a GUI. This is actually not very simple
under UNIX however.

Thoughts?

Cheers,
Leif





-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] wrapper executable fails to restart JVM

[Patrick W. <wo...@em...>]

To follow up with a little more info in case it's of any use.  We've
been running duration tests with the debug output on, on a number of
boxes for two weeks, but haven't seen this problem on any of them.  We
recently reinstalled the application on one box but forgot to turn the
debugging output on, and of course 21 hours later the JVM process was
gone.  The log snippet from the previous email is from that failure. 
We've now turned debugging on again, but it's not clear whether we can
reproduce the problem with debugging on.


--- Patrick Woodworth <wo...@em...> wrote:
> I'm using the wrapper to run a service and I'm seeing odd behaviour
> on
> two Solaris 8 boxes.  Basically the java process dies and goes away. 
> The wrapper executable is still running but never restarts the JVM. 
> This has happened on two different boxes, sometimes after running for
> 2
> weeks and sometimes after only 21 hours or so.  Unfortunately I
> haven't
> been able to reproduce the error with debug flags on, but below is a
> snippet of what does appear in the log file.  Basically the first
> line
> of the snippet is the last thing sent to the log before manual
> intervention.  The rest of the snippet occurs after we noticed the
> JVM
> process no longer existed and we manually told the wrapper to
> restart. 
> Any suggestions on what this might be?
> 
> INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.
> STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper
> code
> did not ping the JVM for 30 seconds. Quit and let the Wrapper
> resynch.
> INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service
> Tomcat-Standalone
> INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not
> received
> any CPU time for 104525 seconds. Extending timeouts.
> STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
> process...
> DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
> STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as
> Console
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for
> IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys
> admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: [Wrapper-user] Service recovery

[George K. <gk...@in...>]

Leif thanks for this.
I'll try the WrapperManager.start() fix you're suggesting.
Just to let you know however: I was exiting normally by just logging the
exception.
Then I tried to do this:
try {
...
}
catch (Exception e) {
log(e.getMessage());
throw new RuntimeException();
}
that is before stopping I throw a new RuntimeException just to stop the
program with an exception.
The wrapper still doesn't seem to restart the service however although the
program didn't terminate normally.

Thanks again both for the Wrapper and the excellent support you're providing
for it.

-George

----- Original Message ----- 
From: "Leif Mortenson" <le...@ta...>
To: <wra...@li...>; <gk...@in...>
Sent: Monday, January 05, 2004 10:41 AM
Subject: Re: [Wrapper-user] Service recovery


> George,
>     If I read this correctly then your client application is throwing an
> error because it has lost
> contact with the server.   When that happens the client is exiting by
> calling System.exit?
> Is that correct?
>
>     I have high goals for the Wrapper, but so far it has not yet
> achieved sentience.  At this
> point, when the application exits by calling System.exit, the Wrapper
> currently assumes
> that it wanted to exit.   The Wrapper thus shuts down normally.
>
>     If you want your client application to restart in this event, you
> will need to tell the
> Wrapper so by calling WrapperManager.restart().  Do this rather than
> calling System.exit.
>
>     There is currently a feature request to be able to configure the
> wrapper so that it will
> restart on its own if System.exit is called, but that is not yet
> implemented.
>
>     After the restart, you may also be interested in the
> wrapper.restart.delay property
> if your server will take a while to restart.
>
>     Let me know if I misunderstood your question.
>
> Cheers,
> Leif
>
> George Kakarontzas wrote:
>
> > I have an RMI-based server and a number of PCs.
> > PCs run a wrapper encapsulated service. This service registers with
> > the RMI server and then sends heartbeat messages at regular intervals
> > at the server.
> > This is how the server knows that a PC is still alive.
> > If the server dies (e.g. the server machine reboots) the heartbeat
> > message at the PC will cause an Exception and the java PC program will
> > stop.
> > It was my understanding that in such cases the wrapper will figure out
> > that there is something wrong with the service and it will restart it
> > after a while.
> > This is not happening. If the server hangs for any reason the PCs
> > someone has to start the service manually to register the PCs again.
> > The PCs run Win XP Pro.
> > (1) Is my understanding correct? Is there recovery of failed services
> > in wrapper?
> > (2) If it is do you have any ideas why this isn't working?
> >
> > Thanks
> > -George
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user

[Wrapper-user] wrapper executable fails to restart JVM

[Patrick W. <wo...@em...>]

I'm using the wrapper to run a service and I'm seeing odd behaviour on
two Solaris 8 boxes.  Basically the java process dies and goes away. 
The wrapper executable is still running but never restarts the JVM. 
This has happened on two different boxes, sometimes after running for 2
weeks and sometimes after only 21 hours or so.  Unfortunately I haven't
been able to reproduce the error with debug flags on, but below is a
snippet of what does appear in the log file.  Basically the first line
of the snippet is the last thing sent to the log before manual
intervention.  The rest of the snippet occurs after we noticed the JVM
process no longer existed and we manually told the wrapper to restart. 
Any suggestions on what this might be?

INFO | jvm 1 | 2003/12/31 10:14:43 | WebApplication: SETUP COMPLETED.
STATUS | wrapper | 2004/01/02 13:43:54 | Shutting down.
INFO | jvm 1 | 2004/01/02 13:43:54 | Wrapper Manager: The Wrapper code
did not ping the JVM for 30 seconds. Quit and let the Wrapper resynch.
INFO | jvm 1 | 2004/01/02 13:43:54 | Stopping service Tomcat-Standalone
INFO | wrapper | 2004/01/02 13:43:54 | Wrapper Process has not received
any CPU time for 104525 seconds. Extending timeouts.
STATUS | wrapper | 2004/01/02 13:43:54 | <-- Wrapper Stopped
DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning intermediate
process...
DEBUG | wrapper | 2004/01/02 13:43:59 | Spawning daemon process...
STATUS | wrapper | 2004/01/02 13:43:59 | --> Wrapper Started as Console

RE: [Wrapper-user] Tomcat console logging: Win XP vs. Win 2K

[Scott W. R. <sr...@in...>]

It's a permissions problem.  The difference is that I'm
logged on as Administrator on the Win2K system.  The=20
default user that the service runs under ("LocalSystem")=20
cannot write to the directories that I created for the
application as Administrator.

Problem solved - thanks for helping me think it through.

> -----Original Message-----
> From: wra...@li...=20
> [mailto:wra...@li...] On Behalf=20
> Of Leif Mortenson
> Sent: Monday, January 05, 2004 12:53 AM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Tomcat console logging: Win XP=20
> vs. Win 2K [faked-from][mx]
>=20
>=20
> Scott,
>     Looking over your wrapper.conf file, I do not see any=20
> problems.  I=20
> actually
> have a Dual CPU W2k system at home and it has been working=20
> perfectly.  So
> I don't think it is an issue with the OS.   I will retest it
again=20
> tonight though just
> to make sure.   I use it for services rather than for day to=20
> day use so=20
> I may have
> overlooked something.
>=20
>     When the Wrapper starts up it will attempt to write to=20
> the log file=20
> specified
> in the wrapper.conf file.  In your case this resolves to=20
> C:/Inventa/ESMIntegrator3.0/portal/var/wrapper.log
>=20
>     If the Wrapper is unable to write to configured file it
will fall=20
> back to writing
> to a log file called wrapper.log which is located in the same=20
> directory=20
> as the
> Wrapper.exe file.   When running as an NT service, there are=20
> some failure
> modes where it is also possible that the wrapper.log file could
be=20
> created in
> the C:\Windows\system32 directory.  Or wherever your Windows
directory
> is located.   Can you please verify that the file does not
exist in=20
> those locations?
>=20
>     The next thing I would have you try is set the following:=20
> wrapper.syslog.loglevel=3DSTATUS
>     This will log all of the info level output to your system
event=20
> log.  It may give
> you some useful information.   If not, try a level of INFO. =20
> That will=20
> fill your log
> up fairly quickly as each individual line of output results=20
> in a log entry.
>=20
> >I get no output to the wrapper.log file regardless of
> >whether I enable debugging or not.
> >
> This is strange.  If you are not even getting any output=20
> before the JVM=20
> is launched
> then the Wrapper must be having some problems writing to the=20
> log file.=20
>=20
> >If I run the app
> >via the wrapper console mode (wrapper.exe -c),
> >I see the console output (of course) - and it gets logged
> >to the wrapper.log file (attached).
> >
> Ok, that file looked normal.
>=20
> >  If I run "wrapper -t"
> >to start the app, I get no output beyond the standard 3 log
> >statements from Wrapper itself.
> >
> You should get more than 3 lines if the debug output is
enabled?  Can=20
> you show me
> what 3 lines you are talking about?
>=20
> >  If I start it from the
> >Windows Management Console, *no* wrapper.log file gets
> >created at all.  I searched the filesystems to see if it's
> >getting created somewhere else, but it's not...
> > =20
> >
> Hmm.   Please recheck the locations I mentioned above.
>=20
> >Any thoughts?
> > =20
> >
> "Mondays!" :-)   There must be a logical reason for this.  Post
back=20
> with info I asked for
> above and I'll try to think of what could be going wrong for
you.
>=20
> Are you sure that the Wrapper and its JVM are actually=20
> running after you=20
> start it?  There
> was a bug fixed for the next release that involved the setting
of=20
> environment variables
> when running as an NT service.  It is possible that your use of

> environment variables
> with the set.xxx properties could be running into this=20
> problem.   This=20
> but would cause
> one or more environment variables to not actually be set.  If
your=20
> application happened to
> be using that particular environment variable, it would fail.
>=20
> Try hardcoding the paths into your wrapper.conf file without=20
> using the=20
> environment
> variable replacements.  If that makes the problem go away=20
> then you most=20
> likely running
> into this bug.

[Wrapper-user] Ping

[Charles B. <CB...@me...>]

Hi,
=20
I have an application that I plan to run as an NT Service. All I need =
seems to be covered by this product. The only thing I need that I can't =
find is an applicative ping. What I mean by that is I need to ping my =
application at a regular interval. I know the wrapper is doing just that =
to monitor the health of the VM. But, is there a way to customize the =
way the ping is done ? What could be even better is have the =
controlEvent method of the wrapper interface notified when a ping needs =
to be done. This will allow my application to be restarted if the ping =
is not answering. As an example if I would run Tomcat as a service, I =
would open a socket on my process and make sure I can fetch a file. If =
this failed, Tomcat is not running properly so the wrapper should =
restart my service.
=20
Thank you !
=20
Charles.

Re: [Wrapper-user] Service recovery

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

George,
    If I read this correctly then your client application is throwing an 
error because it has lost
contact with the server.   When that happens the client is exiting by 
calling System.exit?
Is that correct?

    I have high goals for the Wrapper, but so far it has not yet 
achieved sentience.  At this
point, when the application exits by calling System.exit, the Wrapper 
currently assumes
that it wanted to exit.   The Wrapper thus shuts down normally.

    If you want your client application to restart in this event, you 
will need to tell the
Wrapper so by calling WrapperManager.restart().  Do this rather than 
calling System.exit.

    There is currently a feature request to be able to configure the 
wrapper so that it will
restart on its own if System.exit is called, but that is not yet 
implemented.

    After the restart, you may also be interested in the 
wrapper.restart.delay property
if your server will take a while to restart.

    Let me know if I misunderstood your question.

Cheers,
Leif

George Kakarontzas wrote:

> I have an RMI-based server and a number of PCs.
> PCs run a wrapper encapsulated service. This service registers with 
> the RMI server and then sends heartbeat messages at regular intervals 
> at the server.
> This is how the server knows that a PC is still alive.
> If the server dies (e.g. the server machine reboots) the heartbeat 
> message at the PC will cause an Exception and the java PC program will 
> stop.
> It was my understanding that in such cases the wrapper will figure out 
> that there is something wrong with the service and it will restart it 
> after a while.
> This is not happening. If the server hangs for any reason the PCs 
> someone has to start the service manually to register the PCs again.
> The PCs run Win XP Pro.
> (1) Is my understanding correct? Is there recovery of failed services 
> in wrapper?
> (2) If it is do you have any ideas why this isn't working?
>  
> Thanks
> -George

[Wrapper-user] Service recovery

[George K. <gk...@in...>]

I have an RMI-based server and a number of PCs.
PCs run a wrapper encapsulated service. This service registers with the =
RMI server and then sends heartbeat messages at regular intervals at the =
server.
This is how the server knows that a PC is still alive.
If the server dies (e.g. the server machine reboots) the heartbeat =
message at the PC will cause an Exception and the java PC program will =
stop.
It was my understanding that in such cases the wrapper will figure out =
that there is something wrong with the service and it will restart it =
after a while.
This is not happening. If the server hangs for any reason the PCs =
someone has to start the service manually to register the PCs again.
The PCs run Win XP Pro.
(1) Is my understanding correct? Is there recovery of failed services in =
wrapper?
(2) If it is do you have any ideas why this isn't working?

Thanks
-George

[Wrapper-user] Request for opinions on the API for requesting user information.

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

The next version of the Wrapper will include the ability to request
information about the user currently running the Wrapper as well
as the user, if any, that is currently logged in to a Windows box.
This is implemented using the following two calls:

WrapperUser WrapperManager.getUser( boolean groups )
WrapperUser WrapperManager.getInteractiveUser( boolean groups )

Both methods take a parameter that specifies whether or not the returned
WrapperUser object should contain information about which groups the
user belongs to. This is a fairly heavy operation on Windows so I wanted
to give the user the option of not requesting the groups if it is not
needed.

The returned WrapperUser object is actually an instance of a
WrapperWin32User or a WrapperUNIXUser. They each contain additional
platform specific information.

On Windows the getUser call will always return a user. But when the Wrapper
is being run as a service, this will most likely be the SYSTEM user. Which
is not very interesting.

If the getInteractiveUser method is called before a user logs on to the
machine
it will return null. Otherwise it will return the user, if any, which
currently
has interactive status with the Wrapper as a service. If the service is not
interactive then this will always return null.

User code will need to poll these methods manually to detect when a user
logs on. They are not super heavy, but heavy enough that I do not want
the wrapper to be making the calls unless the user code actually needs
the user information.

First of all does anyone have any opinions or concerns about the Windows
implementation?

My next question is what do you think would be best to do on the UNIX
side?

The getUser call will return the user that is currently running the Wrapper.

But what should the getInteractiveUser method return?
Currently I am thinking of having it return null unless a DISPLAY
environment variable is detected. Otherwise it would return null.

Users often ask how to detect when a user has opened an XWindows session
under Linux so they can display a GUI. This is actually not very simple
under UNIX however.

Thoughts?

Cheers,
Leif

Re: [Wrapper-user] Tomcat console logging: Win XP vs. Win 2K

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

Scott,
    Looking over your wrapper.conf file, I do not see any problems.  I 
actually
have a Dual CPU W2k system at home and it has been working perfectly.  So
I don't think it is an issue with the OS.   I will retest it again 
tonight though just
to make sure.   I use it for services rather than for day to day use so 
I may have
overlooked something.

    When the Wrapper starts up it will attempt to write to the log file 
specified
in the wrapper.conf file.  In your case this resolves to
C:/Inventa/ESMIntegrator3.0/portal/var/wrapper.log

    If the Wrapper is unable to write to configured file it will fall 
back to writing
to a log file called wrapper.log which is located in the same directory 
as the
Wrapper.exe file.   When running as an NT service, there are some failure
modes where it is also possible that the wrapper.log file could be 
created in
the C:\Windows\system32 directory.  Or wherever your Windows directory
is located.   Can you please verify that the file does not exist in 
those locations?

    The next thing I would have you try is set the following:
wrapper.syslog.loglevel=STATUS
    This will log all of the info level output to your system event 
log.  It may give
you some useful information.   If not, try a level of INFO.  That will 
fill your log
up fairly quickly as each individual line of output results in a log entry.

>I get no output to the wrapper.log file regardless of
>whether I enable debugging or not.
>
This is strange.  If you are not even getting any output before the JVM 
is launched
then the Wrapper must be having some problems writing to the log file. 

>If I run the app
>via the wrapper console mode (wrapper.exe -c),
>I see the console output (of course) - and it gets logged
>to the wrapper.log file (attached).
>
Ok, that file looked normal.

>  If I run "wrapper -t" 
>to start the app, I get no output beyond the standard 3 log
>statements from Wrapper itself.
>
You should get more than 3 lines if the debug output is enabled?  Can 
you show me
what 3 lines you are talking about?

>  If I start it from the 
>Windows Management Console, *no* wrapper.log file gets
>created at all.  I searched the filesystems to see if it's
>getting created somewhere else, but it's not...
>  
>
Hmm.   Please recheck the locations I mentioned above.

>Any thoughts?
>  
>
"Mondays!" :-)   There must be a logical reason for this.  Post back 
with info I asked for
above and I'll try to think of what could be going wrong for you.

Are you sure that the Wrapper and its JVM are actually running after you 
start it?  There
was a bug fixed for the next release that involved the setting of 
environment variables
when running as an NT service.  It is possible that your use of 
environment variables
with the set.xxx properties could be running into this problem.   This 
but would cause
one or more environment variables to not actually be set.  If your 
application happened to
be using that particular environment variable, it would fail.

Try hardcoding the paths into your wrapper.conf file without using the 
environment
variable replacements.  If that makes the problem go away then you most 
likely running
into this bug.

Cheers,
Leif

RE: [Wrapper-user] Tomcat console logging: Win XP vs. Win 2K

[Scott W. R. <sr...@in...>]

Leif,

I'm not getting anywhere with this - it seems to be
an environmental issue.  Perhaps you can take a look
at the wrapper.conf file (attached)?  I'm using the
same configuration, installation directory and binaries
on the two different OS's.  The only difference
is the OS and the hardware.  The Win2K system is a 
dual CPU machine.

I get no output to the wrapper.log file regardless of
whether I enable debugging or not.  If I run the app
via the wrapper console mode (wrapper.exe -c),
I see the console output (of course) - and it gets logged
to the wrapper.log file (attached).  If I run "wrapper -t" 
to start the app, I get no output beyond the standard 3 log
statements from Wrapper itself.  If I start it from the 
Windows Management Console, *no* wrapper.log file gets
created at all.  I searched the filesystems to see if it's
getting created somewhere else, but it's not...

Any thoughts?

Thanks much,

Scott

> -----Original Message-----
> From: wra...@li... 
> [mailto:wra...@li...] On Behalf 
> Of Leif Mortenson
> Sent: Saturday, January 03, 2004 11:23 AM
> To: wra...@li...
> Subject: Re: [Wrapper-user] Tomcat console logging: Win XP 
> vs. Win 2K [faked-from][mx]
> 
> 
> Scott,
>     There are no problems that I am aware of on Win 2K with
logging.
> Version 3.0.5 simply redirects all stdout and stderr output 
> from the JVM
> process into the wrapper.log file.   Are you sure that the JVM
is not 
> redirecting
> that output to another location?   It is possible to redirect 
> System.out 
> to another
> stream.
> 
>     Try setting the wrapper.debug=true property in the 
> wrapper.conf file 
> and restart your
> application.  You should see debug ping output from the JVM 
> and Wrapper 
> every 5-6
> seconds.  If you are only seeing the output from the Wrapper
then the 
> JVM output may
> be getting redirected.   Check any other log files to see if 
> the output 
> is showing up in
> them.   If you are unable to get this figured out then post
back with 
> the above wrapper.log
> output with debug enabled.  I may be able to give you some 
> further clues.
> 
> Cheers,
> Leif
> 
> 
> Scott W. Ruch wrote:
> 
> >Wrapper version: win32 3.0.5
> >
> >I'm running Tomcat 4.1.29 as an NT service on Win 2K 
> >and Win XP with the following logging configuration.  
> >On XP, the Tomcat console log is directed to wrapper.log
> >as expected, but on Win 2K it is not.  On 2K, all I get 
> >is the initial STATUS & INFO logging from Wrapper.  
> >
> >Any ideas what would be causing this?
> >

Re: [Wrapper-user] Tomcat console logging: Win XP vs. Win 2K

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

Scott,
    There are no problems that I am aware of on Win 2K with logging.
Version 3.0.5 simply redirects all stdout and stderr output from the JVM
process into the wrapper.log file.   Are you sure that the JVM is not 
redirecting
that output to another location?   It is possible to redirect System.out 
to another
stream.

    Try setting the wrapper.debug=true property in the wrapper.conf file 
and restart your
application.  You should see debug ping output from the JVM and Wrapper 
every 5-6
seconds.  If you are only seeing the output from the Wrapper then the 
JVM output may
be getting redirected.   Check any other log files to see if the output 
is showing up in
them.   If you are unable to get this figured out then post back with 
the above wrapper.log
output with debug enabled.  I may be able to give you some further clues.

Cheers,
Leif


Scott W. Ruch wrote:

>Wrapper version: win32 3.0.5
>
>I'm running Tomcat 4.1.29 as an NT service on Win 2K 
>and Win XP with the following logging configuration.  
>On XP, the Tomcat console log is directed to wrapper.log
>as expected, but on Win 2K it is not.  On 2K, all I get 
>is the initial STATUS & INFO logging from Wrapper.  
>
>Any ideas what would be causing this?
>
>Thanks,
>
>Scott
>  
>

Re: [Wrapper-user] Wrapper and Time

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

Grant,
    Thanks for pointing this out.  The Wrapper has always worked great 
in an environment
where the system time is reliable but I agree that the changes you 
suggest would be a
good idea.  The changes are easy on the Java side, let me look into ways 
of making things
work in the native code.  I'll see if I can get this into the next 
release.  I'll post back if I
run into any problems.

Cheers,
Leif

Grant (ProtectionNET) wrote:

>Leif,
>
>Another thing, when DST comes into effect, some regions change +- by 2 hours
>so this is going to cause a problem relying on time in the wrapper code.
>
>I poked around in the wrapper.c and WrapperManager.java source and I
>absolutely think you could modify the code to include a no-time dependant
>counter.
>
>This would require you to create your own timer thread that polls every
>second and increments an unsigned long.
>
>I use this code in some of my Java apps to get a counter that continues
>forward independant of the actual system time.
>
>private long secondTimer = 0;
>
>Thread t = new Thread()
>{
> public void run()
> {
>  while (true)
>  {
>   try
>   {
>    secondTimer++;
>    if (secondTimer == Long.MAX_VALUE-1) secondTimer = 0;
>    sleep(1000);
>   }
>   catch (Exception e)
>   {
>   }
>  }
> }
>
>};
>t.start();
>
>I'm sure it wouldn't take long to develop the same code for the wrapper.c on
>Win32 and Unix ? The lack of standard threads in unix could be an issue? but
>using time the way you have will definitely cause an issue every DST
>adjustment or when the user changes the system time. They'll need to restart
>wrapper to fix this.
>
>I would continue to use a date based timer for understanding CPU load but
>ignore anything that jumps by more than 10 seconds as time adjustment above
>this is likely a time change. 10 seconds with no CPU time is a LONG time. If
>everything else moves to a CPU timer (on unix you could just count every 1/4
>second or adjust that sleep to 1 second and continue counting).
>
>When using NTP, the systems tend to drift time upwards and downwards
>gracefully so that apps don't notice the change - most hwclocks will only
>loose 1 second a day at worst so this would not really be worth worrying
>about.
>
>Grant
>
>----- Original Message ----- 
>From: "Leif Mortenson" <le...@ta...>
>To: <wra...@li...>
>Sent: Friday, December 26, 2003 10:33 AM
>Subject: Re: [Wrapper-user] Wrapper and Time
>
>
>  
>
>>Grant,
>>    :-/  That doesn't surprise me in the least that you are having
>>problems there.  The
>>Wrapper makes extensive use of time both in its native and Java
>>components to keep
>>track of various timeouts.   The Wrapper currently relies on the system
>>time being
>>fairly reliable.
>>
>>    I could probably add some code to reset the various timeouts in the
>>event that either
>>component of the Wrapper detects that the system time appears to have
>>been changed.
>>Ie when the time decreases or is increased by a large amount.
>>
>>    Small forward adjustments of the system time would be very difficult
>>to detect
>>because the Wrapper contains features to detect when the system has been
>>heavily
>>loaded.  I am not sure that it would be possible to differentiate
>>between the cases where
>>the process is not given any CPU for a minute vs the clock being
>>instantly set ahead
>>by a minute.
>>
>>    Could you describe how you are adjusting the time?  Ie by how much,
>>in which
>>direction and why?  It will help me to prioritize this.   If you know
>>that the Wrapper
>>simply does not like having the clock changed, would it be unreasonable
>>to just not
>>do this? Or is changing the clock a common operation?
>>
>>    I know I can make the Wrapper behave better than it is now, but am
>>unsure of how
>>perfect I can make it perform under all situations.
>>
>>Cheers,
>>Leif
>>
>>Grant (ProtectionNET) wrote:
>>
>>    
>>
>>>Hi,
>>>
>>>I have a case where the Java app changes the system time (via OS calls
>>>etc) and when Wrapper is running, I have sometimes seen strange
>>>problems and the wrapper service shuts down or goes crazy when the
>>>time is changed around.
>>>
>>>I'm only starting to investigate this now, so I don't have all the
>>>facts yet.
>>>
>>>Can someone explain to me what reliance Wrapper has to time and how it
>>>uses it... that would help me track this problem down...
>>>
>>>Thanks a billion.... and merry-xmas and all that ;-)
>>>
>>>Regards,
>>>
>>>Grant
>>>      
>>>
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: IBM Linux Tutorials.
>>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>>_______________________________________________
>>Wrapper-user mailing list
>>Wra...@li...
>>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>>    
>>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: IBM Linux Tutorials.
>Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
>Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
>Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>

[Wrapper-user] Tomcat console logging: Win XP vs. Win 2K

[Scott W. R. <sr...@in...>]

Wrapper version: win32 3.0.5

I'm running Tomcat 4.1.29 as an NT service on Win 2K=20
and Win XP with the following logging configuration. =20
On XP, the Tomcat console log is directed to wrapper.log
as expected, but on Win 2K it is not.  On 2K, all I get=20
is the initial STATUS & INFO logging from Wrapper. =20

Any ideas what would be causing this?

Thanks,

Scott

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

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

# Log file to use for wrapper output logging.
wrapper.logfile=3D%PORTAL_HOME%/var/wrapper.log

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

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