[jboss-jira] [JBoss JIRA] (WFLY-1719) ClassCastException on clustered deployment

[Matthias Berndt (JIRA)]

Matthias Berndt created WFLY-1719:
-------------------------------------

             Summary: ClassCastException on clustered deployment
                 Key: WFLY-1719
                 URL: https://issues.jboss.org/browse/WFLY-1719
             Project: WildFly
          Issue Type: Bug
          Components: Clustering
    Affects Versions: 8.0.0.Alpha3
         Environment: windows; oracle jdk 1.7.0_17
            Reporter: Matthias Berndt
            Assignee: Paul Ferraro


In a windows 7 environment the cluster replication for a clustered web archive deployed in a server with _full-ha_-profile fails with a class cast exception.

{code}
21:00:03,514 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "cd" (runtime-name: "cd.war")
21:00:05,179 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:00:05,179 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:00:05,182 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-4) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:00:05,182 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:00:05,183 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:00:05,184 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-3) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
21:00:05,228 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 61) ISPN000078: Starting JGroups Channel
21:00:05,240 INFO  [stdout] (ServerService Thread Pool -- 61) 
21:00:05,240 INFO  [stdout] (ServerService Thread Pool -- 61) -------------------------------------------------------------------
21:00:05,240 INFO  [stdout] (ServerService Thread Pool -- 61) GMS: address=master:server-three/web, cluster=web, physical address=127.0.0.1:55450
21:00:05,240 INFO  [stdout] (ServerService Thread Pool -- 61) -------------------------------------------------------------------

21:00:07,251 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 61) ISPN000094: Received new cluster view: [master:server-three/web|0] [master:server-three/web]
21:00:07,317 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 61) ISPN000079: Cache local address is master:server-three/web, physical addresses are [127.0.0.1:55450]
21:00:07,326 INFO  [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 61) ISPN000128: Infinispan version: Infinispan 'Tactical Nuclear Penguin' 5.3.0.Final
21:00:07,492 INFO  [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 61) ISPN000031: MBeans were successfully registered to the platform MBean server.
21:00:07,492 INFO  [org.infinispan.jmx.CacheJmxRegistration] (ServerService Thread Pool -- 65) ISPN000031: MBeans were successfully registered to the platform MBean server.
21:00:07,505 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 65) JBAS010281: Started default-host/cd cache from web container
21:00:07,505 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 61) JBAS010281: Started repl cache from web container
21:00:07,637 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS018210: Register web context: /cd
21:00:07,675 INFO  [org.jboss.as.server] (host-controller-connection-threads - 1) JBAS018559: Deployed "cd" (runtime-name : "cd.war")
21:00:57,609 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016009: Caught:: java.lang.ClassCastException: org.infinispan.transaction.TransactionTable cannot be cast to org.infinispan.transaction.xa.XaTransactionTable
	at org.infinispan.transaction.xa.TransactionXaAdapter.<init>(TransactionXaAdapter.java:100)
	at org.infinispan.CacheImpl.getXAResource(CacheImpl.java:875)
	at org.infinispan.AbstractDelegatingAdvancedCache.getXAResource(AbstractDelegatingAdvancedCache.java:158)
	at org.jboss.as.clustering.infinispan.subsystem.CacheService$InfinispanXAResourceRecovery.getXAResources(CacheService.java:112)
	at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:503) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
	at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:159) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
{code}

The exception is reoccuring every ten seconds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira