[JBoss JIRA] (ISPN-8290) Mixed "capacity-factor" and "capacity" in org.infinispan.configuration.parsing.Attribute
by Michael Pasternak (JIRA)
[ https://issues.jboss.org/browse/ISPN-8290?page=com.atlassian.jira.plugin.... ]
Michael Pasternak updated ISPN-8290:
------------------------------------
Description:
1. According to documentation in 9.1 and XSD schema should be two separate attributes in
type="tns:distributed-cache" "capacity" and "capacity-factor", however
org.infinispan.configuration.parsing.Attribute enum using "capacity" name for CAPACITY_FACTOR enum entry, e.g CAPACITY_FACTOR("capacity"), what is causing parsing error when "capacity-factor" is used in "distributed-cache" configuration
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,96]
Message: Unexpected attribute 'capacity-factor' encountered
2. org.infinispan.configuration.parsing.Parser#parseDistributedCache:2106 uses CAPACITY_FACTOR (which was collected from "capacity" attribute) to map to builder clustering().hash().capacityFactor
this is misleading and one that not familiar with this bug, won't be able to set "capacity-factor" in cache configuration:
<distributed-cache capacity-factor="...">
...
</distributed-cache>
was:
1. According to documentation in 9.1 and XSD schema should be two separate attributes in
type="tns:distributed-cache" "capacity" and "capacity-factor", however
org.infinispan.configuration.parsing.Attribute enum using "capacity" name for CAPACITY_FACTOR enum entry, e.g CAPACITY_FACTOR("capacity"), what is causing parsing error when "capacity-factor" is used in "distributed-cache" configuration
javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,96]
Message: Unexpected attribute 'capacity-factor' encountered
2. org.infinispan.configuration.parsing.Parser#parseDistributedCache:2106 uses CAPACITY_FACTOR (which was collected from "capacity" attribute) to map to
builder.clustering().hash().capacityFactor
this is misleading and one that not familiar with this bug, won't be able to set "capacity-factor"
in cache configuration:
<distributed-cache capacity-factor="...">
...
</distributed-cache>
> Mixed "capacity-factor" and "capacity" in org.infinispan.configuration.parsing.Attribute
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-8290
> URL: https://issues.jboss.org/browse/ISPN-8290
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 9.1.0.Final
> Reporter: Michael Pasternak
>
> 1. According to documentation in 9.1 and XSD schema should be two separate attributes in
> type="tns:distributed-cache" "capacity" and "capacity-factor", however
> org.infinispan.configuration.parsing.Attribute enum using "capacity" name for CAPACITY_FACTOR enum entry, e.g CAPACITY_FACTOR("capacity"), what is causing parsing error when "capacity-factor" is used in "distributed-cache" configuration
> javax.xml.stream.XMLStreamException: ParseError at [row,col]:[14,96]
> Message: Unexpected attribute 'capacity-factor' encountered
> 2. org.infinispan.configuration.parsing.Parser#parseDistributedCache:2106 uses CAPACITY_FACTOR (which was collected from "capacity" attribute) to map to builder clustering().hash().capacityFactor
> this is misleading and one that not familiar with this bug, won't be able to set "capacity-factor" in cache configuration:
> <distributed-cache capacity-factor="...">
> ...
> </distributed-cache>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-8291) JmxManagementIT.testMemCachedConnectionCount and testHotRodConnectionCount fail randomly
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8291?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8291:
----------------------------------
Summary: JmxManagementIT.testMemCachedConnectionCount and testHotRodConnectionCount fail randomly (was: JmxManagementIT.testMemCachedConnectionCount fails randomly)
> JmxManagementIT.testMemCachedConnectionCount and testHotRodConnectionCount fail randomly
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-8291
> URL: https://issues.jboss.org/browse/ISPN-8291
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.1.0.Final
> Reporter: Tristan Tarrant
> Labels: testsuite_stability
>
> Error Message
> expected:<3> but was:<2>
> Stacktrace
> java.lang.AssertionError: expected:<3> but was:<2>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:555)
> at org.junit.Assert.assertEquals(Assert.java:542)
> at org.infinispan.server.test.jmx.management.JmxManagementIT.testMemCachedConnectionCount(JmxManagementIT.java:142)
> Standard Output
> [TestSuiteProgress] Test succeeded: JmxManagementIT.testMemcachedServerAttributes
> [TestSuiteProgress] Tests succeeded: 163, failed: 0, skipped: 5
> [TestSuiteProgress] Test starting: JmxManagementIT.testMemCachedConnectionCount
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-8291) JmxManagementIT.testMemCachedConnectionCount fails randomly
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-8291:
-------------------------------------
Summary: JmxManagementIT.testMemCachedConnectionCount fails randomly
Key: ISPN-8291
URL: https://issues.jboss.org/browse/ISPN-8291
Project: Infinispan
Issue Type: Bug
Components: Test Suite - Server
Affects Versions: 9.1.0.Final
Reporter: Tristan Tarrant
Error Message
expected:<3> but was:<2>
Stacktrace
java.lang.AssertionError: expected:<3> but was:<2>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:555)
at org.junit.Assert.assertEquals(Assert.java:542)
at org.infinispan.server.test.jmx.management.JmxManagementIT.testMemCachedConnectionCount(JmxManagementIT.java:142)
Standard Output
[TestSuiteProgress] Test succeeded: JmxManagementIT.testMemcachedServerAttributes
[TestSuiteProgress] Tests succeeded: 163, failed: 0, skipped: 5
[TestSuiteProgress] Test starting: JmxManagementIT.testMemCachedConnectionCount
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-7869) modules for EAP does not include all necessary indexes
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-7869?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec resolved ISPN-7869.
---------------------------------------
Resolution: Won't Fix
As I explained in JDG-998 and in [Pull Request|https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/164], this change is not needed. See this quotation:
{quote}
Previously, the CDI Quickstart Guide instructions required the JBoss Data Grid EAP modules be bundled with the application. However, the quickstart did not work in this case. The quickstart now specifies the JDG EAP modules be installed directly on the server, which allows the quickstart to work as expected.
{quote}
> modules for EAP does not include all necessary indexes
> ------------------------------------------------------
>
> Key: ISPN-7869
> URL: https://issues.jboss.org/browse/ISPN-7869
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Reporter: Wolf-Dieter Fink
> Assignee: Sebastian Łaskawiec
>
> To use JCache with CDI annotations together with the WildFly modules it is necessary to have a jandex.idx index file within the jar files.
> This is needed for Wildfly, otherwise no annotations are found if the dependency (MANIFEST or jboss-deployment-structure.xml) is declared with annotations=true
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-7869) modules for EAP does not include all necessary indexes
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-7869?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-7869:
--------------------------------------
Comment: was deleted
(was: As I explained in JDG-998 and in [Pull Request|https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/164], this change is not needed. See this quotation:
{quote}
Previously, the CDI Quickstart Guide instructions required the JBoss Data Grid EAP modules be bundled with the application. However, the quickstart did not work in this case. The quickstart now specifies the JDG EAP modules be installed directly on the server, which allows the quickstart to work as expected.
{quote})
> modules for EAP does not include all necessary indexes
> ------------------------------------------------------
>
> Key: ISPN-7869
> URL: https://issues.jboss.org/browse/ISPN-7869
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Reporter: Wolf-Dieter Fink
> Assignee: Sebastian Łaskawiec
>
> To use JCache with CDI annotations together with the WildFly modules it is necessary to have a jandex.idx index file within the jar files.
> This is needed for Wildfly, otherwise no annotations are found if the dependency (MANIFEST or jboss-deployment-structure.xml) is declared with annotations=true
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-7869) modules for EAP does not include all necessary indexes
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-7869?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec commented on ISPN-7869:
-------------------------------------------
As I explained in JDG-998 and in [Pull Request|https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/164], this change is not needed. See this quotation:
{quote}
Previously, the CDI Quickstart Guide instructions required the JBoss Data Grid EAP modules be bundled with the application. However, the quickstart did not work in this case. The quickstart now specifies the JDG EAP modules be installed directly on the server, which allows the quickstart to work as expected.
{quote}
> modules for EAP does not include all necessary indexes
> ------------------------------------------------------
>
> Key: ISPN-7869
> URL: https://issues.jboss.org/browse/ISPN-7869
> Project: Infinispan
> Issue Type: Bug
> Components: WildFly modules
> Reporter: Wolf-Dieter Fink
> Assignee: Sebastian Łaskawiec
>
> To use JCache with CDI annotations together with the WildFly modules it is necessary to have a jandex.idx index file within the jar files.
> This is needed for Wildfly, otherwise no annotations are found if the dependency (MANIFEST or jboss-deployment-structure.xml) is declared with annotations=true
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-8155) SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8155?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8155:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: (was: 9.2.0.Final)
Resolution: Done
> SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
> ---------------------------------------------------------------------------------
>
> Key: ISPN-8155
> URL: https://issues.jboss.org/browse/ISPN-8155
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.1.0.Final
> Reporter: Gustavo Fernandes
> Assignee: William Burns
> Labels: testsuite_stability
> Fix For: 9.1.1.Final
>
>
> {noformat}
> testExecutorTriConsumerTimeoutException on SingleClusterExecutorTest{ local = true}(org.infinispan.manager.SingleClusterExecutorTest) Time elapsed: 1.049 sec <<< FAILURE!
> java.lang.AssertionError: Should have thrown an class java.util.concurrent.ExecutionException
> at org.infinispan.test.Exceptions.assertException(Exceptions.java:21)
> at org.infinispan.test.Exceptions.expectExecutionException(Exceptions.java:136)
> at org.infinispan.manager.AllClusterExecutorTest$17.call(AllClusterExecutorTest.java:390)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1474)
> at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:376)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-8280) RemoteStoreRawValuesTest.testStopStartDoesNotNukeValues fails randomly
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-8280?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8280:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: (was: 9.2.0.Final)
Resolution: Done
> RemoteStoreRawValuesTest.testStopStartDoesNotNukeValues fails randomly
> ----------------------------------------------------------------------
>
> Key: ISPN-8280
> URL: https://issues.jboss.org/browse/ISPN-8280
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores, Remote Protocols
> Affects Versions: 9.1.0.Final
> Reporter: Tristan Tarrant
> Assignee: William Burns
> Labels: testsuite_stability
> Fix For: 9.1.1.Final
>
>
> Error Message
> java.lang.NullPointerException
> Stacktrace
> org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=1132 returned server error (status=0x85): java.lang.NullPointerException
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:363)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:152)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:138)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:60)
> at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.sendKeyOperation(AbstractKeyOperation.java:51)
> at org.infinispan.client.hotrod.impl.operations.GetWithMetadataOperation.executeOperation(GetWithMetadataOperation.java:38)
> at org.infinispan.client.hotrod.impl.operations.GetWithMetadataOperation.executeOperation(GetWithMetadataOperation.java:24)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:56)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.getWithMetadata(RemoteCacheImpl.java:210)
> at org.infinispan.persistence.remote.RemoteStore.load(RemoteStore.java:125)
> at org.infinispan.persistence.BaseStoreTest.testStopStartDoesNotNukeValues(BaseStoreTest.java:355)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> ... Removed 16 stack frames
> The server log:
> java.lang.NullPointerException: null
> at org.infinispan.expiration.impl.ExpirationManagerImpl.lambda$handleInMemoryExpiration$0(ExpirationManagerImpl.java:135) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.container.DefaultDataContainer.lambda$compute$6(DefaultDataContainer.java:341) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at com.github.benmanes.caffeine.cache.BoundedLocalCache.lambda$remap$16(BoundedLocalCache.java:2043) ~[caffeine-2.4.0.jar:?]
> at java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1853) ~[?:1.8.0_141]
> at com.github.benmanes.caffeine.cache.BoundedLocalCache.remap(BoundedLocalCache.java:2038) ~[caffeine-2.4.0.jar:?]
> at com.github.benmanes.caffeine.cache.BoundedLocalCache.compute(BoundedLocalCache.java:1991) ~[caffeine-2.4.0.jar:?]
> at com.github.benmanes.caffeine.cache.LocalCache.compute(LocalCache.java:101) ~[caffeine-2.4.0.jar:?]
> at org.infinispan.container.DefaultDataContainer.compute(DefaultDataContainer.java:340) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.expiration.impl.ExpirationManagerImpl.handleInMemoryExpiration(ExpirationManagerImpl.java:134) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.container.DefaultDataContainer.get(DefaultDataContainer.java:203) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.container.EntryFactoryImpl.getFromContainerForRead(EntryFactoryImpl.java:193) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.container.EntryFactoryImpl.wrapEntryForReading(EntryFactoryImpl.java:69) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.impl.EntryWrappingInterceptor.visitDataReadCommand(EntryWrappingInterceptor.java:216) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.impl.EntryWrappingInterceptor.visitGetCacheEntryCommand(EntryWrappingInterceptor.java:211) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.commands.read.GetCacheEntryCommand.acceptVisitor(GetCacheEntryCommand.java:38) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:58) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.locking.NonTransactionalLockingInterceptor.visitDataReadCommand(NonTransactionalLockingInterceptor.java:32) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitGetCacheEntryCommand(AbstractLockingInterceptor.java:115) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.commands.read.GetCacheEntryCommand.acceptVisitor(GetCacheEntryCommand.java:38) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNext(BaseAsyncInterceptor.java:58) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.impl.CacheMgmtInterceptor.visitDataReadCommand(CacheMgmtInterceptor.java:94) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.impl.CacheMgmtInterceptor.visitGetCacheEntryCommand(CacheMgmtInterceptor.java:88) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.commands.read.GetCacheEntryCommand.acceptVisitor(GetCacheEntryCommand.java:38) ~[infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.BaseAsyncInterceptor.invokeNextAndExceptionally(BaseAsyncInterceptor.java:127) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.impl.InvocationContextInterceptor.visitCommand(InvocationContextInterceptor.java:97) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.interceptors.impl.AsyncInterceptorChainImpl.invoke(AsyncInterceptorChainImpl.java:248) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.cache.impl.CacheImpl.getCacheEntry(CacheImpl.java:534) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.cache.impl.CacheImpl.getCacheEntry(CacheImpl.java:540) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.cache.impl.AbstractDelegatingAdvancedCache.getCacheEntry(AbstractDelegatingAdvancedCache.java:292) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.cache.impl.EncoderCache.getCacheEntry(EncoderCache.java:409) [infinispan-core.jar:9.1.1-SNAPSHOT]
> at org.infinispan.server.hotrod.CacheDecodeContext.get(CacheDecodeContext.java:148) [infinispan-server-hotrod.jar:9.1.1-SNAPSHOT]
> at org.infinispan.server.hotrod.LocalContextHandler.realChannelRead(LocalContextHandler.java:42) [infinispan-server-hotrod.jar:9.1.1-SNAPSHOT]
> at org.infinispan.server.hotrod.LocalContextHandler.channelRead(LocalContextHandler.java:28) [infinispan-server-hotrod.jar:9.1.1-SNAPSHOT]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:293) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:267) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.ChannelInboundHandlerAdapter.channelRead(ChannelInboundHandlerAdapter.java:86) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at org.infinispan.server.core.transport.StatsChannelHandler.channelRead(StatsChannelHandler.java:26) [infinispan-server-core.jar:9.1.1-SNAPSHOT]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1334) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:926) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:1017) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:394) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:299) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:858) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) [netty-all-4.1.9.Final.jar:4.1.9.Final]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_141]
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months
[JBoss JIRA] (ISPN-8155) SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-8155?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-8155:
--------------------------------
Fix Version/s: 9.2.0.Final
9.1.1.Final
> SingleClusterExecutorTest.testExecutorTriConsumerTimeoutException random failures
> ---------------------------------------------------------------------------------
>
> Key: ISPN-8155
> URL: https://issues.jboss.org/browse/ISPN-8155
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.1.0.Final
> Reporter: Gustavo Fernandes
> Assignee: William Burns
> Labels: testsuite_stability
> Fix For: 9.2.0.Final, 9.1.1.Final
>
>
> {noformat}
> testExecutorTriConsumerTimeoutException on SingleClusterExecutorTest{ local = true}(org.infinispan.manager.SingleClusterExecutorTest) Time elapsed: 1.049 sec <<< FAILURE!
> java.lang.AssertionError: Should have thrown an class java.util.concurrent.ExecutionException
> at org.infinispan.test.Exceptions.assertException(Exceptions.java:21)
> at org.infinispan.test.Exceptions.expectExecutionException(Exceptions.java:136)
> at org.infinispan.manager.AllClusterExecutorTest$17.call(AllClusterExecutorTest.java:390)
> at org.infinispan.test.TestingUtil.withCacheManagers(TestingUtil.java:1474)
> at org.infinispan.manager.AllClusterExecutorTest.testExecutorTriConsumerTimeoutException(AllClusterExecutorTest.java:376)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 6 months