January 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-779) DefaultCacheManager.removeListener throwing NPE when server stopped

by Galder Zamarreño (JIRA)

DefaultCacheManager.removeListener throwing NPE when server stopped ------------------------------------------------------------------- Key: ISPN-779 URL: https://jira.jboss.org/browse/ISPN-779 Project: Infinispan Issue Type: Bug Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.CR1 I'm seeing a NPE when Memcached server shutdowns: Exception in thread "Thread-2" java.lang.RuntimeException: Exception encountered in shutting down the server at org.infinispan.server.core.ShutdownHook.run(Main.scala:239) Caused by: java.util.concurrent.ExecutionException: org.infinispan.CacheException: Unable to invoke method private void org.infinispan.transaction.xa.TransactionTable.stop() on object at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.infinispan.server.core.ShutdownHook.run(Main.scala:235) Caused by: org.infinispan.CacheException: Unable to invoke method private void org.infinispan.transaction.xa.TransactionTable.stop() on object at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:173) at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:861) at org.infinispan.factories.AbstractComponentRegistry.internalStop(AbstractComponentRegistry.java:709) at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:603) at org.infinispan.factories.ComponentRegistry.stop(ComponentRegistry.java:166) at org.infinispan.CacheDelegate.stop(CacheDelegate.java:325) at org.infinispan.manager.DefaultCacheManager.stop(DefaultCacheManager.java:521) at org.infinispan.server.core.ShutdownHook$$anon$5.call(Main.scala:230) at org.infinispan.server.core.ShutdownHook$$anon$5.call(Main.scala:226) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:170) ... 13 more Caused by: java.lang.NullPointerException at org.infinispan.manager.DefaultCacheManager.removeListener(DefaultCacheManager.java:541) at org.infinispan.transaction.xa.TransactionTable.stop(TransactionTable.java:87) ... 18 more The origin seems to be in ISPN-771 Maybe since transaction table now removes the listener, it needs to stop *before* the cache manager notifier does? -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
12
0 / 0

[JBoss JIRA] Created: (ISPN-659) Consider migrate from log4j to slf4j+logback

by Niktia Koksharov (JIRA)

Consider migrate from log4j to slf4j+logback -------------------------------------------- Key: ISPN-659 URL: https://jira.jboss.org/browse/ISPN-659 Project: Infinispan Issue Type: Feature Request Affects Versions: 4.2.0.ALPHA2 Reporter: Niktia Koksharov Assignee: Manik Surtani Please use slf4j module as logging component and logback. The author of log4j went on to write "logback" which is an implementation of slf4j that has much better performance than log4j and much cleaner output. Hibernate, EHCache have moved to SLF4j -- 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

13 years

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-471) HotRod client in Python

by Manik Surtani (JIRA)

HotRod client in Python ----------------------- Key: ISPN-471 URL: https://jira.jboss.org/browse/ISPN-471 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final C++ client impl for HotRod. Protocol is documented here: http://community.jboss.org/wiki/HotRodProtocol Could be based off the Java reference impl client: http://fisheye.jboss.org/browse/Infinispan/trunk/client/hotrod-client -- 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

13 years

1
6
0 / 0

[JBoss JIRA] Created: (ISPN-888) Support both Synchronization and XAResource for interacting with the TransactionManager

by Mircea Markus (JIRA)

Support both Synchronization and XAResource for interacting with the TransactionManager --------------------------------------------------------------------------------------- Key: ISPN-888 URL: https://issues.jboss.org/browse/ISPN-888 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 4.2.0.Final Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.0.0.Final This might be a configuration option on <transaction registerSynchronization="true" .../>. This would be false by default. Syncs have the advantage that TMs can optimise 2PC with a 1PC where only 1 XAResource is present. Useful when used as a simple cache in front of a DB. E.g., as a Hibernate second level cache: if the cache would register itself with the TM as a XAResource than at commit time, the TM would see two XAResources (cache and db) and would not be able to make this optimization. This means that it would write to disk tx logs - time consuming. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-221) Parse JPA-QL like DSL to generate Lucene Query objects for searching

by Manik Surtani (JIRA)

Parse JPA-QL like DSL to generate Lucene Query objects for searching -------------------------------------------------------------------- Key: ISPN-221 URL: https://jira.jboss.org/jira/browse/ISPN-221 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.GA This will allow people to use JPA-QL to build queries rather than Lucene query objects. Will probably use an Antlr grammar, possibly reuse stuff from Hibernate? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

4
17
0 / 0

[JBoss JIRA] Created: (ISPN-194) Finalise Query API based on tech preview in 4.0.0

by Manik Surtani (JIRA)

Finalise Query API based on tech preview in 4.0.0 ------------------------------------------------- Key: ISPN-194 URL: https://jira.jboss.org/jira/browse/ISPN-194 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA See ISPN-32 which is a tech preview of the query API. In addition to the dependencies set out in this JIRA, there is also a dependency on http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-397 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

3
11
0 / 0

[JBoss JIRA] Created: (ISPN-256) Enable Infinispan SPIs to implement their own commands

by Galder Zamarreno (JIRA)

Enable Infinispan SPIs to implement their own commands ------------------------------------------------------ Key: ISPN-256 URL: https://jira.jboss.org/jira/browse/ISPN-256 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Much nicer IMHO would be a nice SPI / plug point to allow applications to extend the set of commands. Let an app create an ExtensionCommand; if that comes in off the channel pass it off to the handler the application registered. This could for example be used instead of the solution currently used in http://opensource.atlassian.com/projects/hibernate/browse/HHH-3818. In HHH-3818, the cache is used as a notification vehicle which is a bit of a hack and has some limitations for example when trying to implement a similar solution for evict(key) op. Another use case for it would be HTTP session ownership, from Brian Stansberry: (09:32:09 AM) brian_stansberry: ... it's just that only 1 server at a time s/b able to use a session (09:32:25 AM) brian_stansberry: so on failover i send an extension command requesting ownership (09:33:19 AM) brian_stansberry: there's actually a servlet spec requirement that only one server at a time access a session (09:33:23 AM) brian_stansberry: ejb spec too (09:33:37 AM) brian_stansberry: we don't properly handle that ... (09:34:18 AM) brian_stansberry: basically it's a lock ... (09:34:35 AM) brian_stansberry: that's all it is, a distributed lock (09:35:03 AM) brian_stansberry: but once you have the distributed lock it's yours until you give it up (09:35:29 AM) brian_stansberry: so once 1 request acquires it, subsequent requests to same server can just use a local lock ... (09:41:59 AM) brian_stansberry: the key thing is there should only be a cluster-wide operation once per session (09:42:11 AM) brian_stansberry: unless there is failover -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
13
0 / 0

[JBoss JIRA] Created: (ISPN-272) recover from transaction failures

by Mircea Markus (JIRA)

recover from transaction failures --------------------------------- Key: ISPN-272 URL: https://jira.jboss.org/jira/browse/ISPN-272 Project: Infinispan Issue Type: Feature Request Components: Transactions Affects Versions: 5.0.0.GA Reporter: Mircea Markus Assignee: Manik Surtani We currently don't support any sort of recovery from transaction failures. E.g. tm.start(); database.delete(account); ispnCache.put(account); tm.commit(): At tm commit: -prepare is successful on both enlisted resources. - database.commit - fails What shall we do with the locks/state from ispnCache. Possible solutions: - configure to automatically commit/rollback after a timeout - keep locks on resources and allow manual intervention through JMX - others? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

4
19
0 / 0

[JBoss JIRA] Created: (ISPN-748) provide an API to expose core operations omitting return values as safe alternative to Flags

by Sanne Grinovero (JIRA)

provide an API to expose core operations omitting return values as safe alternative to Flags -------------------------------------------------------------------------------------------- Key: ISPN-748 URL: https://jira.jboss.org/browse/ISPN-748 Project: Infinispan Issue Type: Feature Request Components: Core API Reporter: Sanne Grinovero Assignee: Manik Surtani Priority: Minor Fix For: 5.0.0.BETA1, 5.0.0.Final On mailing list we discussed the possibility to provide the same methods as defined by Map but omitting return values. This would be useful for those cases in which return values are not needed, so that Infinispan can enable all possible optimizations to disregard retrieveing an appropriate return value. Several alternatives where proposed, and there's also an interesting proposal to do the same relating to async methods, and the combination of async+noReturn A suggestion: cache.noReturnValue().remote(K); //returns void and enables both flags SKIP_CACHE_LOAD and SKIP_REMOTE_LOOKUP. The advantage is that people refactoring code don't have to remember to adjust flags according to using the return value or not, or would at least get a compiler error in case of abuse of method; also Infinispan might introduce more optimizations in future and apply them without code changes for new flags arising. See all discussion started by: http://lists.jboss.org/pipermail/infinispan-dev/2010-October/006484.html -- 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

13 years, 1 month

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-706) Enable Hot Rod server caches to be accessed without extra marshalling

by Galder Zamarreño (JIRA)

Enable Hot Rod server caches to be accessed without extra marshalling --------------------------------------------------------------------- Key: ISPN-706 URL: https://jira.jboss.org/browse/ISPN-706 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final People are starting to ask for this: Write to Hot Rod remotely and then being able to retrieve objects from the server side cache without any extra steps. At the moment, a marshalling layer is necessary so that those byte[] are converted into objects. -- 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

13 years, 1 month

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2011