Re: [Wrapper-user] Graceful shutdown problem.

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

Oded,
The access violation is probably being caused by a SecurityManager(??)  
If that is the
case then you will need to give wrapper.jar full privileges in your 
policy file.

The only reason I could think why you would be getting the unexpected 
exit was if
the JVM called Runtime.halt(), or if you have the Wrapper's shutdown hook
disabled.  Is it possible that BEA is calling halt after that access 
violation?

You can try turning on wrapper.debug, but I am not sure if that will 
give you
any more info in this case.

Cheers,
Leif

Oded Blayer wrote:

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