[JBoss JIRA] (ISPN-3279) Delete ConfigurationOverrides and GlobalConfigurationOverrides in Spring module
by Navin Surtani (JIRA)
[ https://issues.jboss.org/browse/ISPN-3279?page=com.atlassian.jira.plugin.... ]
Navin Surtani updated ISPN-3279:
--------------------------------
Description: Delete the ConfigurationOverrides and GlobalConfigurationOverrides classes. Methods that otherwise make use of this code should provide an API to take in ConfigurationBuilder or GlobalConfigurationBuilder objects. This is to make the code-base easier to maintain. (was: There is some duplicate code in the ConfigurationOverrides and GlobalConfigurationOverrides in the Spring module. These classes (and relevant code) should be merged together where possible.)
> Delete ConfigurationOverrides and GlobalConfigurationOverrides in Spring module
> -------------------------------------------------------------------------------
>
> Key: ISPN-3279
> URL: https://issues.jboss.org/browse/ISPN-3279
> Project: Infinispan
> Issue Type: Enhancement
> Components: Spring integration, Test Suite
> Affects Versions: 6.0.0.Alpha1
> Reporter: Navin Surtani
> Assignee: Navin Surtani
>
> Delete the ConfigurationOverrides and GlobalConfigurationOverrides classes. Methods that otherwise make use of this code should provide an API to take in ConfigurationBuilder or GlobalConfigurationBuilder objects. This is to make the code-base easier to maintain.
--
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, 9 months
[JBoss JIRA] (ISPN-2702) RecoveryWithCustomCacheDistTest.testNodeCrashesAfterPrepare failing randomly
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-2702?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo commented on ISPN-2702:
-----------------------------------
[~anistor] the testSimpleTx is because the testNodeCrashesAfterPrepare has run before it and it has killed the manager(1). then the test throws an ArrayOutOfBoundException when it tries to access it. Should never happen now since we have the class annotated with @CleanupAfterMethod.
still looking testNodeCrashesAfterPrepare
> RecoveryWithCustomCacheDistTest.testNodeCrashesAfterPrepare failing randomly
> ----------------------------------------------------------------------------
>
> Key: ISPN-2702
> URL: https://issues.jboss.org/browse/ISPN-2702
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Reporter: Galder Zamarreño
> Assignee: Pedro Ruivo
> Labels: testsuite_stability
> Fix For: 6.0.0.Alpha1, 6.0.0.Final
>
> Attachments: RecoveryWithCustomCacheDistTest.log.gz, testNodeCrashesAfterPrepare-1.log
>
>
> {code}testNodeCrashesAfterPrepare(org.infinispan.tx.recovery.RecoveryWithCustomCacheDistTest) Time elapsed: 0.083 sec <<< FAILURE!
> java.lang.RuntimeException: javax.transaction.xa.XAException
> at org.infinispan.tx.recovery.RecoveryTestUtil.prepareTransaction(RecoveryTestUtil.java:58)
> at org.infinispan.tx.recovery.RecoveryWithDefaultCacheDistTest.testNodeCrashesAfterPrepare(RecoveryWithDefaultCacheDistTest.java:124)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: javax.transaction.xa.XAException
> at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:161)
> at org.infinispan.transaction.TransactionCoordinator.prepare(TransactionCoordinator.java:123)
> at org.infinispan.transaction.xa.TransactionXaAdapter.prepare(TransactionXaAdapter.java:110)
> at org.infinispan.tx.recovery.RecoveryTestUtil.prepareTransaction(RecoveryTestUtil.java:56)
> ... 22 more{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
12 years, 9 months
[JBoss JIRA] (ISPN-3197) Message ordering of Get and Invalidation can cause L1 to be inconsistent
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3197?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3197:
--------------------------------
Fix Version/s: 6.0.0.Alpha1
6.0.0.Final
> Message ordering of Get and Invalidation can cause L1 to be inconsistent
> ------------------------------------------------------------------------
>
> Key: ISPN-3197
> URL: https://issues.jboss.org/browse/ISPN-3197
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.6.Final
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 6.0.0.Alpha1, 6.0.0.Final
>
>
> This is based off of discussion here: https://issues.jboss.org/browse/ISPN-2990?focusedCommentId=12779491&page=...
> This can occur with a synchronous cache.
> 1. A reads k1. This is an OOB call.
> 2. B processes the read message and sends back the response
> 3. C updates k1, at this stage B sends the invalidation message to A (OOB call)
> 4. A processes(ignores) the invalidation message
> 5. A puts the stale value sent at 2 in L1
> The OOB portions don't actually matter that they are OOB as even if B's messages were ordered it sill could process the get and update in a different order since they originate from different nodes.
> The initial thought is to solve this with some type of tombstone to sygnal the removal of the L1 cache, but this also still doesn't catch the problem if A did not have key k1 in it's L1 cache to receive an invalidation message.
--
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, 9 months
[JBoss JIRA] (ISPN-3227) Server loader configuration breaks when properties are specified
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3227?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3227:
-----------------------------------------------
Shay Matasaro <smatasar(a)redhat.com> made a comment on [bug 973763|https://bugzilla.redhat.com/show_bug.cgi?id=973763]
PATCH NAME: JDG-6.1.0.GA-BZ973763
PRODUCT NAME: JDG
VERSION:JDG-6.1.0.GA
SHORT DESCRIPTION: Support For Child Elements of <loader> Missing When Defining Custom Cache Loader
MANUAL INSTALL INSTRUCTIONS:
Backup and remove the following files:
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/jboss-datagrid-infinispan-6.1.0.GA-redhat-1.jar
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/module.xml
Extract the patched files by either:
Using unzip:
unzip -d $JBOSS_HOME/JDG-6.1.0.GA-BZ973763.zip
Or by extracting the files from the zip to the following locations:
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/jboss-datagrid-infinispan-6.1.0.GA-redhat-1-BZ973763.jar
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/module.xml
CREATOR:
Shay Matasaro
DATE:
Jul 9, 2013
> Server loader configuration breaks when properties are specified
> ----------------------------------------------------------------
>
> Key: ISPN-3227
> URL: https://issues.jboss.org/browse/ISPN-3227
> Project: Infinispan
> Issue Type: Feature Request
> Components: Server
> Affects Versions: 5.2.6.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 5.2.7.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, 9 months
[JBoss JIRA] (ISPN-3157) Realign Infinispan subsystem to match AS7.2/EAP6.1
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3157?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3157:
-----------------------------------------------
Shay Matasaro <smatasar(a)redhat.com> made a comment on [bug 973763|https://bugzilla.redhat.com/show_bug.cgi?id=973763]
PATCH NAME: JDG-6.1.0.GA-BZ973763
PRODUCT NAME: JDG
VERSION:JDG-6.1.0.GA
SHORT DESCRIPTION: Support For Child Elements of <loader> Missing When Defining Custom Cache Loader
MANUAL INSTALL INSTRUCTIONS:
Backup and remove the following files:
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/jboss-datagrid-infinispan-6.1.0.GA-redhat-1.jar
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/module.xml
Extract the patched files by either:
Using unzip:
unzip -d $JBOSS_HOME/JDG-6.1.0.GA-BZ973763.zip
Or by extracting the files from the zip to the following locations:
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/jboss-datagrid-infinispan-6.1.0.GA-redhat-1-BZ973763.jar
$JBOSS_HOME/modules/org/jboss/as/clustering/infinispan/main/module.xml
CREATOR:
Shay Matasaro
DATE:
Jul 9, 2013
> Realign Infinispan subsystem to match AS7.2/EAP6.1
> --------------------------------------------------
>
> Key: ISPN-3157
> URL: https://issues.jboss.org/browse/ISPN-3157
> Project: Infinispan
> Issue Type: Task
> Components: Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Critical
> Fix For: 5.3.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, 9 months