June 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2893) GUI Demo sample configs include old RELAY configuration instead of RELAY2

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2893?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2893: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > GUI Demo sample configs include old RELAY configuration instead of RELAY2 > ------------------------------------------------------------------------- > > Key: ISPN-2893 > URL: https://issues.jboss.org/browse/ISPN-2893 > Project: Infinispan > Issue Type: Feature Request > Components: Demos and Tutorials > Affects Versions: 5.2.3.Final > Reporter: Tristan Tarrant > Assignee: Mircea Markus > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > The files in infinispan/demos/gui/src/main/release/etc/config-samples related to xsite configuration still reference the old RELAY stack instead of the newer RELAY2. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2901) Update the configuration files for xsite documentation

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2901?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2901: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Update the configuration files for xsite documentation > ------------------------------------------------------ > > Key: ISPN-2901 > URL: https://issues.jboss.org/browse/ISPN-2901 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > Fix For: 6.0.0.Alpha1 > > > The xsite configuration files are not correct and require updating: https://docs.jboss.org/author/pages/viewpageattachments.action?pageId=544... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2879) Have ResultIterator implement AutoCloseable

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2879?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2879: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Have ResultIterator implement AutoCloseable > -------------------------------------------- > > Key: ISPN-2879 > URL: https://issues.jboss.org/browse/ISPN-2879 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > Assuming we'll baseline on Java7, it would be very nice to have the following code valid and changing the default Fetch to LAZY: > {code} > Query query = queryBuilder.all().createQuery(); > CacheQuery cacheQuery = searchManager.getQuery(query, Bean.class); > for (Object object : cacheQuery) { > ... > }{code} > the problem is the implicit iterable opened needs to be closed. > see also ISPN-2874. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2964) putForExternalRead to L1 not invalidated

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2964?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2964: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > putForExternalRead to L1 not invalidated > ---------------------------------------- > > Key: ISPN-2964 > URL: https://issues.jboss.org/browse/ISPN-2964 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 5.2.1.Final > Reporter: Sebastian Tusk > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha1 > > Attachments: SebastianTusk_ISPN-2964_fix.patch > > > With transactional distributed caches it happens that Cache.putForExternalRead(k,v) places an entry into L1 that never gets invalidated. It seems to happen when the the owner of k doesn't have the entry. In this case the non owner puts k into his cache without having the owner registering this. Usually the owner stores all requesters in L1ManagerImpl.addRequester and sends out invalidations to the requesters. What should happen is that the entry is replicated to the owner. > Cache config: > <namedCache name="entity"> > <jmxStatistics enabled="true" /> > <clustering mode="dist"> > <stateTransfer fetchInMemoryState="false" timeout="20000" /> > <async /> > <l1 enabled="true" /> > <hash numOwners="1"/> > </clustering> > <locking isolationLevel="READ_COMMITTED" > lockAcquisitionTimeout="15000" useLockStriping="false" /> > <eviction maxEntries="10000" strategy="LRU" /> > <expiration maxIdle="100000" wakeUpInterval="5000"/> > <storeAsBinary storeKeysAsBinary="true" storeValuesAsBinary="false" enabled="false" /> > <transaction transactionMode="TRANSACTIONAL" autoCommit="false" lockingMode="OPTIMISTIC"/> > </namedCache> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2958) Lucene Directory Read past EOF

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2958?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2958: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Lucene Directory Read past EOF > ------------------------------ > > Key: ISPN-2958 > URL: https://issues.jboss.org/browse/ISPN-2958 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.1.Final > Reporter: Clement Pang > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > This seems to be happening rather deterministically. > Infinispan configuration (in JBoss EAP 6.1.0.Alpha): > {code} > <cache-container name="lucene"> > <local-cache name="dshell-index-data" start="EAGER"> > <eviction strategy="LIRS" max-entries="50000"/> > <file-store path="lucene" passivation="true" purge="false"/> > </local-cache> > <local-cache name="dshell-index-metadata" start="EAGER"> > <file-store path="lucene" passivation="true" purge="false"/> > </local-cache> > <local-cache name="dshell-index-lock" start="EAGER"> > <file-store path="lucene" passivation="true" purge="false"/> > </local-cache> > </cache-container> > {code} > Upon shutting down the server and confirming that passivation did indeed write the data to disk, the subsequent start-up would fail right away with: > {code} > Caused by: org.hibernate.search.SearchException: Could not initialize index > at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:162) > at org.hibernate.search.infinispan.impl.InfinispanDirectoryProvider.start(InfinispanDirectoryProvider.java:103) > at org.hibernate.search.indexes.impl.DirectoryBasedIndexManager.initialize(DirectoryBasedIndexManager.java:104) > at org.hibernate.search.indexes.impl.IndexManagerHolder.createIndexManager(IndexManagerHolder.java:227) > ... 64 more > Caused by: java.io.IOException: Read past EOF > at org.infinispan.lucene.SingleChunkIndexInput.readByte(SingleChunkIndexInput.java:77) > at org.apache.lucene.store.ChecksumIndexInput.readByte(ChecksumIndexInput.java:41) > at org.apache.lucene.store.DataInput.readInt(DataInput.java:86) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:272) > at org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:182) > at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1168) > at org.hibernate.search.store.impl.DirectoryProviderHelper.initializeIndexIfNeeded(DirectoryProviderHelper.java:157) > ... 67 more > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2955) Async marshalling executor retry when queue fills

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2955?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2955: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Async marshalling executor retry when queue fills > ------------------------------------------------- > > Key: ISPN-2955 > URL: https://issues.jboss.org/browse/ISPN-2955 > Project: Infinispan > Issue Type: Enhancement > Components: Marshalling > Affects Versions: 5.2.5.Final > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 6.0.0.Alpha1 > > > When using an async transport and async marshalling, an executor is used to process the marshalling task in a separate thread and the caller's thread is allowed to return immediately. > When the executor's queue fills and the queue cannot accept any more tasks, it throws a {{RejectedExecutionException}}, causing a very bad user/developer experience. A more correct approach to this is to catch the {{RejectedExecutionException}}, block and retry the task submission. > The end result is that, in the degenerate case (when the executor queue is full) instead of throwing exceptions, those invocations will perform slightly slower. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2932) Verify that preloading a read only index in a cache will never hit the cacheloader

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2932?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2932: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Verify that preloading a read only index in a cache will never hit the cacheloader > ---------------------------------------------------------------------------------- > > Key: ISPN-2932 > URL: https://issues.jboss.org/browse/ISPN-2932 > Project: Infinispan > Issue Type: Task > Components: Lucene Directory > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > With a warm cache (with no eviction) we should never need to hit the CacheLoader again. > Was reported - specifically with DIST on multiple nodes - that occasionall IO is triggered; we should add tests to verify this doesn't happen (or to understand why it should) > I'm suspecting demand of null valued entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2930) ChainingCacheLoaderTest intermittent failure

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2930?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2930: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > ChainingCacheLoaderTest intermittent failure > -------------------------------------------- > > Key: ISPN-2930 > URL: https://issues.jboss.org/browse/ISPN-2930 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Test Suite > Affects Versions: 5.2.5.Final > Reporter: Adrian Nistor > Assignee: Mircea Markus > Labels: testsuite_stability > Fix For: 6.0.0.Alpha1 > > Attachments: ChainingCacheLoaderTest.log > > > Test fails sometimes. See attached log. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2926) MBean to access cache content

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2926?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2926: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > MBean to access cache content > ----------------------------- > > Key: ISPN-2926 > URL: https://issues.jboss.org/browse/ISPN-2926 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Affects Versions: 5.2.5.Final > Reporter: Edoardo Schepis > Assignee: Manik Surtani > Fix For: 6.0.0.Alpha1 > > > It would be great to have a tool to access the cache and inspect it. > For troubleshooting, debugging or simply for monitoring, it would be very helpful to show the content of the cache using some kind of tool -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2991) Management of DistExec / Map Reduce jobs

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2991?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2991: ------------------------------- Fix Version/s: 6.0.0.Alpha1 (was: 5.3.0.Final) > Management of DistExec / Map Reduce jobs > ---------------------------------------- > > Key: ISPN-2991 > URL: https://issues.jboss.org/browse/ISPN-2991 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce, JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Vladimir Blagojevic > Fix For: 6.0.0.Alpha1 > > > We should expose a management interface for both DistExec and Map/reduce jobs so that at the very least we can: > - list running jobs with starting time and duration > - list recently terminated jobs > - allow cancelling running jobs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2013