November 2009 - infinispan-issues

[JBoss JIRA] Created: (ISPN-261) Cachemanager instantiated in different threads in same JVM don't interact

by Sanne Grinovero (JIRA)

Cachemanager instantiated in different threads in same JVM don't interact ------------------------------------------------------------------------- Key: ISPN-261 URL: https://jira.jboss.org/jira/browse/ISPN-261 Project: Infinispan Issue Type: Bug Components: Locking and Concurrency Affects Versions: 4.0.0.CR1 Environment: both Sun JDK 6u16 and IcedTea, on both Fedora 11 64 bit and Ubuntu 9.10 64bit Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.0.0.CR2 When I create several cachemanagers in clustered mode in the same thread, they will join and share the cluster view. If I try to create cachemanagers configured the same way in different threads, they will not join. Attaching demo code with a workaround. -- 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

14 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-280) Lucene testsuite endlessly looping

by Galder Zamarreno (JIRA)

Lucene testsuite endlessly looping ---------------------------------- Key: ISPN-280 URL: https://jira.jboss.org/jira/browse/ISPN-280 Project: Infinispan Issue Type: Bug Components: Lucene Directory Reporter: Galder Zamarreno Assignee: Sanne Grinovero Fix For: 4.0.0.GA I just ran the testsuite and the lucene testsuite seems to reach an endless loop. Please find attached 3 thread dumps taken while my CPU was at 100%. Sanne, could you please have a look to it? -- 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

14 years, 4 months

3
5
0 / 0

[JBoss JIRA] Commented: (ISPN-58) Create a TaskQueueExecutorFactory and TaskQueueScheduledExecutorFactory

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-58?page=com.atlassian.jira.plugin... ] Vladimir Blagojevic commented on ISPN-58: ----------------------------------------- How are we going to implement service behind this URI? Is it going to be a servlet that runs submitted Runnable/Callable? > Create a TaskQueueExecutorFactory and TaskQueueScheduledExecutorFactory > ----------------------------------------------------------------------- > > Key: ISPN-58 > URL: https://jira.jboss.org/jira/browse/ISPN-58 > Project: Infinispan > Issue Type: Sub-task > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.1.0.BETA1, 4.1.0.GA > > > These executors will not spawn separate threads, but hook in to Google's TaskQueue API > http://code.google.com/appengine/docs/java/taskqueue/overview.html > This will enable Infinispan to run without spawning any additional threads, thereby enabling it to run on Google's App Engine runtime. > Will need to expose a URI (/taskqueueexecutor ?) which is invoked to process arbitrary Callable/Runnables. May need to use the DataStore to store the actual Callable/Runnable, and pass the taskqueueexecutor the key of the stored object. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-39) Distributed executors

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-39?page=com.atlassian.jira.plugin... ] Manik Surtani commented on ISPN-39: ----------------------------------- Perhaps look at the JDK7 fork/join API, perhaps provide a "smart" distributed Fork/Join impl. distributing tasks according to data requirements. A nicer API for map/reduce. > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://jira.jboss.org/jira/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 5.1.0.BETA1, 5.1.0.GA > > > A new API to allow users to provide a Runnable/Callable and a set of keys to run this on, and the ability to move the code to where the data is and execute it there, returning results (if any) across a network. -- 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

14 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-274) Interactive demo of Lucene Directory

by Sanne Grinovero (JIRA)

Interactive demo of Lucene Directory ------------------------------------ Key: ISPN-274 URL: https://jira.jboss.org/jira/browse/ISPN-274 Project: Infinispan Issue Type: Task Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 4.0.0.CR2 Create a simple demo to show off the Lucene clustering capabilities -- 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

14 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-265) Show Jopr percentages properly

by Galder Zamarreno (JIRA)

Show Jopr percentages properly ------------------------------ Key: ISPN-265 URL: https://jira.jboss.org/jira/browse/ISPN-265 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 4.0.0.CR1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR2 I need to confirm this but I believe, based on information heiko passed me, that percentages need to be returned as doubles between 0..1 -- 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

14 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-267) Change Infinispan cache manager jmx name to be hostname:<jmx-port> based

by Galder Zamarreno (JIRA)

Change Infinispan cache manager jmx name to be hostname:<jmx-port> based ------------------------------------------------------------------------ Key: ISPN-267 URL: https://jira.jboss.org/jira/browse/ISPN-267 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 4.0.0.CR1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR2 <galderz> until now, i had named the CacheManager in jopr as: global-jmx-domain@address <galderz> this is a bit of pain because the address changes everytime you restart infinispan <galderz> but jopr does not realise this and considers an infinispan started in same jmx port in same address to be the same <galderz> so, when you restart, u see infinispan cache manager in jopr but it has the wrong name, this will be confusing <galderz> heiko told me this is a limitation of the jopr <galderz> on top of that, if u wanna do things correctly and import the new cache manager, u need to delete the old one, let auto discovery run and get the new one <galderz> and then you're back to your starting point, so if had tweaked any scheduling options in the previous infinispan instance, you're back to defaults <galderz> so, i'm gonna change this name to simply be: global-jmx-domain(a)InetAddress.getLocalHost().getHostName():<jmx:port> <galderz> that way we'll avoid this confusion and you can always get the address from the RpcManager, so not big deal -- 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

14 years, 5 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-268) Enhance the plugin so that Infinispan instances can be added manually

by Galder Zamarreno (JIRA)

Enhance the plugin so that Infinispan instances can be added manually --------------------------------------------------------------------- Key: ISPN-268 URL: https://jira.jboss.org/jira/browse/ISPN-268 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR2 Enhance the plugin so that Infinispan instances can be added manually. This is necessary in order to support monitoring of multiple Infinispan instances in the same host. -- 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

14 years, 5 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-259) Verify whether JBCACHE-1555 affects Infinispan

by Galder Zamarreno (JIRA)

Verify whether JBCACHE-1555 affects Infinispan ---------------------------------------------- Key: ISPN-259 URL: https://jira.jboss.org/jira/browse/ISPN-259 Project: Infinispan Issue Type: Task Components: Locking and Concurrency Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR2 Verify whether JBCACHE-1555 affects Infinispan. -- 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

14 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-193) Allow QueryInterceptor to be picked up from config.xml

by Navin Surtani (JIRA)

Allow QueryInterceptor to be picked up from config.xml ------------------------------------------------------ Key: ISPN-193 URL: https://jira.jboss.org/jira/browse/ISPN-193 Project: Infinispan Issue Type: Feature Request Components: Querying Reporter: Navin Surtani Assignee: Navin Surtani Fix For: 4.1.0.BETA1 Allow the QueryInterceptor within the query module to be picked up from the xml configuration. This way the temporary class QueryHelper will not be needed. -- 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

14 years, 5 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2009