[jboss-jira] [JBoss JIRA] (WFLY-4647) RemoteOutboundConnectionReconnectTestCase, EJBClientReconnectionTestCase configured as clustered test cases
[
https://issues.jboss.org/browse/WFLY-4647?page=com.atlassian.jira.plugin....
]
Kabir Khan updated WFLY-4647:
-----------------------------
Fix Version/s: 10.0.0.Final
I am bulk closing old issues that were resolved with no fix version. There are quite many
of these so I am not checking the history properly. From the lastModified date of this
issue it looks like it was done for 10.0.0.Final (I am not caring about alpha/beta etc.
for this exercise). If that is incorrect please adjust as needed.
RemoteOutboundConnectionReconnectTestCase,
EJBClientReconnectionTestCase configured as clustered test cases
-----------------------------------------------------------------------------------------------------------
Key: WFLY-4647
URL: https://issues.jboss.org/browse/WFLY-4647
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 10.0.0.Alpha1
Reporter: Richard Achmatowicz
Assignee: Michal Vinkler
Fix For: 10.0.0.Final
In the Wildfly integration testsuite, manual mode section, there are two test cases
which are running in a clustered environment when they should not be:
- RemoteOutboundConnectionReconnectTestCase
- EJBClientReconnectionTestCase
These two cases test outbound connections from one server A to another server B, and
connection from a client to a server A when the server is stopped and started. There is no
clustering functionality being tested.
Two problems with this situation:
- exceptions are generated in the logs which result from the fact that the test cases are
not being run in the correct environment
- the fact that the environment is incorrectly configured may also be preventing real
bugs from otherwise being detected
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)