RE: OpenJMS crashing! Help!

You're running openjms 0.7.5?

NON_PERSISTENT messaging can cause the server to run out of memory
if:
. you are publishing a lot of messages in short period of time
. subscribers aren't consuming messages as fast as they are being
  produced

To start with, you could try to increase the available memory
to the server:

E.g, to increase the memory on Windows, edit or create the
$OPENJMS_HOME/bin/setenv.bat
batch file and, and add:

rem Set the max memory to 256 MB
set JAVA_OPTS=-Xmx256M

Next, try playing round with the <MessageManagerConfiguration/> and
<GarbageCollectionConfiguration/> configuration elements.
See:
http://openjms.sourceforge.net/config/reference.html#MessageManagerConfigura
tion and
http://openjms.sourceforge.net/config/reference.html#GarbageCollectionConfig
uration

Regards,

Tim

> -----Original Message-----
> From: openjms-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> [mailto:openjms-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org]On Behalf Of
> Thomas, Ivy
> Sent: Saturday, 26 July 2003 6:13 AM
> To: 'openjms-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org'
> Subject: [openjms-developer] OpenJMS crashing! Help!
>
>
> Hello
> I am running the server in non persistent, tcp mode.
>
> Here is what I see when I have around 50 publishers and subscribers to
> same/multiple topics.
> Can someone tell me if there is a configuration piece I missed
> and why this
> is happenning? This is not like the server is running for days.. it
> happenned in just an hour of all the publishers/subscribers coming in.
>
> 15:26:18.968 ERROR [Scheduler-Worker-2] - javax.jms.JMSException:
> Could not
> get message for handle Handle : 4:1059159614031:3267
> :ID:6202634392488269420
> javax.jms.JMSException: Could not get message for handle Handle :
> 4:1059159614031:3267:ID:6202634392488269420
>         at
> org.exolab.jms.server.JmsServerSession.onMessage(Unknown Source)
>         at org.exolab.jms.messagemgr.TopicConsumerEndpoint.run(Unknown
> Source)
>         at
> org.exolab.core.threadPool.ThreadPoolWorker.runIt(ThreadPoolWorker
> .java:186)
>         at
> org.exolab.core.threadPool.ThreadPoolWorker.runWork(ThreadPoolWork
> er.java:17
> 3)
>         at
> org.exolab.core.threadPool.ThreadPoolWorker.access$000(ThreadPoolW
> orker.java
> :67)
>         at
> org.exolab.core.threadPool.ThreadPoolWorker$1.run(ThreadPoolWorker
> .java:117)
>         at java.lang.Thread.run(Thread.java:536)
>
>
> after a period of time I start seeing this:
>
> java.lang.OutOfMemoryError
> java.lang.OutOfMemoryError
> java.lang.OutOfMemoryError15:52:34.031 INFO  [EventManager-Worker-3] -
> Failed to verify that session 976118066399111786 is active.
>
> Thanks
> Ivy
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072
> 303_01/01
> _______________________________________________
> openjms-developer mailing list
> openjms-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/openjms-developer
>