You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/09/15 13:38:40 UTC
[jira] Created: (AMQ-2919) OutOfMemory exception possible when
using ByteMessage-s due to JVM bug
OutOfMemory exception possible when using ByteMessage-s due to JVM bug
----------------------------------------------------------------------
Key: AMQ-2919
URL: https://issues.apache.org/activemq/browse/AMQ-2919
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.4.0
Reporter: Dejan Bosanac
Assignee: Dejan Bosanac
Fix For: 5.4.1
Due to following http://bugs.sun.com/view_bug.do?bug_id=4797189 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.
[jira] Commented: (AMQ-2919) OutOfMemory exception possible when
using ByteMessage-s due to JVM bug
Posted by "Tim George (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62833#action_62833 ]
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:
{noformat}
Caused by: java.lang.NullPointerException: Deflater has been closed
at java.util.zip.Deflater.ensureOpen(Deflater.java:427)
at java.util.zip.Deflater.deflate(Deflater.java:305)
at java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:159)
at java.util.zip.DeflaterOutputStream.finish(DeflaterOutputStream.java:134)
at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:146)
at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
at org.apache.activemq.command.ActiveMQBytesMessage$1.close(ActiveMQBytesMessage.java:808)
at java.io.FilterOutputStream.close(FilterOutputStream.java:143)
at org.apache.activemq.command.ActiveMQBytesMessage.storeContent(ActiveMQBytesMessage.java:124)
at org.apache.activemq.command.ActiveMQBytesMessage.reset(ActiveMQBytesMessage.java:765)
...
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:565)
at org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:536)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:466)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:534)
{noformat}
> OutOfMemory exception possible when using ByteMessage-s due to JVM bug
> ----------------------------------------------------------------------
>
> Key: AMQ-2919
> URL: https://issues.apache.org/activemq/browse/AMQ-2919
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.1
>
>
> Due to following http://bugs.sun.com/view_bug.do?bug_id=4797189 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.
[jira] Commented: (AMQ-2919) OutOfMemory exception possible when
using ByteMessage-s due to JVM bug
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62893#action_62893 ]
Dejan Bosanac commented on AMQ-2919:
------------------------------------
Hi Tim,
any chance you can create a test case that demonstrates the issue?
Thanks,
Dejan
> OutOfMemory exception possible when using ByteMessage-s due to JVM bug
> ----------------------------------------------------------------------
>
> Key: AMQ-2919
> URL: https://issues.apache.org/activemq/browse/AMQ-2919
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.1
>
>
> Due to following http://bugs.sun.com/view_bug.do?bug_id=4797189 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.
[jira] Resolved: (AMQ-2919) OutOfMemory exception possible when
using ByteMessage-s due to JVM bug
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-2919.
--------------------------------
Resolution: Fixed
Fixed with svn revision 997290
> OutOfMemory exception possible when using ByteMessage-s due to JVM bug
> ----------------------------------------------------------------------
>
> Key: AMQ-2919
> URL: https://issues.apache.org/activemq/browse/AMQ-2919
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.4.1
>
>
> Due to following http://bugs.sun.com/view_bug.do?bug_id=4797189 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.