[JBoss JIRA] Created: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
5:55 p.m.
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Deployment services, Test Suite
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:45 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=comments#action_12367451 ]
Carlo de Wolf commented on JBAS-4292:
-------------------------------------
This is also true when process throws an exception.
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:11 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=comments#action_12367503 ]
Brian Stansberry commented on JBAS-4292:
----------------------------------------
I think something recently changed in the deployer code. I have a test that deployers a
sar where some beans are deliberately meant to fail. At the end of the deployment, the
following is logged:
2007-07-01 10:30:16,968 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] Fully
Deployed vfsfile:/C:/dev/jboss/jboss-head/testsuite/output/lib/partitionstatetransfer.sar
2007-07-01 10:30:16,968 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
file:/C:/dev/jboss/jboss-head/testsuite/output/lib/partitionstatetransfer.sar
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** CONTEXTS IN ERROR: Name -> Error
BadStatePartition -> org.jboss.test.cluster.partition.BadHAPartitionStateException:
BadHAPartitionState cannot be deserialized
BadProviderPartition -> java.lang.IllegalStateException: Initial serviceState transfer
failed: Channel.getState() returned false
at
org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:552)
at
org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:379)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:814)
at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:587)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:270)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at
org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at
org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:815)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:416)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
The test then does some stuff accessing other bean for a couple seconds, and then
undeploys the sar. This doesn't go correctly. You get this logging:
2007-07-01 10:30:19,312 WARN [org.jboss.deployment.MainDeployer] undeploy
'file:/C:/dev/jboss/jboss-head/testsuite/output/lib/partitionstatetransfer.sar' :
package not deployed
Thereafter, any test that includes testServerFound() will fail with an
org.jboss.deployers.client.spi.IncompleteDeploymentException that lists the above two
failed deployments.
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:29 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=comments#action_12367505 ]
Brian Stansberry commented on JBAS-4292:
----------------------------------------
Simply changing the order of operations in MainDeployer.deploy(URL) fixes my problem
above.
From:
// TODO: JBAS-4292
delegate.checkComplete();
contextMap.put(url, deploymentName);
To:
contextMap.put(url, deploymentName);
// TODO: JBAS-4292
delegate.checkComplete();
Doing that seems a bit dodgy, but it works. If an exception causes a bypass of the
contextMap.put call, you can never undeploy.
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:44 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=comments#action_12367514 ]
Carlo de Wolf commented on JBAS-4292:
-------------------------------------
Nope, cheered too soon.
2007-07-03 09:38:48,868 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Remove
deployment context:
vfsfile:/home/carlo/work/jboss-head/ejb3/output/test-lib/jsr181-client.jar
2007-07-03 09:38:48,868 DEBUG [org.jboss.deployers.plugins.main.MainDeployerImpl] Not
scheduling removal of context already in error:
vfsfile:/home/carlo/work/jboss-head/ejb3/output/test-lib/jsr181-client.jar
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:21 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=comments#action_12367516 ]
Adrian Brock commented on JBAS-4292:
------------------------------------
PLEASE, PLEASE, PLEASE. Create a forum thread. Don't try to "guess" here.
JIRA issues should be raised when the problem is understand and we know what needs fixing
JIRA is not a discussion forum!!!!!
The real issue is that for backwards compatibility (same semantics as JBoss4), the old
MainDeployer.deploy()
should not be doing delegate.checkComplete() there is a seperate invocation for this.
However, I believe Scott also added a "checkIncomplete" to the JBoss-Head
testsuite
so even removing it from the old MainDeployer won't help?
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:04 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Carlo de Wolf updated JBAS-4292:
--------------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059873
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4059873
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:22 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Dimitris Andreadis reassigned JBAS-4292:
----------------------------------------
Assignee: (was: Dimitris Andreadis)
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:14 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Ales Justin reassigned JBAS-4292:
---------------------------------
Assignee: Ales Justin
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Ales Justin
Fix For: JBossAS-5.0.0.Beta3
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:18 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Dimitris Andreadis updated JBAS-4292:
-------------------------------------
Fix Version/s: JBossAS-5.0.0.CR1
(was: JBossAS-5.0.0.Beta3)
Moving to CR1. If there is a problem with this, please contact me.
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Ales Justin
Fix For: JBossAS-5.0.0.CR1
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:48 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Scott M Stark updated JBAS-4292:
--------------------------------
Priority: Critical (was: Major)
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Ales Justin
Priority: Critical
Fix For: JBossAS-5.0.0.Beta4
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:39 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Dimitris Andreadis updated JBAS-4292:
-------------------------------------
Comment: was deleted
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Ales Justin
Priority: Critical
Fix For: JBossAS-5.0.0.Beta4
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-4292) Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test failures
[ http://jira.jboss.com/jira/browse/JBAS-4292?page=all ]
Dimitris Andreadis resolved JBAS-4292.
--------------------------------------
Resolution: Done
I understand we can close this issue. If now, please re-open.
Legacy MainDeployer.deploy use of checkIncomplete causes leaks/test
failures
----------------------------------------------------------------------------
Key: JBAS-4292
URL: http://jira.jboss.com/jira/browse/JBAS-4292
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite, Deployment services
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Scott M Stark
Assigned To: Ales Justin
Priority: Critical
Fix For: JBossAS-5.0.0.Beta4
If one adds a checkIncomplete call to validate a deployment in the legacy
org.jboss.deployment.MainDeployer used by the testsuite deploy calls, there are additional
failures and memory leaks that prevent the run from completing. It appears that tests are
not cleaning up after failed deployments.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6174
days inactive
6478
days old
12 comments
6 participants
participants (6)
-
Adrian Brock (JIRA) -
Ales Justin (JIRA)
-
Brian Stansberry (JIRA)
-
Carlo de Wolf (JIRA)
-
Dimitris Andreadis (JIRA)
-
Scott M Stark (JIRA)