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

[Wrapper-user] why wrapper Unable to get the path for ...

[赵才文 <zh...@li...>]

 
I download a brand-new aix wrapper community version,and chmod +x ./wrapper ,and then execute the wrapper like this:

dnserv1:/4A/wrapper-aix-ppc-64-3.4.0/bin>./wrapper
FATAL  | wrapper  | Unable to get the path for './wrapper'-Permission denied

but if I changed to use "root" user, wrapper works ok, when I change back to a normal user, the fatal error occured. why ?
any help is appreciated!

2010-03-22 



cowrie

Re: [Wrapper-user] Exit codes/LSB compliance of Linux wrapper startscript

[<chr...@ic...>]

Thanks for the quick response.

Yes, I indeed modified the start script regarding exit codes at a couple 
of points (particularly in the checkUser() function that spawns a child 
process for another user but forgets to pass back the exit code to the 
original caller. I just hesitate to reapply these pacthes with every JSW 
upgrade!
I can send you a diff early next week, so you can see whether these 
changes make sense for you.

cheers
Christian

Leif Mortenson <lei...@ta...> wrote on 12.03.2010 
18:03:05:

> [image removed] 
> 
> Re: [Wrapper-user] Exit codes/LSB compliance of Linux wrapper start 
script
> 
> Leif Mortenson 
> 
> to:
> 
> wrapper-user
> 
> 12.03.2010 18:35
> 
> Please respond to wrapper-user
> 
> Christian,
> I admit that I had not seen this standard base in the past.  We are
> about to release 3.4.0, but will look into how closely we can follow
> these standards in the near future.
> 
> In the mean time, the status exit code can be changed in the
> "status()" function of the shell script.
> 
> All of the error recovery features of the Wrapper are contained within
> the wrapper process itself so changes to the shell script will not
> affect how that works.
> 
> Thank you for pointing this out.
> 
> Cheers,
> Leif
> 
> On Sat, Mar 13, 2010 at 12:47 AM,  <chr...@ic...> wrote:
> >
> > Hi,
> >
> > while connecting the Linux wrapper start scripts to OCF resource 
agents for
> > (optional) HA deployment of our application, I noticed that the exit 
codes
> > to neither comply with LSB (Linux standard base) nor OCF specs. I'm
> > referring to JSW 3.3.9.
> > See
> > http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-
> Core-generic/iniscrptact.html for
> > LSB.
> >
> > - running the script as another user (in check_user() function) drops 
the
> > exit code and always returns 0.
> > The exit code should be passed back to the caller.
> >
> > - status should exit with 3 if process not running (currently 1)
> > - status should exit with 1 if process seems to be crashed (currently 
1)
> >
> > In addition to straightforward success, the following situations are 
also to
> > be considered successful:
> > - running start on a service already running
> > - running stop on a service already stopped or not running
> > - running restart on a service already stopped or not running
> >
> > I wonder how a change of exit codes would affect the 
monitoring/restarting
> > capabilities of JSW?
> >
> > regards
> > Christian
> 
> 
------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user



InterComponentWare AG:  
Vorstand: Peter Kirschbauer (Vors.), Jörg Stadler / Aufsichtsratsvors.: Prof. Dr. Christof Hettich  
Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516  

Re: [Wrapper-user] Exit codes/LSB compliance of Linux wrapper start script

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

Christian,
I admit that I had not seen this standard base in the past.  We are
about to release 3.4.0, but will look into how closely we can follow
these standards in the near future.

In the mean time, the status exit code can be changed in the
"status()" function of the shell script.

All of the error recovery features of the Wrapper are contained within
the wrapper process itself so changes to the shell script will not
affect how that works.

Thank you for pointing this out.

Cheers,
Leif

On Sat, Mar 13, 2010 at 12:47 AM,  <chr...@ic...> wrote:
>
> Hi,
>
> while connecting the Linux wrapper start scripts to OCF resource agents for
> (optional) HA deployment of our application, I noticed that the exit codes
> to neither comply with LSB (Linux standard base) nor OCF specs. I'm
> referring to JSW 3.3.9.
> See
> http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html for
> LSB.
>
> - running the script as another user (in check_user() function) drops the
> exit code and always returns 0.
> The exit code should be passed back to the caller.
>
> - status should exit with 3 if process not running (currently 1)
> - status should exit with 1 if process seems to be crashed (currently 1)
>
> In addition to straightforward success, the following situations are also to
> be considered successful:
> - running start on a service already running
> - running stop on a service already stopped or not running
> - running restart on a service already stopped or not running
>
> I wonder how a change of exit codes would affect the monitoring/restarting
> capabilities of JSW?
>
> regards
> Christian

[Wrapper-user] Exit codes/LSB compliance of Linux wrapper start script

[<chr...@ic...>]

Hi, 

while connecting the Linux wrapper start scripts to OCF resource agents 
for (optional) HA deployment of our application, I noticed that the exit 
codes to neither comply with LSB (Linux standard base) nor OCF specs. I'm 
referring to JSW 3.3.9. 
See 
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
 for LSB. 

- running the script as another user (in check_user() function) drops the 
exit code and always returns 0. 
The exit code should be passed back to the caller. 

- status should exit with 3 if process not running (currently 1) 
- status should exit with 1 if process seems to be crashed (currently 1) 

In addition to straightforward success, the following situations are also 
to be considered successful: 
- running start on a service already running 
- running stop on a service already stopped or not running 
- running restart on a service already stopped or not running 

I wonder how a change of exit codes would affect the monitoring/restarting 
capabilities of JSW? 

regards 
Christian 






InterComponentWare AG:  
Vorstand: Peter Kirschbauer (Vors.), Jörg Stadler / Aufsichtsratsvors.: Prof. Dr. Christof Hettich  
Firmensitz: 69190 Walldorf, Industriestraße 41 / AG Mannheim HRB 351761 / USt.-IdNr.: DE 198388516  

Re: [Wrapper-user] Restart JVM for updating the application

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

Beck,
This was a featured that we implemented in the Professional edition
for exactly this kind of situation.
http://wrapper.tanukisoftware.org/doc/english/props-event.html#command

Cheers,
Leif

On Tue, Mar 2, 2010 at 9:29 PM, Beck Ingmar <ing...@ec...> wrote:
> Hello,
>
> I want to update my Java application ... from the application.
>
> I thought I was doing the update and then I restart the JVM via wrapper.
> The problem is that the replacement of the jar files will only work if the
> application is not started.
> Is there any way prior to the restart of the JVM to run a batch file (an
> operating system command).
>
> Although I am already met on the event control of the wrappers, but 1 we
> have only the Standard Edition and 2nd I just need something like a
> prelaunch ... each JVM startup, and no comprehensive event management.
>
> Does anyone make a different approach this?
>
> regards

[Wrapper-user] Restart JVM for updating the application

[Beck I. <ing...@ec...>]

Hello,
 
I want to update my Java application ... from the application.
 
I thought I was doing the update and then I restart the JVM via wrapper.
The problem is that the replacement of the jar files will only work if
the application is not started.
Is there any way prior to the restart of the JVM to run a batch file (an
operating system command).
 
Although I am already met on the event control of the wrappers, but 1 we
have only the Standard Edition and 2nd I just need something like a
prelaunch ... each JVM startup, and no comprehensive event management.

Does anyone make a different approach this?
 
regards

Re: [Wrapper-user] Help with Event Logging

[Ryan C. <ry...@gm...>]

Thanks for all of the great info, Leif.  This really helps me understand why
I was unable to use the logging property.  As I am wrapping a project that
already has log4j as a dependency I think ill keep it that way for now I
instead of introducing an additional dependency on the wrapper API.  Ill
keep this in mind for future development, however.  Thanks again!

-Ryan

On Feb 22, 2010 6:38 PM, "Leif Mortenson" <lei...@ta...>
wrote:

Ryan,
The Wrapper's Event Log / syslog target is used to output the
Wrapper's log output to the event log in addition to the wrapper.log
and console.   By default it is disabled.  We do not recommend setting
the Event Log's loglevel to DEBUG or INFO as it will very quickly fill
up the event log.  It is mainly useful for logging warnings and error
messages.

Normally, all output to the JVMs console will be logged by the Wrapper
at the INFO log level.

You can log to a higher level like ERROR or FATAL, but using the following
API:
import org.tanukisoftware.wrapper.WrapperManager;
WrapperManager.log(WrapperManager.WRAPPER_LOG_LEVEL_ERROR, "This is a
test Error");
See the Javadocs here:
http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware/wrapper/WrapperManager.html

This output will then show up everywhere that the ERROR log output is
enabled.  On UNIX platforms it could go to the syslog.
http://wrapper.tanukisoftware.org/doc/english/prop-syslog-loglevel.html
http://wrapper.tanukisoftware.org/doc/english/prop-logfile-loglevel.html
http://wrapper.tanukisoftware.org/doc/english/prop-console-loglevel.html
http://wrapper.tanukisoftware.org/doc/english/props-logging.html

What is an example of what you are trying to do?  I may have some
suggestions.

Cheers,
Leif


On Mon, Feb 22, 2010 at 10:38 PM, Ryan Connolly <ry...@gm...> wrote:
> Leif:
>      Thank you ...

Re: [Wrapper-user] Problem with Windows 2008 Server...

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

Dante,
The message you are seeing is because you are running "wrapper.exe -s
..¥conf¥wrapper.conf"
The "-s" command stands for "--service", which is used exclusively by
the Windows Service Manager to run the Wrapper as a service.  It is a
bit confusing, but continues to work this way for historical reasons.
We have added a much better error message for the 3.4.0 release which
should help to avoid such confusion.

Please run "wrapper.exe -?" to see a list of available commands.

To starT the service once it is installed, you can use the "-t" or
"--start" commands.

Please let me know if you have any more questions getting up and running.

Cheers,
Leif

On Fri, Feb 26, 2010 at 3:12 AM, Dante Cesar Basso Filho
<dc...@gm...> wrote:
> Hello There!
> I having some problema to get Wraper Working in Windows 2008 Server... When
> i tru to start the service i got this message:
>
> "Calling StartServiceCtrlDispatcher... please wait"
> StartServiceCtrlDispatcher failed!
> For help type
> wraper.exe /?
>
> I can fix that?!
> Thanks all!

Re: [Wrapper-user] Wrapper X Windows 2008 Server...

[Christian M. <chr...@ta...>]

Hello,

the problem is basically that with windows vista, microsoft reduced
for security issues the opportunities services can interact with the
desktop. they are running since then in an dedicated desktop.

please have a look at point 'Session 0 Isolation'

http://msdn.microsoft.com/en-us/library/bb203962%28VS.85%29.aspx

Your GUI application is actually running in this Desktop.

We will work on a workaround for this in an upcoming release.

best regards,
christian

On Fri, Feb 26, 2010 at 5:14 AM, hand01 <dc...@gm...> wrote:
>
> Hello there!
> People, i have test with WIN. XP/2003 server and the Wrapper works VERY
> fine, but in 2008 Server I could not start normally the Java program!
>
> Its seems to starting, but dont shows the GUI! I dont know what should i do!
> Anyone please!
>
> Thanks, and sorry my English!
> --
> View this message in context: http://old.nabble.com/Wrapper-X-Windows-2008-Server...-tp27714515p27714515.html
> Sent from the Java Service Wrapper mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>

[Wrapper-user] Wrapper X Windows 2008 Server...

[hand01 <dc...@gm...>]

Hello there!
People, i have test with WIN. XP/2003 server and the Wrapper works VERY
fine, but in 2008 Server I could not start normally the Java program!

Its seems to starting, but dont shows the GUI! I dont know what should i do! 
Anyone please!

Thanks, and sorry my English!
-- 
View this message in context: http://old.nabble.com/Wrapper-X-Windows-2008-Server...-tp27714515p27714515.html
Sent from the Java Service Wrapper mailing list archive at Nabble.com.

[Wrapper-user] Problem with Windows 2008 Server...

[Dante C. B. F. <dc...@gm...>]

Hello There!
I having some problema to get Wraper Working in Windows 2008 Server... When
i tru to start the service i got this message:

*"Calling StartServiceCtrlDispatcher... please wait"
StartServiceCtrlDispatcher failed!
For help type
wraper.exe /?*

I can fix that?!

Thanks all!

-- 
Dante Cesar Basso Filho
MSN: dc...@gm...

"As pessoas são do tamanho dos sonhos que almejam..."

Re: [Wrapper-user] Stopping Service before Standby?

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

Daniel,
Sorry for the delay.   This currently requires that some code be
written in the Java Application.   The good news though is that you
can easily create a simple "wrapper" class between the
WrapperSimpleApp class, and the main class of your executable jar.

You will need to look in the Manifest file of your executable jar to
get its main class as you will not be able to use it as an executable
jar.   Set up the Wrapper using Method #1 (WrapperSimpleApp) and
specify the helper class below as its first parameter.   Then hard
code the fully qualified main class of your jar file in the end of the
helper class's main method.

By doing this, the WrapperSimpleApp will start up this helper class,
it will do what it needs to do to restart when the system is resumed.
 Then it calls your main class to start up your application as usual.

This helper class will cause the Wrapper to restart the JVM when the
system is resumed rather than when it suspends.  ( If you restart it
just before suspending then you may not get the results you want
depending how far along the restart gets before the system actually
suspends.   You may be able to make this work if you specify a long
restart delay (wrapper.restart.delay=30) to make sure the JVM does not
get relaunched before the system is fully suspended.  It should then
start back up when the system is resumed. )

Please give this a try and let me know how it works for you.

I have added a feature to our TODO list to make the Wrapper stop the
JVM before the system is suspended, and then start it back up after it
resumes.  This will be done in the Wrapper itself to let you avoid
having to write code.  It won't make it into the next release however.

Cheers,
Leif

---
/*
 * javac -classpath ..\lib\wrapper.jar;..\lib\wrappertest.jar *.java
 */

import org.tanukisoftware.wrapper.WrapperManager;
import org.tanukisoftware.wrapper.event.WrapperEvent;
import org.tanukisoftware.wrapper.event.WrapperEventListener;
import org.tanukisoftware.wrapper.event.WrapperServiceControlEvent;
import org.tanukisoftware.wrapper.test.Main;


public class HibernateRestartTest
    implements WrapperEventListener
{
    private static HibernateRestartTest m_app;

    /*---------------------------------------------------------------
     * Constructors
     *-------------------------------------------------------------*/
    HibernateRestartTest()
    {
    }

    /*---------------------------------------------------------------
     * WrapperEventListener Methods
     *-------------------------------------------------------------*/
    public void fired( WrapperEvent event )
    {
        System.out.println( "Received event: " + event );
        if ( event instanceof WrapperServiceControlEvent )
        {
			WrapperServiceControlEvent scEvent = (WrapperServiceControlEvent)event;
			
			switch ( scEvent.getServiceControlCode() )
			{
			case WrapperManager.SERVICE_CONTROL_CODE_POWEREVENT_SUSPEND:
				System.out.println( "  The system is about to be suspended.  Let
this happen here." );
				break;
				
			case WrapperManager.SERVICE_CONTROL_CODE_POWEREVENT_POWERSTATUSCHANGE:
				System.out.println( "  There was a power status change." );
				break;
				
			case WrapperManager.SERVICE_CONTROL_CODE_POWEREVENT_RESUMESUSPEND:
			case WrapperManager.SERVICE_CONTROL_CODE_POWEREVENT_RESUMEAUTOMATIC:
				System.out.println( "  There system was resumed.  Trigger a
restart to let the JVM reinitialize." );
				WrapperManager.restartAndReturn();
				break;
				
			default:
				System.out.println( "  Got an unhandled power event: " +
scEvent.getServiceControlCode() );
				break;
			}
        }
    }

    /*---------------------------------------------------------------
     * Main Method
     *-------------------------------------------------------------*/
    public static void main( String[] args )
    {
        System.out.println( "Start" );
        m_app = new HibernateRestartTest();

        WrapperManager.addWrapperEventListener( m_app,
WrapperEventListener.EVENT_FLAG_SERVICE );

		// Replace the following with your main class.
        org.tanukisoftware.wrapper.test.BackgroundThreads.main( args );
    }
}
---




On Sat, Feb 20, 2010 at 11:30 PM, Daniel Weinand <ma...@gm...> wrote:
> So, the problem finaly needs to be fixed. Haven't worked a while with
> the wrapper and the service it controls.
> In the previous mail you told me to use a WrapperServiceControlEvent.
> For my service i'm using method 4 because
> the app/service can run as configurable jar. But now i have no idea how
> to integrate or act on wrapper events.
>
> Basically i need the wrapper to stop the service if a standby/hibernate
> request is coming in. when the system is
> resuming normal operation the wrapper should restart the service. This
> should solve my com port issues.
>
> Can this be configured in my wrapper.conf or how can i listen to the
> events, because my app doesn't and
> should not know anything about the wrapper. Any advice is appreciated.
>
> regards
>
> Daniel
>
> Leif Mortenson schrieb:
>> Daniel,
>> Sorry for the delay.  The Wrapper actually supports Windows POWER
>> events and will fire events in the JVM to give your application a
>> chance to respond to them.  Please see the WrapperServiceControlEvent
>> class in javadocs for details on the events that can be processed.
>>
>> http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware/wrapper/event/WrapperServiceControlEvent.html
>>
>> The various events can be handled by passing a WrapperEventListener
>> instance to the WrapperManager.addWrapperEventListener(...) method.
>> Please take a look at the Javacocs for details and let me know how it
>> works for you or if you have any questions getting things working.
>>
>> Cheers,
>> Leif
>>
>>
>> On Sat, Dec 5, 2009 at 12:15 AM, Daniel Weinand <ma...@gm...> wrote:
>>
>>> Hello,
>>>
>>> is it possible to stop a Windows service before the computer enters standby?
>>> my application is polling hardware via an virtual com port. every time the computer
>>> wakes up the service is up and running again. but the com port is blocked by another
>>> app instance.
>>>
>>> i know this is not entirely related to the wrapper. but for now i have no idea
>>> how to solve my problem. any hints?
>>>
>>> regards

Re: [Wrapper-user] Help with Event Logging

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

Ryan,
The Wrapper's Event Log / syslog target is used to output the
Wrapper's log output to the event log in addition to the wrapper.log
and console.   By default it is disabled.  We do not recommend setting
the Event Log's loglevel to DEBUG or INFO as it will very quickly fill
up the event log.  It is mainly useful for logging warnings and error
messages.

Normally, all output to the JVMs console will be logged by the Wrapper
at the INFO log level.

You can log to a higher level like ERROR or FATAL, but using the following API:
import org.tanukisoftware.wrapper.WrapperManager;
WrapperManager.log(WrapperManager.WRAPPER_LOG_LEVEL_ERROR, "This is a
test Error");
See the Javadocs here:
http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware/wrapper/WrapperManager.html

This output will then show up everywhere that the ERROR log output is
enabled.  On UNIX platforms it could go to the syslog.
http://wrapper.tanukisoftware.org/doc/english/prop-syslog-loglevel.html
http://wrapper.tanukisoftware.org/doc/english/prop-logfile-loglevel.html
http://wrapper.tanukisoftware.org/doc/english/prop-console-loglevel.html
http://wrapper.tanukisoftware.org/doc/english/props-logging.html

What is an example of what you are trying to do?  I may have some suggestions.

Cheers,
Leif

On Mon, Feb 22, 2010 at 10:38 PM, Ryan Connolly <ry...@gm...> wrote:
> Leif:
>      Thank you so much for the very detailed reply.  I finally got the
> logging working and as usual it was a silly mistake on my part:  I had
> neglected to call the NTEventLogAppender.setThreshold(Priority p) method.
> Once I included that call, everything is working as expected.
>
> However, it would seem that using the built-in system logging would be much
> cleaner (and platform independent) so I would be interested in getting that
> working instead.  Simply changing the wrapper.syslog.loglevel property value
> from "none" to "info" or "debug" did not seem to work out.  Is there
> anything else I would need to do besides setting increasing the log level
> there?
>
> Thanks again for the help!  I was beginning to lose hope :)
> -Ryan
> On Mon, Feb 22, 2010 at 4:38 AM, Leif Mortenson <le...@ta...>
> wrote:
>>
>> Ryan,
>> The Java Service Wrapper has its own method of logging to the Windows
>> Event Logs.  It sounds like you have located the configuration for
>> that.
>>
>> Log4J is an independent implementation that does not make use of the
>> Wrapper's features.
>>
>> Looking at the following javadoc page, it says that it requires that
>> you place a NTEventLogAppender.dll native library on the PATH.
>>
>> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/nt/NTEventLogAppender.html
>> When Java specifies a specific Library Path, as is done with the
>> Wrapper, Java does NOT search the PATH by default.
>> Please go in and either add the location of the NTEventLogAppender.dll
>> file to the library path with the following property:
>>
>> http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-n.html
>> Or tell the Wrapper to append the PATH again:
>>
>> http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-append-system-path.html
>> I would suggest the first option.
>>
>> Another possibility is that your log4j properties file is not being
>> found correctly when the JVM is launched.
>> Please try setting the following property and rerunning your
>> application to make sure that the Wrapper is generating the Java
>> command line that you expect:
>> wrapper.java.command.loglevel=INFO
>>
>> Please let me know how this works for you, or if you have more questions.
>>
>> Cheers,
>> Leif
>>
>>
>> On Sun, Feb 21, 2010 at 12:35 PM, Ryan Connolly <ry...@gm...> wrote:
>> > Hello wrapper users!
>> > I am new to the list so please take it easy on me.  I'm sorry if this
>> > has
>> > been asked previously but I've had no luck finding any answers to my
>> > question.  I'm hoping y'all can help me out.
>> > I have a requirement to perform some logging to the Windows Event Logs
>> > and
>> > I'm just not getting it... I've been using the log4j NTEventLogAppender
>> > successfully in my unit tests however no logging occurs while running
>> > from WrapperSimpleApp.  I've noticed in the logging docs a
>> > "wrapper.syslog.loglevel" property so I went ahead and changed its value
>> > from NONE to INFO, still no dice.  Does anyone have any additional
>> > information or experience with this?  I'd really like to get this sorted
>> > out!
>> > Thanks to any in advance!
>> > -Ryan

Re: [Wrapper-user] Help with Event Logging

[Ryan C. <ry...@gm...>]

Leif:
     Thank you so much for the very detailed reply.  I finally got the
logging working and as usual it was a silly mistake on my part:  I had
neglected to call the NTEventLogAppender.setThreshold(Priority p) method.
Once I included that call, everything is working as expected.

However, it would seem that using the built-in system logging would be much
cleaner (and platform independent) so I would be interested in getting that
working instead.  Simply changing the wrapper.syslog.loglevel property value
from "none" to "info" or "debug" did not seem to work out.  Is there
anything else I would need to do besides setting increasing the log level
there?

Thanks again for the help!  I was beginning to lose hope :)
-Ryan
On Mon, Feb 22, 2010 at 4:38 AM, Leif Mortenson <le...@ta...>wrote:

> Ryan,
> The Java Service Wrapper has its own method of logging to the Windows
> Event Logs.  It sounds like you have located the configuration for
> that.
>
> Log4J is an independent implementation that does not make use of the
> Wrapper's features.
>
> Looking at the following javadoc page, it says that it requires that
> you place a NTEventLogAppender.dll native library on the PATH.
>
> http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/nt/NTEventLogAppender.html
> When Java specifies a specific Library Path, as is done with the
> Wrapper, Java does NOT search the PATH by default.
> Please go in and either add the location of the NTEventLogAppender.dll
> file to the library path with the following property:
> http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-n.html
> Or tell the Wrapper to append the PATH again:
>
> http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-append-system-path.html
> I would suggest the first option.
>
> Another possibility is that your log4j properties file is not being
> found correctly when the JVM is launched.
> Please try setting the following property and rerunning your
> application to make sure that the Wrapper is generating the Java
> command line that you expect:
> wrapper.java.command.loglevel=INFO
>
> Please let me know how this works for you, or if you have more questions.
>
> Cheers,
> Leif
>
>
> On Sun, Feb 21, 2010 at 12:35 PM, Ryan Connolly <ry...@gm...> wrote:
> > Hello wrapper users!
> > I am new to the list so please take it easy on me.  I'm sorry if this has
> > been asked previously but I've had no luck finding any answers to my
> > question.  I'm hoping y'all can help me out.
> > I have a requirement to perform some logging to the Windows Event Logs
> and
> > I'm just not getting it... I've been using the log4j NTEventLogAppender
> > successfully in my unit tests however no logging occurs while running
> > from WrapperSimpleApp.  I've noticed in the logging docs a
> > "wrapper.syslog.loglevel" property so I went ahead and changed its value
> > from NONE to INFO, still no dice.  Does anyone have any additional
> > information or experience with this?  I'd really like to get this sorted
> > out!
> > Thanks to any in advance!
> > -Ryan
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>



-- 
®¥@N

Re: [Wrapper-user] Help with Event Logging

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

Ryan,
The Java Service Wrapper has its own method of logging to the Windows
Event Logs.  It sounds like you have located the configuration for
that.

Log4J is an independent implementation that does not make use of the
Wrapper's features.

Looking at the following javadoc page, it says that it requires that
you place a NTEventLogAppender.dll native library on the PATH.
http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/nt/NTEventLogAppender.html
When Java specifies a specific Library Path, as is done with the
Wrapper, Java does NOT search the PATH by default.
Please go in and either add the location of the NTEventLogAppender.dll
file to the library path with the following property:
http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-n.html
Or tell the Wrapper to append the PATH again:
http://wrapper.tanukisoftware.org/doc/english/prop-java-library-path-append-system-path.html
I would suggest the first option.

Another possibility is that your log4j properties file is not being
found correctly when the JVM is launched.
Please try setting the following property and rerunning your
application to make sure that the Wrapper is generating the Java
command line that you expect:
wrapper.java.command.loglevel=INFO

Please let me know how this works for you, or if you have more questions.

Cheers,
Leif


On Sun, Feb 21, 2010 at 12:35 PM, Ryan Connolly <ry...@gm...> wrote:
> Hello wrapper users!
> I am new to the list so please take it easy on me.  I'm sorry if this has
> been asked previously but I've had no luck finding any answers to my
> question.  I'm hoping y'all can help me out.
> I have a requirement to perform some logging to the Windows Event Logs and
> I'm just not getting it... I've been using the log4j NTEventLogAppender
> successfully in my unit tests however no logging occurs while running
> from WrapperSimpleApp.  I've noticed in the logging docs a
> "wrapper.syslog.loglevel" property so I went ahead and changed its value
> from NONE to INFO, still no dice.  Does anyone have any additional
> information or experience with this?  I'd really like to get this sorted
> out!
> Thanks to any in advance!
> -Ryan

[Wrapper-user] Help with Event Logging

[Ryan C. <ry...@gm...>]

Hello wrapper users!

I am new to the list so please take it easy on me.  I'm sorry if this has
been asked previously but I've had no luck finding any answers to my
question.  I'm hoping y'all can help me out.

I have a requirement to perform some logging to the Windows Event Logs and
I'm just not getting it... I've been using the log4j NTEventLogAppender
successfully in my unit tests however no logging occurs while running
from WrapperSimpleApp.  I've noticed in the logging docs a
"wrapper.syslog.loglevel" property so I went ahead and changed its value
from NONE to INFO, still no dice.  Does anyone have any additional
information or experience with this?  I'd really like to get this sorted
out!

Thanks to any in advance!

-Ryan

Re: [Wrapper-user] wrapper refuses to start - using wrong JRE

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

Javier,
The error message you are getting is coming from the Java process, not
the Wrapper itself.  It looks like Java is somehow getting confused.

Could you please try running the following from a command prompt and
see what you get?
X:\jdk1.6.0_18\bin\javaw.exe -version

If that does not cause an error, my next questions will be:
1) Are you running as a service or in a console?

2) If as a service, what happens if you run in a console.  (Could be a
different environment)

Also, when using the Wrapper, you should use the java.exe binary
rather than javaw.exe.   The Wrapper process makes use of Java's
console.
wrapper.java.command=X:\jdk1.6.0_18\bin\java.exe

Cheers,
Leif



On Sun, Feb 21, 2010 at 12:12 AM, Javier Godoy <ma...@rj...> wrote:
> After I installed Java 7 on my system, the wrapper refuses to start, but
> configuration file specifies a 1.6 JVM not 1.7
>
> wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.9
> wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights
> Reserved.
> wrapper  |     http://wrapper.tanukisoftware.org
> wrapper  |
> wrapper  | Launching a JVM...
> jvm 1    | Registry key 'Software\JavaSoft\Java Runtime
> Environment\CurrentVersion'
> jvm 1    | has value '1.7', but '1.6' is required.
> jvm 1    | Error: could not find java.dll
>
> Currently my only setting affecting the JVM is
>  wrapper.java.command=X:\jdk1.6.0_18\bin\javaw.exe
>
> It seems as if the wrapper is looking for the JRE at the registry, can I
> configure it to use a specified JRE?
>
>
> Regards
>
> Javier

[Wrapper-user] wrapper refuses to start - using wrong JRE

[Javier G. <ma...@rj...>]

After I installed Java 7 on my system, the wrapper refuses to start, but 
configuration file specifies a 1.6 JVM not 1.7

wrapper  | Java Service Wrapper Community Edition 32-bit 3.3.9
wrapper  |   Copyright (C) 1999-2009 Tanuki Software, Ltd.  All Rights 
Reserved.
wrapper  |     http://wrapper.tanukisoftware.org
wrapper  |
wrapper  | Launching a JVM...
jvm 1    | Registry key 'Software\JavaSoft\Java Runtime 
Environment\CurrentVersion'
jvm 1    | has value '1.7', but '1.6' is required.
jvm 1    | Error: could not find java.dll

Currently my only setting affecting the JVM is
  wrapper.java.command=X:\jdk1.6.0_18\bin\javaw.exe

It seems as if the wrapper is looking for the JRE at the registry, can I 
configure it to use a specified JRE?


Regards

Javier

Re: [Wrapper-user] Stopping Service before Standby?

[Daniel W. <ma...@gm...>]

So, the problem finaly needs to be fixed. Haven't worked a while with
the wrapper and the service it controls.
In the previous mail you told me to use a WrapperServiceControlEvent.
For my service i'm using method 4 because
the app/service can run as configurable jar. But now i have no idea how
to integrate or act on wrapper events.

Basically i need the wrapper to stop the service if a standby/hibernate
request is coming in. when the system is
resuming normal operation the wrapper should restart the service. This
should solve my com port issues.

Can this be configured in my wrapper.conf or how can i listen to the
events, because my app doesn't and
should not know anything about the wrapper. Any advice is appreciated.

regards

Daniel

Leif Mortenson schrieb:
> Daniel,
> Sorry for the delay.  The Wrapper actually supports Windows POWER
> events and will fire events in the JVM to give your application a
> chance to respond to them.  Please see the WrapperServiceControlEvent
> class in javadocs for details on the events that can be processed.
>
> http://wrapper.tanukisoftware.org/doc/english/javadocs.html?org/tanukisoftware/wrapper/event/WrapperServiceControlEvent.html
>
> The various events can be handled by passing a WrapperEventListener
> instance to the WrapperManager.addWrapperEventListener(...) method.
> Please take a look at the Javacocs for details and let me know how it
> works for you or if you have any questions getting things working.
>
> Cheers,
> Leif
>
>
> On Sat, Dec 5, 2009 at 12:15 AM, Daniel Weinand <ma...@gm...> wrote:
>   
>> Hello,
>>
>> is it possible to stop a Windows service before the computer enters standby?
>> my application is polling hardware via an virtual com port. every time the computer
>> wakes up the service is up and running again. but the com port is blocked by another
>> app instance.
>>
>> i know this is not entirely related to the wrapper. but for now i have no idea
>> how to solve my problem. any hints?
>>
>> regards
>>     
>
>   

Re: [Wrapper-user] confused about waitForStartMain=TRUE

[Jan V. B. <jan...@gm...>]

I've done some more debugging (in the tanuki wrapper code) and looked at 
more logging. As far as I can see, all is good in de Java code, for 
example the logging ends with

jvm 1    | WrapperSimpleApp: main method completed
jvm 1    | WrapperSimpleApp: start(args) end.  Main Completed=true, 
exitCode=null
jvm 1    | WrapperListener.start runner thread stopped.
jvm 1    | returned from WrapperListener.start()


But still, the native script either returns immediately 
(wrapper.daemonize=TRUE) or not at all.

What am I doing wrong or misunderstanding here?

Thanks in advance,
Jan Van Besien

Re: [Wrapper-user] confused about waitForStartMain=TRUE

[Jan V. B. <jan...@gm...>]

Forgot to say, but ofcourse I have this in my wrapper.conf file:

wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE

I've also tried with

wrapper.java.additional.1=-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=100

but it makes no difference.

Kind regards
Jan

Jan Van Besien wrote:
> Hi all,
> 
> I am trying to run tomcat-6.0.18 on linux (centos 5.4) with tanuki 
> wrapper 3.2.3.
> 
> This all works very nice, but now I would like the 
> "/etc/init.d/tomcat-tanuki start" command to return only after tomcat is 
> fully started.
> 
> I thought the 
> -Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE 
> option to be what I am looking for, but I don't seem to get it to work 
> as I expect it to be supposed to work.
> 
> What I did:
> 
> I am using the WrapperSimpleApp.
> 
> I start tomcat using "org.apache.catalina.startup.Bootstrap startd".
> 
> When I enable debug logging in the wrapper, I see this:
> 
> INFO: Server startup in 19484 ms
> WrapperSimpleApp: main method completed
> 
> The first line is tomcat saying it has completed starting the server. 
> The second line is the tanuki wrapper saying the main method has 
> returned. So it seems this is OK.
> 
> But unfortunately when I run the tanuki wrapper as the /etc/init.d 
> script does:
> 
> /usr/sbin/tanukiwrapper "/usr/local/tomcat6/conf/wrapper.conf" 
> wrapper.syslog.ident=tomcat6 
> wrapper.pidfile="/usr/local/tomcat6/tomcat6.pid" wrapper.daemonize=TRUE
> 
> This command returns immediately. Without "daemonize" it never returns.
> 
> I would like it to return when it says "main method completed". Is this 
> possible?
> 
> Thanks in advance!
> 
> Kind regards,
> Jan Van Besien
> 
> 

[Wrapper-user] confused about waitForStartMain=TRUE

[Jan V. B. <jan...@gm...>]

Hi all,

I am trying to run tomcat-6.0.18 on linux (centos 5.4) with tanuki 
wrapper 3.2.3.

This all works very nice, but now I would like the 
"/etc/init.d/tomcat-tanuki start" command to return only after tomcat is 
fully started.

I thought the 
-Dorg.tanukisoftware.wrapper.WrapperSimpleApp.waitForStartMain=TRUE 
option to be what I am looking for, but I don't seem to get it to work 
as I expect it to be supposed to work.

What I did:

I am using the WrapperSimpleApp.

I start tomcat using "org.apache.catalina.startup.Bootstrap startd".

When I enable debug logging in the wrapper, I see this:

INFO: Server startup in 19484 ms
WrapperSimpleApp: main method completed

The first line is tomcat saying it has completed starting the server. 
The second line is the tanuki wrapper saying the main method has 
returned. So it seems this is OK.

But unfortunately when I run the tanuki wrapper as the /etc/init.d 
script does:

/usr/sbin/tanukiwrapper "/usr/local/tomcat6/conf/wrapper.conf" 
wrapper.syslog.ident=tomcat6 
wrapper.pidfile="/usr/local/tomcat6/tomcat6.pid" wrapper.daemonize=TRUE

This command returns immediately. Without "daemonize" it never returns.

I would like it to return when it says "main method completed". Is this 
possible?

Thanks in advance!

Kind regards,
Jan Van Besien

Re: [Wrapper-user] Using Same Wrapper on Two Machines

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

Wandrille,
This is a special case for the Wrapper script.   If you modify the
shell script so it does not check if the pid file is stale, this
should be pretty easy to do.  Simply modify it so it assumes that the
Wrapper is up if the pid file exists at all.

Look for the getpid() function in the script and remove everything
after it reads the pid file.  The rest of the script expects pid to
have a value or be "".

Haven't tested it, but this should work:

getpid() {
    pid=""
    if [ -f "$PIDFILE" ]
    then
        if [ -r "$PIDFILE" ]
        then
            pid=`cat "$PIDFILE"`
        else
            echo "Cannot read $PIDFILE."
            exit 1
        fi
    fi
}

Please post back with the results.

Cheers,
Leif

On Thu, Feb 11, 2010 at 1:29 AM,  <wan...@bn...> wrote:
> Hi,
>
> We have two machine load balanced lets say unix1 and unix2
> They both mount the same filesystem.
>
> I want to make sure wrapper can't be started on both machines at the same
> time.
>
> This is how it works now:
> unix1: wrapper.sh start -> pidfile is created
> unix2: wrapper.sh start -> sees the pidfile (since it's the same fs), thinks
> it's a stale pid file (since it's not the same machine), then removes it and
> starts the wrapper
>
> Is there a workaround for this ?
>
> Thanks a lot,

[Wrapper-user] Using Same Wrapper on Two Machines

[<wan...@bn...>]

Hi,

We have two machine load balanced lets say unix1 and unix2
They both mount the same filesystem.

I want to make sure wrapper can't be started on both machines at the same
time.

This is how it works now:
unix1: wrapper.sh start   -> pidfile is created
unix2: wrapper.sh start   -> sees the pidfile (since it's the same fs),
thinks it's a stale pid file (since it's not the same machine), then
removes it and starts the wrapper

Is there a workaround for this ?

Thanks a lot,
--
Wandrille M





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

                ---------------------------------------------

Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.
N'imprimez ce message que si necessaire,
pensez a l'environnement.

Re: [Wrapper-user] wrapper.conf classpath syntax

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

Dave,
Yes this is possible.  The following example includes 3 jars and a
directory on the classpath:
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/myapp.jar
wrapper.java.classpath.3=../lib/mysql.jar
wrapper.java.classpath.4=../classes

You can also do this to add all jars matching the specified pattern:
wrapper.java.classpath.1=../lib/*.jar
wrapper.java.classpath.2=../classes

See the following page:
http://wrapper.tanukisoftware.org/doc/english/prop-java-classpath-n.html

Let me know if you have any other questions.

Cheers,
Leif

On Wed, Feb 10, 2010 at 6:16 AM, Dave Garratt <dav...@ma...> wrote:
> Should it be possible to reference directories rather than individual .jar
> files in the config file.  I know that java 1.6 command lines support this.
>
>
>
> Thanks
>
>
>
> Dave