[ openjms-Bugs-673303 ] Workaround for the OutOfMemoryError

Bugs item #673303, was opened at 2003-01-23 19:54
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=673303&group_id=54559

Category: server
Group: v0.7.4
Status: Open
Resolution: None
Priority: 8
Submitted By: Jim Alateras (jalateras)
Assigned to: Jim Alateras (jalateras)
Summary: Workaround for the OutOfMemoryError 

Initial Comment:
Need to do a couple of things to better handle OME.

1. First set the status code in the JMSException so that 
the client can detect the OME and take some action (i.e 
retry the publication at a later stage).

2. At the server end if we get an OME then force GC, 
wait for a period of time and then try again.

3. Add some more statistics to the server so that we 
can monitor pubication and subscription rates and better 
allocate openjms resources to prevent OME.

----------------------------------------------------------------------

>Comment By: Tim Anderson (tanderson)
Date: 2003-01-26 03:19

Message:
Logged In: YES 
user_id=557161

Another approach would be to use SoftReferences to 
cached messages - at least for persistent messages. A 
different strategy would be required for non-persistent 
messages, using flow control. 


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=474136&aid=673303&group_id=54559