June 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2057) Allow storage of Lucene indexes in an indexed cache

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2057: ------------------------------------- Summary: Allow storage of Lucene indexes in an indexed cache Key: ISPN-2057 URL: https://issues.jboss.org/browse/ISPN-2057 Project: Infinispan Issue Type: Enhancement Components: Lucene Directory, Querying Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.2.0.ALPHA1 I think it should be better to keep them using separate caches, still it's easier for many cases in which top efficiency is not required to allow this. (Today you'd get an exception similar to: {quote} java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.lucene.FileListCacheKey.{quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

4
7
0 / 0

[JBoss JIRA] (ISPN-2139) ping_on_startup ignored

by Michal Linhard (JIRA)

Michal Linhard created ISPN-2139: ------------------------------------ Summary: ping_on_startup ignored Key: ISPN-2139 URL: https://issues.jboss.org/browse/ISPN-2139 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.5.FINAL Reporter: Michal Linhard Assignee: Manik Surtani When a configuration property infinispan.client.hotrod.ping_on_startup=false is passed to the properties of RemoteCacheManager, this avoids ping in RemoteCacheManager.start() but RemoteCacheManager.getCache() does ping without checking this property and thus rendering this setting useless for scenario where we want to specify infinispan.client.hotrod.server_list with list of servers with some of the servers possibly not available yet. In such case we would expect the client to failover to first working server and retrying the first operation we want to do with the cache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

7
29
0 / 0

[JBoss JIRA] (ISPN-2032) MarshalledValue improvements

by Manik Surtani (JIRA)

Manik Surtani created ISPN-2032: ----------------------------------- Summary: MarshalledValue improvements Key: ISPN-2032 URL: https://issues.jboss.org/browse/ISPN-2032 Project: Infinispan Issue Type: Enhancement Components: Core API, Marshalling Affects Versions: 5.1.4.FINAL Reporter: Manik Surtani Assignee: Galder Zamarreño Fix For: 5.1.x, 5.2.0.ALPHA1, 5.2.0.FINAL Improve MarshalledValues by using custom streams (instead of ExposedByteArrayOutputStream) which incurs a penalty of the JDK's BAOS constructor when allocating the initial byte array which is then thrown away. This patch also changes the signature of getRaw() to return the reusable buffer and prevent an unnecessary array copy. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] (ISPN-2096) Duplicate join requests break destabilizes the cluster

by Dan Berindei (JIRA)

Dan Berindei created ISPN-2096: ---------------------------------- Summary: Duplicate join requests break destabilizes the cluster Key: ISPN-2096 URL: https://issues.jboss.org/browse/ISPN-2096 Project: Infinispan Issue Type: Bug Components: State transfer Affects Versions: 5.1.5.FINAL Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 5.2.0.ALPHA1 When the coordinator receives a {{CacheViewControlCommand(REQUEST_JOIN)}} command from a node that's already a member of the cache, it should just ignore it. Currently it tries to install a new cache view with a duplicate member, and the new cache view installation fails with this error: {noformat} [13:37:08,442] [WARN] (CacheViewControlCommand.java:141) - ISPN000071: Caught exception when handling command CacheViewControlCommand{cache=Demo, type=PREPARE_VIEW, sender=ppl-poz-nb0074/testy, newViewId=2, newMembers=[PPL-POZ-NB0074-33316, PPL-POZ-NB0074-33316], oldViewId=1, oldMembers=[PPL-POZ-NB0074-33316]} java.lang.IllegalStateException: Cannot prepare new view CacheView{viewId=2, members=[PPL-POZ-NB0074-33316, PPL-POZ-NB0074-33316]} on cache Demo, we are currently preparing view CacheView{viewId=2, members=[PPL-POZ-NB0074-33316, PPL-POZ-NB0074-33316]} at org.infinispan.cacheviews.CacheViewInfo.prepareView(CacheViewInfo.java:102) at org.infinispan.cacheviews.CacheViewsManagerImpl.handlePrepareView(CacheViewsManagerImpl.java:481) at org.infinispan.commands.control.CacheViewControlCommand.perform(CacheViewControlCommand.java:126) {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

5
10
0 / 0

[JBoss JIRA] (ISPN-1948) Invalid magic number

by Michal Linhard (JIRA)

Michal Linhard created ISPN-1948: ------------------------------------ Summary: Invalid magic number Key: ISPN-1948 URL: https://issues.jboss.org/browse/ISPN-1948 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.3.CR1 Reporter: Michal Linhard Assignee: Galder Zamarreño Here we have the good old "invalid magic number" problem again (JDG 6.0.0.ER5 testing): https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-RESILIENCE/... {code} 2012-03-26 15:18:43,524 253444 ERROR [org.jboss.smartfrog.edg.loaddriver.DriverNode] (Client-477:) Error doing PUT(key410977) to node node02 (lastOpTime 1 ms) org.infinispan.client.hotrod.exceptions.InvalidResponseException:: Invalid magic number. Expected 0xa1 and received 0x0 at org.infinispan.client.hotrod.impl.protocol.Codec10.readHeader(Codec10.java:92) at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:78) at org.infinispan.client.hotrod.impl.operations.AbstractKeyValueOperation.sendPutOperation(AbstractKeyValueOperation.java:72) at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:52) at org.infinispan.client.hotrod.impl.operations.PutOperation.executeOperation(PutOperation.java:41) at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:68) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.put(RemoteCacheImpl.java:219) at org.infinispan.CacheSupport.put(CacheSupport.java:52) at org.jboss.qa.edg.adapter.HotRodAdapter$HotRodRemoteCacheAdapter.put(HotRodAdapter.java:249) at org.jboss.qa.edg.adapter.HotRodAdapter$HotRodRemoteCacheAdapter.put(HotRodAdapter.java:234) at org.jboss.smartfrog.edg.loaddriver.DriverNodeImpl$ClientThread.makeRequest(DriverNodeImpl.java:244) at org.jboss.smartfrog.edg.loaddriver.DriverNodeImpl$ClientThread.run(DriverNodeImpl.java:375) {code} The exception repeats many times in the log and the "received" part of "Expected 0xa1 and received 0xXX" takes on different values. Also happens in both PUT and GET operations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

7
110
0 / 0

[JBoss JIRA] (ISPN-1978) Support configuration parsers in modules

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-1978: ------------------------------------- Summary: Support configuration parsers in modules Key: ISPN-1978 URL: https://issues.jboss.org/browse/ISPN-1978 Project: Infinispan Issue Type: Enhancement Components: Configuration Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.FINAL Modules (cache loaders, query, etc), should be able to provide their own configuration parsers (with specific schemas) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-1346) Transactional listeners method order problem

by Tomas Fecko (JIRA)

Transactional listeners method order problem -------------------------------------------- Key: ISPN-1346 URL: https://issues.jboss.org/browse/ISPN-1346 Project: Infinispan Issue Type: Bug Components: Listeners Affects Versions: 5.0.0.FINAL Environment: fedora, windows Reporter: Tomas Fecko Assignee: Manik Surtani I'm using listeners as from the @Listener javadoc examples. When I register listener on VM where the cache is and put items to it, the methods of my listener are called in this order: @TransactionRegistered startTransaction @CacheEntryCreated handleEvent @CacheEntryCreated handleEvent @TransactionCompleted endTransaction which is as it should be, but when I register listener on second node, and put to cache in first node, methods on listener on second node are called in order: handleEvent handleEvent startTransaction endTransaction -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

9
18
0 / 0

[JBoss JIRA] (ISPN-2034) Ass backwards serialization compatibility tests

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2034: -------------------------------------- Summary: Ass backwards serialization compatibility tests Key: ISPN-2034 URL: https://issues.jboss.org/browse/ISPN-2034 Project: Infinispan Issue Type: Enhancement Components: Marshalling Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.x, 5.2.0.ALPHA1, 5.2.0.FINAL Take each existing minor branch, i.e. 4.1.x, 4.0.x,...etc and modify VersionAwareMarshallerTest so that payloads are stored in a data file. Then, take data files for each branch and store in git (master and 5.1.x), and try reading them with the existing externalizer/marshalling set up. It should work... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
8
0 / 0

[JBoss JIRA] Created: (ISPN-750) Infinispan servers should be accessible via SSL sockets

by Galder Zamarreño (JIRA)

Infinispan servers should be accessible via SSL sockets ------------------------------------------------------- Key: ISPN-750 URL: https://jira.jboss.org/browse/ISPN-750 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA1, 5.1.0.Final Clients should be able to configure Hot Rod/Memcached servers for SSL access, in order to encrypt communications. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-800) Infinispan inside OSGI

by luca stancapiano (JIRA)

Infinispan inside OSGI ---------------------- Key: ISPN-800 URL: https://jira.jboss.org/browse/ISPN-800 Project: Infinispan Issue Type: Feature Request Components: Core API Affects Versions: 4.2.0.CR1 Reporter: luca stancapiano Assignee: Manik Surtani We need to import infinispan inside a OSGI repository. Tests are made with Felix. I added the configuration to use infinispan inside a osgi repository. We need to ignore all listed dependencies. With this configuration we can install infinispan-core.jar inside OSGI. Its achievement will be as a base installation here: https://github.com/flashboss/infinispan I added the Import-Package because you are forced to put manually in Felix all dependencies as jgroups, jboss marshalling, jcip, all apache commons. I've seen infinispan core working by default without all those libraries, so I think the same achievement should be replicated in OSGI. Inside the Import-Package tag I excluded those libraries so Infinispan core can be started in default mode without errors. If we want use the replication in OSGI, it is enough add manually the other packages (jgroups.jar etc etc) Actually the core bundle can be installed. But to be used it needs theese projects be installed as osgi bundles: jboss transaction api 1.0.1.GA (It is not yet a OSGI bundle. Waiting for a response to: https://jira.jboss.org/browse/JBEE-67) jgroups 2.10.1.GA (fixed in jgroups 1.12) river 1.2.3.GA marshalling-api 1.2.3.GA jboss common core 2.2.14.GA jboss logging spi 2.0.5.GA rhq plugin annotations 1.4.0.B01 i18nlog 1.0.9 log4j 1.2.16 We should make sure proper 'Import-Package' property is specified in the MANIFEST.MF so that: 1- it fails to load obviously when there's any missing bundles that are essential in using the very core functionality of Infinispan. 2 - it does not fail due to the dependency that is not really essential. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

6
61
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2012