Re: [Wrapper-user] Re: Converting RMID into a NT/2000 service - Windows Crash

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

George,
    When you say the machine crashes, I want to confirm that you mean 
that your
entire system is blue screening or something and not that the Wrapper 
itself is
crashing.

    I did just fix a problem with 3.1.0 where the Wrapper would sometimes
crash on multi-CPU systems.   This was ONLY a problem if the new 
experimental
tick based timer was being used however.

    Other than that, I am not aware of any other crash problems with the 
Wrapper,
and have never known of a Wrapper related problem which causes the entire
system to crash.

    In my experience, Windows is in general quite good at crashing on 
its own.  :-)
My XP notebook does so 2~3 times per week whether I am using the Wrapper
or not..  I have several other systems which running the Wrapper which 
run for
months without ever rebooting.  When they are rebooted, it is for other 
reasons.

    I often install and remove services without rebooting.  There is 
nothing in the
Wrapper which should require that you do a reboot.

    I don't have any ideas off hand other than to try and think if you 
have installed
any new drivers or run windows update lately.   I have found that 
Windows update
is often bad for the health of a system due to the way the changes 
interact with
various drivers...  Of course if don't do it then your system is insecure...
(snip off rest of rant... :-)

Cheers,
Leif

zge...@ex... wrote:

>I now have several services that use JSW on Win 2000. Everything 
>
>works fine except that ever since I started using JSW - my 
>
>machine seems to crash for no apparent reason. 
>
>
>
>I am still in dev. mode - hence I frequently install and remove and re-install the services from the machine WITHOUT REBOOTING 
>
>after each "remove". Is this an issue?
>
>
>
>The reason I ask is that if I do reboot after each remove the 
>
>crashes do not seem to happen as often. 
>
>
>
>Of course, this may have nothing to do with JSW and everything 
>
>to do with my machine. But has anyone else seen this 
>
>behavior? Could it have something to do with the fact that I do NOT 
>
>reboot each time I remove a set of services.
>
>
>
>Thanks in advance.
>
>Zac George
>
>
>
>  
>
>
>  
>
>>Subject:
>>    
>>
>
>  
>
>>Re: [Wrapper-user] Converting RMID into a NT/2000 service
>>    
>>
>
>  
>
>>From:
>>    
>>
>
>  
>
>>""<zge...@ex...>
>>    
>>
>
>  
>
>>Date:
>>    
>>
>
>  
>
>>Fri, 28 May 2004 12:26:40 -0400
>>    
>>
>
>  
>
>>To:
>>    
>>
>
>  
>
>>wra...@li...
>>    
>>
>
>  
>
>
>  
>
>
>  
>
>>Leif,
>>    
>>
>
>  
>
>
>  
>
>>Thanks for the response. My first attempt at this was to try the 
>>    
>>
>
>  
>
>
>  
>
>>approach you recommend below 
>>    
>>
>
>  
>
>
>  
>
>>(in fact that's the approach I took with the java 
>>    
>>
>
>  
>
>
>  
>
>>Name Service which worked). 
>>    
>>
>
>  
>
>
>  
>
>>I did not have much success with it for rmid.
>>    
>>
>
>  
>
>
>  
>
>
>  
>
>
>  
>
>>However, I did NOT also set the policy file to give specific 
>>    
>>
>
>  
>
>
>  
>
>>permissions to the wrapper jar. Wrapper jar was bundled into my 
>>    
>>
>
>  
>
>
>  
>
>>codebase jar file. I'll try the route you suggest once again. 
>>    
>>
>
>  
>
>
>  
>
>
>  
>
>
>  
>
>>The second issue with the approach you suggest was that I could not 
>>    
>>
>
>  
>
>
>  
>
>>find a way to pass the "-C" command line options that 
>>    
>>
>
>  
>
>
>  
>
>>I can typically pass on the command line to rmid.exe for 
>>    
>>
>
>  
>
>
>  
>
>>passing on to child JVMs if I call on the sun implemenation 
>>    
>>
>
>  
>
>
>  
>
>>directly.
>>    
>>
>
>  
>
>
>  
>
>
>  
>
>
>  
>
>>Even if there is a way around the above two issues, 
>>    
>>
>
>  
>
>
>  
>
>>I believe there may still be a third issue - the rmid daemon will 
>>    
>>
>
>  
>
>
>  
>
>>activate JVMs for activatable objects. I need those JVMs to survive 
>>    
>>
>
>  
>
>
>  
>
>>login/logouts. The launch sequence is as follows:
>>    
>>
>
>  
>
>
>  
>
>>wrapper.exe->rmid.exe->java.exe (contains activatable object). Since 
>>    
>>
>
>  
>
>
>  
>
>>wrapper does not own these "sub" processes they clearly will not 
>>    
>>
>
>  
>
>
>  
>
>>survive the login/logout. What would have been ideal was for a 
>>    
>>
>
>  
>
>
>  
>
>>parent process to own the child process. THe child process may choose 
>>    
>>
>
>  
>
>
>  
>
>>to exit on its own - if it did not make that choice, then the parent 
>>    
>>
>
>  
>
>
>  
>
>>process must control its life cycle. 
>>    
>>
>
>  
>
>
>  
>
>
>  
>
>
>  
>
>>Again, thanks for your response.
>>    
>>
>
>  
>
>
>  
>
>>--
>>    
>>
>
>  
>
>
>  
>
>>Zac
>>    
>>
>
>  
>
>
>  
>
>
>
>
>_______________________________________________
>Join Excite! - http://www.excite.com
>The most personalized portal on the Web!
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the new InstallShield X.
>>From Windows to Linux, servers to mobile, InstallShield X is the one
>installation-authoring solution that does it all. Learn more and
>evaluate today! http://www.installshield.com/Dev2Dev/0504
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>