[JBoss JIRA] (ISPN-4631) NodeAuthentication*PassIT.testReadItemOnJoiningNode fails on RHEL6
by Dan Berindei (JIRA)
[ https://issues.jboss.org/browse/ISPN-4631?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-4631:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.1.0.Alpha1
Resolution: Done
> NodeAuthentication*PassIT.testReadItemOnJoiningNode fails on RHEL6
> ------------------------------------------------------------------
>
> Key: ISPN-4631
> URL: https://issues.jboss.org/browse/ISPN-4631
> Project: Infinispan
> Issue Type: Bug
> Components: Integration , Security
> Affects Versions: 7.0.0.Beta1
> Reporter: Dan Berindei
> Assignee: Vojtech Juranek
> Priority: Blocker
> Labels: testsuite_stability
> Fix For: 7.1.0.Alpha1, 7.0.0.CR1
>
>
> Failures appear only on the RHEL agents in CI, both in NodeAuthenticationKrbPassIT and NodeAuthenticationMD5PassIT:
> {noformat}
> java.lang.AssertionError: expected:<test_value> but was:<null>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.infinispan.test.integration.security.embedded.AbstractNodeAuthentication.testReadItemOnJoiningNode(AbstractNodeAuthentication.java:94)
> at org.infinispan.test.integration.security.embedded.NodeAuthenticationKrbPassIT.testReadItemOnJoiningNode(NodeAuthenticationKrbPassIT.java:71)
> {noformat}
> The failure in {{NodeAuthentication*FailIT.testReadItemOnJoiningNode}} is almost certainly related:
> {noformat}
> java.lang.Exception: Unexpected exception, expected<org.infinispan.manager.EmbeddedCacheManagerStartupException> but was<java.lang.Exception>
> at org.junit.Assert.fail(Assert.java:88)
> at org.junit.Assert.failNotEquals(Assert.java:743)
> at org.junit.Assert.assertEquals(Assert.java:118)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.infinispan.test.integration.security.embedded.AbstractNodeAuthentication.testReadItemOnJoiningNode(AbstractNodeAuthentication.java:94)
> at org.infinispan.test.integration.security.embedded.NodeAuthenticationMD5FailIT.testReadItemOnJoiningNode(NodeAuthenticationMD5FailIT.java:55)
> {noformat}
> http://ci.infinispan.org/viewLog.html?buildId=10776&tab=buildResultsDiv&b...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (ISPN-4975) Cross site state transfer - status of push gets stuck at "SENDING" after being cancelled
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4975?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4975:
-----------------------------------------------
Pedro Ruivo <pruivo(a)redhat.com> changed the Status of [bug 1163337|https://bugzilla.redhat.com/show_bug.cgi?id=1163337] from NEW to POST
> Cross site state transfer - status of push gets stuck at "SENDING" after being cancelled
> ----------------------------------------------------------------------------------------
>
> Key: ISPN-4975
> URL: https://issues.jboss.org/browse/ISPN-4975
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 7.0.0.Final
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
> Fix For: 7.1.0.Alpha1
>
>
> After invoking: site --cancelpush backupSite on the producer site, status of the push operation seems to get stuck at "SENDING" value (tested by site --pushstatus), even if state transfer is not currently in progress.
> Invoking site --cancelreceive mainSite on the consumer site works correctly. New invocation of site --push backupsite leads to "X-Site state transfer to '%s' already started!" being displayed. The issue seems to be caused by XSiteStateTransferManagerImpl.siteCollector not being cleared.
> Used configuration:
> distributed caches, site A: 2 nodes, site B: 3 nodes, B is a backup for A.
> Scenario
> - Start A,B
> - Take B offline using takeSiteOffline
> - Load data into A
> - Push state into B
> - CancelPushState B
> -- PushStateStatus remains stuck at SENDING & new push is not possible
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (ISPN-5022) Create a cachestore archetype
by Tristan Tarrant (JIRA)
Tristan Tarrant created ISPN-5022:
-------------------------------------
Summary: Create a cachestore archetype
Key: ISPN-5022
URL: https://issues.jboss.org/browse/ISPN-5022
Project: Infinispan
Issue Type: Feature Request
Components: Demos and Tutorials, Loaders and Stores
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 7.1.0.Final
We should have an AdvancedCacheWriter archetype which describes how to implement a proper cache store.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month
[JBoss JIRA] (ISPN-4983) Public API for tracking completion of Infinispan work for a given user transaction
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-4983?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-4983:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.1.0.Final
Resolution: Done
> Public API for tracking completion of Infinispan work for a given user transaction
> ----------------------------------------------------------------------------------
>
> Key: ISPN-4983
> URL: https://issues.jboss.org/browse/ISPN-4983
> Project: Infinispan
> Issue Type: Feature Request
> Reporter: Randall Hauch
> Assignee: Pedro Ruivo
> Labels: modeshape
> Fix For: 7.1.0.Alpha1, 7.1.0.Final
>
>
> When using Infinispan with user transactions, Infinispan will persist the changes to the cache store using a synchronization on the user transaction. This means the persistence operation begins when the user transaction has committed. However, components using Infinispan will likely want to know when Infinispan's work has completed for a given transaction.
> In Infinispan 6, it was possible to do this by registering a transaction listener:
> {code}
> org.infinispan.Cache cache = ...
> javax.transaction.Transaction activeTransaction = ...
> org.infinispan.transaction.TransactionTable txnTable = cache.getAdvancedCache().getComponentRegistry().getComponent(TransactionTable.class);
> org.infinispan.transaction.xa.GlobalTransaction ispnTxID = txnTable.getLocalTransaction(activeTransaction).getGlobalTransaction();
> {code}
> We'd then use the {{GlobalTransaction}} in our {{@Listener}}:
> {code}
> @Listener
> class TxnListener {
> @TransactionCompleted
> public void transactionCompleted( TransactionCompletedEvent event ) {
> if ( !event.isOriginLocal() ) return;
> GlobalTransaction eventIspnTransaction = event.getGlobalTransaction();
> if (eventIspnTransaction == null ||
> ispnTxID.getId() != eventIspnTransaction.getId()) return;
> if ( !event.isSuccessful() ) {
> // do stuff
> } else {
> // do other stuff
> }
> }
> {code}
> However, this is no longer possible in Infinispan 7 since these classes were moved to an "impl" package.
> Can we please have a public API to be notified when Infinispan has complete its work for a specific user transaction? It doesn't have to be like it was in 6, but ModeShape needs something (see MODE-2353 for details).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years, 1 month