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

Craig Pfeifer <[email protected]> Mon, 14 Apr 2008 12:12:14 -0400
Newsgroups gmane.comp.windows.devel.java.advanced
Message-ID <[email protected]>
On Mon, Apr 14, 2008 at 12:04 PM, Bob Lee <[email protected]> wrote:
> On Mon, Apr 14, 2008 at 6:44 AM, Randall R Schulz <[email protected]> wrote:
>
>  > I did essentially this:
>  >
>  >    <http://www.javaspecialists.eu/archive/Issue092.html>
>  >
>
>  I wouldn't recommend it. Heinz says himself, "since constructing new objects
>  is a rather fast operation in Java, it may happen that the JVM runs out of
>  memory before getting a chance to notify us." This is especially true when
>  you have concurrent threads.
>
>  If you're interested in exploring multiple VMs more (if only for future
>  reference), check out java.lang.ProcessBuilder and keep in mind that you can
>  send a serialized result back over stdout.

Another idea might be to use multiple VMs across multiple machines to
create a large virtual memory space. My first instinct would be to use
a JBoss cache-esque widget, but I think they just do replication among
VMs, but I could be wrong.

--
[email protected]

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

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