Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 900037 (JBPAPP6-1524)

Summary: Unstable Tests failing frequently in EAP6 testsuite due to 'Server Already Running' or DuplicateServiceException(probably due to bad clean-up from previous tests or order of tests)
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Madhumita Sadhukhan <msadhukh>
Component: TestsuiteAssignee: Rajesh Rajasekaran <rajesh.rajasekaran>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0.0CC: atangrin, jlanik, msadhukh, ozizka, pslavice, rajesh.rajasekaran
Target Milestone: ---   
Target Release: TBD EAP 6   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1524
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-03 19:54:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
server.log
none
server.log none

Description Madhumita Sadhukhan 2012-03-13 15:57:15 UTC 
project_key: JBPAPP6

I am enlisting tests that are failing because some service or datasource is already registered as follows:

Job link on Hudson:

https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-AS-Testsuite/job/eap-60-as-testsuite-RHEL-matrix-OracleJDK7/4/

1) XaDataSourceCfgMetricUnitTestCase.testDefaultXaDsAttributes and XaDataSourceCfgMetricUnitTestCase.testNoXaDsProperties

Stacktrace:
org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation failed: {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014749: Operation handler failed: Service jboss.xa-data-source-config.DS.xa-datasource-properties.DatabaseName is already registered"}}
..............................................................................................................................................................
("xa-datasource-properties" => "DatabaseName")
]): org.jboss.msc.service.DuplicateServiceException: Service jboss.xa-data-source-config.DS.xa-datasource-properties.DatabaseName is already registered


2) ConnectorTestCase.testHttpsConnector and ConnectorTestCase.testAddAndRemoveRollbacks

Stacktrace:

org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation failed: "JBAS014749: Operation handler failed: Service jboss.binding.test-http is already registered"
........................................................................................................................................................................
  ("socket-binding-group" => "standard-sockets"),
    ("socket-binding" => "test-http")
]): org.jboss.msc.service.DuplicateServiceException: Service jboss.binding.test-http is already registered

3) BasicIIOPInvocationTestCase and TransactionIIOPInvocationTestCase fails due to ' server is already running'.....probably not stopped by some previous testcase.

Sine we use the EAP testsuite for regression check such inconsistent failures will create difficulties in future and should be cleaned up.
Comment 1 Madhumita Sadhukhan 2012-03-13 15:58:21 UTC 
Ondrej again this got assigned to you by default please feel free to reassign to concerned person if required.
Comment 2 Madhumita Sadhukhan 2012-03-13 16:15:31 UTC 
Attachment: Added: server.log
Attachment: Added: server.log
Comment 3 Ondřej Žižka 2012-03-13 22:58:41 UTC 
Both cases are due to some tests not cleaning up after they fail. Someone from QA needs to fix that.
My suggestion is to delete the http-test binding and datasource both *before* and after the test; that would make it stable.

Assigning to Jan Lanik since IIRC he was the one coding the datasource tests, right Honzo?
Comment 4 Ondřej Žižka 2012-03-13 23:00:13 UTC 
Btw not sure what exactly happened but seems like a result of JBPAPP-8368. Linking.
Comment 5 Ondřej Žižka 2012-03-13 23:00:29 UTC 
Link: Added: This issue is related to JBPAPP-8368
Comment 6 Ondřej Žižka 2012-03-13 23:00:54 UTC 
Link: Removed: This issue is related to JBPAPP-8368
Comment 7 Ondřej Žižka 2012-03-13 23:01:02 UTC 
Link: Added: This issue relates to JBPAPP-8368
Comment 8 Jan Lanik 2012-03-14 07:35:38 UTC 
Ondra: I have not been coding specific datasource tests. I've just used some non-default datasource configuration for password-masking and loginmodules tests. So If you find out that this issue is caused by those, you can assign it to me, but as nothing in the description suggests that, I'm going to reassign this back for now.
Comment 10 Ondřej Žižka 2012-03-30 12:54:36 UTC 
Link: Added: This issue relates to AS7-4070
Comment 11 Rajesh Rajasekaran 2012-06-06 22:50:33 UTC 
Madhumita, do you have an update on this issue with the latest CR1 build?
Comment 12 Madhumita Sadhukhan 2012-06-07 10:29:22 UTC 
Rajesh,

        There is big improvement as I have not seen any unstable tests on RHEL or Solaris with above issues in EAP6 CR1.
However Windows testsuite is still highly unstable and under investigation.
Comment 13 Rajesh Rajasekaran 2012-09-20 18:36:17 UTC 
Labels: Added: eap601-qe-triage
Comment 15 Anne-Louise Tangring 2012-10-08 15:10:05 UTC 
Not approved for EAP 6.0.1. If this should be reconsidered, please add the label: eap601-qe-triage
Comment 16 Anne-Louise Tangring 2012-10-08 15:10:05 UTC 
Labels: Removed: eap601-qe-triage
Comment 17 Ondřej Žižka 2012-10-16 11:18:38 UTC 
With JBPAPP-8368 fixed, does this still happen?
Comment 18 Madhumita Sadhukhan 2012-10-16 11:42:47 UTC 
I did not see any test failures due to 'Server Already Running' or DuplicateServiceException during 6.0.1.Er2 testing cycle on any platform.
Closing this.
Comment 19 Anne-Louise Tangring 2012-11-13 21:01:41 UTC 
Docs QE Status: Removed: NEW