[JBoss JIRA] (ISPN-3084) BaseBackupInterceptor creates new logger on every XSite call
by Erik Salter (JIRA)
Erik Salter created ISPN-3084:
---------------------------------
Summary: BaseBackupInterceptor creates new logger on every XSite call
Key: ISPN-3084
URL: https://issues.jboss.org/browse/ISPN-3084
Project: Infinispan
Issue Type: Bug
Components: Cross-Site Replication
Affects Versions: 5.2.6.Final
Reporter: Erik Salter
Assignee: Mircea Markus
The BaseBackupInterceptor creates a new logger instance on every transactional backup. This ends up slowing down the performance of the backup sender, resulting in degraded performance.
--
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
11 years, 2 months
[JBoss JIRA] (ISPN-2933) MixedModeTest.testMixedMode fails intermittently
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2933?page=com.atlassian.jira.plugin.... ]
Mircea Markus commented on ISPN-2933:
-------------------------------------
Whilst the patch (I think) will fix the intermittent failure I'm not sure there's no underlying problem caused by state transfer.
We don't wait for the cluster to form and on a INVALIDATION SYNC cache we do:
c.withFlag(LOCAL).put(k,v);
c.get(k); //this returns null, but as I've mentioned the cluster is still forming
I'm not sure how state transfer and invalidation works precisely, but I'd expect entries not to be shuffled around and c.get above not to be null - [~dan.berindei] can you please confirm?
If that's the case please close this JIRA (and the intermittent failure) and open a new one describing the specific problem.
> MixedModeTest.testMixedMode fails intermittently
> ------------------------------------------------
>
> Key: ISPN-2933
> URL: https://issues.jboss.org/browse/ISPN-2933
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.5.Final
> Reporter: Adrian Nistor
> Assignee: Mircea Markus
> Fix For: 5.3.0.Final
>
> Attachments: MixedModeTest.log
>
>
> {noformat}
> 2013-03-19 00:19:26,917 ERROR [org.infinispan.test.fwk.UnitTestTestNGListener] (testng-MixedModeTest) Test testMixedMode(org.infinispan.api.MixedModeTest) failed.
> java.lang.NullPointerException
> at org.infinispan.api.MixedModeTest.testMixedMode(MixedModeTest.java:72)
> {noformat}
--
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
11 years, 2 months
[JBoss JIRA] (ISPN-3078) @AfterMethod/alwaysRun and alike are not used correctly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3078?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3078:
--------------------------------
Description:
alwaysRun=true makes the invocation of that method to happen even if the test that has the method is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#...
E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod.
This is causing the suite to exit:
{quote}
[14:53:10][org.infinispan:infinispan-server-core]
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
{quote}
AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
was:
This is causing the suite to exit:
{quote}
[14:53:10][org.infinispan:infinispan-server-core]
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
{quote}
AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
The above issue is caused by the following:
This makes the invocation of that method happen even if the test is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#...
E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod.
> @AfterMethod/alwaysRun and alike are not used correctly
> --------------------------------------------------------
>
> Key: ISPN-3078
> URL: https://issues.jboss.org/browse/ISPN-3078
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 5.3.0.Beta1
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 5.3.0.Beta2
>
>
> alwaysRun=true makes the invocation of that method to happen even if the test that has the method is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#...
> E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod.
> This is causing the suite to exit:
> {quote}
> [14:53:10][org.infinispan:infinispan-server-core]
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> {quote}
> AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
>
> http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
--
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
11 years, 2 months
[JBoss JIRA] (ISPN-3078) @AfterMethod/alwaysRun and alike are not used correctly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3078?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3078:
--------------------------------
Summary: @AfterMethod/alwaysRun and alike are not used correctly (was: Marshalling test not cleaning up resources)
> @AfterMethod/alwaysRun and alike are not used correctly
> --------------------------------------------------------
>
> Key: ISPN-3078
> URL: https://issues.jboss.org/browse/ISPN-3078
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 5.3.0.Beta1
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 5.3.0.Beta2
>
>
> This is causing the suite to exit:
> {quote}
> [14:53:10][org.infinispan:infinispan-server-core]
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> {quote}
> AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
>
> http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
--
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
11 years, 2 months
[JBoss JIRA] (ISPN-3078) @AfterMethod/alwaysRun and alike are not used correctly
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3078?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3078:
--------------------------------
Description:
This is causing the suite to exit:
{quote}
[14:53:10][org.infinispan:infinispan-server-core]
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
{quote}
AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
The above issue is caused by the following:
This makes the invocation of that method happen even if the test is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#...
E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod.
was:
This is causing the suite to exit:
{quote}
[14:53:10][org.infinispan:infinispan-server-core]
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
[14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
{quote}
AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
> @AfterMethod/alwaysRun and alike are not used correctly
> --------------------------------------------------------
>
> Key: ISPN-3078
> URL: https://issues.jboss.org/browse/ISPN-3078
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 5.3.0.Beta1
> Reporter: Mircea Markus
> Assignee: Mircea Markus
> Fix For: 5.3.0.Beta2
>
>
> This is causing the suite to exit:
> {quote}
> [14:53:10][org.infinispan:infinispan-server-core]
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) Exiting because MarshallingTest has NOT shut down all the cache managers it has started !!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!! (testng-MarshallingTest) The still-running cacheManager was created here: org.infinispan.server.core.AbstractMarshallingTest.setUp(AbstractMarshallingTest.scala:49) !!!!!!!
> [14:53:10][org.infinispan:infinispan-server-core] !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> {quote}
> AbstractMarshallingTest.tearDown is always invoked(always=true) so I don't know why this doesn't get cleaned up. Anyway better to use TestUtil.killCacheManager(..) for handling this.
>
> http://ci.infinispan.org/viewLog.html?buildId=1005&buildTypeId=bt2&tab=bu...
> The above issue is caused by the following:
> This makes the invocation of that method happen even if the test is not in the running group:http://testng.org/javadoc/org/testng/annotations/BeforeMethod.html#...
> E.g. if I want to run the "xsite" groups, all the @AfterMethod(alwaysRun=true) from the "functional" groups are also invoked, most likely causing NPEs as the resources from this tests haven't been initialised. So unless used for an abstract test class that would be extended by multiple classes from different groups, I don't see any point in using "alwaysRun" on neither @BeforeMethod nor on @AfterMethod.
--
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
11 years, 2 months
[JBoss JIRA] (ISPN-3083) Recovery parser always enable it
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-3083:
---------------------------------
Summary: Recovery parser always enable it
Key: ISPN-3083
URL: https://issues.jboss.org/browse/ISPN-3083
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 5.3.0.Beta1
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
Priority: Minor
Fix For: 5.3.0.Final
in TransactionConfigurationBuilder:
{code:java}
public RecoveryConfigurationBuilder recovery() {
recovery.enable();
return recovery;
}
{code}
This will enable the Recovery in configurations like this:
{code:xml}
<namedCache name="noRecovery">
<transaction (...) transactionMode="NON_TRANSACTIONAL">
<recovery enabled="false" recoveryInfoCacheName="someName"/>
</transaction>
</namedCache>
{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
11 years, 2 months
[JBoss JIRA] (ISPN-3083) Recovery parser always enable it
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-3083?page=com.atlassian.jira.plugin.... ]
Work on ISPN-3083 started by Pedro Ruivo.
> Recovery parser always enable it
> --------------------------------
>
> Key: ISPN-3083
> URL: https://issues.jboss.org/browse/ISPN-3083
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 5.3.0.Beta1
> Reporter: Pedro Ruivo
> Assignee: Pedro Ruivo
> Priority: Minor
> Fix For: 5.3.0.Final
>
>
> in TransactionConfigurationBuilder:
> {code:java}
> public RecoveryConfigurationBuilder recovery() {
> recovery.enable();
> return recovery;
> }
> {code}
> This will enable the Recovery in configurations like this:
> {code:xml}
> <namedCache name="noRecovery">
> <transaction (...) transactionMode="NON_TRANSACTIONAL">
> <recovery enabled="false" recoveryInfoCacheName="someName"/>
> </transaction>
> </namedCache>
> {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
11 years, 2 months