November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9769) Do not initialize the SASL classes if not needed

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-9769: ------------------------------------- Summary: Do not initialize the SASL classes if not needed Key: ISPN-9769 URL: https://issues.jboss.org/browse/ISPN-9769 Project: Infinispan Issue Type: Bug Components: Security Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Alpha2 If SASL is not needed, don't even load the classes. This can save some memory. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9768) Do not register MBeans if they are disabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9768?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9768: ---------------------------------- Status: Open (was: New) > Do not register MBeans if they are disabled > ------------------------------------------- > > Key: ISPN-9768 > URL: https://issues.jboss.org/browse/ISPN-9768 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Alpha2 > > > If JMX is disabled, don't touch any of the MBean classes. This avoids initializing some internal JDK structures and reduces class count. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9768) Do not register MBeans if they are disabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9768?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9768: ---------------------------------- Fix Version/s: (was: 9.4.3.Final) > Do not register MBeans if they are disabled > ------------------------------------------- > > Key: ISPN-9768 > URL: https://issues.jboss.org/browse/ISPN-9768 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Alpha2 > > > If JMX is disabled, don't touch any of the MBean classes. This avoids initializing some internal JDK structures and reduces class count. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9768) Do not register MBeans if they are disabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9768?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9768: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6467 > Do not register MBeans if they are disabled > ------------------------------------------- > > Key: ISPN-9768 > URL: https://issues.jboss.org/browse/ISPN-9768 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Alpha2 > > > If JMX is disabled, don't touch any of the MBean classes. This avoids initializing some internal JDK structures and reduces class count. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9768) Do not register MBeans if they are disabled

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-9768: ------------------------------------- Summary: Do not register MBeans if they are disabled Key: ISPN-9768 URL: https://issues.jboss.org/browse/ISPN-9768 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.Alpha2, 9.4.3.Final If JMX is disabled, don't touch any of the MBean classes. This avoids initializing some internal JDK structures and reduces class count. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8663) The log is swapping the name and template

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8663?page=com.atlassian.jira.plugin.... ] Tristan Tarrant closed ISPN-8663. --------------------------------- Fix Version/s: 9.2.0.Final Assignee: Tristan Tarrant Resolution: Done This was fixed as part of ISPN-8670 > The log is swapping the name and template > ----------------------------------------- > > Key: ISPN-8663 > URL: https://issues.jboss.org/browse/ISPN-8663 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.0.Beta2 > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Minor > Fix For: 9.2.0.Final > > > Create a Java Class that access the cluster configuration using the Hot Rod protocol and execute the following code: > RemoteCache<Object, Object> cache = rmc.administration().getOrCreateCache("my-cache", "template-example"); > It will return: “ISPN000374: No such template ‘my-cache’ when declaring 'template-example' > To reproduce this issue the "template-example" must not exists. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8663) The log is swapping the name and template

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8663?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8663: ---------------------------------- Status: Open (was: New) > The log is swapping the name and template > ----------------------------------------- > > Key: ISPN-8663 > URL: https://issues.jboss.org/browse/ISPN-8663 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 9.2.0.Beta2 > Reporter: Diego Lovison > Priority: Minor > > Create a Java Class that access the cluster configuration using the Hot Rod protocol and execute the following code: > RemoteCache<Object, Object> cache = rmc.administration().getOrCreateCache("my-cache", "template-example"); > It will return: “ISPN000374: No such template ‘my-cache’ when declaring 'template-example' > To reproduce this issue the "template-example" must not exists. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9701) TransactionTable does not shutdown gracefully

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/ISPN-9701?page=com.atlassian.jira.plugin.... ] Paul Ferraro commented on ISPN-9701: ------------------------------------ {quote} Merged in 10.x and 9.4.x. 9.3.x, and 8.2.x are pending.{quote} To clarify, the backport to 8.2.x is needed for EAP 7.1.x; the backport to 9.3.x is needed for EAP 7.2.x. > TransactionTable does not shutdown gracefully > --------------------------------------------- > > Key: ISPN-9701 > URL: https://issues.jboss.org/browse/ISPN-9701 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 9.2.4.Final, 9.3.5.Final, 9.4.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Here's a sample stacktrace during shutdown: > {noformat} > 16:54:15,033 WARN [org.wildfly.clustering.web.undertow] (default task-1) ISPN000472: Cache manager is stopping: org.infinispan.IllegalLifecycleStateException: ISPN000472: Cache manager is stopping > at org.infinispan.marshall.core.GlobalMarshaller.getExternalizer(GlobalMarshaller.java:420) > at org.infinispan.marshall.core.GlobalMarshaller.writeNonNullableObject(GlobalMarshaller.java:400) > at org.infinispan.marshall.core.GlobalMarshaller.writeNullableObject(GlobalMarshaller.java:355) > at org.infinispan.marshall.core.GlobalMarshaller.writeObjectOutput(GlobalMarshaller.java:183) > at org.infinispan.marshall.core.GlobalMarshaller.writeObjectOutput(GlobalMarshaller.java:176) > at org.infinispan.marshall.core.GlobalMarshaller.objectToBuffer(GlobalMarshaller.java:305) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.marshallRequest(JGroupsTransport.java:1009) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.sendCommand(JGroupsTransport.java:1209) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.performAsyncRemoteInvocation(JGroupsTransport.java:1105) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotelyAsync(JGroupsTransport.java:246) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotelyAsync(RpcManagerImpl.java:291) > at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:323) > at org.infinispan.transaction.impl.TransactionTable.removeTransactionInfoRemotely(TransactionTable.java:900) > at org.infinispan.transaction.impl.TransactionTable.releaseLocksForCompletedTransaction(TransactionTable.java:886) > at org.infinispan.transaction.xa.XaTransactionTable.forgetSuccessfullyCompletedTransaction(XaTransactionTable.java:195) > at org.infinispan.transaction.xa.XaTransactionTable.commit(XaTransactionTable.java:128) > at org.infinispan.transaction.xa.TransactionXaAdapter.commit(TransactionXaAdapter.java:68) > at org.infinispan.commons.tx.TransactionImpl.finishResource(TransactionImpl.java:419) > at org.infinispan.commons.tx.TransactionImpl.commitResources(TransactionImpl.java:466) > at org.infinispan.commons.tx.TransactionImpl.runCommit(TransactionImpl.java:335) > at org.infinispan.commons.tx.TransactionImpl.commit(TransactionImpl.java:110) > {noformat} > The problem seems to be that shutDownGracefully() first waits for the localTransactions map to be empty. However, when the cache is clustered, releaseLocksForCompletedTransaction(...) removes the transaction from the localTransactions map *before* invoking removeTransactionInfoRemotely(...), which means that the subsequent TxCompletionNotificationCommand can fail to marshal (see above), or the transport might close before this command is sent. > A naive fix would simply reorder the removeLocalTransaction(...) to happen after the call to removeTransactionInfoRemotely(...) within the releaseLocksForCompletedTransaction(...) method, but I'm sure there's more to it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9766) Ickle query return unexpected (many) results for an optional numeric field in inner object if checked for "is null"

by Wolf-Dieter Fink (Jira)

[ https://issues.jboss.org/browse/ISPN-9766?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink edited comment on ISPN-9766 at 11/23/18 7:54 AM: ------------------------------------------------------------------ Same happen if I use runIckleQuery(qf, "from playground.Company c where c.employee is not empty and c.employee.age is null"); runIckleQuery(qf, "from playground.Company c where c.employee is empty"); Will find also all companies which have employees and will show the same results as runIckleQuery(qf, "from playground.Company c where c.employee is not empty"); was (Author: wdfink): Same happen if I use runIckleQuery(qf, "from playground.Company c where c.employee is not empty and c.employee.age is null"); runIckleQuery(qf, "from playground.Company c where c.employee is empty"); Will find also all companies which have employees > Ickle query return unexpected (many) results for an optional numeric field in inner object if checked for "is null" > ------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9766 > URL: https://issues.jboss.org/browse/ISPN-9766 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.4.2.Final > Environment: Follow the README of https://github.com/wfink/infinispan.playground.ickle > and use CompanyQueryHotRodClient > Reporter: Wolf-Dieter Fink > Priority: Major > Labels: Query > > If an object is declared like this: > https://github.com/wfink/infinispan.playground.ickle/blob/master/HotRodCl... > and the query is the following (in the linked project) > runIckleQuery(qf, "from playground.Company c where c.employee.age is null"); > the result return with Company object which does not have any Employee. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9766) Ickle query return unexpected (many) results for an optional numeric field in inner object if checked for "is null"

by Wolf-Dieter Fink (Jira)

[ https://issues.jboss.org/browse/ISPN-9766?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on ISPN-9766: ---------------------------------------- Same happen if I use runIckleQuery(qf, "from playground.Company c where c.employee is not empty and c.employee.age is null"); runIckleQuery(qf, "from playground.Company c where c.employee is empty"); Will find also all companies which have employees > Ickle query return unexpected (many) results for an optional numeric field in inner object if checked for "is null" > ------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9766 > URL: https://issues.jboss.org/browse/ISPN-9766 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Affects Versions: 9.4.2.Final > Environment: Follow the README of https://github.com/wfink/infinispan.playground.ickle > and use CompanyQueryHotRodClient > Reporter: Wolf-Dieter Fink > Priority: Major > Labels: Query > > If an object is declared like this: > https://github.com/wfink/infinispan.playground.ickle/blob/master/HotRodCl... > and the query is the following (in the linked project) > runIckleQuery(qf, "from playground.Company c where c.employee.age is null"); > the result return with Company object which does not have any Employee. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2018