[JBoss JIRA] (DROOLS-4175) Error in compiling BigLiteral binding as literal
by Luca Molteni (Jira)
Luca Molteni created DROOLS-4175:
------------------------------------
Summary: Error in compiling BigLiteral binding as literal
Key: DROOLS-4175
URL: https://issues.jboss.org/browse/DROOLS-4175
Project: Drools
Issue Type: Bug
Reporter: Luca Molteni
Assignee: Luca Molteni
When beta joining two fields with a BigDecimal or BigInteger field, if a field is assigned as a binding the drools-model-compiler fails the compilation.
"import " + Result.class.getCanonicalName() + ";" +
"import " + Person.class.getCanonicalName() + ";" +
"rule R when\n" +
" $r : Result()\n" +
" $markV : Person(name == \"Mark\", $markMoney : money)\n" +
" $richerV : Person(name != \"Mark\", money > $markMoney)\n" +
"then\n" +
" $r.setValue($richerV.getName() + \" is richer than \" + $markV.getName());\n" +
"end";
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12188) What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
by Flavia Rainone (Jira)
[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ]
Flavia Rainone commented on WFLY-12188:
---------------------------------------
It appears that those variables are not being set at all, I'm investigating this to come to a full answer and a fix.
> What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12188
> URL: https://issues.jboss.org/browse/WFLY-12188
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 17.0.0.Final
> Reporter: Joerg Baesner
> Assignee: Flavia Rainone
> Priority: Major
>
> What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See:
> {code}
> <remote connector-ref="http-remoting-connector" thread-pool-name="default">
> <channel-creation-options>
> <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/>
> <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
> </channel-creation-options>
> </remote>
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <!-- server-side configuration -->
> <properties>
> <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/>
> <property name="KEEP_ALIVE" value="true"/>
> <property name="READ_TIMEOUT" value="10000"/>
> <property name="WRITE_TIMEOUT" value="10000"/>
> </properties>
> </http-connector>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12188) What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
by Joerg Baesner (Jira)
[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ]
Joerg Baesner updated WFLY-12188:
---------------------------------
Summary: What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem (was: What's the different of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem)
> What's the difference of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
> ----------------------------------------------------------------------------------
>
> Key: WFLY-12188
> URL: https://issues.jboss.org/browse/WFLY-12188
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 17.0.0.Final
> Reporter: Joerg Baesner
> Assignee: Flavia Rainone
> Priority: Major
>
> What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See:
> {code}
> <remote connector-ref="http-remoting-connector" thread-pool-name="default">
> <channel-creation-options>
> <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/>
> <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
> </channel-creation-options>
> </remote>
> {code}
> {code}
> <subsystem xmlns="urn:jboss:domain:remoting:4.0">
> <endpoint/>
> <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
> <!-- server-side configuration -->
> <properties>
> <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/>
> <property name="KEEP_ALIVE" value="true"/>
> <property name="READ_TIMEOUT" value="10000"/>
> <property name="WRITE_TIMEOUT" value="10000"/>
> </properties>
> </http-connector>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFLY-12188) What's the different of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
by Joerg Baesner (Jira)
Joerg Baesner created WFLY-12188:
------------------------------------
Summary: What's the different of the READ_TIMEOUT in ejb3 subsystem vs. remoting subsystem
Key: WFLY-12188
URL: https://issues.jboss.org/browse/WFLY-12188
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 17.0.0.Final
Reporter: Joerg Baesner
Assignee: Flavia Rainone
What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See:
{code}
<remote connector-ref="http-remoting-connector" thread-pool-name="default">
<channel-creation-options>
<option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/>
<option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/>
</channel-creation-options>
</remote>
{code}
{code}
<subsystem xmlns="urn:jboss:domain:remoting:4.0">
<endpoint/>
<http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm">
<!-- server-side configuration -->
<properties>
<property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/>
<property name="KEEP_ALIVE" value="true"/>
<property name="READ_TIMEOUT" value="10000"/>
<property name="WRITE_TIMEOUT" value="10000"/>
</properties>
</http-connector>
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4174) Test Scenario: Add support to recursive types in DMN
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-4174?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-4174:
---------------------------------------
+1, or maybe if generated, generate only the first level.
> Test Scenario: Add support to recursive types in DMN
> ----------------------------------------------------
>
> Key: DROOLS-4174
> URL: https://issues.jboss.org/browse/DROOLS-4174
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
>
> Review DMN data type extraction (DMNTypeService) and DMN test scenario template creation (DMNSimulationCreationStrategy) to be sure it works with recursive types.
> Please consider that template creation should not expand recursive types at all
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (DROOLS-4174) Test Scenario: Add support to recursive types in DMN
by Daniele Zonca (Jira)
[ https://issues.jboss.org/browse/DROOLS-4174?page=com.atlassian.jira.plugi... ]
Daniele Zonca commented on DROOLS-4174:
---------------------------------------
[~tirelli]
I think field with a recursive type should not be generated during template creation so user will need to manually add them. Wdyt?
[~tari_manga]
Can you please attach to the ticket a dmn model with recursive type?
> Test Scenario: Add support to recursive types in DMN
> ----------------------------------------------------
>
> Key: DROOLS-4174
> URL: https://issues.jboss.org/browse/DROOLS-4174
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Daniele Zonca
> Priority: Major
> Labels: ScenarioSimulation
>
> Review DMN data type extraction (DMNTypeService) and DMN test scenario template creation (DMNSimulationCreationStrategy) to be sure it works with recursive types.
> Please consider that template creation should not expand recursive types at all
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month
[JBoss JIRA] (WFCORE-4525) Fix failing tests on IBM JDK
by Richard Opalka (Jira)
[ https://issues.jboss.org/browse/WFCORE-4525?page=com.atlassian.jira.plugi... ]
Richard Opalka edited comment on WFCORE-4525 at 6/13/19 8:47 AM:
-----------------------------------------------------------------
I was able to fix some tests applying the following patch on maven surefire upstream:
{code}
blackhole][/home/opalka/git/apache/maven-surefire]>git diff
diff --git a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
index ebc1b276..5ec0e4ea 100644
--- a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
+++ b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
@@ -83,9 +83,9 @@ private void setupBooter( String tmpDir, String dumpFileName, String surefirePro
{
BooterDeserializer booterDeserializer =
new BooterDeserializer( createSurefirePropertiesIfFileExists( tmpDir, surefirePropsFileName ) );
+ setSystemProperties( new File( tmpDir, effectiveSystemPropertiesFileName ) );
// todo: print PID in debug console logger in version 2.21.2
pingScheduler = isDebugging() ? null : listenToShutdownCommands( booterDeserializer.getPluginPid() );
- setSystemProperties( new File( tmpDir, effectiveSystemPropertiesFileName ) );
providerConfiguration = booterDeserializer.deserialize();
DumpErrorSingleton.getSingleton()
{code}
was (Author: ropalka):
I was able to fix some tests applying the following patch on maven surefire upstream:
{quote}
blackhole][/home/opalka/git/apache/maven-surefire]>git diff
diff --git a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
index ebc1b276..5ec0e4ea 100644
--- a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
+++ b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java
@@ -83,9 +83,9 @@ private void setupBooter( String tmpDir, String dumpFileName, String surefirePro
{
BooterDeserializer booterDeserializer =
new BooterDeserializer( createSurefirePropertiesIfFileExists( tmpDir, surefirePropsFileName ) );
+ setSystemProperties( new File( tmpDir, effectiveSystemPropertiesFileName ) );
// todo: print PID in debug console logger in version 2.21.2
pingScheduler = isDebugging() ? null : listenToShutdownCommands( booterDeserializer.getPluginPid() );
- setSystemProperties( new File( tmpDir, effectiveSystemPropertiesFileName ) );
providerConfiguration = booterDeserializer.deserialize();
DumpErrorSingleton.getSingleton()
{quote}
> Fix failing tests on IBM JDK
> ----------------------------
>
> Key: WFCORE-4525
> URL: https://issues.jboss.org/browse/WFCORE-4525
> Project: WildFly Core
> Issue Type: Bug
> Components: Logging
> Reporter: Richard Opalka
> Assignee: James Perkins
> Priority: Major
> Fix For: 9.0.2.Final
>
> Attachments: forked-booter.png, ibm-jdk8.png, oracle-jdk.png
>
>
> The following tests are failing on latest IBM JDK 8:
> ---
> # testsuite/standalone
> SilentModeTestCase
> # testsuite/manualmode
> CLIEmbedHostControllerTestCase
> CLIEmbedServerTestCase
> ---
> Tested on:
> ---
> java version "1.8.0_211"
> Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36))
> IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled)
> OpenJ9 - 46e57f9
> OMR - 06a046a
> IBM - 0b909bf)
> JCL - 20190409_01 based on Oracle jdk8u211-b25
> ---
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 1 month