I'm willing to log this as a bug. But can you tell me why this is a problem
that can't be worked around by other means? Seriously, I think your request
is reasonable, but on the other hand it'd help to have a good reason why
you'd want to stop an embedded instance of JRun without exiting the JVM.
Scott Stirling
Allaire Corporation
http://www.allaire.com/developer/jrunreferencedesk/
> -----Original Message-----
> From: Hammon, Randy [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 25, 2000 2:37 PM
> To: '[EMAIL PROTECTED]'
> Subject: Another Example of the problem with JRun3.0 exit() behavior
>
>
> Last month I discovered a very uncool behavior of JRun3.0, in
> which it calls
> exit() when
> it stops. This is a huge problem for OEMS trying to embedding JRun3.0.
>
> I just ran into another example of why it's a bad idea for
> JRun3.0 to call
> exit().
>
> An internal customer had accidently started an instance of JRun, then
> proceeded to
> boot our application which internally starts JRun. After taking a few
> minutes to boot,
> our app started JRun, JRun found it's listening ports were
> being used, then
> it called
> exit and brought down OUR app along with it. Ouch!
>
> Allaire. Please fix this in the next release.
>
> Thanks,
> -Randy Hammon
> Evolve Software, Inc
> 1400 65th St. Suite 100
> Emeryville, CA 94608
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
