September 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6996) Update to Netty 4.1.5.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6996?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6996: ------------------------------------ Status: Open (was: New) > Update to Netty 4.1.5.Final > --------------------------- > > Key: ISPN-6996 > URL: https://issues.jboss.org/browse/ISPN-6996 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6996) Update to Netty 4.1.5.Final

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6996?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes reassigned ISPN-6996: --------------------------------------- Assignee: Gustavo Fernandes > Update to Netty 4.1.5.Final > --------------------------- > > Key: ISPN-6996 > URL: https://issues.jboss.org/browse/ISPN-6996 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 9.0.0.Alpha4, 8.2.4.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6996) Update to Netty 4.1.5.Final

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6996: --------------------------------------- Summary: Update to Netty 4.1.5.Final Key: ISPN-6996 URL: https://issues.jboss.org/browse/ISPN-6996 Project: Infinispan Issue Type: Component Upgrade Affects Versions: 8.2.4.Final, 9.0.0.Alpha4 Reporter: Gustavo Fernandes -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6994) Introduce an AdvancedCache.as(Subject) method for explicit authorization

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6994?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6994: ---------------------------------- Summary: Introduce an AdvancedCache.as(Subject) method for explicit authorization (was: Introduce an AdvancedCache.doAs(Subject) method for explicit authorization) > Introduce an AdvancedCache.as(Subject) method for explicit authorization > ------------------------------------------------------------------------ > > Key: ISPN-6994 > URL: https://issues.jboss.org/browse/ISPN-6994 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: performance > Fix For: 9.0.0.Final > > > Currently the subject is extracted either from the AccessControlContext or from the lightweight security implementation (which uses a ThreadLocal). > Both of these approaches have fairly high costs, so we should, if possible, use an explicit Subject. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6981) AffinityIndexManager sometimes fails to index document in async mode

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-6981?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-6981: ------------------------------------ Description: During topology changes in async mode ("<index>.worker.execution" set to "async"), the {{AfinityIndexManager}} sometimes fails to index entries. Some of errors thrown: {noformat} 19:06:04,638 ERROR (Hibernate Search: Index updates queue processor for index entity.5-1) [LogErrorHandler] HSEARCH000058: Exception occurred org.apache.lucene.store.LockObtainFailedException: lock instance already assigned {noformat} {noformat} 18:53:59,553 ERROR (Hibernate Search: Index updates queue processor for index entity.2-1) [LuceneBackendQueueTask] HSEARCH000073: Error in backend org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:720) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:734) {noformat} {noformat} 18:55:31,328 ERROR (Hibernate Search: Commit Scheduler for index entity.143-1) [AffinityErrorHandler] HSEARCH000117: IOException on the IndexWriter java.io.IOException: This lock is no longer being held at org.infinispan.lucene.impl.BaseLuceneLock.ensureValid(BaseLuceneLock.java:89) at org.apache.lucene.store.LockValidatingDirectoryWrapper.createOutput(LockValidatingDirectoryWrapper.java:43) at org.apache.lucene.store.TrackingDirectoryWrapper.createOutput(TrackingDirectoryWrapper.java:43) at org.apache.lucene.codecs.lucene50.Lucene50PostingsWriter.<init>(Lucene50PostingsWriter.java:105) {noformat} was: During topology changes in async mode ("<index>.worker.execution" set to "async"), the {{AfinityIndexManager}} sometimes fails to index entries. Some of errors thrown: {noformat} 19:06:04,638 ERROR (Hibernate Search: Index updates queue processor for index entity.5-1) [LogErrorHandler] HSEARCH000058: Exception occurred org.apache.lucene.store.LockObtainFailedException: lock instance already assigned {noformat} {noformat} 18:53:59,553 ERROR (Hibernate Search: Index updates queue processor for index entity.2-1) [LuceneBackendQueueTask] HSEARCH000073: Error in backend org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:720) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:734) {noformat} {noformat} 18:55:31,328 ERROR (Hibernate Search: Commit Scheduler for index entity.143-1) [AffinityErrorHandler] HSEARCH000117: IOException on the IndexWriter java.io.IOException: This lock is no longer being held at org.infinispan.lucene.impl.BaseLuceneLock.ensureValid(BaseLuceneLock.java:89) at org.apache.lucene.store.LockValidatingDirectoryWrapper.createOutput(LockValidatingDirectoryWrapper.java:43) at org.apache.lucene.store.TrackingDirectoryWrapper.createOutput(TrackingDirectoryWrapper.java:43) at org.apache.lucene.codecs.lucene50.Lucene50PostingsWriter.<init>(Lucene50PostingsWriter.java:105) {noformat} > AffinityIndexManager sometimes fails to index document in async mode > -------------------------------------------------------------------- > > Key: ISPN-6981 > URL: https://issues.jboss.org/browse/ISPN-6981 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.0.Alpha4 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > > During topology changes in async mode ("<index>.worker.execution" set to "async"), the {{AfinityIndexManager}} sometimes fails to index entries. Some of errors thrown: > {noformat} > 19:06:04,638 ERROR (Hibernate Search: Index updates queue processor for index entity.5-1) [LogErrorHandler] HSEARCH000058: Exception occurred > org.apache.lucene.store.LockObtainFailedException: lock instance already assigned > {noformat} > {noformat} > 18:53:59,553 ERROR (Hibernate Search: Index updates queue processor for index entity.2-1) [LuceneBackendQueueTask] HSEARCH000073: Error in > backend > org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed > at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:720) > at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:734) > {noformat} > {noformat} > 18:55:31,328 ERROR (Hibernate Search: Commit Scheduler for index entity.143-1) [AffinityErrorHandler] HSEARCH000117: IOException > on the IndexWriter > java.io.IOException: This lock is no longer being held > at org.infinispan.lucene.impl.BaseLuceneLock.ensureValid(BaseLuceneLock.java:89) > at org.apache.lucene.store.LockValidatingDirectoryWrapper.createOutput(LockValidatingDirectoryWrapper.java:43) > at org.apache.lucene.store.TrackingDirectoryWrapper.createOutput(TrackingDirectoryWrapper.java:43) > at org.apache.lucene.codecs.lucene50.Lucene50PostingsWriter.<init>(Lucene50PostingsWriter.java:105) > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6726) ContinuousQueryListener.resultJoining notifications generated by 'modify' operations contain the old value not the new one

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6726?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-6726: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1340827|https://bugzilla.redhat.com/show_bug.cgi?id=1340827] from ON_QA to VERIFIED > ContinuousQueryListener.resultJoining notifications generated by 'modify' operations contain the old value not the new one > -------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6726 > URL: https://issues.jboss.org/browse/ISPN-6726 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha3, 9.0.0.Final, 8.2.3.Final > > > If the query happens to contain projections the correct (new) value will be projected. The bug only happens for queries without projections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6995) org.apache.lucene.store.AlreadyClosedException when indexing with AffinityIndexManager

by Gustavo Fernandes (JIRA)

Gustavo Fernandes created ISPN-6995: --------------------------------------- Summary: org.apache.lucene.store.AlreadyClosedException when indexing with AffinityIndexManager Key: ISPN-6995 URL: https://issues.jboss.org/browse/ISPN-6995 Project: Infinispan Issue Type: Bug Components: Embedded Querying Affects Versions: 9.0.0.Alpha4 Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Somehow difficult to reproduce, but during topology changes some entries are not indexed, the indexing backend throws the exception: {noformat} 14:07:31,089 ERROR (Hibernate Search sync consumer thread for index entity.119) [LuceneBackendQueueTask] HSEARCH000073: Error in backend org.apache.lucene.store.AlreadyClosedException: this IndexWriter is closed at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:720) at org.apache.lucene.index.IndexWriter.ensureOpen(IndexWriter.java:734) at org.apache.lucene.index.IndexWriter.getAnalyzer(IndexWriter.java:1163) at org.hibernate.search.backend.impl.lucene.IndexWriterDelegate.<init>(IndexWriterDelegate.java:39) at org.hibernate.search.backend.impl.lucene.AbstractWorkspaceImpl.getIndexWriterDelegate(AbstractWorkspaceImpl.java:206) at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.applyUpdates(LuceneBackendQueueTask.java:80) at org.hibernate.search.backend.impl.lucene.LuceneBackendQueueTask.run(LuceneBackendQueueTask.java:46) at org.hibernate.search.backend.impl.lucene.SyncWorkProcessor$Consumer.applyChangesets(SyncWorkProcessor.java:165) {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6726) ContinuousQueryListener.resultJoining notifications generated by 'modify' operations contain the old value not the new one

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-6726?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-6726: ----------------------------------------------- Vaclav Dedik <vdedik(a)redhat.com> changed the Status of [bug 1340827|https://bugzilla.redhat.com/show_bug.cgi?id=1340827] from MODIFIED to ON_QA > ContinuousQueryListener.resultJoining notifications generated by 'modify' operations contain the old value not the new one > -------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6726 > URL: https://issues.jboss.org/browse/ISPN-6726 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha3, 9.0.0.Final, 8.2.3.Final > > > If the query happens to contain projections the correct (new) value will be projected. The bug only happens for queries without projections. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6994) Introduce an AdvancedCache.doAs(Subject) method for explicit authorization

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6994?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6994: ---------------------------------- Labels: performance (was: ) > Introduce an AdvancedCache.doAs(Subject) method for explicit authorization > -------------------------------------------------------------------------- > > Key: ISPN-6994 > URL: https://issues.jboss.org/browse/ISPN-6994 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: performance > Fix For: 9.0.0.Final > > > Currently the subject is extracted either from the AccessControlContext or from the lightweight security implementation (which uses a ThreadLocal). > Both of these approaches have fairly high costs, so we should, if possible, use an explicit Subject. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6994) Introduce an AdvancedCache.doAs(Subject) method for explicit authorization

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6994?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6994: ---------------------------------- Description: Currently the subject is extracted either from the AccessControlContext or from the lightweight security implementation (which uses a ThreadLocal). Both of these approaches have fairly high costs, so we should, if possible, use an explicit Subject. > Introduce an AdvancedCache.doAs(Subject) method for explicit authorization > -------------------------------------------------------------------------- > > Key: ISPN-6994 > URL: https://issues.jboss.org/browse/ISPN-6994 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Final > > > Currently the subject is extracted either from the AccessControlContext or from the lightweight security implementation (which uses a ThreadLocal). > Both of these approaches have fairly high costs, so we should, if possible, use an explicit Subject. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2016