October 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-1462) JGroupsTransport doesn't initialize properly when it receives an already-connected JGroups channel

by Dan Berindei (Created) (JIRA)

JGroupsTransport doesn't initialize properly when it receives an already-connected JGroups channel -------------------------------------------------------------------------------------------------- Key: ISPN-1462 URL: https://issues.jboss.org/browse/ISPN-1462 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 5.1.0.BETA1 Reporter: Dan Berindei Assignee: Dan Berindei Priority: Blocker Fix For: 5.1.0.BETA2 When the JGroups channel is connected outside Infinispan, before passing it to JGroupsTransport, the member list is not initialized. This can lead to strange errors like this one: java.lang.IllegalArgumentException: Invalid cache list for consistent hash: [] at org.infinispan.distribution.ch.AbstractWheelConsistentHash.setCaches(AbstractWheelConsistentHash.java:96) at org.infinispan.distribution.ch.ConsistentHashHelper.createConsistentHash(ConsistentHashHelper.java:122) at org.infinispan.statetransfer.ReplicatedStateTransferManagerImpl.createConsistentHash(ReplicatedStateTransferManagerImpl.java:56) at org.infinispan.statetransfer.BaseStateTransferManagerImpl.start(BaseStateTransferManagerImpl.java:143) -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-658) DistributionManager not considerate of cache state changes

by Paul Ferraro (JIRA)

DistributionManager not considerate of cache state changes ---------------------------------------------------------- Key: ISPN-658 URL: https://jira.jboss.org/browse/ISPN-658 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.2.0.ALPHA2 Reporter: Paul Ferraro Assignee: Manik Surtani Considering a cache manager with 2 caches in DIST mode (C1 and C2) deployed on 2 nodes (N1 and N2). Currently, the DistributionManager does not properly handle the following scenarios: 1. Stop C1 on N1. This ought to trigger a rehash for the C1 cache. Currently, rehashing is only triggered via view change. Failure to rehash on stopping of a cache can inadvertently cause data loss, if all backups of a given cache entry have stopped. 2. A new DIST mode cache, C3, is started on N2. If N1 is the coordinator, the join request sent to N1 will get stuck in an infinite loop, since the cache manager on N1 does not contain a C3 cache. 3. Less critically, a new node, N3 is started. It does not yet have a C1 or C2 cache, though it's cache manager is started. This prematurely triggers a rehash of C1 and C2, even though there are no new caches instances to consider. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

11
24
0 / 0

[JBoss JIRA] (ISPN-1456) Improve transactions performance by defining a non-system hashCode

by Sanne Grinovero (Created) (JIRA)

Improve transactions performance by defining a non-system hashCode ------------------------------------------------------------------ Key: ISPN-1456 URL: https://issues.jboss.org/browse/ISPN-1456 Project: Infinispan Issue Type: Enhancement Components: Transactions Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.1.0.BETA2 I'm experiencing an impressively high overhead of Object.hashCode for org.infinispan.transaction.xa.TransactionXaAdapter, being invoked in the TransactionManager to store it HashTable(s). Adding a simple hashCode implementation provides a 5X performance improvement in synthetic microbenchmarks. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] (ISPN-1454) Upgrade to javax.cache:cache-api:0.3

by Juergen Zimmermann (Created) (JIRA)

Upgrade to javax.cache:cache-api:0.3 ------------------------------------ Key: ISPN-1454 URL: https://issues.jboss.org/browse/ISPN-1454 Project: Infinispan Issue Type: Bug Components: CDI integration Affects Versions: 5.1.0.BETA1 Reporter: Juergen Zimmermann Assignee: Manik Surtani Please see http://repo1.maven.org/maven2/javax/cache/cache-api/0.3 -- 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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-1383) Data caching multiplying memory requirements of Hot Rod server

by Galder Zamarreño (JIRA)

Data caching multiplying memory requirements of Hot Rod server -------------------------------------------------------------- Key: ISPN-1383 URL: https://issues.jboss.org/browse/ISPN-1383 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.1.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.ALPHA2 , 5.1.0.FINAL After inserting a 160MB object in Hot Rod, the memory consumption of the server goes through the roof. The screenshot shows a couple of interesting things: 1. Both the HotRodDecoder and the DataContainer have a byte[] of approx 160mb each. So, it seems like it's actually two copies of the same byte[]. It's clear though that only the cache container should have it, and any cache decoder data should be cleared when the request is completed. 2. Netty's UnsafeDynamicChannelBuffer is still holding to a byte[] of 268MB approx. Judging by the 2nd screenshot attached, this appears to be belonging to the underlying ReplayingDecoder. That should also, if possible, be cleared up. I'll have a look around in the Netty code and maybe ping Trustin. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

5
12
0 / 0

[JBoss JIRA] (ISPN-1451) Upgrade to JCache 0.3

by Kevin Pollet (Created) (JIRA)

Upgrade to JCache 0.3 --------------------- Key: ISPN-1451 URL: https://issues.jboss.org/browse/ISPN-1451 Project: Infinispan Issue Type: Component Upgrade Components: CDI integration Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.BETA2, 5.1.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, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (ISPN-1372) Make sure Infinispan works with Cassandra CQL

by Tristan Tarrant (JIRA)

Make sure Infinispan works with Cassandra CQL --------------------------------------------- Key: ISPN-1372 URL: https://issues.jboss.org/browse/ISPN-1372 Project: Infinispan Issue Type: Task Reporter: Tristan Tarrant Assignee: Tristan Tarrant -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

4
4
0 / 0

[JBoss JIRA] (ISPN-1446) Upgrade to Seam Solder 3.1.0.Beta3

by Juergen Zimmermann (Created) (JIRA)

Upgrade to Seam Solder 3.1.0.Beta3 ---------------------------------- Key: ISPN-1446 URL: https://issues.jboss.org/browse/ISPN-1446 Project: Infinispan Issue Type: Bug Components: CDI integration Affects Versions: 5.1.0.BETA1 Reporter: Juergen Zimmermann Assignee: Manik Surtani Seam Solder changed its package structure since 3.1.0.Beta3. The upcoming release 5.1.0 should support the latest Seam release, expecially since Seam 3.0 so far only has a pretty small adoption compared to Seam 2, and Seam 3.1 hopefully gets a larger attention. -- 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, 6 months

8
7
0 / 0

[JBoss JIRA] Created: (ISPN-1435) JCache interceptors need to be serializable

by Kevin Pollet (JIRA)

JCache interceptors need to be serializable ------------------------------------------- Key: ISPN-1435 URL: https://issues.jboss.org/browse/ISPN-1435 Project: Infinispan Issue Type: Bug Components: CDI integration Affects Versions: 5.0.1.FINAL, 5.0.0.FINAL Reporter: Kevin Pollet Assignee: Kevin Pollet Fix For: 5.1.0.BETA1, 5.1.0.FINAL The JCache interceptors need to be serializable to be used in beans with a passivating scope. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

6
7
0 / 0

[JBoss JIRA] (ISPN-1444) Infinispan fails to shutdown gracefully

by Luc Boudreau (Created) (JIRA)

Infinispan fails to shutdown gracefully --------------------------------------- Key: ISPN-1444 URL: https://issues.jboss.org/browse/ISPN-1444 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.1.FINAL, 4.2.1.FINAL Reporter: Luc Boudreau Assignee: Manik Surtani Priority: Blocker We have embeded Infinispan into our project, but when used, we cannot gracefully shutdown the JVM anymore. There are a few exceptions thrown by late-access to the classloader from log4j, but these errors are easy to work around. Tomcat blocks any class loading after an application has been marked as shutting down. I can load them in the classloader in my application at runtime and circumvent those issues. The main problem is the fact that the threads are just hanging there. They are not marked as daemon threads, so the JVM doesn't shut them off automatically, if required. The culprit threads are: - OOB-1 - OOB-2 - multicast receiver - unicast-receiver - TransferQueueBuilder Some of these threads might be related to JGroups. Please advise, and I will create a separate ticket in their bug tracker if needed. I know Infinispan registers a shutdown hook in order to cleanly shut down, but it looks quite unreliable and causes a lot of problems for us. -- 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, 6 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2011