December 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-360) create NodeJoined event

by Mircea Markus (JIRA)

create NodeJoined event ----------------------- Key: ISPN-360 URL: https://jira.jboss.org/jira/browse/ISPN-360 Project: Infinispan Issue Type: Feature Request Components: Listeners, State transfer Reporter: Mircea Markus Assignee: Manik Surtani In relation to http://community.jboss.org/message/529547#529547 It's an well known scenario to start a cluster, and only after the ENTIRE cluster is started to start and do work. Right now, we have CacheStarted and ViewChanged notifications. First only tells us that the local node is started but other nodes might still be in the process of starting. Second one tells us that the view has changed, but not that the cluster has started, i.e. the cache might be in the process of rebalancing state etc. A possible solution would be to have an NodeJoined event, that would be called whenever a new node finished joining the cluster. Finished joining means state transfer happened and that node is started. For a possible workaround to this feature see the forum post. -- 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

12 years, 11 months

4
12
0 / 0

[JBoss JIRA] Created: (ISPN-749) Infinispan servers should expose some stats over JMX

by Galder Zamarreño (JIRA)

Infinispan servers should expose some stats over JMX ---------------------------------------------------- Key: ISPN-749 URL: https://jira.jboss.org/browse/ISPN-749 Project: Infinispan Issue Type: Feature Request Components: Cache Server, JMX, reporting and management Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final Infinispan servers should expose some stats of their own, such as: amount of data read, amount of data written back to clients...etc. -- 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, 11 months

2
11
0 / 0

[JBoss JIRA] Created: (ISPN-530) Hot Rod client should load balance between different owners for a key

by Galder Zamarreno (JIRA)

Hot Rod client should load balance between different owners for a key --------------------------------------------------------------------- Key: ISPN-530 URL: https://jira.jboss.org/browse/ISPN-530 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Mircea Markus Fix For: 5.0.0.BETA1 While doing the demo for JUDCon, I realised that smart routing on the client side always choses the same node for the same key. IOW, assume you have k1 stored in nodes A, B and the cluster is formed of nodes A, B and C. Now, when the client figures out that the owner is A, any further requests on k1 will be sent to A. This has the possibility of overloading A. I think the client should, from the given list of owners of a key, do round robin between them for requests on the same key. -- 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, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-380) Be compliant with JBoss AS logging requirements

by Manik Surtani (JIRA)

Be compliant with JBoss AS logging requirements ----------------------------------------------- Key: ISPN-380 URL: https://jira.jboss.org/jira/browse/ISPN-380 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.CR1, 4.1.0.Final This (JBoss internal) document has details of standardised logging formats and codes, to enable easy i18n, etc. in future. https://docspace.corp.redhat.com/docs/DOC-30217 -- 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

2
16
0 / 0

[JBoss JIRA] Created: (ISPN-850) RemoteCache.replaceWithVersion javadoc is incorrect

by Galder Zamarreño (JIRA)

RemoteCache.replaceWithVersion javadoc is incorrect --------------------------------------------------- Key: ISPN-850 URL: https://issues.jboss.org/browse/ISPN-850 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.ALPHA1, 4.2.0.Final Reporter: Galder Zamarreño Assignee: Mircea Markus Priority: Minor Fix For: 5.0.0.BETA1, 5.0.0.Final replaceWithVersion javadoc is incorrect: /** * Removes the given value only if its version matches the supplied version. See {@link #removeWithVersion(Object, * long)} for a sample usage. * * @return true if the method has been replaced * @see #getVersioned(Object) * @see VersionedValue */ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-792) Migrate to David's JBoss Logging

by Galder Zamarreño (JIRA)

Migrate to David's JBoss Logging -------------------------------- Key: ISPN-792 URL: https://jira.jboss.org/browse/ISPN-792 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Manik Surtani Based on what David Lloyd said in the AS7 podcast, it performs much better than log4j and in particular, when it comes to log level checks (it apparently uses volatile int checks). This could have a direct impact on the Infinispan performance since we do a fair few level checks. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-559) refactor transaction class hierarchy

by Mircea Markus (JIRA)

refactor transaction class hierarchy ------------------------------------ Key: ISPN-559 URL: https://jira.jboss.org/browse/ISPN-559 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.0.0.Final Actual transactional logic should be implemented in InitiatorTransaction (vs RemoteTransaction) Rename TxXaAdapter should be renamed to TxCoordinator -- 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

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-561) Replace JOPR references with RHQ

by Galder Zamarreno (JIRA)

Replace JOPR references with RHQ -------------------------------- Key: ISPN-561 URL: https://jira.jboss.org/browse/ISPN-561 Project: Infinispan Issue Type: Task Components: JMX, reporting and management Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Fix For: 5.0.0.BETA1, 5.0.0.Final >From Heiko: Hi Galder, as we are slowly phasing out Jopr - could you for the Infinispan monitoring in the future use the term "RHQ plugin" (and link to http://rhq-project.org/ ) instead of the old "Jopr" term and link to JBoss.org/jopr ? Thanks Heiko -- 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

2
5
0 / 0

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2010