May 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6699) Update to Hibernate Search 5.6.0.Beta1

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6699?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6699: ------------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/4254, https://github.com/infinispan/infinispan/pull/4372 (was: https://github.com/infinispan/infinispan/pull/4254) > Update to Hibernate Search 5.6.0.Beta1 > -------------------------------------- > > Key: ISPN-6699 > URL: https://issues.jboss.org/browse/ISPN-6699 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha3, 8.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6522) Cannot use @DateBridge with WildFly modules: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6522?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6522: ------------------------------------ Fix Version/s: 9.0.0.Alpha3 8.2.3.Final > Cannot use @DateBridge with WildFly modules: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter > ------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6522 > URL: https://issues.jboss.org/browse/ISPN-6522 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, WildFly modules > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Critical > Fix For: 9.0.0.Alpha3, 8.2.3.Final > > > The Hibernate Search engine detects if the elasticsearch backend is on the classpath, > and if so, adds {{o.h.s.backend.elasticsearch.impl.ElasticsearchBridgeProvider}} to the top of the list of the annotation based bridge providers. > When processing an entity with a @DateBridge annotation, it picks the elasticsearch provider to converted from/to {{Date}} objects (since it has priority) which in turn fails with the exception: > {code} > org.infinispan.commons.CacheException: java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93) > at org.hibernate.search.backend.elasticsearch.impl.ElasticsearchBridgeProvider$EsDateBridge.convertToString(ElasticsearchBridgeProvider.java:71) > at org.hibernate.search.backend.elasticsearch.impl.ElasticsearchBridgeProvider$EsDateBridge.set(ElasticsearchBridgeProvider.java:54) > at org.hibernate.search.bridge.util.impl.ContextualExceptionBridgeHelper$OneWayConversionContextImpl.set(ContextualExceptionBridgeHelper.java:110) > at org.hibernate.search.engine.spi.DocumentBuilderIndexedEntity.buildDocumentFieldsForProperties(DocumentBuilderIndexedEntity.java:626) > {code} > > This exception happens only when using the infinispan modules, where the elasticsearch backend is added as a dependency; in embedded mode the aforementioned provider is not loaded since the elasticsearch is not on the classpath. > This current behaviour is not the best for two reasons: > * When using Wildlfy modules, the elasticsearch backend is marked as optional, but still, it's visible in the classpath and gets loaded > * If the user is not using the elasticsearch backend, but the jar is on the classpath, elasticsearch date conversion will take precedence over the built-in bridge providers, and it shouldn't -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6704) NullPointerException if authentication configuration is not complete

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6704?page=com.atlassian.jira.plugin.... ] Work on ISPN-6704 started by Galder Zamarreño. ---------------------------------------------- > NullPointerException if authentication configuration is not complete > -------------------------------------------------------------------- > > Key: ISPN-6704 > URL: https://issues.jboss.org/browse/ISPN-6704 > Project: Infinispan > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > {code} > <subsystem xmlns="urn:infinispan:server:core:9.0" default-cache-container="clustered"> > <cache-container name="clustered" default-cache="default" statistics="true"> > <transport lock-timeout="60000"/> > <global-state/> > <distributed-cache name="securedCache" mode="SYNC" start="EAGER"> > <security> > <authorization roles="reader"/> > </security> > </distributed-cache> > </subsystem> > {code} > Throws: > {code} > Caused by: java.lang.NullPointerException > at org.infinispan.security.impl.AuthorizationManagerImpl.init(AuthorizationManagerImpl.java:32) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6704) NullPointerException if authentication configuration is not complete

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6704?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6704: ----------------------------------- Status: Open (was: New) > NullPointerException if authentication configuration is not complete > -------------------------------------------------------------------- > > Key: ISPN-6704 > URL: https://issues.jboss.org/browse/ISPN-6704 > Project: Infinispan > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Alpha2, 8.2.2.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha3, 9.0.0.Final > > > {code} > <subsystem xmlns="urn:infinispan:server:core:9.0" default-cache-container="clustered"> > <cache-container name="clustered" default-cache="default" statistics="true"> > <transport lock-timeout="60000"/> > <global-state/> > <distributed-cache name="securedCache" mode="SYNC" start="EAGER"> > <security> > <authorization roles="reader"/> > </security> > </distributed-cache> > </subsystem> > {code} > Throws: > {code} > Caused by: java.lang.NullPointerException > at org.infinispan.security.impl.AuthorizationManagerImpl.init(AuthorizationManagerImpl.java:32) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6704) NullPointerException if authentication configuration is not complete

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-6704: -------------------------------------- Summary: NullPointerException if authentication configuration is not complete Key: ISPN-6704 URL: https://issues.jboss.org/browse/ISPN-6704 Project: Infinispan Issue Type: Bug Components: Security Affects Versions: 8.2.2.Final, 9.0.0.Alpha2 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 9.0.0.Alpha3, 9.0.0.Final {code} <subsystem xmlns="urn:infinispan:server:core:9.0" default-cache-container="clustered"> <cache-container name="clustered" default-cache="default" statistics="true"> <transport lock-timeout="60000"/> <global-state/> <distributed-cache name="securedCache" mode="SYNC" start="EAGER"> <security> <authorization roles="reader"/> </security> </distributed-cache> </subsystem> {code} Throws: {code} Caused by: java.lang.NullPointerException at org.infinispan.security.impl.AuthorizationManagerImpl.init(AuthorizationManagerImpl.java:32) {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6699) Update to Hibernate Search 5.6.0.Beta1

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6699?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6699: ------------------------------------ Fix Version/s: 8.2.3.Final > Update to Hibernate Search 5.6.0.Beta1 > -------------------------------------- > > Key: ISPN-6699 > URL: https://issues.jboss.org/browse/ISPN-6699 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Alpha3, 8.2.3.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6700) Restart required dialog show only after editing distributed cache

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6700?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6700: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-management-console/pull/105 > Restart required dialog show only after editing distributed cache > ----------------------------------------------------------------- > > Key: ISPN-6700 > URL: https://issues.jboss.org/browse/ISPN-6700 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Page: Cache configuration page (select cache container -> select cache -> click Configuration) > When editing any property of replicated, local and invalidation cache, for example expiration lifespan. When I change somehow the value, right next to the input box, there appears: " (Undo) Restart needed". Then I click "Apply changes", a confirmation dialog pops up with text: "Update configuration template <cache>?", I click "Update" and it's done. I have to manually search for the option of restarting the cluster. > However, if I do it with distributed cache, after clicking "Update" in confirmation dialog, another dialog pops up with text: "Attributes changed require a restart of the affected servers. If you need to make additional configuration changes right now, consider restarting servers after the last change." with options "Restart now" and "Restart later". > IMHO this should be consistent and the latter option is correct. If restart is needed (as the tooltip says), console should offer it right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6700) Restart required dialog show only after editing distributed cache

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6700?page=com.atlassian.jira.plugin.... ] Ryan Emerson commented on ISPN-6700: ------------------------------------ [~jholusa] The reason that the restart dialog does not appear for eviction->size is because the resource-description returned by the server indicates that changing this field does not require a restart. This is also why this field only states undo to the right and does not state "restart required." The restart dialog was not previously shown for caches other than distributed ones, was because a reference to the outside-controller (which handles the restart dialog) was not passed to the configuration-section directive. > Restart required dialog show only after editing distributed cache > ----------------------------------------------------------------- > > Key: ISPN-6700 > URL: https://issues.jboss.org/browse/ISPN-6700 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Page: Cache configuration page (select cache container -> select cache -> click Configuration) > When editing any property of replicated, local and invalidation cache, for example expiration lifespan. When I change somehow the value, right next to the input box, there appears: " (Undo) Restart needed". Then I click "Apply changes", a confirmation dialog pops up with text: "Update configuration template <cache>?", I click "Update" and it's done. I have to manually search for the option of restarting the cluster. > However, if I do it with distributed cache, after clicking "Update" in confirmation dialog, another dialog pops up with text: "Attributes changed require a restart of the affected servers. If you need to make additional configuration changes right now, consider restarting servers after the last change." with options "Restart now" and "Restart later". > IMHO this should be consistent and the latter option is correct. If restart is needed (as the tooltip says), console should offer it right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6700) Restart required dialog show only after editing distributed cache

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6700?page=com.atlassian.jira.plugin.... ] Ryan Emerson reassigned ISPN-6700: ---------------------------------- Assignee: Ryan Emerson (was: Vladimir Blagojevic) > Restart required dialog show only after editing distributed cache > ----------------------------------------------------------------- > > Key: ISPN-6700 > URL: https://issues.jboss.org/browse/ISPN-6700 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Page: Cache configuration page (select cache container -> select cache -> click Configuration) > When editing any property of replicated, local and invalidation cache, for example expiration lifespan. When I change somehow the value, right next to the input box, there appears: " (Undo) Restart needed". Then I click "Apply changes", a confirmation dialog pops up with text: "Update configuration template <cache>?", I click "Update" and it's done. I have to manually search for the option of restarting the cluster. > However, if I do it with distributed cache, after clicking "Update" in confirmation dialog, another dialog pops up with text: "Attributes changed require a restart of the affected servers. If you need to make additional configuration changes right now, consider restarting servers after the last change." with options "Restart now" and "Restart later". > IMHO this should be consistent and the latter option is correct. If restart is needed (as the tooltip says), console should offer it right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6700) Restart required dialog show only after editing distributed cache

by Ryan Emerson (JIRA)

[ https://issues.jboss.org/browse/ISPN-6700?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-6700: ------------------------------- Status: Open (was: New) > Restart required dialog show only after editing distributed cache > ----------------------------------------------------------------- > > Key: ISPN-6700 > URL: https://issues.jboss.org/browse/ISPN-6700 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 8.2.2.Final > Reporter: Jiří Holuša > Assignee: Ryan Emerson > > Page: Cache configuration page (select cache container -> select cache -> click Configuration) > When editing any property of replicated, local and invalidation cache, for example expiration lifespan. When I change somehow the value, right next to the input box, there appears: " (Undo) Restart needed". Then I click "Apply changes", a confirmation dialog pops up with text: "Update configuration template <cache>?", I click "Update" and it's done. I have to manually search for the option of restarting the cluster. > However, if I do it with distributed cache, after clicking "Update" in confirmation dialog, another dialog pops up with text: "Attributes changed require a restart of the affected servers. If you need to make additional configuration changes right now, consider restarting servers after the last change." with options "Restart now" and "Restart later". > IMHO this should be consistent and the latter option is correct. If restart is needed (as the tooltip says), console should offer it right away. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 May 2016