December 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3836) TxCleanupService can cause TCCL leak

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3836?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3836: -------------------------------- Labels: (was: 620) > TxCleanupService can cause TCCL leak > ------------------------------------ > > Key: ISPN-3836 > URL: https://issues.jboss.org/browse/ISPN-3836 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Brent Douglas > Assignee: Dan Berindei > > Looks to me like this should be using infinispan's classloader rather than the TCCL when creating a thread. > https://issues.jboss.org/browse/WFLY-2605 -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3666) Fix CI failures regarding L1 issues

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3666?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3666: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Fix CI failures regarding L1 issues > ----------------------------------- > > Key: ISPN-3666 > URL: https://issues.jboss.org/browse/ISPN-3666 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: William Burns > Assignee: William Burns > > There are some L1 failures that occur intermittently as seen here > -http://ci.infinispan.org/viewLog.html?buildId=3905&buildTypeId=bt9- > -http://ci.infinispan.org/viewLog.html?buildId=3921&tab=buildResultsDiv&buildTypeId=bt9- > http://ci.infinispan.org/viewLog.html?buildId=4932&buildTypeId=bt9 > Looking into them they appear to be test failures only and not related to core code. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3844) Cluster Registry cache does not need to provide return value for put and remove

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3844?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3844: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1045082, https://bugzilla.redhat.com/show_bug.cgi?id=1043791 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1045082) > Cluster Registry cache does not need to provide return value for put and remove > ------------------------------------------------------------------------------- > > Key: ISPN-3844 > URL: https://issues.jboss.org/browse/ISPN-3844 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Minor > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > This internal registry needs to be efficient, and the return types of put and remove operations are redundant for our purposes: I'm removing them. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3833) QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3833?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3833: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1045082, https://bugzilla.redhat.com/show_bug.cgi?id=1043791 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1045082) > QueryInterceptor#updateKnownTypesIfNeeded invokes into the cluster registry too frequently > ------------------------------------------------------------------------------------------ > > Key: ISPN-3833 > URL: https://issues.jboss.org/browse/ISPN-3833 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > The QueryInterceptor should use a local cache to avoid unnecessary invocations, especially as the cluster registry is transactional this is a source of garbage generation. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3834) New advanced indexing flag to skip deletion of previous entry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3834?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3834: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1045082, https://bugzilla.redhat.com/show_bug.cgi?id=1043791 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1045082) > New advanced indexing flag to skip deletion of previous entry > ------------------------------------------------------------- > > Key: ISPN-3834 > URL: https://issues.jboss.org/browse/ISPN-3834 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > I'm needing to add a org.infinispan.context.Flag.SKIP_INDEX_CLEANUP which does not issue an UPDATE index command but a simple ADD. > Just ADD is way more efficient, just we can't automatically detect it safely so I need a flag to allow for efficient data import. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3704) StateTransfer's PutKeyValueCommand may trigger remote get

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3704?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3704. --------------------------------- Resolution: Done > StateTransfer's PutKeyValueCommand may trigger remote get > --------------------------------------------------------- > > Key: ISPN-3704 > URL: https://issues.jboss.org/browse/ISPN-3704 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.CR1 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > In TX mode with write skew check on, ST executing puts may trigger a remote get. > The condition in TxDistributionInterceptor.handleTxWriteCommand should probably be switched from > {code} > if (ctx.isOriginLocal() && !skipRemoteGet || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command)) > remoteGetBeforeWrite(ctx, command, recipientGenerator); > {code} > to > {code} > if (!skipRemoteGet && (ctx.isOriginLocal() || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command))) > remoteGetBeforeWrite(ctx, command, recipientGenerator); > {code} > EDIT: > I have also registered a situation where the Prepare/Commit command was executed remotely from within the ST because the topology has changed during the remote get. This should be avoided as well. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3704) StateTransfer's PutKeyValueCommand may trigger remote get

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3704?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3704: -------------------------------- Labels: 620 (was: ) > StateTransfer's PutKeyValueCommand may trigger remote get > --------------------------------------------------------- > > Key: ISPN-3704 > URL: https://issues.jboss.org/browse/ISPN-3704 > Project: Infinispan > Issue Type: Bug > Components: Distributed Cache > Affects Versions: 6.0.0.CR1 > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Labels: 620 > Fix For: 7.0.0.Alpha1 > > > In TX mode with write skew check on, ST executing puts may trigger a remote get. > The condition in TxDistributionInterceptor.handleTxWriteCommand should probably be switched from > {code} > if (ctx.isOriginLocal() && !skipRemoteGet || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command)) > remoteGetBeforeWrite(ctx, command, recipientGenerator); > {code} > to > {code} > if (!skipRemoteGet && (ctx.isOriginLocal() || command.isConditional() || shouldFetchRemoteValuesForWriteSkewCheck(ctx, command))) > remoteGetBeforeWrite(ctx, command, recipientGenerator); > {code} > EDIT: > I have also registered a situation where the Prepare/Commit command was executed remotely from within the ST because the topology has changed during the remote get. This should be avoided as well. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3852) Add a section describing the configuration for the java hotrod client

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3852?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3852: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2306 > Add a section describing the configuration for the java hotrod client > --------------------------------------------------------------------- > > Key: ISPN-3852 > URL: https://issues.jboss.org/browse/ISPN-3852 > Project: Infinispan > Issue Type: Feature Request > Components: Documentation > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: 620 > -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3666) Fix CI failures regarding L1 issues

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3666?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3666: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2305 > Fix CI failures regarding L1 issues > ----------------------------------- > > Key: ISPN-3666 > URL: https://issues.jboss.org/browse/ISPN-3666 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: William Burns > Assignee: William Burns > > There are some L1 failures that occur intermittently as seen here > -http://ci.infinispan.org/viewLog.html?buildId=3905&buildTypeId=bt9- > -http://ci.infinispan.org/viewLog.html?buildId=3921&tab=buildResultsDiv&buildTypeId=bt9- > http://ci.infinispan.org/viewLog.html?buildId=4932&buildTypeId=bt9 > Looking into them they appear to be test failures only and not related to core code. -- 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

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3862) Upgrade JBossMarshaller to 1.4.x

by Mircea Markus (JIRA)

Mircea Markus created ISPN-3862: ----------------------------------- Summary: Upgrade JBossMarshaller to 1.4.x Key: ISPN-3862 URL: https://issues.jboss.org/browse/ISPN-3862 Project: Infinispan Issue Type: Feature Request Components: Marshalling Reporter: Mircea Markus Assignee: Galder Zamarreño This is needed not only for moving to the latest and greatest, but alto in order to align with Wildfly 8. -- 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

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2013