February 2013 - infinispan-issues

[JBoss JIRA] (ISPN-2773) Can't access a non-clustered cache via HotRod

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2773?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2773: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 906008|https://bugzilla.redhat.com/show_bug.cgi?id=906008] from MODIFIED to ON_QA > Can't access a non-clustered cache via HotRod > --------------------------------------------- > > Key: ISPN-2773 > URL: https://issues.jboss.org/browse/ISPN-2773 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.2.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Blocker > Fix For: 5.2.0.Final > > > With the ISPN-2632 fix, we switched from using the JGroups view id as a HotRod topology id, to using the topology id of the cache being accessed. > If the cache isn't clustered, however, it doesn't have a RpcManager and attempting to read the cache's topology id results in a NullPointerException: > {noformat} > java.lang.NullPointerException > at org.infinispan.server.hotrod.AbstractEncoder1x.getTopologyResponse(AbstractEncoder1x.scala:160) > at org.infinispan.server.hotrod.AbstractEncoder1x.writeHeader(AbstractEncoder1x.scala:49) > at org.infinispan.server.hotrod.HotRodEncoder.encode(HotRodEncoder.scala:63) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.doEncode(OneToOneEncoder.java:66) > at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:59) > at org.jboss.netty.channel.Channels.write(Channels.java:704) > at org.jboss.netty.channel.Channels.write(Channels.java:671) > at org.jboss.netty.channel.AbstractChannel.write(AbstractChannel.java:248) > at org.infinispan.server.core.AbstractProtocolDecoder.writeResponse(AbstractProtocolDecoder.scala:179) > at org.infinispan.server.hotrod.HotRodDecoder.customDecodeHeader(HotRodDecoder.scala:157) > at org.infinispan.server.core.AbstractProtocolDecoder.decodeHeader(AbstractProtocolDecoder.scala:105) > at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:70) > at org.infinispan.server.core.AbstractProtocolDecoder.decode(AbstractProtocolDecoder.scala:47) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:500) > at org.jboss.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:435) > at org.infinispan.server.core.AbstractProtocolDecoder.messageReceived(AbstractProtocolDecoder.scala:387) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:313) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > 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} -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2770) Wrong format arguments in trace log message

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2770?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2770: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 907500|https://bugzilla.redhat.com/show_bug.cgi?id=907500] from MODIFIED to ON_QA > Wrong format arguments in trace log message > ------------------------------------------- > > Key: ISPN-2770 > URL: https://issues.jboss.org/browse/ISPN-2770 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.CR2 > Reporter: Michal Linhard > Assignee: Adrian Nistor > Fix For: 5.2.1.Final, 5.3.0.Final > > > https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... > {code} > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) java.util.logging.ErrorManager: 5: Formatting error > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) java.util.MissingFormatArgumentException: Format specifier 's' > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at java.util.Formatter.format(Formatter.java:2432) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at java.util.Formatter.format(Formatter.java:2367) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at java.lang.String.format(String.java:2769) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtLogRecord.formatRecord(ExtLogRecord.java:434) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtLogRecord.getFormattedMessage(ExtLogRecord.java:397) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.formatters.Formatters$10.renderRaw(Formatters.java:358) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.formatters.Formatters$JustifyingFormatStep.render(Formatters.java:150) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.formatters.MultistepFormatter.format(MultistepFormatter.java:86) > node05: 11:57:22,950 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtFormatter.format(ExtFormatter.java:35) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.handlers.WriterHandler.doPublish(WriterHandler.java:49) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.ExtHandler.publish(ExtHandler.java:76) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:290) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.LoggerNode.publish(LoggerNode.java:298) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.Logger.logRaw(Logger.java:721) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logmanager.Logger.log(Logger.java:672) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logging.JBossLogManagerLogger.doLogf(JBossLogManagerLogger.java:50) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logging.Logger.logf(Logger.java:2126) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.jboss.logging.DelegatingBasicLogger.tracef(DelegatingBasicLogger.java:134) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterCacheStatus.addMember(ClusterCacheStatus.java:106) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:460) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterTopologyManagerImpl.handleNewView(ClusterTopologyManagerImpl.java:231) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at org.infinispan.topology.ClusterTopologyManagerImpl$ClusterViewListener.handleViewChange(ClusterTopologyManagerImpl.java:597) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > node05: 11:57:22,951 ERROR [stderr] (notification-thread-0) at java.lang.reflect.Method.invoke(Method.java:597) > node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:212) > node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > node05: 11:57:22,952 ERROR [stderr] (notification-thread-0) at java.lang.Thread.run(Thread.java:662) > {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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2803) Memory leak on every cache write.operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2803?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2803: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 910768|https://bugzilla.redhat.com/show_bug.cgi?id=910768] from MODIFIED to ON_QA > Memory leak on every cache write.operation > ------------------------------------------ > > Key: ISPN-2803 > URL: https://issues.jboss.org/browse/ISPN-2803 > Project: Infinispan > Issue Type: Bug > Components: Core API, State transfer > Affects Versions: 5.2.0.Final > Reporter: Erik Salter > Assignee: Erik Salter > Priority: Blocker > Fix For: 5.2.1.Final, 5.3.0.Alpha1 > > > Every cache write operation in a steady state (no state transfer) will write a copy of the key to StateConsumerImpl::updatedKey set. This set is intended to be null during steady state, but it is erroneously being created on a CH_UPDATE with a pendingCH of null. > These keys are not removed during a cache remove operation. > When enough keys are written to the cache, the container will OOM. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2647) ReplaceCommand does not perform any modifications if the entry was not yet transfered during rehashing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2647?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2647: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 902462|https://bugzilla.redhat.com/show_bug.cgi?id=902462] from MODIFIED to ON_QA > ReplaceCommand does not perform any modifications if the entry was not yet transfered during rehashing > ------------------------------------------------------------------------------------------------------ > > Key: ISPN-2647 > URL: https://issues.jboss.org/browse/ISPN-2647 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Blocker > Fix For: 5.2.0.CR3 > > > The local data container does not have the entry yet so the ReplaceCommand fails. See BaseDistStateTransferConsistencyTest.testReplace() and BaseReplStateTransferConsistencyTest.testReplace(). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2804) Memory Leak: TransactionTable never cleans up complete transactions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2804?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2804: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 910768|https://bugzilla.redhat.com/show_bug.cgi?id=910768] from MODIFIED to ON_QA > 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: Erik Salter > Priority: Blocker > Fix For: 5.2.1.Final, 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2785) CLI Codecs are incomplete

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2785?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2785: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 906271|https://bugzilla.redhat.com/show_bug.cgi?id=906271] from MODIFIED to ON_QA > CLI Codecs are incomplete > ------------------------- > > Key: ISPN-2785 > URL: https://issues.jboss.org/browse/ISPN-2785 > Project: Infinispan > Issue Type: Bug > Components: CLI > Affects Versions: 5.2.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 5.3.0.Alpha1 > > > The Memcached and REST codecs do not do anything useful -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2757) ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2757?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2757: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 902462|https://bugzilla.redhat.com/show_bug.cgi?id=902462] from MODIFIED to ON_QA > ReplaceCommand in REPL mode cluster does not perform any modifications if the entry was not yet transfered during rehashing > --------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-2757 > URL: https://issues.jboss.org/browse/ISPN-2757 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 5.2.0.Beta5 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Critical > Fix For: 5.3.0.Final > > > The local data container does not have the entry yet so the ReplaceCommand fails. See BaseReplStateTransferConsistencyTest.testReplace(). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2776) MIMECacheEntry should implement equals() properly to allow Cache.replace(key, oldValue, newValue) to work

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2776?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2776: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 902462|https://bugzilla.redhat.com/show_bug.cgi?id=902462] from MODIFIED to ON_QA > MIMECacheEntry should implement equals() properly to allow Cache.replace(key, oldValue, newValue) to work > --------------------------------------------------------------------------------------------------------- > > Key: ISPN-2776 > URL: https://issues.jboss.org/browse/ISPN-2776 > Project: Infinispan > Issue Type: Bug > Components: Remote protocols > Affects Versions: 5.2.0.CR3 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 5.2.0.Final > > > Equals should compare the payload and the content type but should ignore the timestamp. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2827) rhq-plugin does not work anymore

by Stan Nowogrudski steam (JIRA)

Stan Nowogrudski steam created ISPN-2827: -------------------------------------------- Summary: rhq-plugin does not work anymore Key: ISPN-2827 URL: https://issues.jboss.org/browse/ISPN-2827 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.2.1.Final Environment: RHQ 4.6.0-SNAPSHOT Build-Nummer: 6917de4 Linux Reporter: Stan Nowogrudski steam Assignee: Mircea Markus Fix For: 5.2.2.Final After update to ISPN 5.2.1 and RHQ plugin 5.2.1 final is RHQ plugin not working properly any more. By klicking on on of ISPN Cache MBeans on the JMX Servers tree in RHQ, the RHQ notifies about uncatched exception. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2803) Memory leak on every cache write.operation

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2803?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-2803: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 910768|https://bugzilla.redhat.com/show_bug.cgi?id=910768] from ASSIGNED to MODIFIED > Memory leak on every cache write.operation > ------------------------------------------ > > Key: ISPN-2803 > URL: https://issues.jboss.org/browse/ISPN-2803 > Project: Infinispan > Issue Type: Bug > Components: Core API, State transfer > Affects Versions: 5.2.0.Final > Reporter: Erik Salter > Assignee: Erik Salter > Priority: Blocker > Fix For: 5.2.1.Final, 5.3.0.Alpha1 > > > Every cache write operation in a steady state (no state transfer) will write a copy of the key to StateConsumerImpl::updatedKey set. This set is intended to be null during steady state, but it is erroneously being created on a CH_UPDATE with a pendingCH of null. > These keys are not removed during a cache remove operation. > When enough keys are written to the cache, the container will OOM. -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2013