[
https://issues.jboss.org/browse/ISPN-4421?page=com.atlassian.jira.plugin....
]
Martin Gencur commented on ISPN-4421:
-------------------------------------
I suppose one of the servers, probably the older one, will have to be started via other
means than Arquillian (e.g. antrun plugin or cargo). The other problem is that Infinispan
Arquillian Container (it is used to collect jmx stats) now communicates with the server
over http-remoting-jmx. I can investigate whether ispn-arq can be configured to use
different protocols for different versions of server. Or we can try to not use ispn-arq
for this test.
Migration from jboss-as to wildfly arquillian-container-managed broke
RollingUpgrades tests
-------------------------------------------------------------------------------------------
Key: ISPN-4421
URL:
https://issues.jboss.org/browse/ISPN-4421
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite - Server
Affects Versions: 7.0.0.Alpha4
Reporter: Tomas Sykora
Assignee: Mircea Markus
Labels: test_suite, testsuite_stability
Server was rebased to Wildfly.
For Arquillian, jboss-as-arquillian-container-managed was changed to
wildfly-arquillian-container-managed in order to reflect respective changes.
The problem for Rolling Upgrade tests ( -Psuite.rolling.upgrades ) is that there are used
also old server instances in those tests.
Due to new changes in infinispan-arquillian-container old Infinispan servers are not
properly managed during their startup phase.
Observation:
Switching port to 10099 (wildfly is using 10090 for mgmt ops) does not help. Strange
message is continuously showing until timeout:
13:41:57,691 ERROR [org.jboss.remoting.remote.connection] (Remoting
"node1:MANAGEMENT" read-1) JBREM000200: Remote connection failed:
java.io.IOException: Received an invalid message length of 1195725856
"Experiment" with setting up <property
name="managementProtocol">remoting-jmx</property> for OLD server in
arquillian.xml didn't help either, however, ERROR message ^ disappeared.
But the server can't start properly, better to say, it starts, but Arquillian is not
able to handle it properly and communicate:
testHotRodRollingUpgradesDiffVersions(org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT)
Time elapsed: 60.389 sec <<< ERROR!
org.jboss.arquillian.container.spi.client.container.LifecycleException: Could not start
container
at
org.jboss.as.arquillian.container.managed.ManagedDeployableContainer.startInternal(ManagedDeployableContainer.java:204)
at
org.jboss.as.arquillian.container.CommonDeployableContainer.start(CommonDeployableContainer.java:112)
at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
at
org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
at
org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
at
org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
at
org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
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.container.impl.client.ContainerDeploymentContextHandler.createContainerContext(ContainerDeploymentContextHandler.java:57)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
at
org.jboss.arquillian.container.test.impl.client.container.ClientContainerController.start(ClientContainerController.java:93)
at
org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.testHotRodRollingUpgradesDiffVersions(HotRodRollingUpgradesIT.java:68)
It looks like we need to somehow create a "bridge" or "switch" which
will allow operations for both old and new servers in one test.
Or maybe I'm missing something important.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)