[JBoss JIRA] (ISPN-2304) Hot Rod client testsuite halts with a test dependency issue
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-2304:
--------------------------------------
Summary: Hot Rod client testsuite halts with a test dependency issue
Key: ISPN-2304
URL: https://issues.jboss.org/browse/ISPN-2304
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.2.0.Alpha3
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.Alpha4
{code}[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.2:test (default-test) on project infinispan-client-hotrod:
Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.12.2:test failed: java.lang.reflect.InvocationTargetException; nested exception is java.lang.reflect.InvocationTargetException: null:
[ERROR] org.infinispan.client.hotrod.CSAIntegrationTest.testCorrectSetup() is not allowed to depend on public void org.infinispan.client.hotrod.CSAIntegrationTest.testHashInfoRetrieved() throws java.lang.InterruptedException{code}
--
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
12 years, 3 months
[JBoss JIRA] (ISPN-2288) Do not register the RecoveryManager MBean if recovery is not enabled
by Manik Surtani (JIRA)
Manik Surtani created ISPN-2288:
-----------------------------------
Summary: Do not register the RecoveryManager MBean if recovery is not enabled
Key: ISPN-2288
URL: https://issues.jboss.org/browse/ISPN-2288
Project: Infinispan
Issue Type: Bug
Components: JMX, reporting and management, Transactions
Affects Versions: 5.1.7.Final
Reporter: Manik Surtani
Assignee: Mircea Markus
Priority: Minor
Fix For: 5.2.0.Alpha4, 5.2.0.Final
The RecoveryManager MBean is *always* registered, even in a non-transactional cache. Naturally, any operations on this MBean fail in this case, so it doesn't cause any problems per-se, but it still pollutes the JMX console.
--
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
12 years, 3 months
[JBoss JIRA] (ISPN-2256) Cache creation is serialized
by Mircea Markus (JIRA)
Mircea Markus created ISPN-2256:
-----------------------------------
Summary: Cache creation is serialized
Key: ISPN-2256
URL: https://issues.jboss.org/browse/ISPN-2256
Project: Infinispan
Issue Type: Feature Request
Affects Versions: 5.2.0.Alpha3
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Alpha4, 5.2.0.Final
There is a synchronisation code in DCM which serialisez cache creation. This was added together with ISPN-1051 but can be further optimised to only serialize the access to GlobalComponentRegistry which is the concurrent bit.
--
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
12 years, 3 months
[JBoss JIRA] (ISPN-2283) Cache cannot shut down when disconnected
by Radim Vansa (JIRA)
Radim Vansa created ISPN-2283:
---------------------------------
Summary: Cache cannot shut down when disconnected
Key: ISPN-2283
URL: https://issues.jboss.org/browse/ISPN-2283
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.1.7.Final
Reporter: Radim Vansa
Assignee: Mircea Markus
When the DISCARD protocol is set to discard all messages and then the cache is shut down using cacheManager.stop() an infinite loop is entered throwing these exceptions:
{code}
09:59:23,538 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) Installing new view CacheView{viewId=11, members=[rvansa-31823]} for cache x
09:59:23,539 ERROR [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) ISPN000172: Failed to prepare view CacheView{viewId=11, members=[rvansa-31823]} for cache x, rolling back to view CacheView{viewId=10, members=[rvansa-12248, rvansa-31823, rvansa-2915, rvansa-56921]}
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: x: Received cache view prepare request after the local node has already shut down
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262)
at java.util.concurrent.FutureTask.get(FutureTask.java:119)
at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterPrepareView(CacheViewsManagerImpl.java:323)
at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterInstallView(CacheViewsManagerImpl.java:250)
at org.infinispan.cacheviews.CacheViewsManagerImpl$ViewInstallationTask.call(CacheViewsManagerImpl.java:894)
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)
Caused by: java.lang.IllegalStateException: x: Received cache view prepare request after the local node has already shut down
at org.infinispan.cacheviews.CacheViewsManagerImpl.handlePrepareView(CacheViewsManagerImpl.java:494)
at org.infinispan.cacheviews.CacheViewsManagerImpl$3.call(CacheViewsManagerImpl.java:314)
... 5 more
09:59:23,540 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) x: Rolling back to cache view 10, new view id is 12
09:59:23,540 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) Rolled back to view CacheView{viewId=10, members=[rvansa-12248, rvansa-31823, rvansa-2915, rvansa-56921]} for cache x
09:59:24,538 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) Installing new view CacheView{viewId=13, members=[rvansa-31823]} for cache x
09:59:24,539 ERROR [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) ISPN000172: Failed to prepare view CacheView{viewId=13, members=[rvansa-31823]} for cache x, rolling back to view CacheView{viewId=12, members=[rvansa-12248, rvansa-31823, rvansa-2915, rvansa-56921]}
java.util.concurrent.ExecutionException: java.lang.IllegalStateException: x: Received cache view prepare request after the local node has already shut down
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:262)
at java.util.concurrent.FutureTask.get(FutureTask.java:119)
at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterPrepareView(CacheViewsManagerImpl.java:323)
at org.infinispan.cacheviews.CacheViewsManagerImpl.clusterInstallView(CacheViewsManagerImpl.java:250)
at org.infinispan.cacheviews.CacheViewsManagerImpl$ViewInstallationTask.call(CacheViewsManagerImpl.java:894)
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)
Caused by: java.lang.IllegalStateException: x: Received cache view prepare request after the local node has already shut down
at org.infinispan.cacheviews.CacheViewsManagerImpl.handlePrepareView(CacheViewsManagerImpl.java:494)
at org.infinispan.cacheviews.CacheViewsManagerImpl$3.call(CacheViewsManagerImpl.java:314)
... 5 more
09:59:24,539 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) x: Rolling back to cache view 12, new view id is 14
09:59:24,540 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-1,rvansa-31823) Rolled back to view CacheView{viewId=12, members=[rvansa-12248, rvansa-31823, rvansa-2915, rvansa-56921]} for cache x
{code}
--
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
12 years, 3 months
[JBoss JIRA] (ISPN-2262) Unresponsiveness in resilience test
by Radim Vansa (JIRA)
Radim Vansa created ISPN-2262:
---------------------------------
Summary: Unresponsiveness in resilience test
Key: ISPN-2262
URL: https://issues.jboss.org/browse/ISPN-2262
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 5.2.0.Alpha3
Reporter: Radim Vansa
Assignee: Mircea Markus
Priority: Critical
Basic resilience scenario in library mode:
* spawn 4 nodes
* kill one node (kill = insert DISCARD protocol and then call CacheManger.stop())
* start one node
We use RadarGun (with some modifications) for this test.
When the node is started again the system looses some messages as some timeouts are triggered (and the RadarGun stage acknowledgement is missing as well) and later put/get requests cause exceptions.
The trace logs are too big, therefore, these are published on http://dl.dropbox.com/u/103079234/serverlogs_trace.zip
Note that the test was shutdown manually.
--
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
12 years, 3 months
[JBoss JIRA] (ISPN-2186) Coordinator tries to install new view after graceful shutdown
by Michal Linhard (JIRA)
Michal Linhard created ISPN-2186:
------------------------------------
Summary: Coordinator tries to install new view after graceful shutdown
Key: ISPN-2186
URL: https://issues.jboss.org/browse/ISPN-2186
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.1.6.FINAL (JDG)
Reporter: Michal Linhard
Assignee: Manik Surtani
Priority: Minor
This is not a serious problem, because so far the only thing I discoverd it causes is a superfluous debug level log message.
This happened in elasticity tests with radargun,
In these tests we go from 4 nodes to 8 and back to 4.
See views installed:
http://www.qa.jboss.com/~mlinhard/hyperion2/run218-radargun-08-elasticity...
In this case, each time the node is shutdown it is the coordinator (I'm not sure whether this is accident or coordinators are picked by their seniority in the cluster)
The shutdown is made gracefully via DefaultCacheManager.stop() and each time this happens I can see an attempt of CacheViewsManagerImpl to install a new view - which doesn't complete because the coordinator shuts down few moments later and the new view is really established by a new coordinator.
Log from slave on node0003:
{code}
02:37:32,737 INFO [org.radargun.stages.KillStage] (pool-1-thread-1) Tearing down cache wrapper.
02:38:02,752 WARN [org.infinispan.transaction.TransactionTable] (pool-1-thread-1) ISPN000100: Stopping, but there are 9 local transactions and 0 remote transactions that did not finish in time.
02:38:02,755 DEBUG [org.infinispan.cacheviews.CacheViewsManagerImpl] (CacheViewInstaller-3,hyperion1098-55173) Installing new view CacheView{viewId=9, members=[hyperion1099-41789, hyperion1097-42149, hyperion1100-42888, hyperion1102-1099, hyperion1101-56019, hyperion1103-38655, hyperion1096-46484]} for cache x
02:38:04,279 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-1-thread-1) ISPN000080: Disconnecting and closing JGroups Channel
02:38:04,641 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (pool-1-thread-1) ISPN000082: Stopping the RpcDispatcher
02:38:04,816 INFO [org.radargun.Slave] (pool-1-thread-1) Finished stage: KillStage {tearDown=true, productName='jdg60', useSmartClassLoading=true, slaveIndex=0, activeSlavesCount=8, totalSlavesCount=8, slaves=[0]}
02:38:04,817 INFO [org.radargun.Slave] (main) Ack successfully sent to the master
{code}
--
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
12 years, 3 months
[JBoss JIRA] (ISPN-2277) Remove explicit JGroups dependency from GloabelConfigurationBuilder
by Thomas Fromm (JIRA)
Thomas Fromm created ISPN-2277:
----------------------------------
Summary: Remove explicit JGroups dependency from GloabelConfigurationBuilder
Key: ISPN-2277
URL: https://issues.jboss.org/browse/ISPN-2277
Project: Infinispan
Issue Type: Enhancement
Components: Configuration
Affects Versions: 5.1.6.FINAL
Reporter: Thomas Fromm
Assignee: Mircea Markus
During fix of MODE-1621 we've noticed the requirement of JGroups.
Maybe a working solution is replacing the TransportConfigurationBuilder.DEFAULT_TRANSPORT with class name instead of class, so its only used when default transport is needed.
--
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
12 years, 3 months