[JBoss JIRA] (ISPN-2543) org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer fails periodically on all environments
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2543?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2543:
-----------------------------------------------
Anna Manukyan <amanukya(a)redhat.com> made a comment on [bug 879545|https://bugzilla.redhat.com/show_bug.cgi?id=879545]
The error is the following:
Error Message
Unknown attribute 'NumberOfGlobalConnections'. Known attributes names are: [port, numberWorkerThreads, receiveBufferSize, totalBytesRead, numberOfGlobalConnections, idleTimeout, totalBytesWritten, hostName, numberOfLocalConnections, sendBufferSize, tpcNoDelay]
Stacktrace
javax.management.AttributeNotFoundException: Unknown attribute 'NumberOfGlobalConnections'. Known attributes names are: [port, numberWorkerThreads, receiveBufferSize, totalBytesRead, numberOfGlobalConnections, idleTimeout, totalBytesWritten, hostName, numberOfLocalConnections, sendBufferSize, tpcNoDelay]
at org.infinispan.jmx.ResourceDMBean.getAttribute(ResourceDMBean.java:201)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:668)
at org.infinispan.server.core.ConnectionStatsTests$.testGlobalConnections(ConnectionStatsTests.scala:68)
at org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer(MemcachedClusteredStatsTest.scala:61)
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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
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)
> org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer fails periodically on all environments
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2543
> URL: https://issues.jboss.org/browse/ISPN-2543
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.Beta4
> Reporter: Anna Manukyan
> Assignee: Tristan Tarrant
> Labels: testsuite_stability
>
> org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer test fails periodically on RHEL6_x86 and RHEL6_x86_64 - JDK7, IBM JDK7 & OpenJDK7. The test also fails on Windows 2008 64 bit with Oracle JDK 7.
> The exception is:
> {code}
> Error Message
> Unknown attribute 'NumberOfGlobalConnections'. Known attributes names are: [port, numberWorkerThreads, receiveBufferSize, totalBytesRead, numberOfGlobalConnections, idleTimeout, totalBytesWritten, hostName, numberOfLocalConnections, sendBufferSize, tpcNoDelay]
> Stacktrace
> javax.management.AttributeNotFoundException: Unknown attribute 'NumberOfGlobalConnections'. Known attributes names are: [port, numberWorkerThreads, receiveBufferSize, totalBytesRead, numberOfGlobalConnections, idleTimeout, totalBytesWritten, hostName, numberOfLocalConnections, sendBufferSize, tpcNoDelay]
> at org.infinispan.jmx.ResourceDMBean.getAttribute(ResourceDMBean.java:201)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:668)
> at org.infinispan.server.core.ConnectionStatsTests$.testGlobalConnections(ConnectionStatsTests.scala:68)
> at org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer(MemcachedClusteredStatsTest.scala:61)
> 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.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> 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)
> {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, 1 month
[JBoss JIRA] (ISPN-2605) single node cluster (local mode) can not start with IllegalStateException
by dex chen (JIRA)
dex chen created ISPN-2605:
------------------------------
Summary: single node cluster (local mode) can not start with IllegalStateException
Key: ISPN-2605
URL: https://issues.jboss.org/browse/ISPN-2605
Project: Infinispan
Issue Type: Bug
Components: Core API
Affects Versions: 5.1.4.FINAL
Reporter: dex chen
Assignee: Mircea Markus
I have a single one node cluster configured a cache with cluster mode set to "local", and have several instances with the similar configurations without problem. However, one of system just can not start up.
I made sure there is no duplicate names. Every time, I start the application and get the same error even after I change the cluster name in Infinispan.xml.
I am using Infinisapn 5.1.4.Final for this.
The jgroups channel better does not get started for "local" cluster.
=================
org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.remoting.transport.jgroups.JGroupsTransport.start() on object of type JGroupsTransport
at org.infinispan.factories.GlobalComponentRegistry.start(GlobalComponentRegistry.java:223)
at org.infinispan.manager.DefaultCacheManager.wireCache(DefaultCacheManager.java:684)
at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649)
at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:549)
....
Caused by: java.lang.IllegalStateException: cluster 'local_gw' is already connected to singleton transport: [dummy-1354557074615, dummy-1354557038904, dummy-1354557028675, dummy-1354557069508, dummy-1354557054249, dummy-1354557064426, dummy-1354557049152, dummy-1354557059345, dummy-1354557033791, dummy-1354557044023, local_gw]
at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:909)
at org.jgroups.JChannel.startStack(JChannel.java:841)
at org.jgroups.JChannel.connect(JChannel.java:277)
at org.jgroups.JChannel.connect(JChannel.java:261)
at org.infinispan.remoting.transport.jgroups.JGroupsTransport.startJGroupsChannelIfNeeded(JGroupsTransport.java:184)
... 21 more
--
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, 1 month
[JBoss JIRA] (ISPN-2604) When accessing a Transient entry on one node of a cluster, make sure all copies are touched to avoid expiration
by Ray Tsang (JIRA)
Ray Tsang created ISPN-2604:
-------------------------------
Summary: When accessing a Transient entry on one node of a cluster, make sure all copies are touched to avoid expiration
Key: ISPN-2604
URL: https://issues.jboss.org/browse/ISPN-2604
Project: Infinispan
Issue Type: Enhancement
Components: Distributed Cache
Reporter: Ray Tsang
Assignee: Mircea Markus
Following up on this topic, this is what I have setup:
2 nodes in cluster (either lib mode or remote) - node-1 and node-2
a cache setup as distributed, synchronous (dist_sync)
cache.put("key", "value", -1, TimeUnit.MILLISECONDS, 2000, TimeUnit.MILLISECONDS);
for (i = 0; i < 10; i++) {
sleep(1000) // sleep 1 second
cache.get("key");
}
Here is the weird thing, after a few gets, I'm starting to get null results. This doesn't occur when there is only 1 node in the cluster.
I'm suspecting that, w/ when accessing the data, it could be accessing 1 of the 2 nodes based on load balancing.
cache.get("key") -> node-1 // 1s
cache.get("key") -> node-1 // 2s
cache.get("key") -> node-1 // 3s
cache.get("key") -> node-2 // oops, this is already expired on node-2
It would be nice to be able to make sure when accessing an entry from one node, the entry copies on other nodes are also "touched".
--
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, 1 month
[JBoss JIRA] (ISPN-2603) Intermittent test failure: AsyncAPITest
by Mircea Markus (JIRA)
Mircea Markus created ISPN-2603:
-----------------------------------
Summary: Intermittent test failure: AsyncAPITest
Key: ISPN-2603
URL: https://issues.jboss.org/browse/ISPN-2603
Project: Infinispan
Issue Type: Feature Request
Affects Versions: 5.2.0.Beta5
Reporter: Mircea Markus
Assignee: Mircea Markus
Fix For: 5.2.0.Beta6
AsyncAPITest.testAsyncMethodWithLifespanAndMaxIdle has this logic:
{code:java}
// putIfAbsent lifespan only
f = c.putAsync("k", "v3");
assertNull(f.get());
f = c.putIfAbsentAsync("k", "v4", 1000, TimeUnit.MILLISECONDS);
markStartTime();
assert f != null;
assert !f.isCancelled();
assertEquals("v3", f.get()); //here's the problem!!
{code}
the test assumes that the first put(v3_ executes before the second one (v4) which is not correct.
--
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, 1 month
[JBoss JIRA] (ISPN-2602) Busy wait in BaseStateTransferManagerImpl#waitForStateTransferToStart
by Dennis Reed (JIRA)
Dennis Reed created ISPN-2602:
---------------------------------
Summary: Busy wait in BaseStateTransferManagerImpl#waitForStateTransferToStart
Key: ISPN-2602
URL: https://issues.jboss.org/browse/ISPN-2602
Project: Infinispan
Issue Type: Bug
Components: State transfer
Affects Versions: 5.1.4.FINAL
Reporter: Dennis Reed
Assignee: Mircea Markus
BaseStateTransferManagerImpl#waitForStateTransferToStart does a busy wait, sleeping for 10ms in between checking the condition, instead of synchronizing using condition variables (or the equivalent).
This can cause excessive CPU load if a lot of threads are waiting
(we have seen 300 threads waiting in this loop at once).
--
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, 1 month