November 2010 - infinispan-issues

[JBoss JIRA] Created: (ISPN-651) Document Infinispan tree module

by Galder Zamarreño (JIRA)

Document Infinispan tree module ------------------------------- Key: ISPN-651 URL: https://jira.jboss.org/browse/ISPN-651 Project: Infinispan Issue Type: Task Components: Tree API Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.Final See dev list thread. -- 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, 5 months

1
5
0 / 0

[JBoss JIRA] Created: (ISPN-751) Infinispan release reporting itself as a SNAPSHOT in logs

by Paul Ferraro (JIRA)

Infinispan release reporting itself as a SNAPSHOT in logs --------------------------------------------------------- Key: ISPN-751 URL: https://jira.jboss.org/browse/ISPN-751 Project: Infinispan Issue Type: Bug Affects Versions: 4.2.0.ALPHA5 Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Minor Using infinispan-core-4.2.0.ALPHA5, I see the following in the logs: 2010-10-29 12:20:39,557 INFO [org.infinispan.factories.GlobalComponentRegistry] (RMI TCP Connection(6)-127.0.0.1) Infinispan version: Infinispan 'Ursus' 4.2.0.SNAPSHOT It seems the release was built prior to tagging/labelling? While this is trivial - it is definitely something you'll want to fix before the final release. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (ISPN-752) ClassCastException during rehash if join RPC has any exceptional responses

by Paul Ferraro (JIRA)

ClassCastException during rehash if join RPC has any exceptional responses -------------------------------------------------------------------------- Key: ISPN-752 URL: https://jira.jboss.org/browse/ISPN-752 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.2.0.ALPHA5 Reporter: Paul Ferraro Assignee: Manik Surtani JoinTask.updateTopologyInfo(...) assumes all responses from a JOIN_REHASH_START will be SuccessfulResponse's. ExceptionResponse's are not handled and cause a CCE. org.infinispan.CacheException: Caught exception invoking method public void org.jboss.web.tomcat.service.session.distributedcache.ispn.DistributedCacheManager$ViewChangeListener.viewChanged(org.infinispan.notifications.cachemanagerlistener.event.ViewChangedEvent) on listener instance org.jboss.web.tomcat.service.session.distributedcache.ispn.DistributedCacheManager$ViewChangeListener@69408a75 at org.infinispan.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:179) 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:619) Caused by: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.distribution.DistributionManagerImpl.waitForJoinToComplete() throws java.lang.Throwable 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.internalStart(AbstractComponentRegistry.java:680) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:582) at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:148) at org.infinispan.CacheDelegate.start(CacheDelegate.java:317) at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:493) at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:437) at org.jboss.web.tomcat.service.session.distributedcache.ispn.DistributedCacheManager.getJvmRouteCache(DistributedCacheManager.java:152) at org.jboss.web.tomcat.service.session.distributedcache.ispn.DistributedCacheManager$ViewChangeListener.viewChanged(DistributedCacheManager.java:564) 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.notifications.AbstractListenerImpl$ListenerInvocation$1.run(AbstractListenerImpl.java:175) ... 3 more 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) ... 17 more Caused by: org.infinispan.CacheException: Unexpected exception at org.infinispan.distribution.JoinTask.performRehash(JoinTask.java:145) at org.infinispan.distribution.RehashTask.call(RehashTask.java:53) at org.infinispan.distribution.RehashTask.call(RehashTask.java:33) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) ... 3 more Caused by: java.lang.ClassCastException: org.infinispan.remoting.responses.ExceptionResponse cannot be cast to org.infinispan.remoting.responses.SuccessfulResponse at org.infinispan.distribution.JoinTask.updateTopologyInfo(JoinTask.java:158) at org.infinispan.distribution.JoinTask.performRehash(JoinTask.java:106) -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (ISPN-756) NullPointerException during rehash

by Scott Marlow (JIRA)

NullPointerException during rehash ---------------------------------- Key: ISPN-756 URL: https://jira.jboss.org/browse/ISPN-756 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.2.0.ALPHA5 Reporter: Scott Marlow Assignee: Manik Surtani Fix For: 4.2.0.Final NullPointerException occurs from a org.infinispan.distribution.JoinTask.performRehash Error exception link (let me know if I should paste here next time) http://pastebin.com/E237tmY8 This is happening for me locally and appears to be timing related. I'm trying to understand why (current AS6 testsuite) SessionCountUnitTestCase is failing on hudson, so I have been adding debug logging in various places to gain more understanding. This changes the timing it seems and I get the NPE. The AS test source is at https://anonsvn.jboss.org/repos/jbossas/trunk/testsuite/src/main/org/jbos... and the test is testReplicatedRedeploy. The hudson link (shows a timeout error) is (in case there is interest in seeing the failure we are trying to chase down): https://hudson.jboss.org/hudson/job/JBoss-AS-6.0.x-testSuite-sun16/932/te... -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-759) ClassCastException at the start of 5 nodes cluster

by Jacek Gerbszt (JIRA)

ClassCastException at the start of 5 nodes cluster -------------------------------------------------- Key: ISPN-759 URL: https://jira.jboss.org/browse/ISPN-759 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.0.BETA1 Reporter: Jacek Gerbszt Assignee: Manik Surtani During the start of a cluster containing 5 nodes of HotRod Server, I receive a couple of warnings like this: 2010-11-04 13:55:06,721 WARN [org.infinispan.remoting.InboundInvocationHandlerImpl] (OOB-7,wp-334) Cache named [___defaultcache] exists but isn't in a state to handle invocations. Its state is INSTANTIATED. 2010-11-04 13:55:06,722 WARN [org.infinispan.remoting.InboundInvocationHandlerImpl] (OOB-6,wp-334) Cache named [___defaultcache] exists but isn't in a state to handle invocations. Its state is INSTANTIATED. And eventually an exception: 2010-11-04 13:56:19,199 ERROR [org.infinispan.distribution.JoinTask] (Rehasher-wp-334) Caught exception! java.lang.ClassCastException: org.infinispan.remoting.responses.RequestIgnoredResponse cannot be cast to org.infinispan.remoting.responses.SuccessfulResponse at org.infinispan.distribution.JoinTask.updateTopologyInfo(JoinTask.java:162) at org.infinispan.distribution.JoinTask.broadcastNewCh(JoinTask.java:157) at org.infinispan.distribution.JoinTask.performRehash(JoinTask.java:103) at org.infinispan.distribution.RehashTask.call(RehashTask.java:53) at org.infinispan.distribution.RehashTask.call(RehashTask.java:33) 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:619) By the way, I'm trying to answer the question - is it possiblle to start mid size cluster (let's say 20 nodes) at once - every node at the very same time. Have you ever tried this scenario? -- 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, 5 months

2
3
0 / 0

[JBoss JIRA] Commented: (ISPN-24) JPA-like interface to Infinispan

by Darren Bell (JIRA)

[ https://jira.jboss.org/browse/ISPN-24?page=com.atlassian.jira.plugin.syst... ] Darren Bell commented on ISPN-24: --------------------------------- This is great news. What we're invisioning is a way to slot Infinispan between HIbernate and our app. So, Hibernate would be the Cachestore if possible and we'd use JPA-like constructs to query and persist objects. This would then enable a JPA-like distributed write-behind data grid using JPA objects. Good stuff. > JPA-like interface to Infinispan > -------------------------------- > > Key: ISPN-24 > URL: https://jira.jboss.org/browse/ISPN-24 > Project: Infinispan > Issue Type: Feature Request > Components: Fine-grained API > Reporter: Manik Surtani > Assignee: Emmanuel Bernard > Priority: Blocker > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A replacement for POJO Cache, to provide fine-grained replication. > But also to provide a familiar API which folks can use to migrate stuff off traditional DB-centric apps. > Would use Infinispan AtomicMaps under the covers. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-744) A cloned configuration object should not inherit component status from parent object

by Paul Ferraro (JIRA)

A cloned configuration object should not inherit component status from parent object ------------------------------------------------------------------------------------ Key: ISPN-744 URL: https://jira.jboss.org/browse/ISPN-744 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.2.0.ALPHA4 Reporter: Paul Ferraro Priority: Minor If I clone the GlobalConfiguration from a running cache manager and attempt setTransportProperties(...) on the cloned object, I get a ConfigurationException indicating that I cannot modify a non-dynamic configuration element of a started component. I would expect that a cloned config would be disconnected and would not inherit the component status of its parent object. -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-739) Change default Hot Rod port to 11222

by Galder Zamarreño (JIRA)

Change default Hot Rod port to 11222 ------------------------------------ Key: ISPN-739 URL: https://jira.jboss.org/browse/ISPN-739 Project: Infinispan Issue Type: Task Components: Cache Server Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.BETA1, 4.2.0.Final This is essentially to avoid issues with different port configurations in AS, where the offset between diff ports is 100. Make sure wikis and documentation are updated accordingly. galderz: hi manik [1:31pm] manik: galderz: yo [1:31pm] manik: whassup? [1:31pm] galderz: hey, i've just spotted one thing [1:31pm] galderz: we've defined memcached and hot rod default ports as: 11211 and 11311 [1:31pm] manik: yes [1:32pm] galderz: now, AS uses an offset to define ports for different port settings: ports-default, port-01...etc [1:32pm] galderz: and the offset is 100 [1:32pm] galderz: so, it means that when you use ports-01, your ports are: 11311 and 11411 [1:32pm] galderz: that could confuse things up cos you old default hot rod protocol would now be a memcached port [1:33pm] manik: Yep. [1:33pm] galderz: i was wondering whether we should do something to avoid this [1:33pm] manik: What do you reckon? Configure Hot Rod to listen on 11221 ? [1:33pm] galderz: it could lead to issues [1:34pm] manik: 11222 ? [1:34pm] galderz: yeah, one of those [1:34pm] galderz: we don't wanna change the default memcached port -- 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, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-675) Make Infinispan JOPR plugin friendly with AS environments

by Galder Zamarreño (JIRA)

Make Infinispan JOPR plugin friendly with AS environments --------------------------------------------------------- Key: ISPN-675 URL: https://jira.jboss.org/browse/ISPN-675 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.CR1 Within the descriptor: - Change top level from server to service - Within the service add: <parent-resource-type name="JMX Server" plugin="JMX"/> <parent-resource-type name="JBossAS Server" plugin="JBossAS"/> <parent-resource-type name="JBossAS Server" plugin="JBossAS5"/> Within source: - From "implements ResourceComponent" should convert into "extend MBeanResourceComponent" (like StatisticsComponent) - You might be able to reduce the code with the above change Base your work on what has been done in: https://svn.jboss.org/repos/jopr/trunk/modules/plugins/hibernate Test: - Test with AS6 admin console (drop the plugin jar into the plugins subdirectory in the admin console) - Test with RHQ -- 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, 5 months

3
13
0 / 0

[JBoss JIRA] Created: (ISPN-746) In Memcached, implement 250 character key check

by Galder Zamarreño (JIRA)

In Memcached, implement 250 character key check ----------------------------------------------- Key: ISPN-746 URL: https://jira.jboss.org/browse/ISPN-746 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.2.0.ALPHA4, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 4.2.0.BETA1, 4.2.0.Final Memcached protocol has a limit of 250 characters in the size of keys. We should implement this check as well. -- 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, 5 months

1
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2010