[JBoss JIRA] (ARQ-1949) Memory leak in DeploymentContextImpl.stores
by Falko M. (JIRA)
[ https://issues.jboss.org/browse/ARQ-1949?page=com.atlassian.jira.plugin.s... ]
Falko M. updated ARQ-1949:
--------------------------
Environment:
Java 1.7.0_80
Maven 3.2.5
Surefire-Plugin 2.18.1
Windows7 x64 and CentOS 6.5
was:
Maven 3.2.5
Surefire-Plugin 2.18.1
Windows7 x64 and CentOS 6.5
> Memory leak in DeploymentContextImpl.stores
> -------------------------------------------
>
> Key: ARQ-1949
> URL: https://issues.jboss.org/browse/ARQ-1949
> Project: Arquillian
> Issue Type: Bug
> Affects Versions: 1.1.3.Final, 1.1.7.Final
> Environment: Java 1.7.0_80
> Maven 3.2.5
> Surefire-Plugin 2.18.1
> Windows7 x64 and CentOS 6.5
> Reporter: Falko M.
>
> The {{Deployment}} (which also holds the {{Archive}}) for each test class is added to {{DeploymentContextImpl.stores}}. A {{Deployment}} is deactivated properly but it is *not* getting removed until the {{Manager}} shuts down.
> This can easily blow the heap of the executing JVM in case you have *many* test classes and/or *large* archives to deploy.
> In our environment the JVM forked by maven surefire dies with an OOM after just ~20 test classes. Xmx is set to 512m.
> PS: Another user came across this problem too: https://developer.jboss.org/thread/250124
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARQ-1949) Memory leak in DeploymentContextImpl.stores
by Falko M. (JIRA)
[ https://issues.jboss.org/browse/ARQ-1949?page=com.atlassian.jira.plugin.s... ]
Falko M. commented on ARQ-1949:
-------------------------------
A workaround is to call destroy explicitly:
{code:java}
public class LeakFixHandler {
@Inject
private Instance<DeploymentContext> deploymentContext;
public void destroyDeployment(@Observes(precedence = Integer.MIN_VALUE) final UnDeployDeployment event) {
deploymentContext.get().destroy(event.getDeployment());
}
}
{code}
> Memory leak in DeploymentContextImpl.stores
> -------------------------------------------
>
> Key: ARQ-1949
> URL: https://issues.jboss.org/browse/ARQ-1949
> Project: Arquillian
> Issue Type: Bug
> Affects Versions: 1.1.3.Final, 1.1.7.Final
> Environment: Maven 3.2.5
> Surefire-Plugin 2.18.1
> Windows7 x64 and CentOS 6.5
> Reporter: Falko M.
>
> The {{Deployment}} (which also holds the {{Archive}}) for each test class is added to {{DeploymentContextImpl.stores}}. A {{Deployment}} is deactivated properly but it is *not* getting removed until the {{Manager}} shuts down.
> This can easily blow the heap of the executing JVM in case you have *many* test classes and/or *large* archives to deploy.
> In our environment the JVM forked by maven surefire dies with an OOM after just ~20 test classes. Xmx is set to 512m.
> PS: Another user came across this problem too: https://developer.jboss.org/thread/250124
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARQ-1949) Memory leak in DeploymentContextImpl.stores
by Falko M. (JIRA)
Falko M. created ARQ-1949:
-----------------------------
Summary: Memory leak in DeploymentContextImpl.stores
Key: ARQ-1949
URL: https://issues.jboss.org/browse/ARQ-1949
Project: Arquillian
Issue Type: Bug
Affects Versions: 1.1.7.Final, 1.1.3.Final
Environment: Maven 3.2.5
Surefire-Plugin 2.18.1
Windows7 x64 and CentOS 6.5
Reporter: Falko M.
The {{Deployment}} (which also holds the {{Archive}}) for each test class is added to {{DeploymentContextImpl.stores}}. A {{Deployment}} is deactivated properly but it is *not* getting removed until the {{Manager}} shuts down.
This can easily blow the heap of the executing JVM in case you have *many* test classes and/or *large* archives to deploy.
In our environment the JVM forked by maven surefire dies with an OOM after just ~20 test classes. Xmx is set to 512m.
PS: Another user came across this problem too: https://developer.jboss.org/thread/250124
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARQ-1938) wildfly container does not support serverConfig parameter
by Max Sinelnikov (JIRA)
[ https://issues.jboss.org/browse/ARQ-1938?page=com.atlassian.jira.plugin.s... ]
Max Sinelnikov commented on ARQ-1938:
-------------------------------------
It seems that only embedded wildfly container does not support serverConfig parameter.
I tried it with managed container and it works.
> wildfly container does not support serverConfig parameter
> ---------------------------------------------------------
>
> Key: ARQ-1938
> URL: https://issues.jboss.org/browse/ARQ-1938
> Project: Arquillian
> Issue Type: Feature Request
> Reporter: Karl Pietrzak
>
> h3. arquillian.xml snippet
> {code:xml}
> <container qualifier="wildfly-embedded" default="true">
> <configuration>
> <property name="serverConfig">does_not_matter.xml</property>
> <property name="jbossHome">target/wildfly-embedded/wildfly-8.2.0.Final/</property>
> <property name="modulePath">target/wildfly-embedded/wildfly-8.2.0.Final/modules</property>
>
> </configuration>
> </container>
> {code}
> h3. Details
> * It doesn't matter what I put for {{serverConfig}}, which leads me to believe it isn't used.
> * the JBoss container supports this parameter, so it would be great if the Wildfly one did too.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARQ-1947) Unable to use JUnit Matchers and assertThat
by Tomáš Turek (JIRA)
Tomáš Turek created ARQ-1947:
--------------------------------
Summary: Unable to use JUnit Matchers and assertThat
Key: ARQ-1947
URL: https://issues.jboss.org/browse/ARQ-1947
Project: Arquillian
Issue Type: Bug
Components: OSGi Containers
Reporter: Tomáš Turek
Assignee: Thomas Diesler
Unable to use _Matchers_ and _Assert.assertThat_ because the _arquillian-osgi-bundle_ does not export the package _org.hamcrest_.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARQ-1883) Arquillian Persistence Extension: Cucumber integration
by Rafael Pestano (JIRA)
[ https://issues.jboss.org/browse/ARQ-1883?page=com.atlassian.jira.plugin.s... ]
Rafael Pestano edited comment on ARQ-1883 at 5/1/15 11:35 AM:
--------------------------------------------------------------
ok, fixed the "Can't find a persistence unit" problem.
Now the first step runs ok but the [second step|https://github.com/rmpestano/arquillian-extension-persistence/blob/m...] is failing with the error below:
{noformat}
org.jboss.arquillian.persistence.dbunit.exception.DBUnitDataSetHandlingException: Unable to clean database.
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:60)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanDatabase(DBUnitDataHandler.java:184)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanup(DBUnitDataHandler.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataStateLogger.aroundCleanup(DBUnitDataStateLogger.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
...
...
Caused by: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@1bc5bf4a
at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:155)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:296)
at org.dbunit.database.statement.AbstractBatchStatement.<init>(AbstractBatchStatement.java:50)
at org.dbunit.database.statement.SimpleStatement.<init>(SimpleStatement.java:49)
at org.dbunit.database.statement.PreparedStatementFactory.createBatchStatement(PreparedStatementFactory.java:57)
at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:85)
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:56)
... 218 more
{noformat}
was (Author: kwintesencja):
ok, fixed the "Can't find a persistence unit" problem.
Now the first step runs ok but i receive the error below on the [second step|https://github.com/rmpestano/arquillian-extension-persistence/blob/m...] is failing the error below:
{noformat}
org.jboss.arquillian.persistence.dbunit.exception.DBUnitDataSetHandlingException: Unable to clean database.
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:60)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanDatabase(DBUnitDataHandler.java:184)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanup(DBUnitDataHandler.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataStateLogger.aroundCleanup(DBUnitDataStateLogger.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
...
...
Caused by: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@1bc5bf4a
at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:155)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:296)
at org.dbunit.database.statement.AbstractBatchStatement.<init>(AbstractBatchStatement.java:50)
at org.dbunit.database.statement.SimpleStatement.<init>(SimpleStatement.java:49)
at org.dbunit.database.statement.PreparedStatementFactory.createBatchStatement(PreparedStatementFactory.java:57)
at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:85)
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:56)
... 218 more
{noformat}
> Arquillian Persistence Extension: Cucumber integration
> ------------------------------------------------------
>
> Key: ARQ-1883
> URL: https://issues.jboss.org/browse/ARQ-1883
> Project: Arquillian
> Issue Type: Feature Request
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha7
> Reporter: Rafael Pestano
> Assignee: Bartosz Majsak
>
> Currently we cannot use persistence extension in a Cucumber test.
> Cukespace extension added events that other extensions can observe in order to e.g.: do something before a step.
> see this issue for more details: https://github.com/cukespace/cukespace/issues/37
> Also there this blog post which details the limitations of using both extensions: http://rpestano.wordpress.com/2014/11/08/arquillian-cucumber-dbunit/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months
[JBoss JIRA] (ARQ-1883) Arquillian Persistence Extension: Cucumber integration
by Rafael Pestano (JIRA)
[ https://issues.jboss.org/browse/ARQ-1883?page=com.atlassian.jira.plugin.s... ]
Rafael Pestano edited comment on ARQ-1883 at 5/1/15 11:29 AM:
--------------------------------------------------------------
ok, fixed the "Can't find a persistence unit" problem.
Now the first step runs ok but i receive the error below on the [second step|https://github.com/rmpestano/arquillian-extension-persistence/blob/m...] is failing the error below:
{noformat}
org.jboss.arquillian.persistence.dbunit.exception.DBUnitDataSetHandlingException: Unable to clean database.
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:60)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanDatabase(DBUnitDataHandler.java:184)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanup(DBUnitDataHandler.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataStateLogger.aroundCleanup(DBUnitDataStateLogger.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
...
...
Caused by: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@1bc5bf4a
at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:155)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:296)
at org.dbunit.database.statement.AbstractBatchStatement.<init>(AbstractBatchStatement.java:50)
at org.dbunit.database.statement.SimpleStatement.<init>(SimpleStatement.java:49)
at org.dbunit.database.statement.PreparedStatementFactory.createBatchStatement(PreparedStatementFactory.java:57)
at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:85)
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:56)
... 218 more
{noformat}
was (Author: kwintesencja):
ok, fixed the "Can't find a persistence unit" problem.
Now the first step runs ok but i receive the error below on the [second step|https://github.com/rmpestano/arquillian-extension-persistence/blob/m...] is faling the error below:
{noformat}
org.jboss.arquillian.persistence.dbunit.exception.DBUnitDataSetHandlingException: Unable to clean database.
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:60)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanDatabase(DBUnitDataHandler.java:184)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataHandler.cleanup(DBUnitDataHandler.java:122)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.persistence.dbunit.DBUnitDataStateLogger.aroundCleanup(DBUnitDataStateLogger.java:121)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
...
...
Caused by: java.sql.SQLException: Connection is not associated with a managed connection.org.jboss.jca.adapters.jdbc.jdk7.WrappedConnectionJDK7@1bc5bf4a
at org.jboss.jca.adapters.jdbc.WrappedConnection.lock(WrappedConnection.java:155)
at org.jboss.jca.adapters.jdbc.WrappedConnection.createStatement(WrappedConnection.java:296)
at org.dbunit.database.statement.AbstractBatchStatement.<init>(AbstractBatchStatement.java:50)
at org.dbunit.database.statement.SimpleStatement.<init>(SimpleStatement.java:49)
at org.dbunit.database.statement.PreparedStatementFactory.createBatchStatement(PreparedStatementFactory.java:57)
at org.dbunit.operation.DeleteAllOperation.execute(DeleteAllOperation.java:85)
at org.jboss.arquillian.persistence.dbunit.cleanup.StrictCleanupStrategyExecutor.cleanupDatabase(StrictCleanupStrategyExecutor.java:56)
... 218 more
{noformat}
> Arquillian Persistence Extension: Cucumber integration
> ------------------------------------------------------
>
> Key: ARQ-1883
> URL: https://issues.jboss.org/browse/ARQ-1883
> Project: Arquillian
> Issue Type: Feature Request
> Components: Extension - Persistence
> Affects Versions: persistence_1.0.0.Alpha7
> Reporter: Rafael Pestano
> Assignee: Bartosz Majsak
>
> Currently we cannot use persistence extension in a Cucumber test.
> Cukespace extension added events that other extensions can observe in order to e.g.: do something before a step.
> see this issue for more details: https://github.com/cukespace/cukespace/issues/37
> Also there this blog post which details the limitations of using both extensions: http://rpestano.wordpress.com/2014/11/08/arquillian-cucumber-dbunit/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 8 months