January 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-284) Streamed rehashing

by Manik Surtani (JIRA)

Streamed rehashing ------------------ Key: ISPN-284 URL: https://jira.jboss.org/jira/browse/ISPN-284 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.GA Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA Currently rehashing uses RPC which uses byte array representations of state. These could use streams, perhaps using JGroups' STREAMING_STATE_TRANSFER sockets, for greater performance and robustness. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

9
22
0 / 0

[JBoss JIRA] Created: (ISPN-956) Update RESTEasy version used by REST server

by Michal Linhard (JIRA)

Update RESTEasy version used by REST server ------------------------------------------- Key: ISPN-956 URL: https://issues.jboss.org/browse/ISPN-956 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Michal Linhard Assignee: Michal Linhard Priority: Minor Fix For: 4.2.1.FINAL, 5.0.0.BETA1 Update RESTEasy version (currently 2.0-beta-2) used by REST server to a stable one (2.0.1.GA or 2.1.0.GA). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] (ISPN-1696) <versioning /> element not parsed with new Parser

by Manik Surtani (Created) (JIRA)

<versioning /> element not parsed with new Parser ------------------------------------------------- Key: ISPN-1696 URL: https://issues.jboss.org/browse/ISPN-1696 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.CR2 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.CR3 A user complaint: {quote} I needed to enable versioning. Looking at http://docs.jboss.org/infinispan/5.1/apidocs/config.html#ce_default_versi... I tried to add <versioning versioningScheme="SIMPLE" enabled="true" /> to the <default> section in the configuration file, but apparently I'm doing something wrong, because then I get this exception from the parser: Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[35,5] Message: Unexpected element 'versioning' encountered {quote} -- 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 months

4
4
0 / 0

[JBoss JIRA] (ISPN-1557) Add use1PcForAutoCommitTransactions attribute to the new Configuration structure

by Mircea Markus (Created) (JIRA)

Add use1PcForAutoCommitTransactions attribute to the new Configuration structure -------------------------------------------------------------------------------- Key: ISPN-1557 URL: https://issues.jboss.org/browse/ISPN-1557 Project: Infinispan Issue Type: Bug Components: Configuration Reporter: Mircea Markus Assignee: Pete Muir Fix For: 5.1.0.CR1 use1PcForAutoCommitTransactions was added part of ISPN-1297, but I couldn't also update the new config due to ISPN-1552. The UT added in the description of ISPN-1552 actually tests the functionality required by this jira. Should be a straight-fwd thing to fix once ISPN-1552 is in place. -- 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 months

7
8
0 / 0

[JBoss JIRA] (ISPN-1545) Enhance logging during cache shutdown

by Mircea Markus (Created) (JIRA)

Enhance logging during cache shutdown ------------------------------------- Key: ISPN-1545 URL: https://issues.jboss.org/browse/ISPN-1545 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.1.0.BETA5 Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.0.CR1 When cache shuts down the transaction table recalculates its minViewId value based on the new topology. When the whole cluster shuts down though, the thread that recalculates might throw an exception (expected) because it's internal components (RPC in this example) are not responding anymore. This causes a lot of log noise in the logs, which should be removed: 2011-11-16 17:08:29,045 WARN [jta] (Transaction Reaper Worker 0) ARJUNA16045: attempted rollback of < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac11fa3e:c0a2:4ec3df75:a055, node_name=1, branch_uid=0:ffffac11fa3e:c0a2:4ec3df75:a056, eis_name=unknown eis name > (TransactionXaAdapter{localTransaction=LocalXaTransaction{xid=< formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffffac11fa3e:c0a2:4ec3df75:a055, node_name=1, branch_uid=0:ffffac11fa3e:c0a2:4ec3df75:a056, eis_name=unknown eis name >} LocalTransaction{remoteLockedNodes=[9124b480-6ae0-5267-d9f8-3d66ea7ec581, 86c0fc2d-a0da-adb4-5343-940d6bdb1aa0], isMarkedForRollback=true, transaction=TransactionImple < ac, BasicAction: 0:ffffac11fa3e:c0a2:4ec3df75:a055 status: ActionStatus.ABORTING >, lockedKeys=null, backupKeyLocks=null, viewId=1} org.infinispan.transaction.xa.LocalXaTransaction@2947}) failed with exception code - org.infinispan.CacheException: The cache has been stopped and invocations are not allowed! at org.infinispan.remoting.transport.jgroups.JGroupsTransport.getViewId(JGroupsTransport.java:197) at org.infinispan.transaction.TransactionTable.getCurrentViewId(TransactionTable.java:372) at org.infinispan.transaction.TransactionTable.recalculateMinViewIdIfNeeded(TransactionTable.java:387) at org.infinispan.transaction.TransactionTable.removeLocalTransactionInternal(TransactionTable.java:318) at org.infinispan.transaction.TransactionTable.removeLocalTransaction(TransactionTable.java:306) at org.infinispan.transaction.xa.XaTransactionTable.removeLocalTransaction(XaTransactionTable.java:61) at org.infinispan.transaction.TransactionTable.failureCompletingTransaction(TransactionTable.java:188) at org.infinispan.transaction.TransactionCoordinator.rollback(TransactionCoordinator.java:145) at org.infinispan.transaction.xa.TransactionXaAdapter.rollback(TransactionXaAdapter.java:136) at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.topLevelAbort(XAResourceRecord.java:337) at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2869) at com.arjuna.ats.arjuna.coordinator.BasicAction.doAbort(BasicAction.java:2848) at com.arjuna.ats.arjuna.coordinator.BasicAction.Abort(BasicAction.java:1613) at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.cancel(TwoPhaseCoordinator.java:119) at com.arjuna.ats.arjuna.AtomicAction.cancel(AtomicAction.java:212) at com.arjuna.ats.arjuna.coordinator.TransactionReaper.doCancellations(TransactionReaper.java:367) at com.arjuna.ats.internal.arjuna.coordinator.ReaperWorkerThread.run(ReaperWorkerThread.java:79) -- 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 months

3
5
0 / 0

[JBoss JIRA] (ISPN-1691) Default transport class being used when parsing non-clustered XML files

by Manik Surtani (Created) (JIRA)

Default transport class being used when parsing non-clustered XML files ----------------------------------------------------------------------- Key: ISPN-1691 URL: https://issues.jboss.org/browse/ISPN-1691 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.CR2 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.CR3 When parsing config files, the parser unnecessarily sets up a default Transport even if the <transport /> element is not specified in <global />. This breaks backward compatibility. -- 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 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1692) Unnecessary dependency on Transport in components that may be used in LOCAL mode.

by Manik Surtani (Created) (JIRA)

Unnecessary dependency on Transport in components that may be used in LOCAL mode. --------------------------------------------------------------------------------- Key: ISPN-1692 URL: https://issues.jboss.org/browse/ISPN-1692 Project: Infinispan Issue Type: Bug Components: Core API, Distributed Cache Affects Versions: 5.1.0.CR2 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.CR3 We shouldn't just have components depend on Transport unless we know for sure that the component is only used in a clustered mode. Otherwise, even in local mode, weend up creating and starting a channel which is unnecessary. Seen in the CacheLoaderInterceptor, AbstractLockingInterceptor and the RemoteCommandsFactory so far. -- 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 months

3
2
0 / 0

[JBoss JIRA] (ISPN-1675) InstantiationExceptions using new Configuration API

by Paul Ferraro (Created) (JIRA)

InstantiationExceptions using new Configuration API --------------------------------------------------- Key: ISPN-1675 URL: https://issues.jboss.org/browse/ISPN-1675 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 5.1.0.CR2 Reporter: Paul Ferraro Assignee: Manik Surtani The following code fragments will cause an InstantiationException: new DefaultCacheManager(new GlobalConfigurationBuilder().transport().transport(new JGroupsTransport(channel)).build()).getCache(); new DefaultCacheManager(new GlobalConfigurationBuilder().asyncTransportExecutor().factory(new CustomExecutorFactory(executor)).build()).getCache(); Even though the new configuration API accepts object instances for these configuration properties, they are expected to have no-arg constructors (since the old configuration API relied on this mechanism), hence the InstantiationException. -- 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 months

5
5
0 / 0

[JBoss JIRA] (ISPN-1695) Parser should support eviction.wakeUpInterval even though it's deprecated

by Galder Zamarreño (Created) (JIRA)

Parser should support eviction.wakeUpInterval even though it's deprecated ------------------------------------------------------------------------- Key: ISPN-1695 URL: https://issues.jboss.org/browse/ISPN-1695 Project: Infinispan Issue Type: Bug Affects Versions: 5.1.0.CR2 Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.CR3 Make eviction.wakeUpInterval work from a parser perspective, so that we avoid problems with XML config upgrades from 5.0 to 5.1 -- 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 months

4
3
0 / 0

[JBoss JIRA] (ISPN-1645) FileCacheStore.purgeInternal() not removes empty Bucket files

by Thomas Fromm (Created) (JIRA)

FileCacheStore.purgeInternal() not removes empty Bucket files ------------------------------------------------------------- Key: ISPN-1645 URL: https://issues.jboss.org/browse/ISPN-1645 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 5.1.0.CR2 Reporter: Thomas Fromm Assignee: Manik Surtani FileCacheStore leaves empty files inside storage directory after remove of cache entries. During a purgeInternal (by reaper thread) these files are found, but cannot be removed because loadBucket(..) always return null, because bucketFile.length() == 0. So updateBucket(..) will never reached and these files don't get removed. -- 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 months

4
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2012