[JBoss JIRA] (HRJS-7) Server sending two responses for same Iterator.next request
by Galder Zamarreño (JIRA)
Galder Zamarreño created HRJS-7:
-----------------------------------
Summary: Server sending two responses for same Iterator.next request
Key: HRJS-7
URL: https://issues.jboss.org/browse/HRJS-7
Project: Infinispan Javascript client
Issue Type: Bug
Reporter: Galder Zamarreño
Server receives:
{code}
server.log:10419:2016-04-25 14:55:30,600 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=139, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
server.log:10422:2016-04-25 14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=140, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
server.log:10425:2016-04-25 14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=141, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
{code}
But it replies with:
{code}
server.log:10426:2016-04-25 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=139, cacheName=, operation=IterationNextResponse, status=Success}
server.log:10428:2016-04-25 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
server.log:10430:2016-04-25 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
{code}
As a result, client never receives response for messageId=140.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (HRJS-7) Server sending two responses for same Iterator.next request
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/HRJS-7?page=com.atlassian.jira.plugin.sys... ]
Galder Zamarreño updated HRJS-7:
--------------------------------
Description:
Server receives:
{code}
14:55:30,600 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=139, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=140, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=141, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
{code}
But it replies with:
{code}
14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=139, cacheName=, operation=IterationNextResponse, status=Success}
14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
{code}
As a result, client never receives response for messageId=140.
was:
Server receives:
{code}
server.log:10419:2016-04-25 14:55:30,600 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=139, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
server.log:10422:2016-04-25 14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=140, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
server.log:10425:2016-04-25 14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=141, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
{code}
But it replies with:
{code}
server.log:10426:2016-04-25 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=139, cacheName=, operation=IterationNextResponse, status=Success}
server.log:10428:2016-04-25 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
server.log:10430:2016-04-25 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
{code}
As a result, client never receives response for messageId=140.
> Server sending two responses for same Iterator.next request
> -----------------------------------------------------------
>
> Key: HRJS-7
> URL: https://issues.jboss.org/browse/HRJS-7
> Project: Infinispan Javascript client
> Issue Type: Bug
> Reporter: Galder Zamarreño
>
> Server receives:
> {code}
> 14:55:30,600 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=139, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> 14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=140, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> 14:55:30,601 TRACE [org.infinispan.server.hotrod.HotRodDecoder] (HotRodServerWorker-7-1) Decoded header HotRodHeader{op=IterationNextRequest, version=25, messageId=141, cacheName=, flag=0, clientIntelligence=3, topologyId=0}
> {code}
> But it replies with:
> {code}
> 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=139, cacheName=, operation=IterationNextResponse, status=Success}
> 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
> 14:55:30,608 TRACE [org.infinispan.server.hotrod.ContextHandler] (HotRodServerHandler-10-1) Write response IterationNextResponse{version=25, messageId=141, cacheName=, operation=IterationNextResponse, status=Success}
> {code}
> As a result, client never receives response for messageId=140.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-201) make JDBC cache store use DB transactions for commit/rollback
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-201?page=com.atlassian.jira.plugin.s... ]
Ryan Emerson reassigned ISPN-201:
---------------------------------
Assignee: Ryan Emerson (was: William Burns)
> make JDBC cache store use DB transactions for commit/rollback
> -------------------------------------------------------------
>
> Key: ISPN-201
> URL: https://issues.jboss.org/browse/ISPN-201
> Project: Infinispan
> Issue Type: Feature Request
> Components: Loaders and Stores
> Reporter: Mircea Markus
> Assignee: Ryan Emerson
> Labels: modshape
> Fix For: 9.0.0.Final
>
>
> current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6543) Spark connector fails with CCE when compatibility mode is enabled
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-6543?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes commented on ISPN-6543:
-----------------------------------------
Is this a regression? I thought compatibility mode in the Remote Iterator was fixed by ISPN-6200
> Spark connector fails with CCE when compatibility mode is enabled
> -----------------------------------------------------------------
>
> Key: ISPN-6543
> URL: https://issues.jboss.org/browse/ISPN-6543
> Project: Infinispan
> Issue Type: Bug
> Components: Spark
> Reporter: Vojtech Juranek
>
> Fails with
> {noformat}
> org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=125 returned server error (status=0x85): java.lang.ClassCastException: java.lang.Integer cannot be cast to [B
> at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:132)
> at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:118)
> at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
> at org.infinispan.client.hotrod.impl.operations.IterationNextOperation.execute(IterationNextOperation.java:48)
> at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.fetch(RemoteCloseableIterator.java:100)
> at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.hasNext(RemoteCloseableIterator.java:84)
> at org.infinispan.spark.rdd.InfinispanIterator.hasNext(InfinispanIterator.scala:13)
> at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:327)
> at org.apache.spark.util.random.SamplingUtils$.reservoirSampleAndCount(SamplingUtils.scala:41)
> at org.apache.spark.RangePartitioner$$anonfun$9.apply(Partitioner.scala:261)
> at org.apache.spark.RangePartitioner$$anonfun$9.apply(Partitioner.scala:259)
> at org.apache.spark.rdd.RDD$$anonfun$mapPartitionsWithIndex$1$$anonfun$apply$22.apply(RDD.scala:745)
> at org.apache.spark.rdd.RDD$$anonfun$mapPartitionsWithIndex$1$$anonfun$apply$22.apply(RDD.scala:745)
> at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
> at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:306)
> at org.apache.spark.rdd.RDD.iterator(RDD.scala:270)
> at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66)
> at org.apache.spark.scheduler.Task.run(Task.scala:89)
> at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6544) Management console should not be accessible in standalone mode
by Roman Macor (JIRA)
Roman Macor created ISPN-6544:
---------------------------------
Summary: Management console should not be accessible in standalone mode
Key: ISPN-6544
URL: https://issues.jboss.org/browse/ISPN-6544
Project: Infinispan
Issue Type: Bug
Components: Console
Reporter: Roman Macor
Assignee: Vladimir Blagojevic
Attachments: Screenshot-standaloneMode.png
Management console is supported only in domain mode, but user can still log into console in standalone mode (no values are displayed, only skeleton of the console - please see the screenshot)
I believe Management Console should display a warning, saying that it's only supported in domain mode.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-5210) Support writing multiple modifications to cache stores in batch when using Transactions
by Ryan Emerson (JIRA)
[ https://issues.jboss.org/browse/ISPN-5210?page=com.atlassian.jira.plugin.... ]
Ryan Emerson reassigned ISPN-5210:
----------------------------------
Assignee: Ryan Emerson
> Support writing multiple modifications to cache stores in batch when using Transactions
> ---------------------------------------------------------------------------------------
>
> Key: ISPN-5210
> URL: https://issues.jboss.org/browse/ISPN-5210
> Project: Infinispan
> Issue Type: Feature Request
> Components: Loaders and Stores
> Affects Versions: 6.0.2.Final, 7.1.0.Final
> Reporter: Richard Lucas
> Assignee: Ryan Emerson
> Fix For: 9.0.0.Alpha2
>
>
> Currently writes to a cache store are performed individually for each modification to the cache.
> While this makes sense when using a non-tx cache it would be beneficial to support writing multiple modifications to a cache store in a single call when using a Tx cache.
> Currently all writes are performed in the commit phase and are done by looping through the modifications in the Tx and writing each one in turn to the the store.
> Instead of doing this it would useful to pass all modifications to the store in a single call, this would allow:
> a) Taking advantage of support for batch updates in underlying stores (JDBC, MongoDB, DynamoDB) for a more efficient write through.
> b) Allow store implementations the chance to clean up if one or more updates in the batch fail (this is especially useful if the store does not support Tx and rollbacks as it means the store implementation can at least try to clean up any partial updates it has performed, something which is not currently possible).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6543) Spark connector fails with CCE when compatibility mode is enabled
by Vojtech Juranek (JIRA)
Vojtech Juranek created ISPN-6543:
-------------------------------------
Summary: Spark connector fails with CCE when compatibility mode is enabled
Key: ISPN-6543
URL: https://issues.jboss.org/browse/ISPN-6543
Project: Infinispan
Issue Type: Bug
Components: Spark
Reporter: Vojtech Juranek
Fails with
{noformat}
org.infinispan.client.hotrod.exceptions.HotRodClientException:Request for messageId=125 returned server error (status=0x85): java.lang.ClassCastException: java.lang.Integer cannot be cast to [B
at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:343)
at org.infinispan.client.hotrod.impl.protocol.Codec20.readPartialHeader(Codec20.java:132)
at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:118)
at org.infinispan.client.hotrod.impl.operations.HotRodOperation.readHeaderAndValidate(HotRodOperation.java:56)
at org.infinispan.client.hotrod.impl.operations.IterationNextOperation.execute(IterationNextOperation.java:48)
at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.fetch(RemoteCloseableIterator.java:100)
at org.infinispan.client.hotrod.impl.iteration.RemoteCloseableIterator.hasNext(RemoteCloseableIterator.java:84)
at org.infinispan.spark.rdd.InfinispanIterator.hasNext(InfinispanIterator.scala:13)
at scala.collection.Iterator$$anon$11.hasNext(Iterator.scala:327)
at org.apache.spark.util.random.SamplingUtils$.reservoirSampleAndCount(SamplingUtils.scala:41)
at org.apache.spark.RangePartitioner$$anonfun$9.apply(Partitioner.scala:261)
at org.apache.spark.RangePartitioner$$anonfun$9.apply(Partitioner.scala:259)
at org.apache.spark.rdd.RDD$$anonfun$mapPartitionsWithIndex$1$$anonfun$apply$22.apply(RDD.scala:745)
at org.apache.spark.rdd.RDD$$anonfun$mapPartitionsWithIndex$1$$anonfun$apply$22.apply(RDD.scala:745)
at org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:38)
at org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:306)
at org.apache.spark.rdd.RDD.iterator(RDD.scala:270)
at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:66)
at org.apache.spark.scheduler.Task.run(Task.scala:89)
at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:213)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (ISPN-6159) Remove deprecated continuous query API
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6159?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6159:
--------------------------------
Description:
This is a continuation of ISPN-6069.
The deprecated bits should be removed now:
org.infinispan.client.hotrod.event.ClientEvents.addContinuousQueryListener,
org.infinispan.query.continuous.ContinuousQuery,
org.infinispan.query.continuous.ContinuousQueryResultListener,
org.infinispan.query.continuous.ContinuousQueryListener.
was:
This is a continuation of ISPN-6069.
The deprecated bits should be removed now:
ClientEvents.addContinuousQueryListener,
> Remove deprecated continuous query API
> --------------------------------------
>
> Key: ISPN-6159
> URL: https://issues.jboss.org/browse/ISPN-6159
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Adrian Nistor
> Fix For: 9.0.0.Alpha2, 9.0.0.Final
>
>
> This is a continuation of ISPN-6069.
> The deprecated bits should be removed now:
> org.infinispan.client.hotrod.event.ClientEvents.addContinuousQueryListener,
> org.infinispan.query.continuous.ContinuousQuery,
> org.infinispan.query.continuous.ContinuousQueryResultListener,
> org.infinispan.query.continuous.ContinuousQueryListener.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months