[JBoss JIRA] (ISPN-4409) LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4409?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4409:
-----------------------------------------------
Sebastian Łaskawiec <slaskawi(a)redhat.com> changed the Status of [bug 1139633|https://bugzilla.redhat.com/show_bug.cgi?id=1139633] from MODIFIED to ON_QA
> LevelDBCacheStoreIT fails to initialise with com.arjuna.ats.arjuna.exceptions.FatalError
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-4409
> URL: https://issues.jboss.org/browse/ISPN-4409
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 7.0.0.Alpha5
>
>
> The LevelDBCacheStoreIT fails to start with an error resulting from initialising the server side cache marshaller. The way the cache manager is created is not correct. You might as well just use the same marshaller as for the client.
> Even if you really need a cache's marshaller, you should get it via an injected cache rather than initialising a cache from scratch.
> {code}com.arjuna.ats.arjuna.exceptions.FatalError: null
> at com.arjuna.ats.internal.jts.ORBManager.getPOA(ORBManager.java:96)
> at com.arjuna.ats.internal.jts.OTSImpleManager.<clinit>(OTSImpleManager.java:300)
> at com.arjuna.ats.internal.jta.transaction.jts.TransactionImple.getTransaction(TransactionImple.java:1146)
> at com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.getTransaction(TransactionManagerImple.java:69)
> at org.infinispan.cache.impl.CacheImpl.getOngoingTransaction(CacheImpl.java:1414)
> at org.infinispan.cache.impl.CacheImpl.getInvocationContextForRead(CacheImpl.java:592)
> at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:474)
> at org.infinispan.cache.impl.CacheImpl.keySet(CacheImpl.java:469)
> at org.infinispan.registry.impl.ClusterRegistryImpl.keys(ClusterRegistryImpl.java:81)
> at org.infinispan.query.remote.ProtobufMetadataManager.ensureInit(ProtobufMetadataManager.java:67)
> at org.infinispan.query.remote.ProtobufMetadataManager.getSerializationContext(ProtobufMetadataManager.java:132)
> at org.infinispan.query.remote.LifecycleManager.cacheStarting(LifecycleManager.java:114)
> at org.infinispan.factories.ComponentRegistry.notifyCacheStarting(ComponentRegistry.java:228)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:214)
> at org.infinispan.cache.impl.CacheImpl.start(CacheImpl.java:699)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:573)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:528)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:408)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:381)
> at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.getServerMarshaller(LevelDBCacheStoreIT.java:190)
> at org.infinispan.server.test.cs.leveldb.LevelDBCacheStoreIT.<clinit>(LevelDBCacheStoreIT.java:67)
> « Hide stacktrace{code}
> The fix gets past this particular error but it still shows this afterwards:
> {code}Caused by: javax.management.InstanceNotFoundException: jboss.infinispan:type=Server,name=HotRod,component=Transport{code}
> Tristan is working on this...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-4766) Cache can't start if coordinator leaves during join and joiner becomes the new coordinator
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-4766?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-4766:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Cache can't start if coordinator leaves during join and joiner becomes the new coordinator
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-4766
> URL: https://issues.jboss.org/browse/ISPN-4766
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 7.0.0.CR1
>
>
> When the joiner becomes the coordinator, it tries to recover the current cache topologies, but it receives just one expected member and no current topology. This causes a NPE in ClusterCacheStatus:
> {noformat}
> 22:51:49,547 ERROR (transport-thread-NodeB-p21124-t1:) [ClusterCacheStatus] ISPN000228: Failed to recover cache dist state after the current node became the coordinator
> java.lang.NullPointerException
> at org.infinispan.partionhandling.impl.PreferAvailabilityStrategy.onPartitionMerge(PreferAvailabilityStrategy.java:104)
> at org.infinispan.topology.ClusterCacheStatus.doMergePartitions(ClusterCacheStatus.java:452)
> at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:260)
> at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:180)
> at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener$1.run(ClusterTopologyManagerImpl.java:427)
> {noformat}
> The LocalTopologyManagerImpl waits a bit after receiving the SuspectException and tries again, but this time it receives a {{null}} initial topology, causing another NPE:
> {noformat}
> 22:51:51,319 DEBUG (testng-GlobalKeySetTaskTest:) [LocalTopologyManagerImpl] Error sending join request for cache dist to coordinator
> java.lang.NullPointerException
> at org.infinispan.topology.LocalTopologyManagerImpl.resetLocalTopologyBeforeRebalance(LocalTopologyManagerImpl.java:222)
> at org.infinispan.topology.LocalTopologyManagerImpl.handleTopologyUpdate(LocalTopologyManagerImpl.java:191)
> at org.infinispan.topology.LocalTopologyManagerImpl.join(LocalTopologyManagerImpl.java:105)
> at org.infinispan.statetransfer.StateTransferManagerImpl.start(StateTransferManagerImpl.java:108)
> {noformat}
> This keeps going on until the state transfer timeout expires.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months
[JBoss JIRA] (ISPN-3978) Updating to Infinispan 6.0 on JBoss AS 7.1.1
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/ISPN-3978?page=com.atlassian.jira.plugin.... ]
Paul Ferraro commented on ISPN-3978:
------------------------------------
Infinispan 6.0 is not binary compatible with 5.1.x, so none of the clustering services in AS7 will likely work.
> Updating to Infinispan 6.0 on JBoss AS 7.1.1
> --------------------------------------------
>
> Key: ISPN-3978
> URL: https://issues.jboss.org/browse/ISPN-3978
> Project: Infinispan
> Issue Type: Component Upgrade
> Components: Core
> Affects Versions: 6.0.0.Final
> Environment: Windows 7 FR, NetBeans 7.4, JBoss AS 7.1.1
> Reporter: Adriano Labate
> Assignee: Dan Berindei
> Priority: Minor
> Labels: infinispan, jboss-as7, update
>
> JBoss AS 7.1.1 is bundled with Infinispan 5.1.2.FINAL.
> On the page http://infinispan.org/download, there's a green button "AS 7 Modules" with description "Packaged modules for deploying in JBoss AS 7".
> I understand that this AS 7 module is for updating to Infinispan version 6.0.
> I downloaded and extracted the infinispan-as-modules-6.0.0.Final.zip file in the "\modules" folder. I didn't deleted anything, just copied the archive content into modules.
> Now when I run my application that uses the cache, I can read in my log file the following:
> {code}
> [org.infinispan.factories.GlobalComponentRegistry] ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
> {code}
> So I supposed something is wrong.
> Either the log file displays the wrong version, or my update operation was not sufficient for updating Infinispan to version 6.0 on AS 7.
> For information, in my application POM, I added dependency as below:
> {code:xml}
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-core</artifactId>
> <version>6.0.0.Final</version>
> <scope>provided</scope>
> </dependency>
> {code}
> After some basic tests, I can notice that I can query the cache and put data in it, and find data. So it seems to work. But with which version of Infinispan?
> Could anybody know how to correctly update Infinispan to 6.0? Or why the 5.1.2 version is mentioned in the log file instead of version 6.0?
> Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 2 months