[JBoss JIRA] (ISPN-4091) Transactions and data should prefer to be sourced from a primary owner
by William Burns (JIRA)
[ https://issues.jboss.org/browse/ISPN-4091?page=com.atlassian.jira.plugin.... ]
William Burns updated ISPN-4091:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.0.0.Beta1
Resolution: Done
> Transactions and data should prefer to be sourced from a primary owner
> ----------------------------------------------------------------------
>
> Key: ISPN-4091
> URL: https://issues.jboss.org/browse/ISPN-4091
> Project: Infinispan
> Issue Type: Bug
> Components: State Transfer
> Affects Versions: 5.2.7.Final
> Reporter: Erik Salter
> Assignee: Dan Berindei
> Fix For: 7.0.0.Beta1
>
>
> The current state transfer mechanism will ask the backup segments for transaction and state information. However, this breaks if there is a pessimistic transaction executing on the primary data owner, Consider the following use case:
> A new owner joins and sources the ongoing transactions and data for key k from the backup. Meanwhile, a local transaction has started on the primary owner for k, but has not prepared on any remote nodes. So the new node does not know about the ongoing transaction. While that's going on, a new tx starts on the new owner. Since these are pessimistic, the new transaction will acquires the lock for the same key.
> So we can have data inconsistency.
> The state transfer mechanism should prefer to source the transaction and state information from the primary owner. This should cover all cases: if the originator is not the primary owner, then any (backup) locks must be replicated to all the owners, either directly during the tx or during a previous state transfer.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (ISPN-4300) JPA cachestore fails with DB2-97
by Vojtech Juranek (JIRA)
[ https://issues.jboss.org/browse/ISPN-4300?page=com.atlassian.jira.plugin.... ]
Vojtech Juranek commented on ISPN-4300:
---------------------------------------
Recent build has [passed|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUN...]. AFAIK there weren't any changed related to JPA, so this failure seems to be random. Not sure if related, but I found some other bugs (e.g. [BZ #1067330|https://bugzilla.redhat.com/show_bug.cgi?id=1067330]), which mention similar failure on DB2-97 to be random. One possible explanation *could* be, that there's some issue in our DB2-97 environment, which causes these random failures.
> JPA cachestore fails with DB2-97
> --------------------------------
>
> Key: ISPN-4300
> URL: https://issues.jboss.org/browse/ISPN-4300
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Reporter: Vojtech Juranek
> Assignee: Dan Berindei
>
> When running JPA cachestore with DB2-97, it fails with
> {noformat}
> [...]
> Caused by: org.hibernate.exception.SQLGrammarException: could not extract ResultSet
> [...]
> Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=DBALLO04.__ispn_metadata__, DRIVER=4.14.122
> {noformat}
> Full stack trace of the failure can be found [here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/...], the log of whole build [here|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/...]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (ISPN-4298) HotRod kerberos auth doesn't see the ticket when creating RemoteCachManager
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-4298?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-4298:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1099054|https://bugzilla.redhat.com/show_bug.cgi?id=1099054] from NEW to ON_QA
> HotRod kerberos auth doesn't see the ticket when creating RemoteCachManager
> ---------------------------------------------------------------------------
>
> Key: ISPN-4298
> URL: https://issues.jboss.org/browse/ISPN-4298
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Reporter: Vojtech Juranek
> Assignee: Tristan Tarrant
> Fix For: 7.0.0.Beta1
>
>
> When HR client obtains initial GSSAPI challenge (usually when creating {{RemoteCachManager}}), it fails with
> {noformat}
> Caused by: javax.security.sasl.SaslException: GSS initiate failed [Caused by GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]
> at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:212)
> at org.infinispan.client.hotrod.impl.transport.tcp.SaslTransportObjectFactory.makeObject(SaslTransportObjectFactory.java:67)
> at org.infinispan.client.hotrod.impl.transport.tcp.SaslTransportObjectFactory.makeObject(SaslTransportObjectFactory.java:25)
> at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:306)
> ... 109 more
> Caused by: GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)
> at sun.security.jgss.krb5.Krb5InitCredential.getInstance(Krb5InitCredential.java:147)
> at sun.security.jgss.krb5.Krb5MechFactory.getCredentialElement(Krb5MechFactory.java:121)
> at sun.security.jgss.krb5.Krb5MechFactory.getMechanismContext(Krb5MechFactory.java:187)
> at sun.security.jgss.GSSManagerImpl.getMechanismContext(GSSManagerImpl.java:223)
> at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:212)
> at sun.security.jgss.GSSContextImpl.initSecContext(GSSContextImpl.java:179)
> at com.sun.security.sasl.gsskerb.GssKrb5Client.evaluateChallenge(GssKrb5Client.java:193)
> ... 113 more
> {noformat}
> When the code is wrapped by {{PrivilegedExceptionAction}}, e.g.
> {code}
> final Configuration config = getRemoteCacheManagerConfig(subj);
> Subject.doAs(subj, new PrivilegedExceptionAction<Void>() {
> public Void run() throws Exception {
> remoteCacheManager = new RemoteCacheManager(config, true);
> return null;
> }
> });
> {code}
> everything works fine
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months
[JBoss JIRA] (ISPN-4304) Speed up execution of OSGi tests
by Martin Gencur (JIRA)
Martin Gencur created ISPN-4304:
-----------------------------------
Summary: Speed up execution of OSGi tests
Key: ISPN-4304
URL: https://issues.jboss.org/browse/ISPN-4304
Project: Infinispan
Issue Type: Task
Components: Test Suite - Core
Affects Versions: 7.0.0.Alpha4
Reporter: Martin Gencur
Assignee: Martin Gencur
* Start the Karaf container only once and run all the tests instead of starting the container before each test class
* place the OSGi tests into the default Maven profile
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 5 months