October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10814) Large Objects may not be used in auto-commit mode

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10814?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10814: -------------------------------- Affects Version/s: 10.0.0.CR3 > Large Objects may not be used in auto-commit mode > ------------------------------------------------- > > Key: ISPN-10814 > URL: https://issues.jboss.org/browse/ISPN-10814 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR3 > Reporter: Gustavo Lira e Silva > Assignee: Gustavo Lira e Silva > Priority: Major > Fix For: 10.0.0.Final > > > https://github.com/infinispan/infinispan/blob/d372a4c80d80d149aa82909cee4... > is throwing the following exception with postgres > {noformat} > Large Objects may not be used in auto-commit mode > {noformat} > To fix, we can just change: > {code:java} > ps.setBlob(2, new ByteArrayInputStream(data)); > {code} > to > {code:java} > ps.setBytes(2, data); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10736) Operator Docs: Persistent storage volume

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10736?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10736: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/186 > Operator Docs: Persistent storage volume > ---------------------------------------- > > Key: ISPN-10736 > URL: https://issues.jboss.org/browse/ISPN-10736 > Project: Infinispan > Issue Type: Task > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10514) Server Docs: Describe various methods to create caches

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10514?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10514: ------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #36 (was: DataGrid Sprint #33, DataGrid Sprint #35) > Server Docs: Describe various methods to create caches > ------------------------------------------------------ > > Key: ISPN-10514 > URL: https://issues.jboss.org/browse/ISPN-10514 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Also describes the default cache templates and how to retrieve them via rest and cli. > As a user, I want to create caches at startup. > As a user, I want to create caches on the fly/dynamically. > As a user, I want to create permanent caches. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10591) Remove jboss-marshalling and make Protostream the default user marshaller

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10591?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10591. --------------------------------- Resolution: Done > Remove jboss-marshalling and make Protostream the default user marshaller > ------------------------------------------------------------------------- > > Key: ISPN-10591 > URL: https://issues.jboss.org/browse/ISPN-10591 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Affects Versions: 10.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > > Protostream should be used as the default marshaller for user types unless a user explicitly provides a custom marshaller via {{SerializationConfiguration.marshaller}}. > This requires that all of our testsuite is also updated to provide protostream pojos and that the `infinispan-jboss-marshalling` dependency is removed from all possible sub-modules. Most notably: > * core > * query > * server > * client > This will require various integration tests to also be updated to reflect the new behaviour, as the APPLICATION_JBOSS_MARSHALLING media type will not be available to the client/server by default. > In order for a user to utilise jboss-marshalling on the client side, it's necessary for the `infinispan-jboss-marshalling` jar to be added to the classpath. Furthermore, if APPLICATION_OBJECT storage is desired on the server and jboss-marshalling is utilised on the client, it's also necessary for the dependency to be added to the server. In order to verify that this functionality works as expected, it's necessary for a `integrationtests/jboss-marshalling` sub-module to be created in order to test these scenarios. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10326) Introduce `.impl` package for internal marshalling classes

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10326?page=com.atlassian.jira.plugin... ] Ryan Emerson updated ISPN-10326: -------------------------------- Fix Version/s: (was: 10.0.0.Final) > Introduce `.impl` package for internal marshalling classes > ---------------------------------------------------------- > > Key: ISPN-10326 > URL: https://issues.jboss.org/browse/ISPN-10326 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > Currently the `org.infinispan.marshall.core` and `org.infinispan.commons.marshall` packages expose a lot of internal classes which users should never attempt to use. To make this clearer, we should migrate internal classes to a `impl` package. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10507) Update Marshalling documentation and upgrade notes

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10507?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10507. --------------------------------- Resolution: Done > Update Marshalling documentation and upgrade notes > -------------------------------------------------- > > Key: ISPN-10507 > URL: https://issues.jboss.org/browse/ISPN-10507 > Project: Infinispan > Issue Type: Sub-task > Components: Documentation-Core > Affects Versions: 10.0.0.CR1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10764) Clustered Graceful Shutdown for server

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10764?page=com.atlassian.jira.plugin... ] Gustavo Fernandes updated ISPN-10764: ------------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Clustered Graceful Shutdown for server > -------------------------------------- > > Key: ISPN-10764 > URL: https://issues.jboss.org/browse/ISPN-10764 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.0.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Final > > > * Allow the server to shutdown any other node as well as the whole cluster > * Add REST APIs for specific node shutdown and clustered shutdown > * Add corresponding CLI commands -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10367) Possible loss of (pessimistic) lock if a transaction will reach timeout and/or is removed

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10367?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10367: ------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35 (was: DataGrid Sprint #33, DataGrid Sprint #34) > Possible loss of (pessimistic) lock if a transaction will reach timeout and/or is removed > ----------------------------------------------------------------------------------------- > > Key: ISPN-10367 > URL: https://issues.jboss.org/browse/ISPN-10367 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Affects Versions: 10.0.0.Beta3, 9.4.15.Final > Environment: Infinispan with pessimistic locking enabled > Reporter: Wolf-Dieter Fink > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 10.0.0.Final > > Attachments: StressApp.zip > > > If entries are locked, no matter whether it was done by FORCE_WRITE_LOCK flag or getAdvancedCache().lock(key), and the lock is hold longer than the current Tx timeout setting (.completedTxTimeout(...) ) the transacaction might be removed > - if the node is blocked and expelled from the cluster (and join back later) > - the thread processing the lock will take longer than the Tx-timeout setting > This force to remove the Tx and free the lock. > An indicator is the Exception below which will be shown if the Tx is timing out, it is not a (remote) access timout. > If the originator is back after this this (ongoing) Tx is assumed new and it will continue by accident without lock. > This can cause unexpected inconsistency! > ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (EJB timer - 13) ISPN000136: Error executing command LockControlCommand, writing keys []: org.infinispan.util.concurrent.TimeoutException: Replication timeout for lt-33828 > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:803) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$1(JGroupsTransport.java:641) > at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ERROR [org.jboss.as.ejb3.timer] (EJB timer - 13) WFLYEJB0020: Error invoking timeout for timer: [id=8a53d2c3-190d-4c74-9327-8e7554e1df2c timedObjectId=embeddedStressTest-ejb.embeddedStressTest-ejb.CacheAccessSingletonBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@72c41b07 initialExpiration=Fri Jun 28 10:56:16 CEST 2019 intervalDuration(in milli sec)=1 nextExpiration=Fri Jun 28 10:56:43 CEST 2019 timerState=IN_TIMEOUT info=org.infinispan.wfink.stress.TimerInfo@47ae2053]: javax.ejb.EJBException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for lt-33828 > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:246) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:388) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:146) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > at org.jboss.as.ejb3.component.singleton.ContainerManagedConcurrencyInterceptor.processInvocation(ContainerManagedConcurrencyInterceptor.java:106) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:99) > at org.jboss.as.ejb3.timerservice.TimedObjectInvokerImpl.callTimeout(TimedObjectInvokerImpl.java:109) > at org.jboss.as.ejb3.timerservice.TimerTask.invokeBeanMethod(TimerTask.java:189) > at org.jboss.as.ejb3.timerservice.TimerTask.callTimeout(TimerTask.java:185) > at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:159) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1304) > at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:494) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for lt-33828 > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.checkRsp(JGroupsTransport.java:803) > at org.infinispan.remoting.transport.jgroups.JGroupsTransport.lambda$invokeRemotelyAsync$1(JGroupsTransport.java:641) > at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602) > at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577) > at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474) > at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1962) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:47) > at org.infinispan.remoting.transport.jgroups.RspListFuture.call(RspListFuture.java:16) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10810) Add Serializable override methods for the Async methods

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10810?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10810. --------------------------------- Resolution: Done > Add Serializable override methods for the Async methods > ------------------------------------------------------- > > Key: ISPN-10810 > URL: https://issues.jboss.org/browse/ISPN-10810 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > We added the Serializable override methods for the sync variants of functional methods. We however missed the async variants, we should add these as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10811) Provide utility to convert caches configuration between JSON and XML

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10811?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10811: ----------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide utility to convert caches configuration between JSON and XML > -------------------------------------------------------------------- > > Key: ISPN-10811 > URL: https://issues.jboss.org/browse/ISPN-10811 > Project: Infinispan > Issue Type: Bug > Components: REST > Affects Versions: 10.0.0.CR3 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 October 2019