[JBoss JIRA] (ISPN-10439) Rest server-ng Resource
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10439?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10439:
------------------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #32, DataGrid Sprint #33)
> Rest server-ng Resource
> -----------------------
>
> Key: ISPN-10439
> URL: https://issues.jboss.org/browse/ISPN-10439
> Project: Infinispan
> Issue Type: Feature Request
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
> Labels: console-ng
> Fix For: 10.0.0.CR2
>
>
> A REST resource to expose server-ng informartion and operations. Includes initially:
> * Configuration, including endpoint information
> * JVM stats
> * Shutdown operation
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (ISPN-10418) java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value)
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10418?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10418:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33)
> java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value)
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-10418
> URL: https://issues.jboss.org/browse/ISPN-10418
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Querying
> Affects Versions: 10.0.0.Beta4
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> This started to happen after upgrading to protostream 4.3 which introduces some asserts in FieldDescriptor.getDefaultValue() with the recently fixed IPROTO-80.
> This happens mainly due to IndexingTagHandler.indexMissingFields calling getDefaultValue() regardless of the type.
> {code}
> org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=686 returned server error (status=0x85): org.infinispan.remoting.RemoteException: ISPN000217: Received exception from RemoteContinuousQueryTest-NodeD-22902, see cause for remote stack trace
> org.hibernate.search.bridge.BridgeException: Exception while calling bridge#set
> entity class: org.infinispan.query.remote.impl.indexing.ProtobufValueWrapper
> field bridge: org.infinispan.query.remote.impl.indexing.ProtobufValueWrapperFieldBridge@1b9bf39c
> java.lang.UnsupportedOperationException: FieldDescriptor.getDefaultValue() called on an embedded message field (only scalars can have a default value).
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:340)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:177)
> at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:138)
> at org.infinispan.client.hotrod.impl.transport.netty.HintedReplayingDecoder.callDecode(HintedReplayingDecoder.java:94)
> at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:278)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (ISPN-10419) RocksDB purge should not utilise ArrayList to store multiple expired keys
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10419?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10419:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33)
> RocksDB purge should not utilise ArrayList to store multiple expired keys
> -------------------------------------------------------------------------
>
> Key: ISPN-10419
> URL: https://issues.jboss.org/browse/ISPN-10419
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.CR1
>
>
> Currently the RocksDB purge method stores multiple keys that expire at the same time in a ArrayList associated with the expiry time. This is currently marshallable because ArrayList is serializable and we utilise Jboss-marshalling, however ISPN-10354 means this is no longer possible in embedded mode when `infinispan-jboss-marshalling` is not present. Therefore, we should create a `ExpiryBucket` that can be marshalled via the persistence marshaller i.e. protobuf based.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (ISPN-10409) ByteBuf leak in the REST Server
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10409?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10409:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33)
> ByteBuf leak in the REST Server
> -------------------------------
>
> Key: ISPN-10409
> URL: https://issues.jboss.org/browse/ISPN-10409
> Project: Infinispan
> Issue Type: Bug
> Components: REST
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Critical
> Fix For: 10.0.0.Beta5
>
>
> From the Netty ResourceLeakDetector:
> {noformat}
> [0m[40.039s][info ][gc] GC(6) Pause Young (Normal) (G1 Evacuation Pause) 812M->114M(16384M) 136.927ms
> [31m08:31:03,559 ERROR [io.netty.util.ResourceLeakDetector] (REST-ServerIO-8-12) LEAK: ByteBuf.release() was not called before it's garbage-collected. See http://netty.io/wiki/reference-counted-objects.html for more information.
> Recent access records:
> Created at:
> io.netty:ispn-10.0@4.1.30.Final//io.netty.buffer.AbstractByteBufAllocator.compositeDirectBuffer(AbstractByteBufAllocator.java:221)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.buffer.AbstractByteBufAllocator.compositeBuffer(AbstractByteBufAllocator.java:199)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.handler.codec.MessageAggregator.decode(MessageAggregator.java:255)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:88)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:340)
> io.netty:ispn-10.0@4.1.30.Final//io.netty.handler.codec.MessageToMessageDecoder.channelRead(MessageToMessageDecoder.java:102)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (ISPN-10413) os-maven-plugin not setting `os.detected.classifier` property on partial maven builds
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10413?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10413:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33)
> os-maven-plugin not setting `os.detected.classifier` property on partial maven builds
> -------------------------------------------------------------------------------------
>
> Key: ISPN-10413
> URL: https://issues.jboss.org/browse/ISPN-10413
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> When executing {{mvn clean install -am -pl core}} the commons module will fail because the property {{os.detected.classifier}} is not set by the {{os-maven-plugin}} resulting in a NPE being thrown by the {{proto-schema-compatibility}} maven plugin.
> {code:java}
> [ERROR] Failed to execute goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check (default) on project infinispan-commons: Execution default of goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check failed.: NullPointerException -> [Help 1]
> {code}
> The solution is to add the following to the parent pom:
> {code:java}
> <extensions>
> <extension>
> <groupId>kr.motd.maven</groupId>
> <artifactId>os-maven-plugin</artifactId>
> </extension>
> </extensions>
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (ISPN-10414) Remove AtomicObjectFactory
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10414?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10414:
------------------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33)
> Remove AtomicObjectFactory
> --------------------------
>
> Key: ISPN-10414
> URL: https://issues.jboss.org/browse/ISPN-10414
> Project: Infinispan
> Issue Type: Task
> Components: API
> Affects Versions: 10.0.0.Beta4
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta5
>
>
> The AtomicObjectFactory has not been actively developed since it's inception in ISPN-3695 and is not documented in the user guide. We should remove this module.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
5 years, 3 months
[JBoss JIRA] (ISPN-10367) Possible loss of (pessimistic) lock if a transaction will reach timeout and/or is removed
by Pedro Zapata Fernandez (Jira)
[ https://issues.jboss.org/browse/ISPN-10367?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-10367:
------------------------------------------
Sprint: DataGrid Sprint #33, DataGrid Sprint #34 (was: DataGrid Sprint #33)
> 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
> 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.5#713005)
5 years, 3 months