[JBoss JIRA] (ISPN-3450) Jon plugin - failing RebuildIndex operation on [MassIndexer] component
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3450?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3450:
-----------------------------------------------
Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1002550|https://bugzilla.redhat.com/show_bug.cgi?id=1002550] from NEW to MODIFIED
> Jon plugin - failing RebuildIndex operation on [MassIndexer] component
> ----------------------------------------------------------------------
>
> Key: ISPN-3450
> URL: https://issues.jboss.org/browse/ISPN-3450
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Reporter: Tomas Sykora
> Assignee: Adrian Nistor
> Fix For: 7.0.0.CR2
>
>
> RebuildIndex operation on [MassIndexer] component is failing while issuing in JON with this error:
> java.lang.NullPointerException
> at org.infinispan.rhq.CacheComponent.invokeOperation(CacheComponent.java:157)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> I reused configuration from ISPN test suite + I was able to issue this operation successfully via jconsole tool. That's why I suspect that problems are somewhere in JON-ISPN interaction or plugin.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4843) org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4843?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4843:
-------------------------------
Assignee: (was: Dan Berindei)
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails randomly
> ---------------------------------------------------------------------------------------------------
>
> Key: ISPN-4843
> URL: https://issues.jboss.org/browse/ISPN-4843
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 5.2.10.Final
> Reporter: Michal Vinkler
> Labels: 5.2.x
>
> org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations fails, so far, I've seen it on Windows (seems random there) and on RHEL7 (seems consistent - every JDK).
> Error Message
> {code}
> Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> Stacktrace
> org.infinispan.CacheException: Unable to invoke method public void org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete() throws java.lang.InterruptedException on object of type StateTransferManagerImpl
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:886)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:657)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:646)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:549)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:217)
> at org.infinispan.CacheImpl.start(CacheImpl.java:582)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:686)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:545)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:518)
> at org.infinispan.manager.CacheManagerTest$4$1.call(CacheManagerTest.java:374)
> at org.infinispan.test.TestingUtil.withCacheManager(TestingUtil.java:1237)
> at org.infinispan.manager.CacheManagerTest$4.call(CacheManagerTest.java:370)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1252)
> at org.infinispan.manager.CacheManagerTest.testCacheManagerRestartReusingConfigurations(CacheManagerTest.java:356)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.infinispan.CacheException: Initial state transfer timed out for cache ___defaultcache on CacheManagerTest-NodeA-49570
> at org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete(StateTransferManagerImpl.java:216)
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203)
> ... 36 more
> ... Removed 19 stack frames
> {code}
> Unrelated to https://issues.jboss.org/browse/ISPN-3963.
> Jenkins job link:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/eap-6x-manu-infinisp...
> Downstream BZ was: https://bugzilla.redhat.com/show_bug.cgi?id=1102058
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4539) JPACacheStore is associating same objects to multiple EntityManagers
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4539?page=com.atlassian.jira.plugin.... ]
Radim Vansa updated ISPN-4539:
------------------------------
Assignee: (was: Radim Vansa)
> JPACacheStore is associating same objects to multiple EntityManagers
> --------------------------------------------------------------------
>
> Key: ISPN-4539
> URL: https://issues.jboss.org/browse/ISPN-4539
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Reporter: Sanne Grinovero
>
> An object instance can be managed by at most one EntityManager (at a time). The pattern used in the JPACacheStore's process method is illegal.
> The solution is to clear the primary EntityManager and pass the detached data to the second EntityManager.
> There is a comment about something similar being needed in MySQL when there is a single connection; I'd rather check to have multiple connections available to avoid deadlocks.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-4534) Allow storage of mapped graphs in JPACacheStore
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-4534?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-4534:
-----------------------------------
I don't understand what you're suggesting. Do the embedded types have to be in persistence.xml? Do I have to somehow register those types?
> Allow storage of mapped graphs in JPACacheStore
> -----------------------------------------------
>
> Key: ISPN-4534
> URL: https://issues.jboss.org/browse/ISPN-4534
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Reporter: Sanne Grinovero
>
> While we can't store relations among different entities stored in different Infinispan entries, it is possible that someone stores a single entry which has embedded types. That would map correctly to the database but all of the other types need to be known the the EntityManager too.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months