September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-9425) HotRod Transaction Cache - Wrong values when a transactional cache stops in the middle of PrepareTransactionOperation/CompleteTransactionOperation

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9425?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9425: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR2 9.4.17.Final (was: 10.0.0.Final) Resolution: Done > HotRod Transaction Cache - Wrong values when a transactional cache stops in the middle of PrepareTransactionOperation/CompleteTransactionOperation > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9425 > URL: https://issues.jboss.org/browse/ISPN-9425 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 10.0.0.CR2, 9.4.17.Final > > > There are 3 scenarios and I believe that they are correlated. If it is not the case, a JIRA for each item should be open. > All scenarios below are multiple clients and one server. The following steps should be executed does not matter what is the scenario. > * Add one breakpoint at the first line of the method `acceptResponse` at the class PrepareTransactionOperation > * Add one breakpoint at the first line of the method `executeOperation` at the class PrepareTransactionOperation > *Scenario 1* > * Execute the client code ( Program 1 ) > * Execute the client code ( Program 2 ) > * Program 1 -> Resume, Resume, Resume. It will stop at `acceptResponse`. > * Program 2 -> Resume, Resume. It will stop at `executeOperation`. > * Wait 5 minutes or any time greater than 60 seconds ( I was not able to identify the right period of time but greater than 60 seconds should work), Resume and Resume the "Program 2". It will fail. > * The issue in scenario 1 is: Why doesn't matter the amount of time since it is greater than 60 seconds the request will fail? I am expecting something like a timeout in the "Program 1" and not expire when a call in that key was called for the first time. > * Kill all clients and servers > *Scenario 2* > * Execute the client code ( Program 1 ) > * Execute the client code ( Program 2 ) > * Program 1 -> Resume, Resume, Resume. It will stop at `acceptResponse`. > * Program 2 -> Resume, Resume, Resume, Resume. It will fail. Here you don't need to wait. Just press the Resume. > * Program 1 -> Resume. > * The issue in scenario 2 is: Why the test fails due: expected value 'null' different from 'random-value-generated' > * Kill all clients and servers > *Scenario 3* > * Execute the client code ( Program 1 ) > * Execute the client code ( Program 2 ) > * Program 1 -> Resume, Resume, Resume. It will stop at `acceptResponse`. > * Program 2 -> Resume, Resume, Resume, Resume. It will fail. Here you don't need to wait. Just press the Resume. > * Wait 60 seconds > * Re-run Program 2 -> Resume, Resume, Resume, Resume. It will work. > * Program 1 -> Resume, it will fail due to an assertion error > * The issue in scenario 3 is: When resuming the "Program 1" I am expecting an error during the commit phase and not an assertion error. > * Kill all clients and servers > Program 1 means that you should run the client code. It will create a separated JVM. > Program 2 means that you should run the client code. It will create a separated JVM. > It will be nice if we find out an way to automate this kind of tests. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10552) Ignored caches should be per server and not per endpoint

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10552: ---------------------------------------- Summary: Ignored caches should be per server and not per endpoint Key: ISPN-10552 URL: https://issues.jboss.org/browse/ISPN-10552 Project: Infinispan Issue Type: Bug Components: Server Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes The new server has ignored caches as a configuration for each endopoint, when in the wildfly server it was a global configuration that affected all endpoints -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9425) HotRod Transaction Cache - Wrong values when a transactional cache stops in the middle of PrepareTransactionOperation/CompleteTransactionOperation

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9425?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9425: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7259, https://github.com/infinispan/infinispan/pull/7260 > HotRod Transaction Cache - Wrong values when a transactional cache stops in the middle of PrepareTransactionOperation/CompleteTransactionOperation > -------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9425 > URL: https://issues.jboss.org/browse/ISPN-9425 > Project: Infinispan > Issue Type: Bug > Reporter: Diego Lovison > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 10.0.0.Final > > > There are 3 scenarios and I believe that they are correlated. If it is not the case, a JIRA for each item should be open. > All scenarios below are multiple clients and one server. The following steps should be executed does not matter what is the scenario. > * Add one breakpoint at the first line of the method `acceptResponse` at the class PrepareTransactionOperation > * Add one breakpoint at the first line of the method `executeOperation` at the class PrepareTransactionOperation > *Scenario 1* > * Execute the client code ( Program 1 ) > * Execute the client code ( Program 2 ) > * Program 1 -> Resume, Resume, Resume. It will stop at `acceptResponse`. > * Program 2 -> Resume, Resume. It will stop at `executeOperation`. > * Wait 5 minutes or any time greater than 60 seconds ( I was not able to identify the right period of time but greater than 60 seconds should work), Resume and Resume the "Program 2". It will fail. > * The issue in scenario 1 is: Why doesn't matter the amount of time since it is greater than 60 seconds the request will fail? I am expecting something like a timeout in the "Program 1" and not expire when a call in that key was called for the first time. > * Kill all clients and servers > *Scenario 2* > * Execute the client code ( Program 1 ) > * Execute the client code ( Program 2 ) > * Program 1 -> Resume, Resume, Resume. It will stop at `acceptResponse`. > * Program 2 -> Resume, Resume, Resume, Resume. It will fail. Here you don't need to wait. Just press the Resume. > * Program 1 -> Resume. > * The issue in scenario 2 is: Why the test fails due: expected value 'null' different from 'random-value-generated' > * Kill all clients and servers > *Scenario 3* > * Execute the client code ( Program 1 ) > * Execute the client code ( Program 2 ) > * Program 1 -> Resume, Resume, Resume. It will stop at `acceptResponse`. > * Program 2 -> Resume, Resume, Resume, Resume. It will fail. Here you don't need to wait. Just press the Resume. > * Wait 60 seconds > * Re-run Program 2 -> Resume, Resume, Resume, Resume. It will work. > * Program 1 -> Resume, it will fail due to an assertion error > * The issue in scenario 3 is: When resuming the "Program 1" I am expecting an error during the commit phase and not an assertion error. > * Kill all clients and servers > Program 1 means that you should run the client code. It will create a separated JVM. > Program 2 means that you should run the client code. It will create a separated JVM. > It will be nice if we find out an way to automate this kind of tests. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10550) Docs: REST v2 API Edits, Round Two

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10550?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10550: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7257 > Docs: REST v2 API Edits, Round Two > ---------------------------------- > > Key: ISPN-10550 > URL: https://issues.jboss.org/browse/ISPN-10550 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10550) Docs: REST v2 API Edits, Round Two

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10550?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10550: ------------------------------- Status: Open (was: New) > Docs: REST v2 API Edits, Round Two > ---------------------------------- > > Key: ISPN-10550 > URL: https://issues.jboss.org/browse/ISPN-10550 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10550) Docs: REST v2 API Edits, Round Two

by Donald Naro (Jira)

Donald Naro created ISPN-10550: ---------------------------------- Summary: Docs: REST v2 API Edits, Round Two Key: ISPN-10550 URL: https://issues.jboss.org/browse/ISPN-10550 Project: Infinispan Issue Type: Enhancement Reporter: Donald Naro Assignee: Donald Naro -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10549) Provide Externalizer aware Serialization marshaller as default user marshaller

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10549: ----------------------------------- Summary: Provide Externalizer aware Serialization marshaller as default user marshaller Key: ISPN-10549 URL: https://issues.jboss.org/browse/ISPN-10549 Project: Infinispan Issue Type: Sub-task Components: Marshalling Affects Versions: 10.0.0.CR1 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.CR2 In ISPN-10354 we removed jboss-marshalling from the core and made {{JavaSerializationMarshaller}} the default user marshaller instead of {{JBossUserMarshaller}}. Consequently, externalizers are only respected by the {{GlobalMarshaller}}, meaning that when store's marshall objects via {{InitializationContext::getPersistenceMarshaller}} any user configured externalizers are not used for serialising user types. We should provide a {{ExternalizerAwareSerializationMarshaller}} that first tries to serialize user types via any configured externalizers before defaulting to java Serialization. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10548) Remove UserMarshallerWhiteList

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-10548: ----------------------------------- Summary: Remove UserMarshallerWhiteList Key: ISPN-10548 URL: https://issues.jboss.org/browse/ISPN-10548 Project: Infinispan Issue Type: Sub-task Components: Core Affects Versions: 10.0.0.CR1 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.0.0.CR2 ISPN-10345 Introduced the UserMarshallerWhiteList for adding exceptions the serialization ClassWhiteList for internal types. This should not be necessary if our tests are updated to utilise Externalizers and the Number.class is added to `ClassWhiteList.SYS_ALLOWED_CLASSES`. -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10543) ServerNG Docs: Configure Logging

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10543?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10543: ------------------------------- Status: Open (was: New) > ServerNG Docs: Configure Logging > -------------------------------- > > Key: ISPN-10543 > URL: https://issues.jboss.org/browse/ISPN-10543 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > https://infinispan.org/docs/dev/titles/overview/overview.html#logging_que... > https://infinispan.org/docs/dev/titles/monitoring/monitoring.html#server_... > https://github.com/infinispan/infinispan/blob/fa89f568a34c2595e10eaffaa02... -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10543) ServerNG Docs: Configure Logging

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10543?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10543: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7256 > ServerNG Docs: Configure Logging > -------------------------------- > > Key: ISPN-10543 > URL: https://issues.jboss.org/browse/ISPN-10543 > Project: Infinispan > Issue Type: Enhancement > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > https://infinispan.org/docs/dev/titles/overview/overview.html#logging_que... > https://infinispan.org/docs/dev/titles/monitoring/monitoring.html#server_... > https://github.com/infinispan/infinispan/blob/fa89f568a34c2595e10eaffaa02... -- This message was sent by Atlassian Jira (v7.13.5#713005)

5 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019