[Red Hat JIRA] (ISPN-12730) NPE when mapping a repeated non-indexed field in a schema
by Cristiano Nicolai (Jira)
[ https://issues.redhat.com/browse/ISPN-12730?page=com.atlassian.jira.plugi... ]
Cristiano Nicolai commented on ISPN-12730:
------------------------------------------
Thanks [~gustavonalle] !
> NPE when mapping a repeated non-indexed field in a schema
> ---------------------------------------------------------
>
> Key: ISPN-12730
> URL: https://issues.redhat.com/browse/ISPN-12730
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 12.0.1.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Schema:
> {code}
> package com.redhat;
> message Attack {
> optional string type = 1;
> }
> /**
> * @Indexed
> */
> message ConnectedPlayer {
> optional string uuid = 1;
> optional string userName = 2;
> optional string match = 3;
> repeated Attack attacks = 4;
> /**
> * @Field(index=Index.YES, analyze = Analyze.NO, store = Store.NO)
> */
> optional int32 score = 5;
> optional int64 timestamp = 6;
> }
> {code}
> Cache Definition:
> {code:json}
> {
> "distributed-cache": {
> "mode": "SYNC",
> "encoding": {
> "key": {
> "media-type": "application/x-protostream"
> },
> "value": {
> "media-type": "application/x-protostream"
> }
> },
> "indexing": {
> "enabled":true,
> "indexed-entities" : ["com.redhat.ConnectedPlayer"]
> },
> "transaction": {
> "mode": "NON_XA"
> },
> "memory": {
> "storage": "HEAP"
> }
> }
> }
> {code}
> The cache creation will throw a NPE:
> {noformat}
> 08:25:43,520 ERROR (blocking-thread--p3-t4) [org.hibernate.search.engine.reporting.spi.RootFailureCollector] HSEARCH000521: Hibernate Search encountered a failure during bootstrap; continuing for now to list all problems, but the process will ultimately be aborted.
> Context: Infinispan Search Mapping, type 'com.redhat.ConnectedPlayer ([B)'
> Failure: java.lang.NullPointerException
> at org.infinispan.query.remote.impl.mapping.typebridge.ProtobufMessageBinder$State.bind(ProtobufMessageBinder.java:92)
> at org.infinispan.query.remote.impl.mapping.typebridge.ProtobufMessageBinder.createIndexReferenceProvider(ProtobufMessageBinder.java:49)
> at org.infinispan.query.remote.impl.mapping.typebridge.ProtobufMessageBinder.bind(ProtobufMessageBinder.java:34)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (ISPN-12747) The REST API getDetail cache request admin role
by Katia Aresti (Jira)
Katia Aresti created ISPN-12747:
-----------------------------------
Summary: The REST API getDetail cache request admin role
Key: ISPN-12747
URL: https://issues.redhat.com/browse/ISPN-12747
Project: Infinispan
Issue Type: Bug
Components: REST
Affects Versions: 12.0.1.Final
Reporter: Katia Aresti
Assignee: Katia Aresti
The REST API get detail cache requests data that need different acl
ADMIN, BULK_READ or READ.
Fix the endpoint so every ACL will get the data that can be handled for their access type
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (ISPN-12744) Spring Session Repository should replicate only changed attributes
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12744?page=com.atlassian.jira.plugi... ]
Dan Berindei commented on ISPN-12744:
-------------------------------------
A better option might be to wait for https://github.com/wildfly-clustering/wildfly-clustering-spring-session to support embedded caches, and then to deprecate our bundled session repository in favor of {{wildfly-clustering-spring-session}}.
> Spring Session Repository should replicate only changed attributes
> ------------------------------------------------------------------
>
> Key: ISPN-12744
> URL: https://issues.redhat.com/browse/ISPN-12744
> Project: Infinispan
> Issue Type: Enhancement
> Components: Spring Integration
> Affects Versions: 12.0.1.Final
> Reporter: Dan Berindei
> Priority: Major
>
> bq. During the lifecycle of an HTTP request, the HttpSession is typically persisted to SessionRepository twice. The first persist operation is to ensure that the session is available to the client as soon as the client has access to the session ID, and it is also necessary to write after the session is committed because further modifications to the session might be made. Having this in mind, we generally recommend that a SessionRepository implementation keep track of changes to ensure that only deltas are saved. This is particularly important in highly concurrent environments, where multiple requests operate on the same HttpSession and, therefore, cause race conditions, with requests overriding each other's changes to session attributes. All of the SessionRepository implementations provided by Spring Session use the described approach to persist session changes and can be used for guidance when you implement custom SessionRepository.
> https://docs.spring.io/spring-session/docs/2.4.2/reference/html5/#custom-...
> Our {{AbstractInfinispanSessionRepository}} saves the entire set of attributes of attributes, even if the only thing being updated is the last access timestamp (see {{updateTTL()}}. We could use functional commands (directly when the cache is embedded, via server-side tasks when the cache is remote) to replicate only the subset of created/modified/removed attributes. We should also investigate using our native max-idle support for TTL.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months
[Red Hat JIRA] (ISPN-12713) WELD-001417: Enabled interceptor class org.infinispan.jcache.annotation.CacheResultInterceptor
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12713?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12713:
--------------------------------
Status: Open (was: New)
> WELD-001417: Enabled interceptor class org.infinispan.jcache.annotation.CacheResultInterceptor
> ----------------------------------------------------------------------------------------------
>
> Key: ISPN-12713
> URL: https://issues.redhat.com/browse/ISPN-12713
> Project: Infinispan
> Issue Type: Bug
> Components: CDI
> Reporter: Diego Lovison
> Priority: Critical
>
> The reproducer is on the PR https://github.com/infinispan/infinispan/pull/9041
> {noformat}
> [INFO] Running org.infinispan.test.integration.thirdparty.cdi.GreetingServiceIT
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.045 s <<< FAILURE! - in org.infinispan.test.integration.thirdparty.cdi.GreetingServiceIT
> [ERROR] org.infinispan.test.integration.thirdparty.cdi.GreetingServiceIT Time elapsed: 0.006 s <<< ERROR!
> org.jboss.arquillian.container.spi.client.container.DeploymentException:
> Cannot deploy infinispan-server-integration.war: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"infinispan-server-integration.war\".WeldStartService" => "Failed to start service
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001417: Enabled interceptor class org.infinispan.jcache.annotation.CacheResultInterceptor (<{http://xmlns.jcp.org/xml/ns/javaee}class>org.infinispan.jcache.annotation.CacheResultInterceptor</{http://xmlns.jcp.org/xml/ns/javaee}class> in vfs:/content/infinispan-server-integration.war/WEB-INF/lib/infinispan-jcache-12.1.0-SNAPSHOT.jar/META-INF/beans.xml@8) does not match an interceptor bean: the class is not found, or not annotated with @Interceptor and still not registered through a portable extension, or not annotated with @Dependent inside an implicit bean archive"}}}}
> {noformat}
> I was not able to understand the root cause. Once we have more details, we can update the description and title.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
3 years, 10 months