[JBoss JIRA] (ISPN-2532) Sporadical IllegalStateException on startup
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2532?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2532:
--------------------------------
Assignee: Dan Berindei (was: Mircea Markus)
> Sporadical IllegalStateException on startup
> -------------------------------------------
>
> Key: ISPN-2532
> URL: https://issues.jboss.org/browse/ISPN-2532
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.2.0.Beta4
> Reporter: Thomas Fromm
> Assignee: Dan Berindei
>
> Sporadically when starting a node inside cluster I get this exception and the node does node come up:
> Maybe component startup order problem? I do not have Debug Log, since it appears not often and ispn does not support changing trace level during runtime ;-)
> org.infinispan.CacheException: Unable to invoke method public void org.infinispan.loaders.CacheLoaderManagerImpl.preload() on object of type CacheLoaderManagerImpl
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:883)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:654)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:643)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:546)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:199)
> at org.infinispan.CacheImpl.start(CacheImpl.java:520)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:690)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:653)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:549)
> at org.infinispan.manager.DefaultCacheManager.startCache(DefaultCacheManager.java:906)
> at com.inubit.ibis.server.cache.ispn.ISPNCacheManagerImpl.startCache(ISPNCacheManagerImpl.java:242)
> at com.inubit.ibis.server.cache.ispn.ISPNCacheManagerImpl.startCaches(ISPNCacheManagerImpl.java:216)
> at com.inubit.ibis.server.datafacade.cache.CacheDataFacade.initialize(CacheDataFacade.java:62)
> at com.inubit.ibis.server.IBISRuntime.startup(IBISRuntime.java:108)
> at com.inubit.ibis.servlets.IBISServletContextListener.contextInitialized(IBISServletContextListener.java:28)
> at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4791)
> at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5285)
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
> at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
> at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:618)
> at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1100)
> at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1618)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> 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: Can only check if the local node is the first to join after joining
> at org.infinispan.statetransfer.StateTransferManagerImpl.isLocalNodeFirst(StateTransferManagerImpl.java:250)
> at org.infinispan.loaders.CacheLoaderManagerImpl.preload(CacheLoaderManagerImpl.java:222)
> at sun.reflect.GeneratedMethodAccessor74.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203)
> ... 29 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
13 years, 2 months
[JBoss JIRA] (ISPN-2804) Memory Leak: TransactionTable never cleans up complete transactions
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2804?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2804:
--------------------------------
Priority: Blocker (was: Major)
> Memory Leak: TransactionTable never cleans up complete transactions
> -------------------------------------------------------------------
>
> Key: ISPN-2804
> URL: https://issues.jboss.org/browse/ISPN-2804
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 5.2.0.Final
> Reporter: Erik Salter
> Assignee: Mircea Markus
> Priority: Blocker
> Fix For: 5.2.1, 5.3.0.Alpha1
>
>
> When a transaction commits, we mark it as completed in markCompletedTransaction(). The issue is this map is never cleaned up -- there is no call to cleanupCompletedTransactions().
> (Was this supposed to replace the StaleTransactionCleanupService?)
> So the transaction (and address and UUID object) leak for every transaction, until the node OOMs.
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2756) Enabling/disabling RpcManager statistics via JMX doesn't work
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2756?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-2756:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=906236, https://bugzilla.redhat.com/show_bug.cgi?id=908700 (was: https://bugzilla.redhat.com/show_bug.cgi?id=906236)
> Enabling/disabling RpcManager statistics via JMX doesn't work
> -------------------------------------------------------------
>
> Key: ISPN-2756
> URL: https://issues.jboss.org/browse/ISPN-2756
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 5.2.0.CR2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 5.2.0.Final
>
>
> The test RpcManagerMBeanTest.testEnableJmxStats tries to write to the "StatisticsEnabled" attribute but fails. The operation doesn't throw an exception, but it does log this WARN message:
> {noformat}
> 10:43:42,079 WARN (testng-RpcManagerMBeanTest:) [ResourceDMBean] ISPN000043: Exception while writing value for attribute statisticsEnabled
> java.lang.NullPointerException
> at org.infinispan.jmx.ResourceDMBean$InvokableSetterBasedMBeanAttributeInfo.invoke(ResourceDMBean.java:391)
> at org.infinispan.jmx.ResourceDMBean.setNamedAttribute(ResourceDMBean.java:325)
> at org.infinispan.jmx.ResourceDMBean.setAttribute(ResourceDMBean.java:212)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:746)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:729)
> at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:134)
> {noformat}
> Because statistics are still enabled, the test then fails with an assertion error:
> {noformat}
> 10:43:42,464 ERROR (testng-RpcManagerMBeanTest:) [UnitTestTestNGListener] Test testEnableJmxStats(org.infinispan.jmx.RpcManagerMBeanTest) failed.
> java.lang.AssertionError: expected [-1] but found [1]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertEquals(Assert.java:123)
> at org.testng.Assert.assertEquals(Assert.java:165)
> at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:138)
> {noformat}
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2756) Enabling/disabling RpcManager statistics via JMX doesn't work
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2756?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2756:
-----------------------------------------------
Richard Janík <rjanik(a)redhat.com> made a comment on [bug 908700|https://bugzilla.redhat.com/show_bug.cgi?id=908700]
+++ This bug was initially created as a clone of Bug #906236 +++
Hi,
the test org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats always fails on all environments for ER10 build.
This bug is completely the same as the ISPN-2756 (in JIRA), but I run the tests for infinispan latest version and it works without failures, so issue refers only to JDG 6.1.0.ER10 build.
The log is:
2013-01-30 14:32:24,214 WARN [ResourceDMBean] (testng-RpcManagerMBeanTest) ISPN000043: Exception while writing value for attribute statisticsEnabled
java.lang.NullPointerException
at org.infinispan.jmx.ResourceDMBean$InvokableSetterBasedMBeanAttributeInfo.invoke(ResourceDMBean.java:391)
at org.infinispan.jmx.ResourceDMBean.setNamedAttribute(ResourceDMBean.java:325)
at org.infinispan.jmx.ResourceDMBean.setAttribute(ResourceDMBean.java:212)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:746)
at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:729)
at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:134)
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)
[testng-RpcManagerMBeanTest] Test testEnableJmxStats(org.infinispan.jmx.RpcManagerMBeanTest) failed.
2013-01-30 14:32:24,217 ERROR [UnitTestTestNGListener] (testng-RpcManagerMBeanTest) Test testEnableJmxStats(org.infinispan.jmx.RpcManagerMBeanTest) failed.
java.lang.AssertionError: expected [-1] but found [1]
at org.testng.Assert.fail(Assert.java:89)
at org.testng.Assert.failNotEquals(Assert.java:489)
at org.testng.Assert.assertEquals(Assert.java:118)
at org.testng.Assert.assertEquals(Assert.java:160)
at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:138)
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)
Test suite progress: tests succeeded: 216, failed: 1, skipped: 0.
--- Additional comment from JBoss JIRA Server on 2013-01-31 06:17:39 EST ---
Adrian Nistor <anistor(a)redhat.com> made a comment on jira ISPN-2756
[~amanukyan] ER10 is based on 5.2.CR3 and this bug is fixed only in (the yet unreleased) 5.2.Final.
> Enabling/disabling RpcManager statistics via JMX doesn't work
> -------------------------------------------------------------
>
> Key: ISPN-2756
> URL: https://issues.jboss.org/browse/ISPN-2756
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 5.2.0.CR2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 5.2.0.Final
>
>
> The test RpcManagerMBeanTest.testEnableJmxStats tries to write to the "StatisticsEnabled" attribute but fails. The operation doesn't throw an exception, but it does log this WARN message:
> {noformat}
> 10:43:42,079 WARN (testng-RpcManagerMBeanTest:) [ResourceDMBean] ISPN000043: Exception while writing value for attribute statisticsEnabled
> java.lang.NullPointerException
> at org.infinispan.jmx.ResourceDMBean$InvokableSetterBasedMBeanAttributeInfo.invoke(ResourceDMBean.java:391)
> at org.infinispan.jmx.ResourceDMBean.setNamedAttribute(ResourceDMBean.java:325)
> at org.infinispan.jmx.ResourceDMBean.setAttribute(ResourceDMBean.java:212)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.setAttribute(DefaultMBeanServerInterceptor.java:746)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.setAttribute(JmxMBeanServer.java:729)
> at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:134)
> {noformat}
> Because statistics are still enabled, the test then fails with an assertion error:
> {noformat}
> 10:43:42,464 ERROR (testng-RpcManagerMBeanTest:) [UnitTestTestNGListener] Test testEnableJmxStats(org.infinispan.jmx.RpcManagerMBeanTest) failed.
> java.lang.AssertionError: expected [-1] but found [1]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertEquals(Assert.java:123)
> at org.testng.Assert.assertEquals(Assert.java:165)
> at org.infinispan.jmx.RpcManagerMBeanTest.testEnableJmxStats(RpcManagerMBeanTest.java:138)
> {noformat}
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2805) Disable UNICAST / UNICAST2 connection reaping
by Dan Berindei (JIRA)
Dan Berindei created ISPN-2805:
----------------------------------
Summary: Disable UNICAST / UNICAST2 connection reaping
Key: ISPN-2805
URL: https://issues.jboss.org/browse/ISPN-2805
Project: Infinispan
Issue Type: Task
Components: Configuration
Affects Versions: 5.2.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Priority: Critical
Fix For: 5.2.1, 5.3.0.Alpha1
According to JGRP-1586, connection reaping may lead to message loss in UNICAST/UNICAST2.
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2804) Memory Leak: TransactionTable never cleans up complete transactions
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2804?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-2804:
--------------------------------
Fix Version/s: 5.2.1
5.3.0.Alpha1
> Memory Leak: TransactionTable never cleans up complete transactions
> -------------------------------------------------------------------
>
> Key: ISPN-2804
> URL: https://issues.jboss.org/browse/ISPN-2804
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 5.2.0.Final
> Reporter: Erik Salter
> Assignee: Mircea Markus
> Fix For: 5.2.1, 5.3.0.Alpha1
>
>
> When a transaction commits, we mark it as completed in markCompletedTransaction(). The issue is this map is never cleaned up -- there is no call to cleanupCompletedTransactions().
> (Was this supposed to replace the StaleTransactionCleanupService?)
> So the transaction (and address and UUID object) leak for every transaction, until the node OOMs.
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2804) Memory Leak: TransactionTable never cleans up complete transactions
by Erik Salter (JIRA)
Erik Salter created ISPN-2804:
---------------------------------
Summary: Memory Leak: TransactionTable never cleans up complete transactions
Key: ISPN-2804
URL: https://issues.jboss.org/browse/ISPN-2804
Project: Infinispan
Issue Type: Bug
Components: Transactions
Affects Versions: 5.2.0.Final
Reporter: Erik Salter
Assignee: Mircea Markus
When a transaction commits, we mark it as completed in markCompletedTransaction(). The issue is this map is never cleaned up -- there is no call to cleanupCompletedTransactions().
(Was this supposed to replace the StaleTransactionCleanupService?)
So the transaction (and address and UUID object) leak for every transaction, until the node OOMs.
--
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
13 years, 2 months
[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-2658:
--------------------------------
Attachment: MarshalledValueTest.log
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2658
> URL: https://issues.jboss.org/browse/ISPN-2658
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.Beta6
> Reporter: Anna Manukyan
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 5.2.0.CR1
>
> Attachments: MarshalledValueTest.log, testModificationsOnSameCustomKey-2.log
>
>
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7).
> The error message is:
> {code}
> Error Message
> Serialization count: expected 4 but was 5
> Stacktrace
> java.lang.AssertionError: Serialization count: expected 4 but was 5
> at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135)
> at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452)
> 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
13 years, 2 months
[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ]
Adrian Nistor edited comment on ISPN-2658 at 2/6/13 1:06 PM:
-------------------------------------------------------------
Re-occurred. See attached MarshalledValueTest.log
was (Author: anistor):
Re-occurred. Will add logs soon.
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2658
> URL: https://issues.jboss.org/browse/ISPN-2658
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.Beta6
> Reporter: Anna Manukyan
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 5.2.0.CR1
>
> Attachments: MarshalledValueTest.log, testModificationsOnSameCustomKey-2.log
>
>
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7).
> The error message is:
> {code}
> Error Message
> Serialization count: expected 4 but was 5
> Stacktrace
> java.lang.AssertionError: Serialization count: expected 4 but was 5
> at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135)
> at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452)
> 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
13 years, 2 months
[JBoss JIRA] (ISPN-2658) org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-2658?page=com.atlassian.jira.plugin.... ]
Adrian Nistor commented on ISPN-2658:
-------------------------------------
I stumbled upon this failure again on 5.2.0.final:
{noformat}
Tests run: 2541, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 401.202 sec <<< FAILURE!
testModificationsOnSameCustomKey(org.infinispan.marshall.MarshalledValueTest) Time elapsed: 0.01 sec <<< FAILURE!
java.lang.AssertionError: Serialization count: expected 5 but was 4
at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135)
at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:458)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
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:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
{noformat}
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey fails constantly on all environments
> ------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2658
> URL: https://issues.jboss.org/browse/ISPN-2658
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.Beta6
> Reporter: Anna Manukyan
> Assignee: Galder Zamarreño
> Labels: testsuite_stability
> Fix For: 5.2.0.CR1
>
> Attachments: testModificationsOnSameCustomKey-2.log
>
>
> org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey test fails on all environments (RHEL, Windows, Solaris - JDK7, Open JDK7, IBM JDK7).
> The error message is:
> {code}
> Error Message
> Serialization count: expected 4 but was 5
> Stacktrace
> java.lang.AssertionError: Serialization count: expected 4 but was 5
> at org.infinispan.marshall.MarshalledValueTest.assertSerializationCounts(MarshalledValueTest.java:135)
> at org.infinispan.marshall.MarshalledValueTest.testModificationsOnSameCustomKey(MarshalledValueTest.java:452)
> 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
13 years, 2 months