Yes, the HornetQ test which does a "reload" and belongs to the manual
mode testsuite was failing (often) on the reload operation. There's a
JIRA
https://issues.jboss.org/browse/WFLY-1518 where I've attached the
whole log file. Let me know if you need more data/logs, we might be able
to get it from the TeamCity environment.
-Jaikiran
On Friday 14 June 2013 03:26 PM, Emanuel Muckenhuber wrote:
On 06/14/2013 11:33 AM, Jeff Mesnil wrote:
> Le 14 juin 2013 à 11:25, Tomaž Cerar<tomaz.cerar(a)gmail.com> a écrit :
>
>>>
org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testActiveBackupReload
>>>
org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testLiveReload
> I've sent a PR[1] for these tests. The intermittent failures occur during a
:reload operation when the connection is closed before the operation result returns.
> I swallow up the exception for this special case and this should prevent anymore
failure.
>
> Note that these tests would be revisited when we provide a high-level reload
operation on the client that takes care of the disconnection/reconnection issues.
>
Were those tests still failing recently? Because i thought we fixed the
execution of that :reload operation for good. There are still other
(client side) issues related to reloading a server, but we do have some
better handling for this operation now. So if that is still an issue
then i have to look into it again.
Emanuel
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev