June 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2089) Transactional distributed shared cache store not working

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2089: -------------------------------------- Summary: Transactional distributed shared cache store not working Key: ISPN-2089 URL: https://issues.jboss.org/browse/ISPN-2089 Project: Infinispan Issue Type: Bug Components: Distributed Cache, Loaders and Stores, Transactions Affects Versions: 5.1.5.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Critical Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL This test fails: {code}public class DistSyncTxCacheStoreSharedTest extends BaseDistCacheStoreTest { public DistSyncTxCacheStoreSharedTest() { sync = true; tx = true; testRetVals = true; shared = true; INIT_CLUSTER_SIZE = 2; numOwners = 1; } public void testPutFromNonOwner() throws Exception { Cache<Object, String> cacheX = getFirstNonOwner("key1"); CacheStore storeX = TestingUtil.extractComponent( cacheX, CacheLoaderManager.class).getCacheStore(); cacheX.put("key1", "v1"); assertEquals("v1", cacheX.get("key1")); assertNotNull(storeX.load("key1")); assertEquals("v1", storeX.load("key1").getValue()); } }{code} -- 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, 8 months

4
5
0 / 0

[JBoss JIRA] (ISPN-1564) Make configuration extensible by non-core modules

by Sanne Grinovero (Created) (JIRA)

Make configuration extensible by non-core modules ------------------------------------------------- Key: ISPN-1564 URL: https://issues.jboss.org/browse/ISPN-1564 Project: Infinispan Issue Type: Enhancement Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 5.2.0.FINAL We should think about using generic java/xsd namespaces and have secondary modules define their own specific elements. A good use case is the Query module: indexing requires many options, some of them are currently defined in the core configuration. Other users might be the various properties of the cacheloader implementations: jdbc comes to mind as one which doesn't look very nice to configure. -- 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, 8 months

4
3
0 / 0

[JBoss JIRA] (ISPN-2063) Remove workaround to handle null commands when channel stops before cache manager

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2063: -------------------------------------- Summary: Remove workaround to handle null commands when channel stops before cache manager Key: ISPN-2063 URL: https://issues.jboss.org/browse/ISPN-2063 Project: Infinispan Issue Type: Task Components: Marshalling Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL Revert ISPN-2025 when AS7-3180 is done. -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] (ISPN-1541) NotifyingNotifiableFuture's FutureListener can not invoke Future API on FutureListener#futureDone callback

by Vladimir Blagojevic (Created) (JIRA)

NotifyingNotifiableFuture's FutureListener can not invoke Future API on FutureListener#futureDone callback ---------------------------------------------------------------------------------------------------------- Key: ISPN-1541 URL: https://issues.jboss.org/browse/ISPN-1541 Project: Infinispan Issue Type: Bug Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Invoking Future#get from a FutureListener attached to a NotifyingNotifiableFuture passed as a parameter to RpcManager#invokeRemotelyInFuture throws InterruptedException! -- 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, 9 months

6
15
0 / 0

[JBoss JIRA] Created: (ISPN-1336) Infinispan core fails to build with JDK 7

by Radoslav Husar (JIRA)

Infinispan core fails to build with JDK 7 ----------------------------------------- Key: ISPN-1336 URL: https://issues.jboss.org/browse/ISPN-1336 Project: Infinispan Issue Type: Bug Components: Build process Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Java version: 1.7.0, vendor: Oracle Corporation Reporter: Radoslav Husar Assignee: Manik Surtani "Or is it just me?" {code} [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project infinispan-core: Compilation failure [ERROR] error: Cannot read org.infinispan.util.logging package files, cause : java.io.FileNotFoundException: org.infinispan.util.logging/Log [ERROR] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (default-compile) on project infinispan-core: Compilation failure error: Cannot read org.infinispan.util.logging package files, cause : java.io.FileNotFoundException: org.infinispan.util.logging/Log at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure error: Cannot read org.infinispan.util.logging package files, cause : java.io.FileNotFoundException: org.infinispan.util.logging/Log at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:656) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more {code} Trying on master, last commit was commit e81e8a63fd68b85bc20b3304d62cc5fdcd75f327 Author: Galder Zamarreño Date: Fri Aug 12 13:35:50 2011 +0200 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

2
5
0 / 0

[JBoss JIRA] (ISPN-1794) change default minIdle attribute for hot rod client

by Michal Linhard (JIRA)

Michal Linhard created ISPN-1794: ------------------------------------ Summary: change default minIdle attribute for hot rod client Key: ISPN-1794 URL: https://issues.jboss.org/browse/ISPN-1794 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.1.0.FINAL Reporter: Michal Linhard Assignee: Mircea Markus Priority: Minor This is just a proposal, feel free to reject. Default behaviour in PropsKeyedObjectPoolFactory is minIdle = 1 timeBetweenEvictionRunsMillis = 2min i.e. after 2minutes of idle RemoteCacheManager will try to ensure at least one connection and will try to create one. This might be a surprise for user to get this WARNING without doing anything: {code} 2012-01-26 15:05:00,816 138699 WARN [org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport] (Timer-1:) ISPN004008: Could not connect to server: test1/192.168.11.101:11222 java.net.ConnectException: Connection refused at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:567) at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:100) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:80) at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:57) at org.apache.commons.pool.impl.GenericKeyedObjectPool.addObject(GenericKeyedObjectPool.java:1668) at org.apache.commons.pool.impl.GenericKeyedObjectPool.ensureMinIdle(GenericKeyedObjectPool.java:2038) at org.apache.commons.pool.impl.GenericKeyedObjectPool.ensureMinIdle(GenericKeyedObjectPool.java:2003) at org.apache.commons.pool.impl.GenericKeyedObjectPool.access$1600(GenericKeyedObjectPool.java:203) at org.apache.commons.pool.impl.GenericKeyedObjectPool$Evictor.run(GenericKeyedObjectPool.java:2282) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) {code} of course it's easy to change this via "minIdle" property, I just think this is a strange default and IMHO it should be 0 instead of 1. WDYT? -- 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, 9 months

6
18
0 / 0

[JBoss JIRA] (ISPN-2140) Ping should try all servers in server list.

by Michal Linhard (JIRA)

Michal Linhard created ISPN-2140: ------------------------------------ Summary: Ping should try all servers in server list. Key: ISPN-2140 URL: https://issues.jboss.org/browse/ISPN-2140 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.1.5.FINAL Reporter: Michal Linhard Assignee: Manik Surtani I'm not sure whether this is a bug or freature request. Currently the ping operation that's supposed to fetch topology to the hot rod client simply fails when it tries to fetch from a non-functional server in the server list. It should retry on failure, similar to other cache operations. The documented purpose of the infinispan.client.hotrod.ping_on_startup parameter would be something in the line with: finds the first working server in the server list and obtains the topology information from it. -- 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, 9 months

5
17
0 / 0

[JBoss JIRA] (ISPN-2102) JDBC cacheloader test failing frequently: assertNoLocksHeld

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2102: ------------------------------------- Summary: JDBC cacheloader test failing frequently: assertNoLocksHeld Key: ISPN-2102 URL: https://issues.jboss.org/browse/ISPN-2102 Project: Infinispan Issue Type: Task Components: Loaders and Stores Reporter: Sanne Grinovero Assignee: Mircea Markus Priority: Minor Fix For: 5.2.0.ALPHA1 There are two of them which fail periodically as reported on: https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp/org.in... Someone familiar with them should review and decide to either improve them or disable them. -- 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, 9 months

4
9
0 / 0

[JBoss JIRA] (ISPN-2120) Duplicate counts for some stats

by Galder Zamarreño (JIRA)

11 years, 9 months

4
11
0 / 0

[JBoss JIRA] (ISPN-2117) VersionedReplStateTransferTest.testStateTransfer is unstable

by Galder Zamarreño (JIRA)

11 years, 9 months

4
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2012