#31 Workaround for the OutOfMemoryError

[Jim Alateras]

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.

[Tim Anderson]

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.