[
https://issues.jboss.org/browse/RF-11154?page=com.atlassian.jira.plugin.s...
]
Juraj Huska edited comment on RF-11154 at 9/23/11 8:22 AM:
-----------------------------------------------------------
I have also tried to reproduce this issue on *JBoss AS 7.0.1.Final*. These mentioned
exceptions *are thrown as well*, however when testing with Arquillian *they do not cause
PERM Gen memory errors* and therefore I am able to run whole test suite.
I am not able to say right now whether this will be also enough for larger test suits like
metamer has, but for now it works for showcase. I wil know the answer for Metamer after
successfully migrating to Arquillian.
was (Author: jhuska):
I have also tried to reproduce this issue on *JBoss AS 7.0.1.Final*. These mentioned
exceptions are thrown as well, however when testing with Arquillian *they do not cause
PERM Gen memory errors* and therefore I am able to run whole test suite.
I am not able to say right now whether this will be also enough for larger test suits like
metamer has, but for now it works for showcase. I wil know the answer for Metamer after
successfully migrating to Arquillian.
Push - Showcase - JMS connection is left opened on JBoss AS 7
-------------------------------------------------------------
Key: RF-11154
URL:
https://issues.jboss.org/browse/RF-11154
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-push/poll, examples
Affects Versions: 4.1.0.Milestone1
Environment: richfaces-showcase 4.1.0.-SNAPSHOT, container JBoss AS 7.0.0.Final
Reporter: Juraj Huska
Assignee: Lukáš Fryč
Fix For: 4.1.0.Milestone3
When I am deploying showcase multiple times during running test suite(this multiple
deployment is needed in Arquillian, since for every test class is application deployed
again), I am encountering with java.lang.OutOfMemoryError: PermGen space error which in my
opinion caused by this:
{code}
WARN [org.hornetq.jms.client.HornetQConnection] (Finalizer) I'm closing a JMS
connection you left open. Please make sure you close all JMS connections explicitly before
letting them go out of scope!
13:03:33,712 WARN [org.hornetq.jms.client.HornetQConnection] (Finalizer) The JMS
connection you didn't close was created here:: java.lang.Exception
at org.hornetq.jms.client.HornetQConnection.<init>(HornetQConnection.java:152)
at
org.hornetq.jms.client.HornetQTopicConnection.<init>(HornetQTopicConnection.java:35)
at
org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:682)
at
org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:145)
at
org.hornetq.jms.client.HornetQConnectionFactory.createTopicConnection(HornetQConnectionFactory.java:140)
at
org.richfaces.demo.push.JMSMessageProducer.initializeMessaging(JMSMessageProducer.java:86)
at org.richfaces.demo.push.JMSMessageProducer.sendMessage(JMSMessageProducer.java:66)
at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57)
at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
{code}
When I am deploying showcase.war which is without Push example(4.0.0.Final), so no JMS
communication is opened, no Perm Gen error is thrown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira