March 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7632) Remove useEagerLocking configuration

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7632?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7632: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4992 > Remove useEagerLocking configuration > ------------------------------------ > > Key: ISPN-7632 > URL: https://issues.jboss.org/browse/ISPN-7632 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Fix For: 9.0.0.Final > > > The {{useEagerLocking}} configuration was deprecated in version 5.1, we can safely remove it in 9.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7639) PolarionJUnitXMLReporter doesn't report failures in configuration methods

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7639?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7639: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4991 > PolarionJUnitXMLReporter doesn't report failures in configuration methods > ------------------------------------------------------------------------- > > Key: ISPN-7639 > URL: https://issues.jboss.org/browse/ISPN-7639 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7639) PolarionJUnitXMLReporter doesn't report failures in configuration methods

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7639: ---------------------------------- Summary: PolarionJUnitXMLReporter doesn't report failures in configuration methods Key: ISPN-7639 URL: https://issues.jboss.org/browse/ISPN-7639 Project: Infinispan Issue Type: Bug Components: Test Suite - Core Affects Versions: 9.0.0.CR2 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7639) PolarionJUnitXMLReporter doesn't report failures in configuration methods

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-7639?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7639: ------------------------------- Status: Open (was: New) > PolarionJUnitXMLReporter doesn't report failures in configuration methods > ------------------------------------------------------------------------- > > Key: ISPN-7639 > URL: https://issues.jboss.org/browse/ISPN-7639 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.0.0.CR2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7628) Administration console - the cluster status doesn't reflect "reload-required" state of its nodes

by Roman Macor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7628?page=com.atlassian.jira.plugin.... ] Roman Macor commented on ISPN-7628: ----------------------------------- [~vblagojevic] sounds good, but I wouldn't use "degraded" mode here (as it indicates there has been a cluster partition). Instead if one of the nodes is in reload-required/restart-required state the cluster should be in reload-required/restart-required state in my opinion. An example would be: The user changes the configuration, clicks restart later, this puts all nodes in the cluster to reload-required state, now they click reload action on one of the nodes. > Administration console - the cluster status doesn't reflect "reload-required" state of its nodes > ------------------------------------------------------------------------------------------------ > > Key: ISPN-7628 > URL: https://issues.jboss.org/browse/ISPN-7628 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > The cluster has "Started" status even though all of its nodes have "reload-required" status. > Expected result: > The cluster status should also be "reload-required" > Another suggestion: > "Reload" action should be available from the cluster so that the user doesn't need to perform this action on individual nodes (there could be hundreds of them ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7580) Use of marsheller is not consistent in all places

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/ISPN-7580?page=com.atlassian.jira.plugin.... ] Ramesh Reddy commented on ISPN-7580: ------------------------------------ [~anistor] I have worked couple different working sets, but below is most non-intrusive changes I could make with out breaking any of current code. Can you please take look, if you agree I can submit as pull request https://github.com/rareddy/infinispan-1/commit/659ad4cb31cf69faa7e4b2f12d... https://github.com/rareddy/protostream/commit/f62aae0a9a8b005f5f8b6332102... > Use of marsheller is not consistent in all places > ------------------------------------------------- > > Key: ISPN-7580 > URL: https://issues.jboss.org/browse/ISPN-7580 > Project: Infinispan > Issue Type: Bug > Components: Marshalling, Remote Querying > Reporter: Ramesh Reddy > Assignee: Adrian Nistor > > Usage of extended ProtoStreamMarshaller is not consistent across all the code paths. For the purposes of Teiid translator, I have extended ProtoStreamMarshaller which knows to read/write byte streams in portable fashion for given message type, which are representions of a relational table in Teiid. This works fine, if I just use cache's get/put calls. > However, the same fails when used with RemoteQuery or Continuous query. The reason is, these classes circumvent extended Marsheller and go directly to serialization context registered to do the wrapping/unwrapping. Not only that there are few places code will type cast the SerializationContext to SerializationContextImpl object. Thus I can not even provide my own Serializer nor I can extend this as SerializationContextImpl is declared as final. These need to be corrected such that extended marsheller is used rather than hard coding them. > I am guessing this is first time anyone has even done this without using dedicated java classes as marshellers. > This is extremely critical for me to be fixed to move forward, I can provide the pull request for it? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7320) Upgrade to RestEasy 3.1.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7320?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7320: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4736, https://github.com/infinispan/infinispan/pull/4990 (was: https://github.com/infinispan/infinispan/pull/4736) > Upgrade to RestEasy 3.1.0.Final > ------------------------------- > > Key: ISPN-7320 > URL: https://issues.jboss.org/browse/ISPN-7320 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2, 8.2.7.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7320) Upgrade to RestEasy 3.1.0.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-7320?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-7320: ------------------------------------ Fix Version/s: 8.2.7.Final > Upgrade to RestEasy 3.1.0.Final > ------------------------------- > > Key: ISPN-7320 > URL: https://issues.jboss.org/browse/ISPN-7320 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2, 8.2.7.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7626) eventType is null when CacheEventConverter.convert() is called

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7626?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7626: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > eventType is null when CacheEventConverter.convert() is called > --------------------------------------------------------------- > > Key: ISPN-7626 > URL: https://issues.jboss.org/browse/ISPN-7626 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.0.0.CR3 > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7628) Administration console - the cluster status doesn't reflect "reload-required" state of its nodes

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7628?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-7628: ------------------------------------------- [~ryanemerson] [~rmacor] We can expand cluster status options if needed. So far we had "STARTED", "STOPPED" and "DEGRADED". We can expand it to "STARTED", "RELOAD-REQUIRED", "RESTART-REQUIRED", "STOPPED" and "DEGRADED". The new statuses "RELOAD-REQUIRED" and "RESTART-REQUIRED" are turned on only if all cluster nodes are in those states. If for some reason not all nodes are in the same state we could use "DEGRADED". Thoughts? > Administration console - the cluster status doesn't reflect "reload-required" state of its nodes > ------------------------------------------------------------------------------------------------ > > Key: ISPN-7628 > URL: https://issues.jboss.org/browse/ISPN-7628 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.CR2 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > > The cluster has "Started" status even though all of its nodes have "reload-required" status. > Expected result: > The cluster status should also be "reload-required" > Another suggestion: > "Reload" action should be available from the cluster so that the user doesn't need to perform this action on individual nodes (there could be hundreds of them ) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2017