Re: Out-of-Memory Handling in Long-Running / Server Applications

Randall R Schulz wrote:
> On Monday 14 April 2008 07:09, Endre Stølsvik wrote:
>> Randall R Schulz wrote:
>>> ...
>>>
>>> As far as it being single-threaded, when running as a CLI command,
>>> it is (JVM threads notwithstanding), and in that setting it's no
>>> big deal if OOM handling is disorderly.
>> And this is of course what Bob tried to hint to you: Fork a JVM doing
>> each computation, "CLI style". The JVMs that return with a result are
>> good, and the JVMs that don't return a result are also good (they
>> failed!).
>
> Yes, but many of my users won't use a CLI, they only use the
> browser-based interface.

You don't get the point?! Seriously?

Fork a damn JVM _from the damn webapp_ _for each damn request_, and
collect the damn result _back into the webapp_ (using some means, there
are plenty), then give it to the damn user _on the damn browser_.

>
> Not only are we going in circles, here, but as I said, I have a
> satisfactory solution!

Good.

I think you have a somewhat strange way of thanking the people who are
trying to help you with your problems.

Endre.

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com