[JBoss JIRA] (WFLY-10951) JDK11 elytron UndertowTwoWaySslNeedClientAuthTestCase failure
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10951?page=com.atlassian.jira.plugin... ]
Jan Kalina updated WFLY-10951:
------------------------------
Description:
Following exception occure instead of {{SSLHandshakeException | SocketException}}:
{code}
javax.net.ssl.SSLException: readHandshakeRecord
Caused by: java.net.SocketException: Broken pipe (Write failed)
{code}
To reproduce:
{code}
cd testsuite/integration/elytron
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
{code}
{code}
cd testsuite/integration/manualmode
JAVA_HOME=/opt/jdk-11+28/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=HTTPSWebConnectorTestCase
{code}
was:
Following exception occure instead of {{SSLHandshakeException | SocketException}}:
{code}
javax.net.ssl.SSLException: readHandshakeRecord
Caused by: java.net.SocketException: Broken pipe (Write failed)
{code}
To reproduce:
{code}
cd testsuite/integration/basic
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
{code}
{code}
cd testsuite/integration/elytron
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
{code}
{code}
cd testsuite/integration/manualmode
JAVA_HOME=/opt/jdk-11+28/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=HTTPSWebConnectorTestCase
{code}
> JDK11 elytron UndertowTwoWaySslNeedClientAuthTestCase failure
> -------------------------------------------------------------
>
> Key: WFLY-10951
> URL: https://issues.jboss.org/browse/WFLY-10951
> Project: WildFly
> Issue Type: Sub-task
> Components: Test Suite
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Following exception occure instead of {{SSLHandshakeException | SocketException}}:
> {code}
> javax.net.ssl.SSLException: readHandshakeRecord
> Caused by: java.net.SocketException: Broken pipe (Write failed)
> {code}
> To reproduce:
> {code}
> cd testsuite/integration/elytron
> JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
> {code}
> {code}
> cd testsuite/integration/manualmode
> JAVA_HOME=/opt/jdk-11+28/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=HTTPSWebConnectorTestCase
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (DROOLS-1952) [DMN Editor] Introduce marshalling test in the way DMN - String - DMN
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1952?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-1952:
--------------------------------
Story Points: 2
Sprint: 2018 Week 33-35
> [DMN Editor] Introduce marshalling test in the way DMN - String - DMN
> ---------------------------------------------------------------------
>
> Key: DROOLS-1952
> URL: https://issues.jboss.org/browse/DROOLS-1952
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.2.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Labels: drools-tools
>
> Currently marshaling test assumes as the initial input a *.dmn file that is consequently converted to Graph, next this Graph is converted to XML and finally the XML is transformed to Graph that is asserted for required properties.
> This task should introduce test that will assume as an initial input Graph, that will be converted to xml, this xml will be converted again to Graph and finally this Graph will be asserted for required properties.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (WFLY-10951) JDK11 elytron UndertowTwoWaySslNeedClientAuthTestCase failure
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/WFLY-10951?page=com.atlassian.jira.plugin... ]
Jan Kalina updated WFLY-10951:
------------------------------
Description:
Following exception occure instead of {{SSLHandshakeException | SocketException}}:
{code}
javax.net.ssl.SSLException: readHandshakeRecord
Caused by: java.net.SocketException: Broken pipe (Write failed)
{code}
To reproduce:
{code}
cd testsuite/integration/basic
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
{code}
{code}
cd testsuite/integration/elytron
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
{code}
{code}
cd testsuite/integration/manualmode
JAVA_HOME=/opt/jdk-11+28/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=HTTPSWebConnectorTestCase
{code}
was:
Following exception occure instead of {{SSLHandshakeException | SocketException}}:
{code}
javax.net.ssl.SSLException: readHandshakeRecord
Caused by: java.net.SocketException: Broken pipe (Write failed)
{code}
To reproduce:
{code}
cd testsuite/integration/basic
JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
{code}
{code}
cd testsuite/integration/manualmode
JAVA_HOME=/opt/jdk-11+28/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=HTTPSWebConnectorTestCase
{code}
> JDK11 elytron UndertowTwoWaySslNeedClientAuthTestCase failure
> -------------------------------------------------------------
>
> Key: WFLY-10951
> URL: https://issues.jboss.org/browse/WFLY-10951
> Project: WildFly
> Issue Type: Sub-task
> Components: Test Suite
> Reporter: Jan Kalina
> Assignee: Jan Kalina
>
> Following exception occure instead of {{SSLHandshakeException | SocketException}}:
> {code}
> javax.net.ssl.SSLException: readHandshakeRecord
> Caused by: java.net.SocketException: Broken pipe (Write failed)
> {code}
> To reproduce:
> {code}
> cd testsuite/integration/basic
> JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
> {code}
> {code}
> cd testsuite/integration/elytron
> JAVA_HOME=/opt/jdk-11/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=UndertowTwoWaySslNeedClientAuthTestCase
> {code}
> {code}
> cd testsuite/integration/manualmode
> JAVA_HOME=/opt/jdk-11+28/ PATH=$JAVA_HOME/bin:$PATH mvn test -Dtest=HTTPSWebConnectorTestCase
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month
[JBoss JIRA] (DROOLS-2825) Drools @Expires is not working with x seconds 7.4.1 Final Drools version
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2825?page=com.atlassian.jira.plugi... ]
Mario Fusco resolved DROOLS-2825.
---------------------------------
Resolution: Explained
In your reproducer you're not running drools in STREAM mode. In fact you correctly set the STREAM mode in the kieBaseModel, but then you totally override that configuration by doing:
{code:java}
KieBaseConfiguration configBase = ks.newKieBaseConfiguration();
configBase.setProperty("drools.propertySpecific", "ALWAYS");
kbase = kcontainer.newKieBase(kieBaseName, configBase);
{code}
By doing so you are creating a kiebase with a new configuration and then the existing one defined in the kmodule is ignored. Also note that the other property that you're setting it's useless because it is the default behaviour in drools 7. If you add
{code:java}
configBase.setProperty("drools.eventProcessingMode", "stream");
{code}
to the new config, or if you simply obtain the kbase with the config defined in the kmodule (something that I suggest) with
{code:java}
kbase = kcontainer.getKieBase();
{code}
then drools will run in stream mode and the expired events will be correctly evicted from the working memory as per your expectation.
> Drools @Expires is not working with x seconds 7.4.1 Final Drools version
> ------------------------------------------------------------------------
>
> Key: DROOLS-2825
> URL: https://issues.jboss.org/browse/DROOLS-2825
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.4.1.Final
> Reporter: Srinivas ev
> Assignee: Mario Fusco
> Priority: Blocker
> Fix For: 7.4.1.Final
>
> Attachments: EvictionTest.zip, heap.PNG
>
>
> Attached reproducer. Please check once,
> I inserted 5 Fact POJO's. It should have deleted after 200s based on declaration in the rule file.
> declare Fact
> @role( event )
> @expires(200s)
> end
> Heap dump shows the 5 entries even after I took the heap dump after 10 minutes. Please let me know regarding this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 1 month