wrapper-user

AW: [Wrapper-user] Problems stopping the wrapper

[Luis V. <lui...@ip...>]

Dear Leif,

The liveupdate tries indeed to stop the service. We have sometimes the =
case that while stopping the service and the application we get an error =
message from the application so that the service cannot be stopped =
correctly and it's still running (Status: Stop Pending) after the =
LiveUpdate is down.

Under unix i could solve an similar problem by looking if the pid - file =
still exists (otherwise sleep for an few seconds and try again) but =
under windows there is not this possibility. Do you know a possibility =
how i can prevent the service to be started if the service is still in =
status Stop Pending?

Many thanks.

Cheers,

Luis.

-----Urspr=FCngliche Nachricht-----
Von: wra...@li... =
[mailto:wra...@li...] Im Auftrag von Leif =
Mortenson
Gesendet: Dienstag, 29. November 2005 04:30
An: wra...@li...
Betreff: Re: [Wrapper-user] Problems stopping the wrapper

Luis,
    I am not completely clear about what is happening.   It sounds like=20
your live update
application is attempting to stop the Wrapper as a service, update some =
files and then quickly restart it.  Is that correct?

    When you attempt to restart the service, you are then getting an =
error that the service
is still being stopped.   My guess here is that this is not a wrapper a=20
problem but rather
a problem with your live update tool.  It doesn't sound like it is =
correctly waiting for the service to stop before continuing.

    Let me know if I am misunderstanding something.

Cheers,
Leif


Luis Varon wrote:
> Dear Ladies and Gentleman,
>
> We are using the java service wrapper to stop and start our java =
application.=20
>
> In some cases we have problems stopping our application which causes =
the wrapper to fail with an error message however the application is =
stopped also. Normally this is not an big problem if we restart our =
application but it is if we restart the application using our liveupdate =
functionality. In this case the Liveupdate (a process which stops the =
application, updates the system and restart the application) is finished =
to fast and while trying to start the wrapper we receive the error =
message "The ipex scheduler service service is already running with =
status: STOP_PENDING" and the application is not started.
>
> I would like to ask you if you have had this problem and how has it =
been solved and if not maybe you know an parameter which can be set and =
which slows down the start of the application.
>
> Many thanks in advance for your efforts.
>
> Kind regards
>
> Luis Varon Marques
> iPoint-systems gmbh
>
> Fon  : +49.7121.14489.888
> Fax  : +49.7121.14489.89
> eMail: mailto:Lui...@ip...
> Web  : http://www.ipoint-systems.com
> ----------------------------------------------------------------------
> ------
>
> Februar 2004:
>
> Die Software "iPoint Automotive Agent" hat vom Land =
Baden-W=FCrttemberg die Auszeichnung "Innovation des Monats" im Rahmen =
der Mittelstandsinitiative ebigo.de erhalten.
>
> =20
>
> Mai 2003:
>
> iPoint Automotive Agent belegt als beste Software-L=F6sung den 5. =
Platz beim bwcon award CyberOne 2003.
>
> =20
>
> April 2002:
>
> Die eBusiness-Integrationsl=F6sung iPoint Automotive Agent wurde mit =
dem "tool-award 2002" pr=E4miert.
>
> ----------------------------------------------------------------------
> ------
>
> =20
>
> Events:
>
> 14. September 2005
> iPoint Roadshow
> IBM Forum Frankfurt
>
> 21.-22. September 2005
> AKJ Automotive Prozesse und IT 2005
> Saarbr=FCcken
>
> 21.-23. September 2005
> SAP TechED 05
> Wien, =D6sterreich
>
> 5.-6. Oktober 2005
> 3. iPoint Kundentag
> Bad Kreuznach
> Die Kauzenburg mit Landhotel
> www.kauzenburg.de
>
> 8. November 2005
> iPoint Roadshow
> IBM Forum D=FCsseldorf
>
> 17.-18. November 2005
> Odette Conference
> Paris
> www.odetteconference.org
>
> 23.-24. November 2005
> SAP Automotive Symposium Leipzig
> Congress Center Leipzig
>
> 23.-24. November 2005
> SCM World Ludwigsburg
> Forum am Schlosspark
> Stand Nr. 4
> Vortrag: Systemintegration
> www.scmworld.com
> ----------------------------------------------------------------------
> -----
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log =

> files for problems?  Stop!  Download the new AJAX search engine that=20
> makes searching your log files as easy as surfing the  web.  DOWNLOAD =
SPLUNK!
> http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  =20



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files for problems?  Stop!  Download the new AJAX search engine that =
makes searching your log files as easy as surfing the  web.  DOWNLOAD =
SPLUNK!
http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user

Re: AW: [Wrapper-user] Problems stopping the wrapper

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

Luis,
    What is the error that you are seeing while stopping the service?  
The "net stop app"
command will time out if the app takes a while to shutdown.
If you use "wrapper -p wrapper.conf" to stop the service, you will not 
have this problem.

    You mentioned the pid.  You can actually do this under windows, it 
is just not on by
default.   Take a look at the wrapper.pidfile and wrapper.java.pidfile 
properties.  The
later will give you a pid file for the actual JVM.

    Version 3.2.0 will contain several new ways to test the status of a 
service and also
includes several new status files.

Cheers,
Leif

Luis Varon wrote:
> Dear Leif,
>
> The liveupdate tries indeed to stop the service. We have sometimes the case that while stopping the service and the application we get an error message from the application so that the service cannot be stopped correctly and it's still running (Status: Stop Pending) after the LiveUpdate is down.
>
> Under unix i could solve an similar problem by looking if the pid - file still exists (otherwise sleep for an few seconds and try again) but under windows there is not this possibility. Do you know a possibility how i can prevent the service to be started if the service is still in status Stop Pending?
>
> Many thanks.
>
> Cheers,
>
> Luis.
>
> -----Ursprüngliche Nachricht-----
> Von: wra...@li... [mailto:wra...@li...] Im Auftrag von Leif Mortenson
> Gesendet: Dienstag, 29. November 2005 04:30
> An: wra...@li...
> Betreff: Re: [Wrapper-user] Problems stopping the wrapper
>
> Luis,
>     I am not completely clear about what is happening.   It sounds like 
> your live update
> application is attempting to stop the Wrapper as a service, update some files and then quickly restart it.  Is that correct?
>
>     When you attempt to restart the service, you are then getting an error that the service
> is still being stopped.   My guess here is that this is not a wrapper a 
> problem but rather
> a problem with your live update tool.  It doesn't sound like it is correctly waiting for the service to stop before continuing.
>
>     Let me know if I am misunderstanding something.
>
> Cheers,
> Leif
>
>
> Luis Varon wrote:
>   
>> Dear Ladies and Gentleman,
>>
>> We are using the java service wrapper to stop and start our java application. 
>>
>> In some cases we have problems stopping our application which causes the wrapper to fail with an error message however the application is stopped also. Normally this is not an big problem if we restart our application but it is if we restart the application using our liveupdate functionality. In this case the Liveupdate (a process which stops the application, updates the system and restart the application) is finished to fast and while trying to start the wrapper we receive the error message "The ipex scheduler service service is already running with status: STOP_PENDING" and the application is not started.
>>
>> I would like to ask you if you have had this problem and how has it been solved and if not maybe you know an parameter which can be set and which slows down the start of the application.
>>
>> Many thanks in advance for your efforts.
>>
>> Kind regards
>>
>> Luis Varon Marques
>> iPoint-systems gmbh
>>