March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7228. -------------------------------- Fix Version/s: 9.0.0.Final Resolution: Done > Administration console - creating wrong schema doesn't show error message > ------------------------------------------------------------------------- > > Key: ISPN-7228 > URL: https://issues.jboss.org/browse/ISPN-7228 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Alpha4 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > Fix For: 9.0.0.Final, 9.0.0.CR2 > > Attachments: ISPN-7228.txt > > > Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense) > Result: The dialog is closed and no schema is created. > Expected message: > Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7462) Administration console - server in reload-required state is not working correctly

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-7462?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-7462. -------------------------------- Fix Version/s: 9.0.0.Final Resolution: Done > Administration console - server in reload-required state is not working correctly > ---------------------------------------------------------------------------------- > > Key: ISPN-7462 > URL: https://issues.jboss.org/browse/ISPN-7462 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Fix For: 9.0.0.Final > > > Click on cache-container -> configuration -> change value (e.g. Min Threads) -> Save -> Restart Later -> click on clusters tab -> cluster -> server > Issues: > - Server has status RELOAD-REQUIRED, I suggest we change it to RESTART-REQUIRED. > - Cluster has status STARTED, it should also be RESTART-REQUIRED/RELOAD-REQUIRED > - Server has enabled start button and disabled stop button -> it should be the other way around -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5654) Make DeadlockDetectingLockManager aware of single-node locking

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5654?page=com.atlassian.jira.plugin.... ] Dan Berindei reassigned ISPN-5654: ---------------------------------- Assignee: Dan Berindei > Make DeadlockDetectingLockManager aware of single-node locking > -------------------------------------------------------------- > > Key: ISPN-5654 > URL: https://issues.jboss.org/browse/ISPN-5654 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > > {{DeadlockDetectingLockManager}} seems to assume that the node that started a transaction acquires a local lock before replicating, which is wrong since we switched to locking only on the primary owner. > In particular, {{isSameKeyDeadlock}} can probably be removed altogether. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5654) Make DeadlockDetectingLockManager aware of single-node locking

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5654?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5654: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4924 > Make DeadlockDetectingLockManager aware of single-node locking > -------------------------------------------------------------- > > Key: ISPN-5654 > URL: https://issues.jboss.org/browse/ISPN-5654 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 8.0.0.Beta2 > Reporter: Dan Berindei > Assignee: Dan Berindei > > {{DeadlockDetectingLockManager}} seems to assume that the node that started a transaction acquires a local lock before replicating, which is wrong since we switched to locking only on the primary owner. > In particular, {{isSameKeyDeadlock}} can probably be removed altogether. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7544) Administration console - server cards do not indicate correct status in some cases

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7544?page=com.atlassian.jira.plugin.... ] Roman Macor updated ISPN-7544: ------------------------------ Summary: Administration console - server cards do not indicate correct status in some cases (was: Administration console - server cards do not indice correct status in some cases) > Administration console - server cards do not indicate correct status in some cases > ---------------------------------------------------------------------------------- > > Key: ISPN-7544 > URL: https://issues.jboss.org/browse/ISPN-7544 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > > Server cards (clusters tab -> cluster) don't indicate that the server is in reload-required, restart required state. - they show green check icon in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7544) Administration console - server cards do not indice correct status in some cases

by Roman Macor (JIRA)

Roman Macor created ISPN-7544: --------------------------------- Summary: Administration console - server cards do not indice correct status in some cases Key: ISPN-7544 URL: https://issues.jboss.org/browse/ISPN-7544 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 9.0.0.CR2 Reporter: Roman Macor Server cards (clusters tab -> cluster) don't indicate that the server is in reload-required, restart required state. - they show green check icon in this case. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7524) PutKeyValueCommand.toString should contain commandInvocationId

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-7524?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-7524: -------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > PutKeyValueCommand.toString should contain commandInvocationId > -------------------------------------------------------------- > > Key: ISPN-7524 > URL: https://issues.jboss.org/browse/ISPN-7524 > Project: Infinispan > Issue Type: Enhancement > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7543) Integration tests should try to kill the server before trying to start it

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7543?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7543: ------------------------------- Priority: Critical (was: Major) > Integration tests should try to kill the server before trying to start it > ------------------------------------------------------------------------- > > Key: ISPN-7543 > URL: https://issues.jboss.org/browse/ISPN-7543 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.0.0.Final > > > Some integration tests use an Ant file to start one or more external servers and then kill them. Sometimes the kill step doesn't run, e.g. in this example the JVM died with an internal error: > http://ci.infinispan.org/viewLog.html?buildId=50891&buildTypeId=bt9&tab=b... > The server then stayed up and caused lots of failures in the test suite runs that followed, apparently without the kill step running in any of those runs. We should add a kill step before trying to start the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7543) Integration tests should try to kill the server before trying to start it

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7543?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7543: ------------------------------- Priority: Minor (was: Critical) > Integration tests should try to kill the server before trying to start it > ------------------------------------------------------------------------- > > Key: ISPN-7543 > URL: https://issues.jboss.org/browse/ISPN-7543 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.0.0.Final > > > Some integration tests use an Ant file to start one or more external servers and then kill them. Sometimes the kill step doesn't run, e.g. in this example the JVM died with an internal error: > http://ci.infinispan.org/viewLog.html?buildId=50891&buildTypeId=bt9&tab=b... > The server then stayed up and caused lots of failures in the test suite runs that followed, apparently without the kill step running in any of those runs. We should add a kill step before trying to start the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7543) Integration tests should try to kill the server before trying to start it

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7543?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7543: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4923 > Integration tests should try to kill the server before trying to start it > ------------------------------------------------------------------------- > > Key: ISPN-7543 > URL: https://issues.jboss.org/browse/ISPN-7543 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Minor > Labels: testsuite_stability > Fix For: 9.0.0.Final > > > Some integration tests use an Ant file to start one or more external servers and then kill them. Sometimes the kill step doesn't run, e.g. in this example the JVM died with an internal error: > http://ci.infinispan.org/viewLog.html?buildId=50891&buildTypeId=bt9&tab=b... > The server then stayed up and caused lots of failures in the test suite runs that followed, apparently without the kill step running in any of those runs. We should add a kill step before trying to start the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017