November 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3752) capacityFactor is not effective

by Takayoshi Kimura (JIRA)

[ https://issues.jboss.org/browse/ISPN-3752?page=com.atlassian.jira.plugin.... ] Takayoshi Kimura updated ISPN-3752: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2233 > capacityFactor is not effective > ------------------------------- > > Key: ISPN-3752 > URL: https://issues.jboss.org/browse/ISPN-3752 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.Final > Reporter: Takayoshi Kimura > Assignee: Dan Berindei > > The capacityFactor is not effective because the ClusterCacheStatus.addMember() uses its own, local joinInfo and doesn't use joiner's capacityFactor on method parameter. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3752) capacityFactor is not effective

by Takayoshi Kimura (JIRA)

Takayoshi Kimura created ISPN-3752: -------------------------------------- Summary: capacityFactor is not effective Key: ISPN-3752 URL: https://issues.jboss.org/browse/ISPN-3752 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 6.0.0.Final Reporter: Takayoshi Kimura Assignee: Dan Berindei The capacityFactor is not effective because the ClusterCacheStatus.addMember() uses its own, local joinInfo and doesn't use joiner's capacityFactor on method parameter. -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2577) Silence SuspectExceptions

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2577?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-2577: -------------------------------------- This issue is about silencing the SuspectExceptions - not displaying them as error level message, since it's not an exceptional situation that a node is suspected during topology changes. Of course currently SuspectExceptions may accompany other serious errors, but those should be logged separately. > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta4, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Critical > Fix For: 6.1.0.Final > > > There are lots of SuspectExceptions in resilience test run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > We managed to keep these under cover for 5.1.x branch. > This is of course a cosmetic problem, but it polutes the log with unnecessary ERRORs. > Parsed logs here: > http://www.qa.jboss.com/~mlinhard/test_results/run54-parsed/ -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-2577) Silence SuspectExceptions

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-2577?page=com.atlassian.jira.plugin.... ] Michal Linhard updated ISPN-2577: --------------------------------- Affects Version/s: 6.0.0.Final > Silence SuspectExceptions > ------------------------- > > Key: ISPN-2577 > URL: https://issues.jboss.org/browse/ISPN-2577 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.0.Beta4, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Critical > Fix For: 6.1.0.Final > > > There are lots of SuspectExceptions in resilience test run: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EDG6/view/EDG-REPOR... > We managed to keep these under cover for 5.1.x branch. > This is of course a cosmetic problem, but it polutes the log with unnecessary ERRORs. > Parsed logs here: > http://www.qa.jboss.com/~mlinhard/test_results/run54-parsed/ -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3081) JBoss Modules logging produces garbage at the beginning of line

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-3081?page=com.atlassian.jira.plugin.... ] Michal Linhard updated ISPN-3081: --------------------------------- Summary: JBoss Modules logging produces garbage at the beginning of line (was: Logging produces strange beginning of lines) > JBoss Modules logging produces garbage at the beginning of line > --------------------------------------------------------------- > > Key: ISPN-3081 > URL: https://issues.jboss.org/browse/ISPN-3081 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.3.0.Alpha1, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Tristan Tarrant > Attachments: configs.zip, serverlogs.zip > > > This is what I get on the console when running infinispan-server-5.3.0-SNAPSHOT > {code} > [0m06:38:12,718 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1 > [0m[0m06:38:13,282 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA > [0m[0m06:38:13,486 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) starting > [0m[31m06:38:14,687 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > .. > {code} > configuration: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... > whole logs: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3081) Logging produces strange beginning of lines

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3081?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3081: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1033821 > Logging produces strange beginning of lines > ------------------------------------------- > > Key: ISPN-3081 > URL: https://issues.jboss.org/browse/ISPN-3081 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.3.0.Alpha1, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Tristan Tarrant > Attachments: configs.zip, serverlogs.zip > > > This is what I get on the console when running infinispan-server-5.3.0-SNAPSHOT > {code} > [0m06:38:12,718 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1 > [0m[0m06:38:13,282 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA > [0m[0m06:38:13,486 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) starting > [0m[31m06:38:14,687 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > .. > {code} > configuration: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... > whole logs: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3081) Logging produces strange beginning of lines

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-3081?page=com.atlassian.jira.plugin.... ] Michal Linhard updated ISPN-3081: --------------------------------- Affects Version/s: 6.0.0.Final > Logging produces strange beginning of lines > ------------------------------------------- > > Key: ISPN-3081 > URL: https://issues.jboss.org/browse/ISPN-3081 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 5.3.0.Alpha1, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Tristan Tarrant > Attachments: configs.zip, serverlogs.zip > > > This is what I get on the console when running infinispan-server-5.3.0-SNAPSHOT > {code} > [0m06:38:12,718 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1 > [0m[0m06:38:13,282 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA > [0m[0m06:38:13,486 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss Infinispan Server 5.3.0-SNAPSHOT (AS 7.2.0.Final) starting > [0m[31m06:38:14,687 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > .. > {code} > configuration: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... > whole logs: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jdg-perf-cs-client-s... -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3503) Upstream server build doesn't include protobuf libraries in client/hotrod/java directory

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-3503?page=com.atlassian.jira.plugin.... ] Michal Linhard commented on ISPN-3503: -------------------------------------- This doesn't seem to be an issue anymore on current master, the protobuf libraries aren't included, but hotrod client can somehow live without them... I think at the time of reporting this, I couldn't make a hotrod call without the protobuf library. > Upstream server build doesn't include protobuf libraries in client/hotrod/java directory > ---------------------------------------------------------------------------------------- > > Key: ISPN-3503 > URL: https://issues.jboss.org/browse/ISPN-3503 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Alpha4 > Reporter: Michal Linhard > Assignee: Tristan Tarrant > > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/user/mlinhard@REDHAT.COM... > This is the contents of the client/hotrod/java folder: > {code} > adding: infinispan-server-6.0.x/client/hotrod/java/jboss-marshalling-river-1.3.15.GA.jar (deflated 8%) > adding: infinispan-server-6.0.x/client/hotrod/java/jboss-marshalling-1.3.15.GA.jar (deflated 12%) > adding: infinispan-server-6.0.x/client/hotrod/java/jboss-logging-3.1.1.GA.jar (deflated 10%) > adding: infinispan-server-6.0.x/client/hotrod/java/commons-pool-1.6.jar (deflated 8%) > adding: infinispan-server-6.0.x/client/hotrod/java/infinispan-commons-6.0.0-SNAPSHOT.jar (deflated 13%) > adding: infinispan-server-6.0.x/client/hotrod/java/infinispan-client-hotrod-6.0.0-SNAPSHOT.jar (deflated 12%) > {code} > JDG 6.2.0.DR4 doesn't have this problem, but this affects my regression testing where I use builds from latest upstream snapshots -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3691) Make client side Connection refused error TRACE

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-3691?page=com.atlassian.jira.plugin.... ] Michal Linhard updated ISPN-3691: --------------------------------- Affects Version/s: 6.0.0.Final > Make client side Connection refused error TRACE > ----------------------------------------------- > > Key: ISPN-3691 > URL: https://issues.jboss.org/browse/ISPN-3691 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 6.0.0.CR1, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Mircea Markus > Priority: Minor > > After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused": > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE... > This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place. > Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one... > The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error. > Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes -- 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

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3441) Silence OutdatedTopologyExceptions

by Michal Linhard (JIRA)

[ https://issues.jboss.org/browse/ISPN-3441?page=com.atlassian.jira.plugin.... ] Michal Linhard updated ISPN-3441: --------------------------------- Affects Version/s: 6.0.0.Final > Silence OutdatedTopologyExceptions > ---------------------------------- > > Key: ISPN-3441 > URL: https://issues.jboss.org/browse/ISPN-3441 > Project: Infinispan > Issue Type: Bug > Components: State transfer > Affects Versions: 6.0.0.Alpha3, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Dan Berindei > Priority: Minor > > from: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE... > when crashing one node of four in dist sync (owners=2) config resilience test I get: > {code} > 06:47:16,805 ERROR [org.infinispan.remoting.InboundInvocationHandlerImpl] (remote-thread-20) Exception executing command: org.infinispan.statetransfer.OutdatedTopologyException: Cache topology changed while the command was executing: expected 5, got 6 > at org.infinispan.interceptors.distribution.BaseDistributionInterceptor.handleNonTxWriteCommand(BaseDistributionInterceptor.java:126) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.distribution.NonTxDistributionInterceptor.visitPutKeyValueCommand(NonTxDistributionInterceptor.java:72) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.EntryWrappingInterceptor.invokeNextAndApplyChanges(EntryWrappingInterceptor.java:292) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.EntryWrappingInterceptor.setSkipRemoteGetsAndInvokeNextForDataCommand(EntryWrappingInterceptor.java:374) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.EntryWrappingInterceptor.visitPutKeyValueCommand(EntryWrappingInterceptor.java:157) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.locking.AbstractLockingInterceptor.visitPutKeyValueCommand(AbstractLockingInterceptor.java:47) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:112) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:112) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.statetransfer.StateTransferInterceptor.handleNonTxWriteCommand(StateTransferInterceptor.java:200) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.statetransfer.StateTransferInterceptor.visitPutKeyValueCommand(StateTransferInterceptor.java:128) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.CacheMgmtInterceptor.updateStoreStatistics(CacheMgmtInterceptor.java:148) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.CacheMgmtInterceptor.visitPutKeyValueCommand(CacheMgmtInterceptor.java:134) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:98) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:106) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:70) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.AbstractVisitor.visitPutKeyValueCommand(AbstractVisitor.java:32) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.write.PutKeyValueCommand.acceptVisitor(PutKeyValueCommand.java:62) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:321) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.remote.BaseRpcInvokingCommand.processVisitableCommand(BaseRpcInvokingCommand.java:39) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.commands.remote.SingleRpcCommand.perform(SingleRpcCommand.java:48) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl.handleInternal(InboundInvocationHandlerImpl.java:97) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl.access$000(InboundInvocationHandlerImpl.java:46) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at org.infinispan.remoting.InboundInvocationHandlerImpl$2.run(InboundInvocationHandlerImpl.java:169) [infinispan-core-6.0.0.Alpha3-redhat-1.jar:6.0.0.Alpha3-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {code} > Isn't this similar candidate for silencing as SuspectException (ISPN-2577) ? > The difference here is that it doesn't bubble up to hot rod user. -- 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

11 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2013