[JBoss JIRA] (ISPN-11296) StateResponseOrderingTest uncaught IllegalArgumentException
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11296?page=com.atlassian.jira.plugi... ]
Dan Berindei reopened ISPN-11296:
---------------------------------
> StateResponseOrderingTest uncaught IllegalArgumentException
> -----------------------------------------------------------
>
> Key: ISPN-11296
> URL: https://issues.redhat.com/browse/ISPN-11296
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite
> Affects Versions: 10.1.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev03
>
>
> I think initially I wanted {{MatchCountMatcher}} to count from 1 and handle {{matchCount == 0}} as matching all invocations. All the callers now assume 0 is the first invocation, but the code kept working because the exception was not caught.
> {noformat}
> java.lang.IllegalStateException: State st:after_first_state_response exited twice
> at org.infinispan.test.concurrent.StateSequencer.exit(StateSequencer.java:242)
> at org.infinispan.test.concurrent.StateSequencer.advance(StateSequencer.java:316)
> at org.infinispan.test.concurrent.StateSequencerUtil.advanceMultiple(StateSequencerUtil.java:103)
> at org.infinispan.test.concurrent.InboundRpcSequencerAction$SequencerPerCacheInboundInvocationHandler.advance(InboundRpcSequencerAction.java:101)
> at org.infinispan.test.concurrent.InboundRpcSequencerAction$SequencerPerCacheInboundInvocationHandler.lambda$handle$0(InboundRpcSequencerAction.java:82)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invokedComplete(BaseBlockingRunnable.java:130)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invoke(BaseBlockingRunnable.java:111)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.runAsync(BaseBlockingRunnable.java:72)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:41)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11296) StateResponseOrderingTest uncaught IllegalArgumentException
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11296?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11296:
--------------------------------
Fix Version/s: 11.0.0.Dev03
(was: 11.0.0.Alpha2)
> StateResponseOrderingTest uncaught IllegalArgumentException
> -----------------------------------------------------------
>
> Key: ISPN-11296
> URL: https://issues.redhat.com/browse/ISPN-11296
> Project: Infinispan
> Issue Type: Bug
> Components: Core, Test Suite
> Affects Versions: 10.1.1.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev03
>
>
> I think initially I wanted {{MatchCountMatcher}} to count from 1 and handle {{matchCount == 0}} as matching all invocations. All the callers now assume 0 is the first invocation, but the code kept working because the exception was not caught.
> {noformat}
> java.lang.IllegalStateException: State st:after_first_state_response exited twice
> at org.infinispan.test.concurrent.StateSequencer.exit(StateSequencer.java:242)
> at org.infinispan.test.concurrent.StateSequencer.advance(StateSequencer.java:316)
> at org.infinispan.test.concurrent.StateSequencerUtil.advanceMultiple(StateSequencerUtil.java:103)
> at org.infinispan.test.concurrent.InboundRpcSequencerAction$SequencerPerCacheInboundInvocationHandler.advance(InboundRpcSequencerAction.java:101)
> at org.infinispan.test.concurrent.InboundRpcSequencerAction$SequencerPerCacheInboundInvocationHandler.lambda$handle$0(InboundRpcSequencerAction.java:82)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invokedComplete(BaseBlockingRunnable.java:130)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.invoke(BaseBlockingRunnable.java:111)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.runAsync(BaseBlockingRunnable.java:72)
> at org.infinispan.remoting.inboundhandler.BaseBlockingRunnable.run(BaseBlockingRunnable.java:41)
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11423?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11423:
--------------------------------
Status: Open (was: New)
> Dump information in panic scenarios
> -----------------------------------
>
> Key: ISPN-11423
> URL: https://issues.redhat.com/browse/ISPN-11423
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Server
> Affects Versions: 10.1.3.Final, 11.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev03
>
>
> When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level.
> The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default.
> These files can be sent to support via an SOS report.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11423?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11423:
--------------------------------
Sprint: DataGrid Sprint #40
> Dump information in panic scenarios
> -----------------------------------
>
> Key: ISPN-11423
> URL: https://issues.redhat.com/browse/ISPN-11423
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Server
> Affects Versions: 10.1.3.Final, 11.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev03
>
>
> When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level.
> The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default.
> These files can be sent to support via an SOS report.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios
by Dan Berindei (Jira)
Dan Berindei created ISPN-11423:
-----------------------------------
Summary: Dump information in panic scenarios
Key: ISPN-11423
URL: https://issues.redhat.com/browse/ISPN-11423
Project: Infinispan
Issue Type: Feature Request
Components: Core, Server
Affects Versions: 11.0.0.Alpha2, 10.1.3.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 11.0.0.Dev03
When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level.
The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default.
These files can be sent to support via an SOS report.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month