[JBoss JIRA] (DROOLS-2996) Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2996?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-2996:
--------------------------------
Sprint: 2018 Week 39-41
> Existing Rules are not working as expected after migrating the Drools version from 6.0.3 to 7.4.1.Final
> -------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2996
> URL: https://issues.jboss.org/browse/DROOLS-2996
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.4.1.Final
> Reporter: Prameela Pod
> Assignee: Mario Fusco
> Attachments: DroolsTestPortlet.zip, logs.txt
>
>
> After drools migration from 6.0.3 to 7.4.1.Final version , modify property in 1st rule not validating conditions in 2nd rule.
> Ex: modify($alarm){setEVENTO_EN_TAREA("YES")} - In 1st rule then condition
> $alarm: ALARMA_ERICSSON_2G("NO" == getEVENTO_EN_TAREA()) - When condition in 2nd rule.
> If getEVENTO_EN_TAREA() = "YES" then only it should go inside 2nd rule.But here in this case getEVENTO_EN_TAREA()="YES" or "NO" - For both cases 2nd rule when condition is matched and going inside then condition.Which is wrong
> Please find the attached sample test project with logs.
> Kindly let me know additional information is required.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4018) Remove alias and read-aliases in a batch causes blocking behavior
by Claudio Miranda (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4018?page=com.atlassian.jira.plugi... ]
Claudio Miranda commented on WFCORE-4018:
-----------------------------------------
[~michpetrov] I am ok with closing it as we have a workaround in HAL. Thanks for investigating the issue.
> Remove alias and read-aliases in a batch causes blocking behavior
> -----------------------------------------------------------------
>
> Key: WFCORE-4018
> URL: https://issues.jboss.org/browse/WFCORE-4018
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Claudio Miranda
> Assignee: Michal Petrov
>
> Calling :remove-alias and :read-aliases on key-store resource in a composite operation makes the resource blocked.
> Generate two self signed certificates on a key-store resource and store it.
> {code}
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar,distinguished-name="cn=claudio,c=BR")
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar2,distinguished-name="cn=claudio2,c=BR")
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:store()
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> {
> "outcome" => "success",
> "result" => [
> "foobar2",
> "foobar"
> ]
> }
> {code}
> {code}
> batch
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:remove-alias(alias=foobar)
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> run-batch
> {code}
> The above just blocks the prompt.
> Then the blocking operation is show as:
> {code}
> /host=master/core-service=management/service=management-operations:read-resource(include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => {"active-operation" => {
> "352328021" => {
> "access-mechanism" => "NATIVE",
> "address" => [
> ("host" => "master"),
> ("core-service" => "management"),
> ("service" => "management-operations")
> ],
> "caller-thread" => "management-handler-thread - 1",
> "cancelled" => false,
> "domain-rollout" => false,
> "domain-uuid" => undefined,
> "exclusive-running-time" => -1L,
> "execution-status" => "executing",
> "operation" => "read-resource",
> "running-time" => 10032404L
> },
> "-1467399640" => {
> "access-mechanism" => "NATIVE",
> "address" => [],
> "caller-thread" => "management-handler-thread - 2",
> "cancelled" => false,
> "domain-rollout" => false,
> "domain-uuid" => undefined,
> "exclusive-running-time" => -1L,
> "execution-status" => "executing",
> "operation" => "composite",
> "running-time" => 260150849919L
> }
> }}
> }
> {code}
> After timeout there is the following message on CLI prompt
> {code}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-2
> Operation: /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> Failure: WFLYCTL0409: Execution of operation 'read-aliases' on remote process at address '[
> ("host" => "master"),
> ("server" => "server-three")
> ]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation
> {code}
> To fix the problem in HAL I will run it as individual commands.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (DROOLS-2989) Avoid refire of rules with synthetic Fact Handles
by Luca Molteni (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2989?page=com.atlassian.jira.plugi... ]
Luca Molteni commented on DROOLS-2989:
--------------------------------------
Poker: 5
> Avoid refire of rules with synthetic Fact Handles
> -------------------------------------------------
>
> Key: DROOLS-2989
> URL: https://issues.jboss.org/browse/DROOLS-2989
> Project: Drools
> Issue Type: Enhancement
> Components: core engine
> Reporter: Luca Molteni
> Assignee: Luca Molteni
>
> Currently the FromNode and the AccumulateNode create "synthetic" fact handles, that means they're not serialized and they're recreated in memory each time we need the access.
> There's already a way to avoid the refiring of the rules but involves serializing and deserializing these synthetic Fact Handles without the objects.
> We now want a better way to do it by serializing the objects without their FactHandles and at the same time keep the same behaviour as before (same number of rules should fire)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFCORE-4018) Remove alias and read-aliases in a batch causes blocking behavior
by Michal Petrov (JIRA)
[ https://issues.jboss.org/browse/WFCORE-4018?page=com.atlassian.jira.plugi... ]
Michal Petrov commented on WFCORE-4018:
---------------------------------------
[~claudio4j], I'm guessing this can be closed unless you think this could be somehow improved in CLI.
> Remove alias and read-aliases in a batch causes blocking behavior
> -----------------------------------------------------------------
>
> Key: WFCORE-4018
> URL: https://issues.jboss.org/browse/WFCORE-4018
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Claudio Miranda
> Assignee: Michal Petrov
>
> Calling :remove-alias and :read-aliases on key-store resource in a composite operation makes the resource blocked.
> Generate two self signed certificates on a key-store resource and store it.
> {code}
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar,distinguished-name="cn=claudio,c=BR")
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:generate-key-pair(alias=foobar2,distinguished-name="cn=claudio2,c=BR")
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:store()
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> {
> "outcome" => "success",
> "result" => [
> "foobar2",
> "foobar"
> ]
> }
> {code}
> {code}
> batch
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:remove-alias(alias=foobar)
> /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> run-batch
> {code}
> The above just blocks the prompt.
> Then the blocking operation is show as:
> {code}
> /host=master/core-service=management/service=management-operations:read-resource(include-runtime,recursive)
> {
> "outcome" => "success",
> "result" => {"active-operation" => {
> "352328021" => {
> "access-mechanism" => "NATIVE",
> "address" => [
> ("host" => "master"),
> ("core-service" => "management"),
> ("service" => "management-operations")
> ],
> "caller-thread" => "management-handler-thread - 1",
> "cancelled" => false,
> "domain-rollout" => false,
> "domain-uuid" => undefined,
> "exclusive-running-time" => -1L,
> "execution-status" => "executing",
> "operation" => "read-resource",
> "running-time" => 10032404L
> },
> "-1467399640" => {
> "access-mechanism" => "NATIVE",
> "address" => [],
> "caller-thread" => "management-handler-thread - 2",
> "cancelled" => false,
> "domain-rollout" => false,
> "domain-uuid" => undefined,
> "exclusive-running-time" => -1L,
> "execution-status" => "executing",
> "operation" => "composite",
> "running-time" => 260150849919L
> }
> }}
> }
> {code}
> After timeout there is the following message on CLI prompt
> {code}
> The batch failed with the following error (you are remaining in the batch editing mode to have a chance to correct the error):
> WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:
> Step: step-2
> Operation: /host=master/server=server-three/subsystem=elytron/key-store=keysto1:read-aliases
> Failure: WFLYCTL0409: Execution of operation 'read-aliases' on remote process at address '[
> ("host" => "master"),
> ("server" => "server-three")
> ]' timed out after 305000 ms while awaiting initial response; remote process has been notified to terminate operation
> {code}
> To fix the problem in HAL I will run it as individual commands.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (WFLY-9735) Add systemd unit file to zip distribution
by Arnav Bhati (JIRA)
[ https://issues.jboss.org/browse/WFLY-9735?page=com.atlassian.jira.plugin.... ]
Arnav Bhati commented on WFLY-9735:
-----------------------------------
[~mkopecky] [~kabirkhan] [~jamezp] - Can anyone confirm on the status of this RFE ?
> Add systemd unit file to zip distribution
> -----------------------------------------
>
> Key: WFLY-9735
> URL: https://issues.jboss.org/browse/WFLY-9735
> Project: WildFly
> Issue Type: Feature Request
> Components: Scripts
> Reporter: Osamu Nagano
> Attachments: eap7-standalone.service, tomcat8.service
>
>
> Systemd can handle legacy init.d scripts, but many customers have asked for native integration to systemd. We may be able to provide the out-of-the-box unit file or a template of it with some documentation. It seems JWS is considering the same in JWS-811 so EAP may adopt the same way.
> One advantage of systemd is the ability to depends on socket unit file so that we may be able to omit jsvc to listen a privileged port.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1671) Unable to build javadoc on JDK 10
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1671?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1671:
----------------------------------
Priority: Blocker (was: Major)
> Unable to build javadoc on JDK 10
> ---------------------------------
>
> Key: ELY-1671
> URL: https://issues.jboss.org/browse/ELY-1671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Documentation
> Reporter: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.7.0.CR2
>
>
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.854 s
> [INFO] Finished at: 2018-09-19T13:50:48+01:00
> [INFO] Final Memory: 26M/108M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
> [ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
> [ERROR] are planned to be removed in a future JDK release. These
> [ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
> [ERROR] Users are strongly recommended to migrate to the new APIs.
> [ERROR] javadoc: error - invalid flag: -Xdoclint:none
> [ERROR]
> [ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (ELY-1671) Unable to build javadoc on JDK 10
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-1671?page=com.atlassian.jira.plugin.s... ]
Darran Lofthouse updated ELY-1671:
----------------------------------
Description:
{noformat}
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.854 s
[INFO] Finished at: 2018-09-19T13:50:48+01:00
[INFO] Final Memory: 26M/108M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
[ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
[ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
[ERROR] are planned to be removed in a future JDK release. These
[ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
[ERROR] Users are strongly recommended to migrate to the new APIs.
[ERROR] javadoc: error - invalid flag: -Xdoclint:none
[ERROR]
[ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
> Unable to build javadoc on JDK 10
> ---------------------------------
>
> Key: ELY-1671
> URL: https://issues.jboss.org/browse/ELY-1671
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Documentation
> Reporter: Darran Lofthouse
> Fix For: 1.7.0.CR2
>
>
> {noformat}
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1.854 s
> [INFO] Finished at: 2018-09-19T13:50:48+01:00
> [INFO] Final Memory: 26M/108M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0-M1:javadoc (default-cli) on project wildfly-elytron: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 1 - javadoc: warning - The old Doclet and Taglet APIs in the packages
> [ERROR] com.sun.javadoc, com.sun.tools.doclets and their implementations
> [ERROR] are planned to be removed in a future JDK release. These
> [ERROR] components have been superseded by the new APIs in jdk.javadoc.doclet.
> [ERROR] Users are strongly recommended to migrate to the new APIs.
> [ERROR] javadoc: error - invalid flag: -Xdoclint:none
> [ERROR]
> [ERROR] Command line was: /home/darranl/applications/java/jdk-10.0.2/bin/javadoc @options @argfile
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in '/home/darranl/src/community/wildfly-elytron/target/site/apidocs/api-javadoc' dir.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months