[JBoss JIRA] (ISPRK-51) Infinispan 9.2.0.CR1 cause failures in the StreamingSuite
by Gustavo Fernandes (JIRA)
Gustavo Fernandes created ISPRK-51:
--------------------------------------
Summary: Infinispan 9.2.0.CR1 cause failures in the StreamingSuite
Key: ISPRK-51
URL: https://issues.jboss.org/browse/ISPRK-51
Project: Infinispan Spark
Issue Type: Bug
Reporter: Gustavo Fernandes
Always reproducible:
{noformat}
2018-02-15 11:03:44 [dispatcher-event-loop-3] ERROR ReceiverTracker:70 - Deregistered receiver for stream 0: Stopped by driver
[info] - test stream producer *** FAILED ***
[info] java.lang.Exception: Timeout waiting for condition.
[info] at org.infinispan.spark.test.TestingUtil$.waitForCondition$1(TestingUtil.scala:22)
[info] at org.infinispan.spark.test.TestingUtil$.waitForCondition(TestingUtil.scala:27)
[info] at org.infinispan.spark.test.TestingUtil$.waitForCondition(TestingUtil.scala:30)
[info] at org.infinispan.spark.suites.StreamingSuite$$anonfun$2.apply$mcV$sp(StreamingSuite.scala:76)
[info] at org.infinispan.spark.suites.StreamingSuite$$anonfun$2.apply(StreamingSuite.scala:56)
[info] at org.infinispan.spark.suites.StreamingSuite$$anonfun$2.apply(StreamingSuite.scala:56)
[info] at org.scalatest.Transformer$$anonfun$apply$1.apply$mcV$sp(Transformer.scala:22)
[info] at org.scalatest.OutcomeOf$class.outcomeOf(OutcomeOf.scala:85)
[info] at org.scalatest.OutcomeOf$.outcomeOf(OutcomeOf.scala:104)
[info] at org.scalatest.Transformer.apply(Transformer.scala:22)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8821) Infinispan 6.0.2 - Upgrading JGROUPS from ver 3.4.1 to ver 3.6.7 or later version
by Rohit Singh (JIRA)
Rohit Singh created ISPN-8821:
---------------------------------
Summary: Infinispan 6.0.2 - Upgrading JGROUPS from ver 3.4.1 to ver 3.6.7 or later version
Key: ISPN-8821
URL: https://issues.jboss.org/browse/ISPN-8821
Project: Infinispan
Issue Type: Component Upgrade
Environment: Oracle Linux - Exalogic/Exadata stack
AS: Weblogic 12.1.3
DB: Oracle 12.1.0.2
JDK: 1.8
Reporter: Rohit Singh
Priority: Critical
Ours is a J2EE application (clustered across 4 nodes) internally using Infinispan Cache (Ver 6.0.2) with JGroups (Ver 3.4.1) as transport layer of our cache.
Application had been running perfectly fine, but suddenly on one node, one cache-put got stuck with below stack trace. (Cause being blocked on org.jgroups.protocols.FlowControl$Credit.decrementIfEnoughCredits(FlowControl.java:567)).
Now all further puts are getting stuck - blocked - on the same line on the same node. Other nodes are working fine in this respect.
After discussing with [~belaban], he has suggested to upgrade to a later version of JGROUPS.
*{color:red}Refer: https://issues.jboss.org/browse/JGRP-2250{color}*
h2. *Now, we intend to use JGROUPS 3.6.7 or later version with INFINISPAN 6.0.2.*
*Please suggest on the feasibility of the upgrading JGROUPS.*
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8820) Don't allow lower-bound equals to upper-bound
by Pedro Ruivo (JIRA)
Pedro Ruivo created ISPN-8820:
---------------------------------
Summary: Don't allow lower-bound equals to upper-bound
Key: ISPN-8820
URL: https://issues.jboss.org/browse/ISPN-8820
Project: Infinispan
Issue Type: Bug
Components: Clustered Counter
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
The upper- and lower-bound are both inclusive. However, the case where upper==lower shouldn't be allowed since it can't change the counter's value.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month
[JBoss JIRA] (ISPN-8819) Simplify Hot Rod client security configuration
by Pedro Zapata (JIRA)
Pedro Zapata created ISPN-8819:
----------------------------------
Summary: Simplify Hot Rod client security configuration
Key: ISPN-8819
URL: https://issues.jboss.org/browse/ISPN-8819
Project: Infinispan
Issue Type: Feature Request
Components: Configuration, Hot Rod
Reporter: Pedro Zapata
Assignee: Tristan Tarrant
Configuring a Hot Rod client for authentication can be greatly simplified:
* default to DIGEST-MD5 mech
* use ApplicationRealm as default realm name
* implicitly enable security when setting one of the properties instead of invoking enable()
* add a way to specify a trust cert chain stored in a single PEM file without requiring a full-blown java KeyStore.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 1 month