May 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4303) Integrate jgroups server subsystem with security realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4303?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4303: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1099427|https://bugzilla.redhat.com/show_bug.cgi?id=1099427] from NEW to ASSIGNED > Integrate jgroups server subsystem with security realm > ------------------------------------------------------ > > Key: ISPN-4303 > URL: https://issues.jboss.org/browse/ISPN-4303 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4303) Integrate jgroups server subsystem with security realm

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4303?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4303: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1099427 > Integrate jgroups server subsystem with security realm > ------------------------------------------------------ > > Key: ISPN-4303 > URL: https://issues.jboss.org/browse/ISPN-4303 > Project: Infinispan > Issue Type: Sub-task > Components: Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4303) Integrate jgroups server subsystem with security realm

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-4303: ------------------------------------- Summary: Integrate jgroups server subsystem with security realm Key: ISPN-4303 URL: https://issues.jboss.org/browse/ISPN-4303 Project: Infinispan Issue Type: Sub-task Components: Server Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 7.0.0.Final -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4302) Set default isolation level to READ_COMMITTED in server

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4302?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4302: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2569 > Set default isolation level to READ_COMMITTED in server > ------------------------------------------------------- > > Key: ISPN-4302 > URL: https://issues.jboss.org/browse/ISPN-4302 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Martin Gencur > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4 > > > When <locking> configuration element is present in server configuration but isolation is not specified, the resulting value for isolation will be REPEATABLE_READ - this is inconsistent with library mode and further, REPEATABLE_READ is not a valid value in the server distribution as the server does not support transactions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4302) Set default isolation level to READ_COMMITTED in server

by Martin Gencur (JIRA)

Martin Gencur created ISPN-4302: ----------------------------------- Summary: Set default isolation level to READ_COMMITTED in server Key: ISPN-4302 URL: https://issues.jboss.org/browse/ISPN-4302 Project: Infinispan Issue Type: Bug Components: Server Reporter: Martin Gencur Assignee: Martin Gencur Fix For: 7.0.0.Alpha4 When <locking> configuration element is present in server configuration but isolation is not specified, the resulting value for isolation will be REPEATABLE_READ - this is inconsistent with library mode and further, REPEATABLE_READ is not a valid value in the server distribution as the server does not support transactions. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4298) HotRod kerberos auth doesn't see the ticket when creating RemoteCachManager

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4298?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4298: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Beta1 Resolution: Done > 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4297) Digest HR auth tests fails, unable to find container

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4297?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4297: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Beta1 Resolution: Done > Digest HR auth tests fails, unable to find container > ---------------------------------------------------- > > Key: ISPN-4297 > URL: https://issues.jboss.org/browse/ISPN-4297 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 7.0.0.Beta1 > > > Fails with > {noformat} > java.lang.IllegalArgumentException: Cannot find specified object in InfinispanContext, type: org.infinispan.arquillian.core.RemoteInfinispanServer, qualifier: container1 > {noformat} > Instead of creating new profile, configure the test to be able to run with default profile. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4047) Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24)

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4047?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4047: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Use the sort criteria provided by hql-parser (after fixing HQLPARSER-24) > ------------------------------------------------------------------------ > > Key: ISPN-4047 > URL: https://issues.jboss.org/browse/ISPN-4047 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Affects Versions: 6.0.1.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta1, 7.0.0.Final > > > Currently we have separate handling of the sort criteria in Infinispan because the JPQL parser skips it. See https://hibernate.atlassian.net/browse/HQLPARSER-24. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4294) Upgrade hibernate-hql-parser/hibernate-hql-lucene to 1.0.0.CR1

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-4294?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-4294: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade hibernate-hql-parser/hibernate-hql-lucene to 1.0.0.CR1 > -------------------------------------------------------------- > > Key: ISPN-4294 > URL: https://issues.jboss.org/browse/ISPN-4294 > Project: Infinispan > Issue Type: Component Upgrade > Affects Versions: 7.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta1, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4301) Handle storeMetadata=false in JpaStore.process and JpaStore.purge methods

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-4301?page=com.atlassian.jira.plugin.... ] Radim Vansa commented on ISPN-4301: ----------------------------------- In fact, we shouldn't run purge without metadata at all - no entries can expire without expiration timestamp (which is stored in metadata). > Handle storeMetadata=false in JpaStore.process and JpaStore.purge methods > ------------------------------------------------------------------------- > > Key: ISPN-4301 > URL: https://issues.jboss.org/browse/ISPN-4301 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 7.0.0.Alpha4 > Reporter: Radim Vansa > Assignee: Dan Berindei > > Even when storing metadata is disabled, JpaStore tries to fetch them in process (when ran with fetchMetadata=true) and in purge, the code enumerating and removing the metadata is executed even when there can't be any metadata. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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 May 2014