December 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2621) Introduce a wrapper for entries received via a RemoteCacheStore

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2621?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2621: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated with the optional dependency from infinispan-cachestore-remote to infinispan-server-hotrod. > Introduce a wrapper for entries received via a RemoteCacheStore > --------------------------------------------------------------- > > Key: ISPN-2621 > URL: https://issues.jboss.org/browse/ISPN-2621 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 5.2.0.Beta5 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.Beta6 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2606) RollingUpgradeSynchronizer should be accessible as an MBean

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-2606?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-2606: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated. > RollingUpgradeSynchronizer should be accessible as an MBean > ----------------------------------------------------------- > > Key: ISPN-2606 > URL: https://issues.jboss.org/browse/ISPN-2606 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 5.2.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2640) Design security functionality in Infinispan

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2640?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2640: -------------------------------- Description: This serves as a prerequisite for ISPN-143 which is to be implemented in 6.0. The task is about gathering the requirements, discussing them with the community and sum them up in a requirements document. OpenShift team should also be involved in defining the requirements for this. (was: This serves as a prerequisite for ISPN-143 which is to be implemented in 6.0. The task is about gathering the requirements, discussing them with the community and sum them up in a requirements document.) > Design security functionality in Infinispan > ------------------------------------------- > > Key: ISPN-2640 > URL: https://issues.jboss.org/browse/ISPN-2640 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 5.3.0.Final > > > This serves as a prerequisite for ISPN-143 which is to be implemented in 6.0. The task is about gathering the requirements, discussing them with the community and sum them up in a requirements document. OpenShift team should also be involved in defining the requirements for this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2597) All modules (except arquillian based ones) should use same surefire settings

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2597?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2597: ----------------------------------- Summary: All modules (except arquillian based ones) should use same surefire settings (was: HBase cache store testsuite should stop blocking CI jobs) Description: i.e. https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/941/co... The reason is so that they can run within the same Maven JVM and hence avoid issues in continuous integration where resource consumption is highly controlled. This meant several changes in Maven modules and restructuring HBase cache store so that it can run with sensible settings. ---- Old description: The "ERROR: Maven JVM terminated unexpectedly with exit code 137" error is normally associated with JVM running of memory. HBase has 'perftest' forkMode which means that it creates a new JVM per test. This is way too over the top for what it needs. Trying to run it with forkMode=none and paralell testsuite logs these errors: https://gist.github.com/4224569 This cache store shouldn't be blocking things, so disabling the cache store for the moment to be able to get on with other things. Anyone with Hadoop knowledge? was: i.e. https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/941/co... The "ERROR: Maven JVM terminated unexpectedly with exit code 137" error is normally associated with JVM running of memory. HBase has 'perftest' forkMode which means that it creates a new JVM per test. This is way too over the top for what it needs. Trying to run it with forkMode=none and paralell testsuite logs these errors: https://gist.github.com/4224569 This cache store shouldn't be blocking things, so disabling the cache store for the moment to be able to get on with other things. Anyone with Hadoop knowledge? > All modules (except arquillian based ones) should use same surefire settings > ---------------------------------------------------------------------------- > > Key: ISPN-2597 > URL: https://issues.jboss.org/browse/ISPN-2597 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hadoop > Fix For: 5.2.0.Beta6 > > > i.e. https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/941/co... > The reason is so that they can run within the same Maven JVM and hence avoid issues in continuous integration where resource consumption is highly controlled. > This meant several changes in Maven modules and restructuring HBase cache store so that it can run with sensible settings. > ---- > Old description: > The "ERROR: Maven JVM terminated unexpectedly with exit code 137" error is normally associated with JVM running of memory. > HBase has 'perftest' forkMode which means that it creates a new JVM per test. This is way too over the top for what it needs. > Trying to run it with forkMode=none and paralell testsuite logs these errors: https://gist.github.com/4224569 > This cache store shouldn't be blocking things, so disabling the cache store for the moment to be able to get on with other things. > Anyone with Hadoop knowledge? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2597) All modules (except arquillian based ones) should use same surefire settings

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-2597?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-2597: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/1527 > All modules (except arquillian based ones) should use same surefire settings > ---------------------------------------------------------------------------- > > Key: ISPN-2597 > URL: https://issues.jboss.org/browse/ISPN-2597 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hadoop > Fix For: 5.2.0.Beta6 > > > i.e. https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/941/co... > The reason is so that they can run within the same Maven JVM and hence avoid issues in continuous integration where resource consumption is highly controlled. > This meant several changes in Maven modules and restructuring HBase cache store so that it can run with sensible settings. > ---- > Old description: > The "ERROR: Maven JVM terminated unexpectedly with exit code 137" error is normally associated with JVM running of memory. > HBase has 'perftest' forkMode which means that it creates a new JVM per test. This is way too over the top for what it needs. > Trying to run it with forkMode=none and paralell testsuite logs these errors: https://gist.github.com/4224569 > This cache store shouldn't be blocking things, so disabling the cache store for the moment to be able to get on with other things. > Anyone with Hadoop knowledge? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2640) Design security functionality in Infinispan

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2640: ----------------------------------- Summary: Design security functionality in Infinispan Key: ISPN-2640 URL: https://issues.jboss.org/browse/ISPN-2640 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.3.0.Final This serves as a prerequisite for ISPN-143 which is to be implemented in 6.0. The task is about gathering the requirements, discussing them with the community and sum them up in a requirements document. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2639) Write an adaptor for the JSR 107 API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2639?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2639: -------------------------------- Description: This should be a new Infinispan maven module, implement the API and pass the TCK suite as defined here: https://github.com/jsr107 > Write an adaptor for the JSR 107 API > ------------------------------------ > > Key: ISPN-2639 > URL: https://issues.jboss.org/browse/ISPN-2639 > Project: Infinispan > Issue Type: Feature Request > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Final > > > This should be a new Infinispan maven module, implement the API and pass the TCK suite as defined here: https://github.com/jsr107 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2629) Dist Exec testsuite fails in case of TopologyAware nodes.

by Anna Manukyan (JIRA)

[ https://issues.jboss.org/browse/ISPN-2629?page=com.atlassian.jira.plugin.... ] Anna Manukyan commented on ISPN-2629: ------------------------------------- And the last test which is failing is: TopologyAwareTwoNodesMapReduceTest.testInvokemapperCancellation() which only fails, if the whole distexec testsuite is running. The failure is: testInvokeMapperCancellation(org.infinispan.distexec.mapreduce.TopologyAwareTwoNodesMapReduceTest) Time elapsed: 45.023 sec <<< FAILURE! org.testng.TestException: Expected exception java.util.concurrent.CancellationException but got java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-49858(test2) at org.testng.internal.Invoker.handleInvocationResults(Invoker.java:1503) at org.testng.internal.Invoker.invokeMethod(Invoker.java:764) at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) at org.testng.TestRunner.privateRun(TestRunner.java:767) at org.testng.TestRunner.run(TestRunner.java:617) at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.AssertionError: Mapper not cancelled, root cause org.jgroups.TimeoutException: timeout sending message to TopologyAwareTwoNodesMapReduceTest-NodeB-49858(test2) at org.infinispan.distexec.mapreduce.SimpleTwoNodesMapReduceTest.testInvokeMapperCancellation(SimpleTwoNodesMapReduceTest.java:106) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) ... 15 more I'm sorry for these different issues, but they all are connected to Dist Exec & Map Reduce for Topology Aware nodes. If necessary please let me know, I'll create separate issues in JIRA. > Dist Exec testsuite fails in case of TopologyAware nodes. > --------------------------------------------------------- > > Key: ISPN-2629 > URL: https://issues.jboss.org/browse/ISPN-2629 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Reporter: Anna Manukyan > Assignee: Vladimir Blagojevic > Attachments: DistributedExecutorWithTopologyAwareNodesTest.java, TEST-org.infinispan.distexec.DistributedExecutorWithTopologyAwareNodesTest.xml > > > Many tests from dist exec test suite fail in case of TopologyAware nodes. > It has been found that with both types of Cache configuration (old and new API), the issue appears. > You can find the test and the stacktraces attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-2639) Write an adaptor for the JSR 107 API

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2639: ----------------------------------- Summary: Write an adaptor for the JSR 107 API Key: ISPN-2639 URL: https://issues.jboss.org/browse/ISPN-2639 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 6.0.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (ISPN-375) Enable Hot Rod clients to start transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-375?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-375: ------------------------------- Fix Version/s: 5.3.0.Final (was: 6.0.0.Final) > Enable Hot Rod clients to start transactions > -------------------------------------------- > > Key: ISPN-375 > URL: https://issues.jboss.org/browse/ISPN-375 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Michael Musgrove > Priority: Blocker > Labels: hackathon > Fix For: 5.3.0.Final > > > It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only. > This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction. > Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2012