Try increasing your heap size via java -Xmx=512m or something. If you
want to reduce your RAM footprint use the <usageManager> element and
try using a database in another process (MySQL/Postgresql) rather than
the embedded Derby.
On 9/22/06, HU <[EMAIL PROTECTED]> wrote:
I did a test as below:
1, use below codes to start a broker thread that only create 2 queues:
BrokerService broker = new BrokerService();
broker.addConnector("tcp://localhost:61616");
broker.start();
ActiveMQConnectionFactory connectionFactory;
connectionFactory = new ActiveMQConnectionFactory(
"failover:tcp://localhost:61616");
2, create a sender thread and a consumer thread which use the 2 queues.
3, Send a mesesage from sender thread through a queue then receive the
message on the consumer thread.
4, Send a message from consumer thread through another queue and recieve the
message on the sender thread.
5, repeat 3 and 4.
After send about 380 messages from sendder thread, an error occurred on the
broker thread which is:
Thread[ActiveMQ Transport server: tcp//XXX:61616]( Interrupting...
(Exception OutOfMemoryError)
OpenWireFormat.<int>(int) Line:62
....
Could someone tell me please how to resolve the problem.
--
View this message in context:
http://www.nabble.com/Broker-used-up-the-memory-tf2316972.html#a6444443
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
James
-------
http://radio.weblogs.com/0112098/
