[JBoss JIRA] (ISPN-4989) infinispan-transport thread name is undefined
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-4989?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-4989:
----------------------------------
Status: Open (was: New)
> infinispan-transport thread name is undefined
> ---------------------------------------------
>
> Key: ISPN-4989
> URL: https://issues.jboss.org/browse/ISPN-4989
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 7.0.1.Final
> Reporter: Takayoshi Kimura
> Assignee: Takayoshi Kimura
> Priority: Minor
>
> In stack trace, all infinispan-transport threads appear as "undefined".
> {noformat}
> "undefined" prio=10 tid=0x00007f536528e800 nid=0x7da waiting on condition [0x00007f534835b000]
> {noformat}
> We can add the {{thread-name-pattern="%G %f-%t"}} on the infinispan-transport thread factory.
> {noformat}
> %t - emit the per-factory thread sequence number
> %g - emit the global thread sequence number
> %f - emit the factory sequence number
> %i - emit the thread ID
> %G - emit the thread group name
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5009) Upgrade server base to WildFly 8.2
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-5009:
-------------------------------------
Summary: Upgrade server base to WildFly 8.2
Key: ISPN-5009
URL: https://issues.jboss.org/browse/ISPN-5009
Project: Infinispan
Issue Type: Component Upgrade
Components: Build process, Server
Affects Versions: 7.0.2.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 7.1.0.Final
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4855) IndexManager start failed
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4855?page=com.atlassian.jira.plugin.... ]
Radim Vansa closed ISPN-4855.
-----------------------------
Fix Version/s: 7.0.0.CR2
Resolution: Duplicate Issue
As the reported version was 7.0.0.CR1, ISPN-4807 was fixed in CR2 and shows similar symptoms, I am closing this as duplicate.
> IndexManager start failed
> -------------------------
>
> Key: ISPN-4855
> URL: https://issues.jboss.org/browse/ISPN-4855
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 7.0.0.CR1
> Reporter: Radim Vansa
> Fix For: 7.0.0.CR2
>
>
> I have experienced this exception that caused the cacheManager startup to fail:
> Note that this was in library mode, though hotrod client was on the classpath.
> {code}
> org.hibernate.search.exception.SearchException: HSEARCH000103: Unable to initialize IndexManager named 'org.infinispan.query.remote.indexing.ProtobufValueWrapper'
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:260)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:513)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManagers(IndexManagerHolder.java:482)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.buildEntityIndexBinding(IndexManagerHolder.java:91)
> at org.hibernate.search.spi.SearchFactoryBuilder.initDocumentBuilders(SearchFactoryBuilder.java:369)
> at org.hibernate.search.spi.SearchFactoryBuilder.buildNewSearchFactory(SearchFactoryBuilder.java:208)
> at org.hibernate.search.spi.SearchFactoryBuilder.buildSearchFactory(SearchFactoryBuilder.java:126)
> at org.infinispan.query.impl.LifecycleManager.getSearchFactory(LifecycleManager.java:261)
> at org.infinispan.query.impl.LifecycleManager.cacheStarting(LifecycleManager.java:103)
> 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:762)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:584)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:539)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:416)
> at org.radargun.service.InfinispanEmbeddedService.startCaches(InfinispanEmbeddedService.java:111)
> at org.radargun.service.Infinispan51EmbeddedService.startCaches(Infinispan51EmbeddedService.java:95)
> at org.radargun.service.InfinispanLifecycle.start(InfinispanLifecycle.java:45)
> at org.radargun.service.InfinispanKillableLifecycle.start(InfinispanKillableLifecycle.java:47)
> at org.radargun.stages.lifecycle.LifecycleHelper.start(LifecycleHelper.java:57)
> at org.radargun.stages.lifecycle.ServiceStartStage.executeOnSlave(ServiceStartStage.java:76)
> at org.radargun.SlaveBase.scenarioLoop(SlaveBase.java:84)
> at org.radargun.SlaveBase$ScenarioRunner.run(SlaveBase.java:140)
> Caused by: java.lang.NullPointerException
> at org.infinispan.lucene.readlocks.DistributedSegmentReadLocker.deleteOrReleaseReadLock(DistributedSegmentReadLocker.java:73)
> at org.infinispan.lucene.impl.DirectoryImplementor.deleteFile(DirectoryImplementor.java:65)
> at org.infinispan.lucene.impl.DirectoryLuceneV4.deleteFile(DirectoryLuceneV4.java:64)
> at org.apache.lucene.index.IndexFileDeleter.deleteFile(IndexFileDeleter.java:595)
> at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:249)
> at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:781)
> at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:146)
> at org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider.start(InfinispanDirectoryProvider.java:73)
> at org.hibernate.search.indexes.impl.DirectoryBasedIndexManager.initialize(DirectoryBasedIndexManager.java:90)
> at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:256)
> ... 22 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5008) 7.0.x missing cachestore-remote and extended-statistics modules
by Ion Savin (JIRA)
[ https://issues.jboss.org/browse/ISPN-5008?page=com.atlassian.jira.plugin.... ]
Ion Savin updated ISPN-5008:
----------------------------
Issue Type: Bug (was: Feature Request)
Description:
The distribution/package.xml script contains declaration for adding the two modules but they are not present in the package (7.0.0->7.0.2).
{noformat}
<module dir="${output.dir}" target="modules/infinispan-extended-statistics" module="extended-statistics" artifact="infinispan-extended-statistics" />
<module dir="${output.dir}" target="modules/persistence/remote" module="persistence/remote" artifact="infinispan-cachestore-remote" />
{noformat}
was:
The distribution/package.xml script
> 7.0.x missing cachestore-remote and extended-statistics modules
> ---------------------------------------------------------------
>
> Key: ISPN-5008
> URL: https://issues.jboss.org/browse/ISPN-5008
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.2.Final
> Reporter: Ion Savin
> Assignee: Ion Savin
>
> The distribution/package.xml script contains declaration for adding the two modules but they are not present in the package (7.0.0->7.0.2).
> {noformat}
> <module dir="${output.dir}" target="modules/infinispan-extended-statistics" module="extended-statistics" artifact="infinispan-extended-statistics" />
> <module dir="${output.dir}" target="modules/persistence/remote" module="persistence/remote" artifact="infinispan-cachestore-remote" />
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-5008) 7.0.x missing cachestore-remote and extended-statistics modules
by Ion Savin (JIRA)
[ https://issues.jboss.org/browse/ISPN-5008?page=com.atlassian.jira.plugin.... ]
Ion Savin updated ISPN-5008:
----------------------------
Status: Open (was: New)
> 7.0.x missing cachestore-remote and extended-statistics modules
> ---------------------------------------------------------------
>
> Key: ISPN-5008
> URL: https://issues.jboss.org/browse/ISPN-5008
> Project: Infinispan
> Issue Type: Bug
> Components: Build process
> Affects Versions: 7.0.2.Final
> Reporter: Ion Savin
> Assignee: Ion Savin
>
> The distribution/package.xml script contains declaration for adding the two modules but they are not present in the package (7.0.0->7.0.2).
> {noformat}
> <module dir="${output.dir}" target="modules/infinispan-extended-statistics" module="extended-statistics" artifact="infinispan-extended-statistics" />
> <module dir="${output.dir}" target="modules/persistence/remote" module="persistence/remote" artifact="infinispan-cachestore-remote" />
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months
[JBoss JIRA] (ISPN-4969) Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4969?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4969:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1163820|https://bugzilla.redhat.com/show_bug.cgi?id=1163820] from POST to MODIFIED
> Stopping a cache will stop all KeyAffinityServices created for other caches in the cache manager
> ------------------------------------------------------------------------------------------------
>
> Key: ISPN-4969
> URL: https://issues.jboss.org/browse/ISPN-4969
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.2.8.Final, 6.0.2.Final, 7.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Priority: Critical
> Fix For: 7.0.1.Final, 5.2.9.Final, 6.0.3.Final
>
>
> We've had several reports in the WildFly forums of application runtime failures following undeployment of a separate application.
> WF creates a cache instance for each web application within the same cache container. However, KeyAffinityServiceImpl registers a cache manager listener that calls stop() on a @CacheStoppedEvent. However, this event might be triggered by any cache, not necessarily the cache with to which the KeyAffinityService is associated.
> The KeyAffinityServiceImpl.handleCacheStopped(CacheStoppedEvent) should only call stop() if the event.getCacheName() equals the name of the cache to which the affinity service is associated.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 4 months