July 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5618) Upgrade to WildFly 9.0.0.Final

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5618: ------------------------------------- Summary: Upgrade to WildFly 9.0.0.Final Key: ISPN-5618 URL: https://issues.jboss.org/browse/ISPN-5618 Project: Infinispan Issue Type: Task Components: Server Affects Versions: 8.0.0.Beta1 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 8.0.0.Beta2, 8.0.0.Final Now that WildFly 9.0.0.Final is out, we should upgrade our server to it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5617) Clearly define which cachestores are shared and which are non-shared

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-5617: ------------------------------------- Summary: Clearly define which cachestores are shared and which are non-shared Key: ISPN-5617 URL: https://issues.jboss.org/browse/ISPN-5617 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Cache stores should explicitly declare if they work in shared or non-shared mode, so that unsupported configurations cannot be started. See http://lists.jboss.org/pipermail/infinispan-dev/2015-July/016076.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5617) Clearly define which cachestores are shared and which are non-shared

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5617?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5617: ---------------------------------- Fix Version/s: 8.0.0.Final > Clearly define which cachestores are shared and which are non-shared > -------------------------------------------------------------------- > > Key: ISPN-5617 > URL: https://issues.jboss.org/browse/ISPN-5617 > Project: Infinispan > Issue Type: Task > Reporter: Tristan Tarrant > Fix For: 8.0.0.Final > > > Cache stores should explicitly declare if they work in shared or non-shared mode, so that unsupported configurations cannot be started. > See http://lists.jboss.org/pipermail/infinispan-dev/2015-July/016076.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5293) Create generic execution framework from EntryIterator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5293?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5293: ---------------------------------- Fix Version/s: 8.0.0.Beta2 > Create generic execution framework from EntryIterator > ----------------------------------------------------- > > Key: ISPN-5293 > URL: https://issues.jboss.org/browse/ISPN-5293 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > This framework could be used to power a segment aware map/reduce framework and other events that require execution across the cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5293) Create generic execution framework from EntryIterator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5293?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5293: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Create generic execution framework from EntryIterator > ----------------------------------------------------- > > Key: ISPN-5293 > URL: https://issues.jboss.org/browse/ISPN-5293 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 8.0.0.Beta2, 8.0.0.Final > > > This framework could be used to power a segment aware map/reduce framework and other events that require execution across the cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4914) The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file'

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4914?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4914: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1229875|https://bugzilla.redhat.com/show_bug.cgi?id=1229875] from ASSIGNED to POST > The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file' > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-4914 > URL: https://issues.jboss.org/browse/ISPN-4914 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.0.0.Final > > > The server only supports READ_COMMITTED isolation and should print a warning in case someone sets a value. Unfortunately the check is wrong and the warning is always printed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4914) The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file'

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4914?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4914: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1229875|https://bugzilla.redhat.com/show_bug.cgi?id=1229875] from NEW to ASSIGNED > The server erroneusly prints 'Ignoring XML attribute isolation, please remove from configuration file' > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-4914 > URL: https://issues.jboss.org/browse/ISPN-4914 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 7.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 7.0.0.Final > > > The server only supports READ_COMMITTED isolation and should print a warning in case someone sets a value. Unfortunately the check is wrong and the warning is always printed -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5595) Operation [Registering Deployed Cache Store service...] happens too late on slower machines

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5595?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5595: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1223395|https://bugzilla.redhat.com/show_bug.cgi?id=1223395] from NEW to ASSIGNED > Operation [Registering Deployed Cache Store service...] happens too late on slower machines > ------------------------------------------------------------------------------------------- > > Key: ISPN-5595 > URL: https://issues.jboss.org/browse/ISPN-5595 > Project: Infinispan > Issue Type: Bug > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5523) Enabling eager caching can lead to sever throwing "OutOfMemoryError: Direct buffer memory"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5523?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5523: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1228676|https://bugzilla.redhat.com/show_bug.cgi?id=1228676] from NEW to ASSIGNED > Enabling eager caching can lead to sever throwing "OutOfMemoryError: Direct buffer memory" > ------------------------------------------------------------------------------------------- > > Key: ISPN-5523 > URL: https://issues.jboss.org/browse/ISPN-5523 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.2.2.Final, 8.0.0.Alpha1 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.Beta2, 7.2.4.Final, 8.0.0.Final > > > Some near caching tests are throwing: > {code} > [0m[31m04:11:24,499 ERROR [org.infinispan.server.hotrod.CacheDecodeContext] (HotRodServerWorker-43) ISPN005009: Unexpected error before any request parameters read: java.lang.OutOfMemoryError: Direct buffer memory > at java.nio.Bits.reserveMemory(Bits.java:658) [rt.jar:1.7.0_75] > at java.nio.DirectByteBuffer.<init>(DirectByteBuffer.java:123) [rt.jar:1.7.0_75] > at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:306) [rt.jar:1.7.0_75] > at io.netty.buffer.PoolArena$DirectArena.newChunk(PoolArena.java:433) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.PoolArena.allocateNormal(PoolArena.java:179) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.PoolArena.allocate(PoolArena.java:168) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.PoolArena.allocate(PoolArena.java:98) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:241) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:155) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:146) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.buffer.AbstractByteBufAllocator.ioBuffer(AbstractByteBufAllocator.java:107) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:106) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:494) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:461) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:378) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:350) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [netty-all-4.0.18.Final-redhat-1.jar:4.0.18.Final-redhat-1] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75] > {code} > KeyValueVersionConverter allocates a byte buffer but does not release it. It could be the cause... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5576) Use MessageToByteEncoder to avoid ByteBuf leak w/ exceptions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5576?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5576: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1228676|https://bugzilla.redhat.com/show_bug.cgi?id=1228676] from NEW to ASSIGNED > Use MessageToByteEncoder to avoid ByteBuf leak w/ exceptions > ------------------------------------------------------------ > > Key: ISPN-5576 > URL: https://issues.jboss.org/browse/ISPN-5576 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 7.2.3.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 8.0.0.Beta1, 7.2.4.Final, 8.0.0.Final > > > Encoder implementation allocates buffers but does not release them in case of exception before the encoded buffer is added to the response list. As a result, if encoding faces exceptions, it could leak byte buffers and show messages like this: > {code} > [io.netty.util.ResourceLeakDetector] LEAK: ByteBuf.release() was not called before it's garbage-collected. > Enable advanced leak reporting to find out where the leak occurred. To enable advanced leak reporting, > specify the JVM option '-Dio.netty.leakDetectionLevel=advanced' or call ResourceLeakDetector.setLevel() > LEAK: ByteBuf.release() was not called before it's garbage-collected. > Recent access records: 0 > Created at: > io.netty.buffer.PooledByteBufAllocator.newDirectBuffer(PooledByteBufAllocator.java:259) > io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:155) > io.netty.buffer.AbstractByteBufAllocator.directBuffer(AbstractByteBufAllocator.java:141) > io.netty.buffer.AbstractByteBufAllocator.buffer(AbstractByteBufAllocator.java:75) > org.infinispan.server.hotrod.HotRodEncoder.encode(HotRodEncoder.scala:29) > io.netty.handler.codec.MessageToMessageEncoder.write(MessageToMessageEncoder.java:89) > io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:633) > io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:691) > io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:626) > io.netty.handler.timeout.IdleStateHandler.write(IdleStateHandler.java:266) > io.netty.channel.AbstractChannelHandlerContext.invokeWrite(AbstractChannelHandlerContext.java:633) > io.netty.channel.AbstractChannelHandlerContext.write(AbstractChannelHandlerContext.java:691) > io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:681) > io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(AbstractChannelHandlerContext.java:716) > io.netty.channel.DefaultChannelPipeline.writeAndFlush(DefaultChannelPipeline.java:954) > io.netty.channel.AbstractChannel.writeAndFlush(AbstractChannel.java:243) > org.infinispan.server.core.AbstractProtocolDecoder.writeResponse(AbstractProtocolDecoder.scala:220) > org.infinispan.server.hotrod.HotRodDecoder.customDecodeHeader(HotRodDecoder.scala:153) > org.infinispan.server.core.AbstractProtocolDecoder.org$infinispan$server$core$AbstractProtocolDecoder$$decodeHeader(AbstractProtocolDecoder.scala:137) > org.infinispan.server.core.AbstractProtocolDecoder$$anon$2.run(AbstractProtocolDecoder.scala:98) > org.infinispan.server.core.AbstractProtocolDecoder$$anon$2.run(AbstractProtocolDecoder.scala:95) > org.infinispan.security.Security.doAs(Security.java:143) > org.infinispan.server.core.AbstractProtocolDecoder.secureDecodeDispatch(AbstractProtocolDecoder.scala:95) > org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:59) > io.netty.handler.codec.ReplayingDecoder.callDecode(ReplayingDecoder.java:370) > io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:168) > org.infinispan.server.core.AbstractProtocolDecoder.channelRead(AbstractProtocolDecoder.scala:459) > io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308) > io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:294) > io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:846) > io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:130) > io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511) > io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468) > io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382) > io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354) > io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) > java.lang.Thread.run(Thread.java:745) > {code} > Also, encoder implementation does not log exceptions reported at encoding time, so exceptions like this can only be noticed via instrumentation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2015