November 2012 - infinispan-issues

[JBoss JIRA] (ISPN-2062) CrashedMemberDetectorListener should check whether invocations are allowed

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2062: -------------------------------------- Summary: CrashedMemberDetectorListener should check whether invocations are allowed Key: ISPN-2062 URL: https://issues.jboss.org/browse/ISPN-2062 Project: Infinispan Issue Type: Enhancement Components: Cache Server Affects Versions: 5.1.5.CR1, 5.1.4.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.5.FINAL Instead of just checking whether the cache is terminated, since this check misses other situations such as stopping. -- 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

12 years

3
8
0 / 0

[JBoss JIRA] (ISPN-2081) Transaction leak caused by reordering between prepare and commit

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2081: ----------------------------------- Summary: Transaction leak caused by reordering between prepare and commit Key: ISPN-2081 URL: https://issues.jboss.org/browse/ISPN-2081 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.1.5.FINAL Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL Attachments: RollbackNotSentBeforePrepareTest.java There's no ordering between the prepare and commit/rollback messages, as the later are sent OOB. With this in mind, the following transaction leak might happen: Tx1 send prepare on nodes {A,B} 1. the message reaches A and timeouts but hasn't yet been processed on B 2. The transaction originator reacts immediately to the timeout received from A without waiting the response from B and sends a rollback request 3. The rollback request is processed on A and B 4. The initial prepare is then processed on B At this point we have an orphan transaction prepare on B. Whilst this is not causing any inconsistencies, it keeps keys locked indefinitely and is a memory leak. The solution would be to wait at 2 for all the prepare messages *before* sending the rollback. Attached is a unit test to reproduce the issue. Related mailing list thread: http://infinispan.markmail.org/search/#query:%20list%3Aorg.jboss.lists.in... -- 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

12 years

5
25
0 / 0

[JBoss JIRA] (ISPN-1954) Wrong ServerWorker thread name in Hot rod server

by Michal Linhard (JIRA)

Michal Linhard created ISPN-1954: ------------------------------------ Summary: Wrong ServerWorker thread name in Hot rod server Key: ISPN-1954 URL: https://issues.jboss.org/browse/ISPN-1954 Project: Infinispan Issue Type: Bug Components: Cache Server Reporter: Michal Linhard Assignee: Galder Zamarreño Priority: Minor When debugging/profiling EDG, we're seeing HotRod server calls being executed by MemcachedServerWorker threads. -- 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

12 years

4
18
0 / 0

[JBoss JIRA] (ISPN-2187) Pre-Invocation flag PUT_FOR_EXTERNAL_READ throws exception

by Anna Manukyan (JIRA)

Anna Manukyan created ISPN-2187: ----------------------------------- Summary: Pre-Invocation flag PUT_FOR_EXTERNAL_READ throws exception Key: ISPN-2187 URL: https://issues.jboss.org/browse/ISPN-2187 Project: Infinispan Issue Type: Bug Components: Core API Reporter: Anna Manukyan Assignee: Manik Surtani Hi, While writing tests for Infinispan Flag.PUT_FOR_EXTERNAL_READ the following issue has been found. In documentation it is said: PUT_FOR_EXTERNAL_READ Flags the invocation as a Cache.putForExternalRead(Object, Object) call, as opposed to a regular Map.put(Object, Object). And the documentation for Cache.putForExternalRead(Object, Object) says: void putForExternalRead(K key, V value) ................... Errors and exceptions are 'silent' - logged at a much lower level than normal, and this method does not throw exceptions The issue is the following: when trying to perform operation using PUT_FOR_EXTERNAL_READ flag, the exception is thrown, it is not 'silent'. cache1.getAdvancedCache().withFlags(Flag.PUT_FOR_EXTERNAL_READ).put(key, value); The test is the following: public void testExceptionSuppression() throws Exception { Cache cache1 = cache(0, "replSync"); Cache cache2 = cache(1, "replSync"); Transport mockTransport = mock(Transport.class); RpcManagerImpl rpcManager = (RpcManagerImpl) TestingUtil.extractComponent(cache1, RpcManager.class); Transport originalTransport = TestingUtil.extractComponent(cache1, Transport.class); try { Address mockAddress1 = mock(Address.class); Address mockAddress2 = mock(Address.class); List<Address> memberList = new ArrayList<Address>(2); memberList.add(mockAddress1); memberList.add(mockAddress2); rpcManager.setTransport(mockTransport); when(mockTransport.getMembers()).thenReturn(memberList); when(mockTransport.getViewId()).thenReturn(originalTransport.getViewId()); when(mockTransport.invokeRemotely(anyAddresses(), (CacheRpcCommand) anyObject(), anyResponseMode(), anyLong(), anyBoolean(), (ResponseFilter) anyObject())) .thenThrow(new RuntimeException("Barf!")); try { cache1.put(key, value); fail("Should have barfed"); } catch (RuntimeException re) { } // clean up any indeterminate state left over try { cache1.remove(key); fail("Should have barfed"); } catch (RuntimeException re) { } assertNull("Should have cleaned up", cache1.get(key)); // should not barf cache1.putForExternalRead(key, value); /** ------------------- Testing the same feature with Flag.PUT_FOR_EXTERNAL_READ **/ try { cache1.remove(key); fail("Should have barfed"); } catch (RuntimeException re) { } cache1.getAdvancedCache().withFlags(Flag.PUT_FOR_EXTERNAL_READ).put(key, value); } finally { if (rpcManager != null) rpcManager.setTransport(originalTransport); } } Best regards, Anna. -- 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

12 years

5
15
0 / 0

[JBoss JIRA] (ISPN-2137) Potential tx lock leaks when nodes are added to the cluster

by Mircea Markus (JIRA)

Mircea Markus created ISPN-2137: ----------------------------------- Summary: Potential tx lock leaks when nodes are added to the cluster Key: ISPN-2137 URL: https://issues.jboss.org/browse/ISPN-2137 Project: Infinispan Issue Type: Bug Components: State transfer, Transactions Affects Versions: 5.1.5.FINAL Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.x, 5.2.0.ALPHA2, 5.2.0.FINAL -- 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

12 years

5
17
0 / 0

[JBoss JIRA] (ISPN-2481) CLI: add XSR commands

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-2481: ------------------------------------- Summary: CLI: add XSR commands Key: ISPN-2481 URL: https://issues.jboss.org/browse/ISPN-2481 Project: Infinispan Issue Type: Feature Request Components: CLI Affects Versions: 5.2.0.Beta3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 5.2.0.CR1, 5.2.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

2
1
0 / 0

[JBoss JIRA] (ISPN-2302) New JdbcCacheStoreConfigurationBuilder should support existing ConnectionFactoryConfig

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2302: ---------------------------------- Summary: New JdbcCacheStoreConfigurationBuilder should support existing ConnectionFactoryConfig Key: ISPN-2302 URL: https://issues.jboss.org/browse/ISPN-2302 Project: Infinispan Issue Type: Feature Request Components: Configuration Affects Versions: 5.2.0.Alpha3 Reporter: Thomas Fromm Assignee: Mircea Markus I've the situation the I need to reuse existing ConnectionFactoryConfigs. Maybe implement ConnectionFactoryConfigurationBuilder with method read(ConnectionFactoryConfig template). Then extend JdbcCacheStoreConfigurationBuilder and add connectionFactory()? -- 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

4
9
0 / 0

[JBoss JIRA] (ISPN-2335) MultiHotRodServersTest not works with ConfigurationBuilder API

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2335: ---------------------------------- Summary: MultiHotRodServersTest not works with ConfigurationBuilder API Key: ISPN-2335 URL: https://issues.jboss.org/browse/ISPN-2335 Project: Infinispan Issue Type: Bug Components: Test Suite Affects Versions: 5.2.0.Alpha4 Reporter: Thomas Fromm Assignee: Tristan Tarrant Attachments: trace-infinispan.log I tried to use ConfigurationBuilder API with addClusterEnabledCacheManager inside MultiHotRodServersTest.addHotRodServer. Unfortunality it works on with the old Configuration object, with the Builder the test fails. I tried to find any relevant difference inside configuration, but wasn't successful :-( So I use a LegacyConfigurationAdaptor to create old config. Attachmed I've traces from the failing tests and from the working one. Maybe it helps. -- 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

3
5
0 / 0

[JBoss JIRA] (ISPN-2498) NPE at CacheManager restart and JMX

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2498: ---------------------------------- Summary: NPE at CacheManager restart and JMX Key: ISPN-2498 URL: https://issues.jboss.org/browse/ISPN-2498 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 5.2.0.Beta3 Reporter: Thomas Fromm Assignee: Thomas Fromm With enabled JMX, a CacheManager stop() and start() afterwards results into a NPE. java.lang.NullPointerException at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:62) at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:709) at org.infinispan.jmx.ComponentsJmxRegistrationTest.testStopStartCM(ComponentsJmxRegistrationTest.java:75) -- 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

2
2
0 / 0

[JBoss JIRA] (ISPN-2494) Transactiontable.cleanupCompletedTransactions fills debug logfile rapidly

by Thomas Fromm (JIRA)

Thomas Fromm created ISPN-2494: ---------------------------------- Summary: Transactiontable.cleanupCompletedTransactions fills debug logfile rapidly Key: ISPN-2494 URL: https://issues.jboss.org/browse/ISPN-2494 Project: Infinispan Issue Type: Enhancement Reporter: Thomas Fromm Assignee: Mircea Markus I suggest using level trace and to reduce base load of cpu, check if committedTX map is empty to avoid further object creations and calculations... -- 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

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2012