RE: OpenJMS crashing! Help!

I tried all kinds of combination: Here are the current configs that I am
working with. I have around 100 publishers publishing to the same topic at a
frequency of 8 secs. The subscribers may not be as many as publishers.

OPENJMS 0.7.5 - mode tcp - persistent

set JAVA_OPTS=-Xmx512M
destinationcachesize - 20000
maxthreads - 500
memorycheckinterval - 60
lowwaterthreshold - 35
garbagecollectionthreadpriority - 2
Still complains about the memory:(

Am running out of options to try and am considering changing the
destinationcachesize to 2000000. 
Another note: Am creating the topic dynamically. Since I am having trouble
doing lookup on topic name, am assuming that on creating an existing topic,
it will return me a reference to the already created topic. Am I correct.

Appreciate your help!
Thanks
Ivy

-----Original Message-----
From: Thomas, Ivy [mailto:ithomas-T2hhe/[email protected]]
Sent: Friday, July 25, 2003 4:13 PM
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(ThreadPoolWorker.java:17
3)
        at
org.exolab.core.threadPool.ThreadPoolWorker.access$000(ThreadPoolWorker.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_072303_01/01