activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim George (JIRA)" <>
Subject [jira] Commented: (AMQ-2919) OutOfMemory exception possible when using ByteMessage-s due to JVM bug
Date Tue, 26 Oct 2010 10:47:41 GMT


Tim George commented on AMQ-2919:

We are experiencing a problem in 5.4.1 (with Spring 3.0.4) which appears to be related to
this fix. No problems with 5.4.0 and the same configuration.

It looks like ActiveMQBytesMessage.storeContent closes the DeflaterStream prematurely, leaving
initializeWriting with nothing to close.

Error log:
Caused by: java.lang.NullPointerException: Deflater has been closed
	at org.apache.activemq.command.ActiveMQBytesMessage$1.close(
	at org.apache.activemq.command.ActiveMQBytesMessage.storeContent(
	at org.apache.activemq.command.ActiveMQBytesMessage.reset(
	at org.springframework.jms.core.JmsTemplate.doSend(
	at org.springframework.jms.core.JmsTemplate$3.doInJms(
	at org.springframework.jms.core.JmsTemplate.execute(
	at org.springframework.jms.core.JmsTemplate.send(

> OutOfMemory exception possible when using ByteMessage-s due to JVM bug
> ----------------------------------------------------------------------
>                 Key: AMQ-2919
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.4.1
> Due to following the custom deflator
is not closed when used with DeflaterOutputStream. A workaround is to explicitly close it.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message