[infinispan-issues] [JBoss JIRA] (ISPN-1472) Investigate halts due to TransactionsSpanningReplicatedCachesTest failures

[Galder Zamarreño (Commented) (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637114#comment-12637114 ] 

Galder Zamarreño commented on ISPN-1472:
----------------------------------------

I've run some tests to verify the behavior when tests fail and in every case the cache managers are stopped.

However, you do see plenty of cache view installation failures in TransactionsSpanningReplicatedCachesTest. However, there's no indication in the logs of whether it affects the startup of a cache. I'd assume it does but logging does not show such thing since the error is logged by the cache view installer thread?

Dan, could we log something on ECM.startCaches() or ECM.getCache() when the cache does not start? Particularly if the issue is due to an error in view installation? At the moment we cannot see if those exceptions somehow stop start procedure or not.

In the test, I'm moving the startCaches() calls to be within the tests to see these cache startup failures more clearly, and so that cache managers are stopped if there's any issues there. Currently cos they're createCacheManagers, the cache managers might not be terminated.
                
> Investigate halts due to TransactionsSpanningReplicatedCachesTest failures
> --------------------------------------------------------------------------
>
>                 Key: ISPN-1472
>                 URL: https://issues.jboss.org/browse/ISPN-1472
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Test Suite
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 5.1.0.CR1
>
>
> Failures in TransactionsSpanningReplicatedCachesTest are causing issues as shown in:
> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/257/console
> https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/243/console
> Investigate why the CacheManager is not stopped.
> Also consider changing the test to use default cleanup method and make each test use different key/value names.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira