[JBoss JIRA] (ISPN-7509) TotalOrderStateTransferInterceptor doesn't handle OutdatedTopologyException for read commands
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7509?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7509.
--------------------------------
Fix Version/s: 9.1.0.Final
Resolution: Done
> TotalOrderStateTransferInterceptor doesn't handle OutdatedTopologyException for read commands
> ---------------------------------------------------------------------------------------------
>
> Key: ISPN-7509
> URL: https://issues.jboss.org/browse/ISPN-7509
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.CR1
> Reporter: Dan Berindei
> Assignee: Pedro Ruivo
> Priority: Critical
> Labels: testsuite_stability
> Fix For: 9.1.0.Final, 9.0.1.Final
>
>
> Since ISPN-6859, read commands can also trigger {{OutdatedTopologyException}}, but these are only handled in the non-TO {{StateTransferInterceptor}}. When a read should be retried because of a topology change in a TO cache, the {{OutdatedTopologyException}} is instead thrown to the user:
> {noformat}
> 16:50:40,595 DEBUG (jgroups-9,Test-NodeA-483:[]) [InvocationContextInterceptor] ISPN000311: Received a command from an outdated topology, returning the exception to caller
> org.infinispan.statetransfer.OutdatedTopologyException: Did not get any successful response, got {Test-NodeC-46564=UnsuccessfulResponse}
> 16:50:40,595 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.tx.totalorder.statetransfer.DistTotalOrderVersionedStateTransferTest.testStateTransfer
> org.infinispan.statetransfer.OutdatedTopologyException: Did not get any successful response, got {Test-NodeC-46564=UnsuccessfulResponse}
> {noformat}
> This causes random failures in {{DistTotalOrderVersionedStateTransferTest}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7712) LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7712?page=com.atlassian.jira.plugin.... ]
Ryan Emerson updated ISPN-7712:
-------------------------------
Fix Version/s: 9.0.1.Final
> LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction
> -------------------------------------------------------------------------
>
> Key: ISPN-7712
> URL: https://issues.jboss.org/browse/ISPN-7712
> Project: Infinispan
> Issue Type: Bug
> Components: Security
> Reporter: Kamesh Sampath
> Assignee: Tristan Tarrant
> Priority: Critical
> Labels: ldap, ldap-realm, role-mapping
> Fix For: 9.1.0.Final, 9.0.1.Final
>
> Attachments: example.com.ldif, jdg-security-demo.tar.gz, ldap_cluster_notworking.xml, ldap_cluster_workaround.xml
>
>
> When enabling security with Inifinispan with LDAP backend and when using `common-role-name-mapper` for authorisation, the extraction fails to extract the role name when the role name attribute e.g. "cn" is used instead of "CN" in the distinguished name.
> Its identified that the `org.infinispan.security.impl.CommonRoleMapper` use a case sensitive search and extracts roles only when the DN is like "CN=Developers,ou=Groups,dc=example,dc=com"
> The current workaround is to use the use a ldap authorization like
> {code:xml}
> <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="cn">
> <group-to-principal search-by="DISTINGUISHED_NAME" base-dn="ou=Groups,dc=example,dc=com">
> <membership-filter principal-attribute="uniqueMember"/>
> </group-to-principal>
> </group-search>
> {code}
> and define the cache-container authorisation like
> {code:xml}
> <security>
> <authorization>
> <!-- This does not work as the role extraction uses case sensitive extraction of cn -->
> <!-- common-name-role-mapper/ -->
> <identity-role-mapper/>
> <role name="ClusterAdmins" permissions="ALL"/>
> <role name="Developers" permissions="WRITE"/>
> <role name="Business" permissions="READ"/>
> <role name="Managers" permissions="ALL_READ ALL_WRITE"/>
> </authorization>
> </security>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7696) RemoveExpired could be called with updated value
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7696?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7696.
--------------------------------
Resolution: Done
> RemoveExpired could be called with updated value
> ------------------------------------------------
>
> Key: ISPN-7696
> URL: https://issues.jboss.org/browse/ISPN-7696
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.0.0.Final
> Reporter: Radim Vansa
> Assignee: William Burns
> Fix For: 9.1.0.Final
>
>
> In {{ClusterExpirationManager.handleLifespanExpireEntry}} the value for {{removeExpired}} is retrieved in the {{Runnable}}, which is not executed under synchronized
> block. There is a comment in CEM.handleInMemoryExpiration about the need
> for synchronization, but it seems to me that the Cache.removeExpired
> does not get the value we're checking the metadata for - there is a
> window when the value can change after we've checked the expiration.
> The value should stored in local variable while under synchronization, and captured in the Runnable/lambda.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7712) LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-7712?page=com.atlassian.jira.plugin.... ]
Ryan Emerson resolved ISPN-7712.
--------------------------------
Fix Version/s: 9.1.0.Final
Assignee: Tristan Tarrant
Resolution: Done
> LDAP Authorization Common RoleName Mapper Case Insensitive CN extraction
> -------------------------------------------------------------------------
>
> Key: ISPN-7712
> URL: https://issues.jboss.org/browse/ISPN-7712
> Project: Infinispan
> Issue Type: Bug
> Components: Security
> Reporter: Kamesh Sampath
> Assignee: Tristan Tarrant
> Priority: Critical
> Labels: ldap, ldap-realm, role-mapping
> Fix For: 9.1.0.Final
>
> Attachments: example.com.ldif, jdg-security-demo.tar.gz, ldap_cluster_notworking.xml, ldap_cluster_workaround.xml
>
>
> When enabling security with Inifinispan with LDAP backend and when using `common-role-name-mapper` for authorisation, the extraction fails to extract the role name when the role name attribute e.g. "cn" is used instead of "CN" in the distinguished name.
> Its identified that the `org.infinispan.security.impl.CommonRoleMapper` use a case sensitive search and extracts roles only when the DN is like "CN=Developers,ou=Groups,dc=example,dc=com"
> The current workaround is to use the use a ldap authorization like
> {code:xml}
> <group-search group-name="SIMPLE" iterative="true" group-dn-attribute="dn" group-name-attribute="cn">
> <group-to-principal search-by="DISTINGUISHED_NAME" base-dn="ou=Groups,dc=example,dc=com">
> <membership-filter principal-attribute="uniqueMember"/>
> </group-to-principal>
> </group-search>
> {code}
> and define the cache-container authorisation like
> {code:xml}
> <security>
> <authorization>
> <!-- This does not work as the role extraction uses case sensitive extraction of cn -->
> <!-- common-name-role-mapper/ -->
> <identity-role-mapper/>
> <role name="ClusterAdmins" permissions="ALL"/>
> <role name="Developers" permissions="WRITE"/>
> <role name="Business" permissions="READ"/>
> <role name="Managers" permissions="ALL_READ ALL_WRITE"/>
> </authorization>
> </security>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7747) Java client library tries to connect to a stopped Infinispan instance over HotRod
by Daniel Breitlauch (JIRA)
Daniel Breitlauch created ISPN-7747:
---------------------------------------
Summary: Java client library tries to connect to a stopped Infinispan instance over HotRod
Key: ISPN-7747
URL: https://issues.jboss.org/browse/ISPN-7747
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 8.2.6.Final
Environment: I have a Infinispan cluster with 4 instances on 4 nodes. There is approx. 16 GB of data on each node. Replication factor is two.
4 Java instances are running on the same hosts and connect to the cluster via HotRod.
Reporter: Daniel Breitlauch
When I stop one instance of Infinispan I see it rebalancing for e few seconds. I also see the topology change propagated to the java clients.
But there seems to be a problem in the java client library. After the topology change it looks like it tries to connect to the Infinispan instance that was stopped.
At least I see these SocketTimeoutExceptions:
{code:java}
java.net.SocketTimeoutException: null
at sun.nio.ch.SocketAdaptor$SocketInputStream.read(SocketAdaptor.java:211) ~[na:1.8.0_111]
at sun.nio.ch.ChannelInputStream.read(ChannelInputStream.java:103) ~[na:1.8.0_111]
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) ~[na:1.8.0_111]
at java.io.BufferedInputStream.read(BufferedInputStream.java:265) ~[na:1.8.0_111]
at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:190) ~[infinispan-client-hotrod-8.2.6.Final.jar:8.2.6.Final]
Wrapped by: org.infinispan.client.hotrod.exceptions.TransportException: java.net.SocketTimeoutException
at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.readByte(TcpTransport.java:195) ~[infinispan-client-hotrod-8.2.6.Final.jar:8.2.6.Final]
at org.infinispan.client.hotrod.impl.protocol.Codec20.readMagic(Codec20.java:312) ~[infinispan-client-hotrod-8.2.6.Final.jar:8.2.6.Final]
at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:122) ~[infinispan-client-hotrod-8.2.6.Final.jar:8.2.6.Final]
at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56) ~[infinispan-client-hotrod-8.2.6.Final.jar:8.2.6.Final]
at org.infinispan.client.hotrod.impl.operations.PutAllOperation.executeOperation(PutAllOperation.java:56) ~[infinispan-client-hotrod-8.2.6.Final.jar:8.2.6.Final]
{code}
Is this a known issue? Is Infinispan not reachable while rebalancing?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7582) Rolling upgrade tests fail
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-7582?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-7582:
------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Rolling upgrade tests fail
> --------------------------
>
> Key: ISPN-7582
> URL: https://issues.jboss.org/browse/ISPN-7582
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.0.0.CR2
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
>
> when running {{HotRodRollingUpgradesIT}} to upgrade from ISPN 8.0 to 9.0, it fails with
> {noformat}
> java.lang.IllegalArgumentException: Invalid Hot Rod protocol version 'null'
> at org.infinispan.client.hotrod.impl.protocol.CodecFactory.getCodec(CodecFactory.java:69) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT]
> at org.infinispan.client.hotrod.RemoteCacheManager.start(RemoteCacheManager.java:185) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT]
> at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:95) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT]
> at org.infinispan.client.hotrod.RemoteCacheManager.<init>(RemoteCacheManager.java:81) ~[infinispan-client-hotrod-9.0.0-SNAPSHOT.jar:9.0.0-SNAPSHOT]
> at org.infinispan.server.test.util.ITestUtils.createCacheManager(ITestUtils.java:54) ~[test-classes/:?]
> at org.infinispan.server.test.util.RemoteCacheManagerFactory.createManager(RemoteCacheManagerFactory.java:51) ~[test-classes/:?]
> at org.infinispan.server.test.util.RemoteCacheManagerFactory.createCache(RemoteCacheManagerFactory.java:35) ~[test-classes/:?]
> at org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.createCache(HotRodRollingUpgradesIT.java:151) ~[test-classes/:?]
> at org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.createCache(HotRodRollingUpgradesIT.java:144) ~[test-classes/:?]
> at org.infinispan.server.test.rollingupgrades.HotRodRollingUpgradesIT.testHotRodRollingUpgradesDiffVersions(HotRodRollingUpgradesIT.java:98)
> {noformat}
> {{HotRodRollingUpgradesDistIT}} fails with
> {noformat}
> ESC[0mESC[31m11:45:37,883 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.as.server.ServerService.boot(ServerService.java:357) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_102]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[169,9]
> Message: Unexpected element '{urn:infinispan:server:endpoint:7.0}subsystem'
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) [wildfly-server-2.2.0.Final.jar:2.2.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-2.2.0.Final.jar:2.2.0.Final]
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7733) Administration console - Incorrect data field columns used on cache nodes page
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7733?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7733:
--------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/206
> Administration console - Incorrect data field columns used on cache nodes page
> ------------------------------------------------------------------------------
>
> Key: ISPN-7733
> URL: https://issues.jboss.org/browse/ISPN-7733
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.1.Final
>
> Attachments: Screen Shot 2017-04-19 at 5.55.58 AM.png
>
>
> We've been using average-read-time value in place for TotalReads, TotalFailedReads, TotalWrites, and TotalFailedWrites. Since we do not have the data for TotalReads, TotalFailedReads, TotalWrites, and TotalFailedWrites we need to replace these four fields with some of the following:
> number-of-entries
> number-of-entries-in-memory
> average-remove-time
> number-of-locks-available
> average-replication-time
> number-of-locks-held
> average-write-time
> off-heap-memory-used
> passivations
> cache-loader-loads
> prepares
> cache-loader-misses
> read-write-ratio
> cache-loader-stores
> remove-hits
> remove-misses
> replication-count
> replication-failures
> rollbacks
> commits
> stores
> success-ratio
> evictions
> hit-ratio
> hits
> Let's pick 4-6 most useful fields and we'll enable admins to choose their own stat fields in subsequent versions.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (ISPN-7746) Administration console - reset statistics action is not wired on General Status cache page
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7746?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7746:
--------------------------------------
Description: We have wired reset stats on Nodes cache page but not on General Status page as well. When admin invokes "Reset statistics" on General Status page statistics are not reset. See screenshot for details. (was: We have wired reset stats on Nodes cache page but not on General Status page as well. When admin invokes "Reset statistics" on General Status page statistics are not reset.)
> Administration console - reset statistics action is not wired on General Status cache page
> ------------------------------------------------------------------------------------------
>
> Key: ISPN-7746
> URL: https://issues.jboss.org/browse/ISPN-7746
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 9.0.0.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.0.1.Final
>
> Attachments: Screen Shot 2017-04-20 at 11.59.26 AM.png
>
>
> We have wired reset stats on Nodes cache page but not on General Status page as well. When admin invokes "Reset statistics" on General Status page statistics are not reset. See screenshot for details.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months