June 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2105) KeyAffinityServiceShutdownTest.testSimpleShutdown randomly fails

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2105: -------------------------------------- Summary: KeyAffinityServiceShutdownTest.testSimpleShutdown randomly fails Key: ISPN-2105 URL: https://issues.jboss.org/browse/ISPN-2105 Project: Infinispan Issue Type: Bug Components: Test Suite Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.2.0.ALPHA1 Attachments: testSimpleShutdown-0.log Fails with: testSimpleShutdown(org.infinispan.affinity.KeyAffinityServiceShutdownTest): expected:<false> but was:<true> See attached TRACE logs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
4
0 / 0

[JBoss JIRA] (ISPN-2115) Relative path in rhq ant task cause build to fail

by Thomas Fromm (JIRA)

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2058) Tree node move concurrency test broken

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2058: -------------------------------------- Summary: Tree node move concurrency test broken Key: ISPN-2058 URL: https://issues.jboss.org/browse/ISPN-2058 Project: Infinispan Issue Type: Bug Components: Tree API Affects Versions: 5.1.5.CR1, 5.1.4.FINAL Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.2.0.FINAL Attachments: treemove_infinispan.log NodeMoveAPITest.testConcurrency() is broken, see attached log. To summarise, when the concurrent moves begin, two threads are allowed to move, '/a/x' to '/d' and '/b'. The result is that 'x' appears under both '/b' and 'd' in the end. This test has been failing as early as https://infinispan.ci.cloudbees.com/job/Infinispan-5.1.x-JDK6-tcp/org.inf... but could have been failing from an earlier stage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
5
0 / 0

[JBoss JIRA] (ISPN-2109) OData for Infinispan

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-2109: ---------------------------------- Summary: OData for Infinispan Key: ISPN-2109 URL: https://issues.jboss.org/browse/ISPN-2109 Project: Infinispan Issue Type: Feature Request Reporter: Tomas Sykora Assignee: Tomas Sykora Infinispan allows clients to connect to the data grid over a RESTful protocol, as described here: https://docs.jboss.org/author/display/ISPN/Infinispan+REST+Server. However, the http://www.odata.org/ specification and API is an ideal, open, RESTful API for interacting with data stores. This student idea is to implement an alternative REST endpoint - similar to Infinispan's existing REST endpoint - that speaks ODATA, and to benchmark and test this endpoint using one or more ODATA clients publicly available on http://www.odata.org/libraries. This feature request will be used for my (tsykora's) diploma thesis on Masaryk University Faculty of Informatics, study branch: Service science, management and engineering. Martin Gencur is leader of my thesis. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

1
1
0 / 0

[JBoss JIRA] (ISPN-2088) NPE when using a particular DefaultCacheManager constructor

by Darrell Burgan (JIRA)

Darrell Burgan created ISPN-2088: ------------------------------------ Summary: NPE when using a particular DefaultCacheManager constructor Key: ISPN-2088 URL: https://issues.jboss.org/browse/ISPN-2088 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.5.FINAL Environment: Ubuntu 12.04, Java 1.6.0_27, Tomcat 5.5 Reporter: Darrell Burgan Assignee: Manik Surtani Priority: Minor In Infinispan 5.1.5, I'm experiencing a consistent NPE in the constructor in DefaultCacheManager at line 434 - DefaultCacheManager(String globalConfigurationFile, String defaultConfigurationFile, String namedCacheFile, boolean start), when the named cache file is specified. On line 447, it calls defineConfiguration(), which ultimately NPEs on line 974 because the globalComponentRegistry has not yet been created. If you look back at line 447, you can see that the globalComponentRegistry is created afterwards on line 450. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

4
7
0 / 0

[JBoss JIRA] (ISPN-1831) Cannot configure hotRodClientProperties programmatically.

by Paul Ferraro (JIRA)

Paul Ferraro created ISPN-1831: ---------------------------------- Summary: Cannot configure hotRodClientProperties programmatically. Key: ISPN-1831 URL: https://issues.jboss.org/browse/ISPN-1831 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.1.CR1 Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Critical Fix For: 5.1.1.FINAL Currently, there's no way to configure hotRotClientProperties programatically via the configuration API. Since there's no builder for a remote cache store, we need to use the generic one. hotRodClientProperties cannot be specified as a property, since it has no corresponding property editor, which is required when translating the CacheLoaderConfiguratoinBuilder to the legacy counterpart. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
8
0 / 0

[JBoss JIRA] (ISPN-2026) Test suite to allow easy customization of GlobalConfiguration

by Manik Surtani (JIRA)

Manik Surtani created ISPN-2026: ----------------------------------- Summary: Test suite to allow easy customization of GlobalConfiguration Key: ISPN-2026 URL: https://issues.jboss.org/browse/ISPN-2026 Project: Infinispan Issue Type: Enhancement Components: Test Suite Affects Versions: 5.1.4.FINAL Reporter: Manik Surtani Assignee: Mircea Markus Fix For: 5.1.x, 5.2.0.FINAL The test suite allows you to create caches easily using the {{createCluster()}} helper, which takes in a {{ConfigurationBuilder}} and a cluster size. This should be overloaded to allow the passing in of a {{GlobalConfigurationBuilder}} as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
3
0 / 0

[JBoss JIRA] (ISPN-2104) Add methods with java.util.concurrent.TimeUnit for specifying expiration intervals

by Samuli Saarinen (JIRA)

Samuli Saarinen created ISPN-2104: ------------------------------------- Summary: Add methods with java.util.concurrent.TimeUnit for specifying expiration intervals Key: ISPN-2104 URL: https://issues.jboss.org/browse/ISPN-2104 Project: Infinispan Issue Type: Feature Request Components: Configuration Reporter: Samuli Saarinen Assignee: Manik Surtani eg. {code:java} ConfigurationBuilder().expiration().lifespan(60000L) -> ConfigurationBuilder().expiration().lifespan(60, SECONDS) {code} This would make the interval unit more obvious. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

3
8
0 / 0

[JBoss JIRA] (ISPN-1999) Improve stability of testsuite

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1999: -------------------------------------- Summary: Improve stability of testsuite Key: ISPN-1999 URL: https://issues.jboss.org/browse/ISPN-1999 Project: Infinispan Issue Type: Enhancement Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.4.FINAL Work related to improving testsuite stability in order to avoid cache managers being left open. So far, this particularly affects the Hot Rod testsuite, but might be more changes needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

2
11
0 / 0

[JBoss JIRA] (ISPN-1890) Unable to create new native thread when running core/ testsuite

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-1890: -------------------------------------- Summary: Unable to create new native thread when running core/ testsuite Key: ISPN-1890 URL: https://issues.jboss.org/browse/ISPN-1890 Project: Infinispan Issue Type: Bug Components: Test Suite Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.1.2.FINAL Suddenly, running core/ testsuite only with -Xmx768m -XX:MaxPermSize=256M, I'm seeing: {code}Test suite progress: tests succeeded: 1695, failed: 4, skipped: 0. Exception in thread "ConnectionMap.Acceptor,null,null" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:658) at org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.start(TCPConnectionMap.java:568) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.start(TCPConnectionMap.java:411) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$600(TCPConnectionMap.java:354) at org.jgroups.blocks.TCPConnectionMap$ConnectionAcceptor.run(TCPConnectionMap.java:259) at java.lang.Thread.run(Thread.java:680) Exception in thread "ConnectionMap.Acceptor,null,null" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:658) at org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.start(TCPConnectionMap.java:568) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.start(TCPConnectionMap.java:411) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$600(TCPConnectionMap.java:354) at org.jgroups.blocks.TCPConnectionMap$ConnectionAcceptor.run(TCPConnectionMap.java:259) at java.lang.Thread.run(Thread.java:680) Exception in thread "ConnectionMap.Acceptor,null,null" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:658) at org.jgroups.blocks.TCPConnectionMap$TCPConnection$ConnectionPeerReceiver.start(TCPConnectionMap.java:568) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.start(TCPConnectionMap.java:411) at org.jgroups.blocks.TCPConnectionMap$TCPConnection.access$600(TCPConnectionMap.java:354) at org.jgroups.blocks.TCPConnectionMap$ConnectionAcceptor.run(TCPConnectionMap.java:259) at java.lang.Thread.run(Thread.java:680) [testng-TopologyAwareDistAsyncFuncTest] Test testPutIfAbsentFromNonOwner(org.infinispan.distribution.topologyaware.TopologyAwareDistAsyncFuncTest) succeeded. Test suite progress: tests succeeded: 1696, failed: 4, skipped: 0. [testng-TopologyAwareDistAsyncFuncTest] Test testRemoveFromNonOwner(org.infinispan.distribution.topologyaware.TopologyAwareDistAsyncFuncTest) succeeded. Test suite progress: tests succeeded: 1697, failed: 4, skipped: 0. [testng-TopologyAwareDistAsyncFuncTest] Test testReplaceFromNonOwner(org.infinispan.distribution.topologyaware.TopologyAwareDistAsyncFuncTest) succeeded. Test suite progress: tests succeeded: 1698, failed: 4, skipped: 0. Exception in thread "CacheViewTrigger,TopologyAwareDistAsyncFuncTest-NodeA-38647" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:658) at java.util.concurrent.ThreadPoolExecutor.addIfUnderMaximumPoolSize(ThreadPoolExecutor.java:727) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:657) at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:92) at org.infinispan.cacheviews.CacheViewsManagerImpl$ViewTriggerThread.run(CacheViewsManagerImpl.java:848){code} See attached thread dump. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 10 months

6
14
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2012