[Red Hat JIRA] (DROOLS-5947) Support multiple indexable constrains in Alpha Network Compiler
by Luca Molteni (Jira)
Luca Molteni created DROOLS-5947:
------------------------------------
Summary: Support multiple indexable constrains in Alpha Network Compiler
Key: DROOLS-5947
URL: https://issues.redhat.com/browse/DROOLS-5947
Project: Drools
Issue Type: Bug
Components: core engine
Reporter: Luca Molteni
Assignee: Luca Molteni
See org.drools.ancompiler.MultipleIndexableConstraintsTest
Currently when facing multiple indexable constraints we disable the switch generation and the inlining.
It could be possible to have multiple extractors and have multiple nested switch for better performances of ANC
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (WFCORE-5243) NullPointerException when invalid <permission> classes specified
by Ricardo Martin Camarero (Jira)
Ricardo Martin Camarero created WFCORE-5243:
-----------------------------------------------
Summary: NullPointerException when invalid <permission> classes specified
Key: WFCORE-5243
URL: https://issues.redhat.com/browse/WFCORE-5243
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 14.0.0.Final
Reporter: Ricardo Martin Camarero
Assignee: Ricardo Martin Camarero
If the security manager contains an invalid class or other data in the minimum-set it throws a NullPointerException instead of a useful error message.
{noformat}
ERROR [management-operation] WFLYCTL0013 : Operation ("add") failed - address ([("subsystem" => "security-manager")]): java.lang.NullPointerException
at java.security.Permissions.getPermissionCollection(Permissions.java:240)
at java.security.Permissions.implies(Permissions.java:179) at org.jboss.modules.security.FactoryPermissionCollection.implies(FactoryPermissionCollection.java:75) at org.wildfly.extension.security.manager.SecurityManagerSubsystemAdd.performBoottime(SecurityManagerSubsystemAdd.java:101)
...{noformat}
The same thing happens with other missing data.
* Works:
{noformat}
<permission class="java.io.FilePermission" name="/foo" actions="read"/>{noformat}
* Fail with NullPointerException:
{noformat}
<permission class="invalid.class.name" name="/foo" actions="read"/>{noformat}
{noformat}
<permission class="java.io.FilePermission" name="/foo"/>{noformat}
{noformat}
<permission class="java.io.FilePermission" actions="read"/>{noformat}
The NullPointerException does not occur if maximum-set is absent, or contains *java.security.AllPermission*
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (DROOLS-5946) Binding a list written in MVEL expression causes a build error in executable model.
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5946?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi moved RHDM-1570 to DROOLS-5946:
-------------------------------------------------
Component/s: executable model
(was: BRE)
Docs QE Status: NEW
Key: DROOLS-5946 (was: RHDM-1570)
QE Status: NEW
Affects Version/s: 7.48.0.Final
(was: 7.1.0.GA)
(was: 7.9.0.GA)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Environment: (was: This issue is reproducible on all releases from RHDM 7.1.0 to 7.9.0.)
Project: Drools (was: Red Hat Decision Manager)
> Binding a list written in MVEL expression causes a build error in executable model.
> -----------------------------------------------------------------------------------
>
> Key: DROOLS-5946
> URL: https://issues.redhat.com/browse/DROOLS-5946
> Project: Drools
> Issue Type: Bug
> Components: executable model
> Affects Versions: 7.48.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
> Labels: support
> Attachments: reproducer_model_compiler_12a.zip
>
>
> Binding a list written in MVEL expression like (\*1-1) causes a build error like (\*2) in executable model.
> This issue does not occur in build with executable model disabled.
> (\*1)
> {noformat}
> package com.example.reproducer
> import com.example.reproducer.Car
> dialect "mvel"
> rule "rule12a"
> when
> $car : Car( $group : ["compact", "medium", "luxury"] ) // ..... (*1-1)
> then
> System.out.println("***** Which group " + $group + " is " + $car + " categorized into?");
> end
> {noformat}
> (\*2)
> {noformat}
> [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel (default-generateModel) on project reproducer_model_compiler_12a: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel failed: Encountered unexpected token: "[" "["
> [ERROR] at line 1, column 10.
> [ERROR]
> [ERROR] Was expecting one of:
> [ERROR]
> [ERROR] "+"
> [ERROR] "++"
> [ERROR] "-"
> [ERROR] "--"
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (DROOLS-5924) String vs Number Coercion behavior difference between standard-drl and exec-model
by Toshiya Kobayashi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5924?page=com.atlassian.jira.plug... ]
Toshiya Kobayashi updated DROOLS-5924:
--------------------------------------
Story Points: 4 (was: 3)
> String vs Number Coercion behavior difference between standard-drl and exec-model
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-5924
> URL: https://issues.redhat.com/browse/DROOLS-5924
> Project: Drools
> Issue Type: Bug
> Components: core engine, executable model
> Affects Versions: 7.47.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Toshiya Kobayashi
> Priority: Major
>
> If there is a constraint to compare String with Number, standard-drl (MvelConstraint) coerces String to Number so the evaluation will be Number comparison (e.g. 10 > 5). But exec-model coerces Number to String so the evaluation will be String comparison (e.g. "10" < "5").
> Note that we need to use Object or Map to test this because simple comparison String vs Number causes a compilation error.
> for example)
> {noformat}
> ObjectHolder($o : value)
> StringHolder( value > $o )
> {noformat}
> or
> {noformat}
> $map : Map()
> StringHolder( value > $map.get("key") )
> {noformat}
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (WFLY-14292) Install Wildfly on IBM Cloud
by Muhammad Arif (Jira)
[ https://issues.redhat.com/browse/WFLY-14292?page=com.atlassian.jira.plugi... ]
Muhammad Arif commented on WFLY-14292:
--------------------------------------
you are welcome, this is tested tutorial and working fine.
> Install Wildfly on IBM Cloud
> ----------------------------
>
> Key: WFLY-14292
> URL: https://issues.redhat.com/browse/WFLY-14292
> Project: WildFly
> Issue Type: Component Upgrade
> Reporter: Muhammad Arif
> Assignee: Brian Stansberry
> Priority: Trivial
> Attachments: Kubernetes1.png, Kubernetes2.png, Kubernetes3.png, Kubernetes4.png, Kubernetes5.png, Kubernetes6.png, Kubernetes7.png, Storage1.png, Storage2.png, Wildfly1.png, Wildfly2.png, WildflyVerify1.png, WildflyVerify2.png, WildflyVerify3.png, WildflyVerify4.png, WildflyVerify5.png, WildflyVerify6.png
>
>
> *Installing Wildfly on IBM Cloud*
>
> This document will describe how to install Wildfly on IBM Cloud using Kubernetes Service.
>
> *+Contents+*
> # Introduction
> # Provision Kubernetes Cluster
> # Deploy IBM Cloud Block-Storage Plugin
> # Deploy Wildfly
> # Verifying the Wildfly Installation
> *Introduction*
> To complete this tutorial, you should have an IBM Cloud account, if you do not have one, please [register/signup|https://cloud.ibm.com/registration] here.
> For installing Wildfly, we have used the Kubernetes cluster, and used the IBM Cloud Block-Storage plugin for our persistent volume. Upon the completion of this tutorial, you would have the Wildfly up and running on the Kubernetes cluster.
> # Provision the Kubernetes cluster, if you have already setup one, skip to step 2.
> # Deploy the IBM Cloud Block-Storage Plugin to the created cluster, if you have already done this, skip to step 3.
> # Deploy the Wildfly.
> *Provision Kubernetes Cluster*
> * Click on the *Catalog* button on top center. Open [Catalog|https://cloud.ibm.com/catalog]. !Kubernetes1.png!
> * In search catalog box, search for *Kubernetes Service* and click on it. !Kubernetes2.png!
> * You are now at Create Kubernetes Cluster page, there you have the two plans to create the Kubernetes cluster, either using free plan or standard plan.
>
> *Option1- Using Free Plan:*
> * Select Pricing Plan as “*Free*”.
> * Click on *Create*. !Kubernetes3.png!
> * Wait a few minutes, and then your Cloud would be ready.
>
> *_Note_*_: Please be careful when choosing free cluster, as your pods could be stuck at pending state due to insufficient compute and memory resources, if you face such kind of issue please increase your resource by creating them choosing the standard plan._
>
> *Option2- Using Standard Plan:*
> * Select Pricing Plan as “*Standard*”
> * Select your Kubernetes Version as latest available or desired one by application. In our example we have set it to be ‘*1.18.14*’.
> * !Kubernetes4.png!
> * Select Infrastructure as “*Classic*”
> * Leave Resource Group to “*Default*”
> * Select Geography as “*Asia*” or your desired one.
> * Select Availability as “*Single Zone*”.
> _This option allows you to create the resources in either single or multi availability zones. Multi availability zone provides you the option to create the resources in more than one availability zones so in case of catastrophe it could sustain the disaster and continues to work._
> * Select Worker Zone as *Chennai 01. !Kubernetes5.png!*
> * In Worker Pool, input your desired number of nodes as “*2*”
> * Leave the Encrypt Local Disk option to “*On*”
> * Select Master Service Endpoint to “*Both private and public endpoints*” !Kubernetes6.png!
> * Give your cluster-name as “*Wildfly-Cluster*”
> * Provide *tags* to your cluster and click on *Create*.
> * Wait a few minutes, and then your Cloud would be ready. !Kubernetes7.png!
> *Deploy IBM Cloud Block-Storage Plugin*
> * Click on the *Catalog* button on top center.
> * In search catalog box, search for *IBM Cloud Block Storage Plug-in* and click on it !Storage1.png!
> * Select your cluster as "*Wildfly-Cluster*"
> * Provide *Target Namespace* as “*wildfly-storage*”, leave *name* and *resource group* to *default*
> * Click on *Install !Storage2.png!*
>
> *Deploy Wildfly*
> * Again go to the *Catalog* and search for Wildfly. !Wildfly1.png!
> * Provide the details as below. !Wildfly2.png!
> * Target: *IBM Kubernetes Service*
> * Method: *Helm chart*
> * Kubernetes cluster: *Wildfly-Cluster*(jp-tok)
> * Target namespace: *wildfly*
> * Workspace: *wildfly-01-13-2021*
> * Resource group: *Default*
> * Click on *Parameters with Default Values*, you can set the deployment values or use the default ones, we have used the default ones in this example.
> * Click on *Install*.
> *Verifying the Wildfly Installation*
> * Go to the *Resources List* in the Left Navigation Menu and click on ** *Kubernetes* and then *Clusters. !WildflyVerify1.png!*
> * Click on your created *Wildfly-Cluster.*
> * A screen would come up for your created cluster, click on *Actions,* and then *Web Terminal !WildflyVerify2.png!*
> * A warning will appear asking you to install the Web Terminal, click on *Install*
> * When the terminal is installed, click on the action button again and click on web terminal and type the following command in below command window. It will show you the workspaces of your cluster, you can see *Wildfly* active.
> {code:java}
> $ kubectl get ns{code}
> !WildflyVerify3.png!
> {code:java}
> $ kubectl get pod –n Namespace –o wide {code}
> !WildflyVerify4.png!
> {code:java}
> $ kubectl get service –n Namespace {code}
> !WildflyVerify5.png!
> Note the IP address and put it into your browser and you would see the Wildfly console would open.
> !WildflyVerify6.png!
>
> The installation is done. Enjoy!
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (WFLY-14293) Regression failures when deploy JMS webservice endpoint and session endpoint
by Jim Ma (Jira)
Jim Ma created WFLY-14293:
-----------------------------
Summary: Regression failures when deploy JMS webservice endpoint and session endpoint
Key: WFLY-14293
URL: https://issues.redhat.com/browse/WFLY-14293
Project: WildFly
Issue Type: Bug
Components: Web Services
Affects Versions: 22.0.0.Final
Reporter: Jim Ma
Assignee: Jim Ma
Fix For: 23.0.0.Beta1, 22.0.1.Final
When run jbossws-cxf testsuite against WFLY 22.0.0.Final release and get these regression test failures :
{code:java}
[ERROR] SessionEndpointTestCase.testSession:77->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<Number is [1]0> but was:<Number is [2]0>
[ERROR] Errors:
[ERROR] JMSEndpointAPITestCase.org.jboss.test.ws.jaxws.cxf.jms.JMSEndpointAPITestCase » Deployment
[ERROR] JMSEndpointOnlyDeploymentTestCase.org.jboss.test.ws.jaxws.cxf.jms.JMSEndpointOnlyDeploymentTestCase » Deployment
[ERROR] JMSHTTPEndpointDeploymentTestCase.org.jboss.test.ws.jaxws.cxf.jms_http.JMSHTTPEndpointDeploymentTestCase » Deployment{code}
The jms deployment failure error statck trace is :
{code:java}
2021-01-13 18:22:29,119 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jaxws-cxf-jms-http-deployment.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-cxf-jms-http-deployment.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-cxf-jms-http-deployment.war"2021-01-13 18:22:29,119 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."jaxws-cxf-jms-http-deployment.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-cxf-jms-http-deployment.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-cxf-jms-http-deployment.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1363) at java.lang.Thread.run(Thread.java:748)Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.ws.endpoint.context=jaxws-cxf-jms-http-deployment."org.jboss.test.ws.jaxws.cxf.jms_http.HelloWorldImpl" is already registered at org.jboss.msc.service.ServiceRegistrationImpl.set(ServiceRegistrationImpl.java:135) at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:243) at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:747) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:260) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2065) at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:260) at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2065) at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:192) at org.jboss.as.webservices.service.EndpointService.install(EndpointService.java:280) at org.jboss.as.webservices.deployers.EndpointServiceDeploymentAspect.start(EndpointServiceDeploymentAspect.java:50) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182) ... 8 more
{code}
It looks these regression failures are caused by https://issues.redhat.com/browse/WFLY-11999
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (WFLY-14292) Install Wildfly on IBM Cloud
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-14292?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-14292:
-----------------------------------------
Thanks, [~arifnafees]!
> Install Wildfly on IBM Cloud
> ----------------------------
>
> Key: WFLY-14292
> URL: https://issues.redhat.com/browse/WFLY-14292
> Project: WildFly
> Issue Type: Component Upgrade
> Reporter: Muhammad Arif
> Assignee: Brian Stansberry
> Priority: Trivial
> Attachments: Kubernetes1.png, Kubernetes2.png, Kubernetes3.png, Kubernetes4.png, Kubernetes5.png, Kubernetes6.png, Kubernetes7.png, Storage1.png, Storage2.png, Wildfly1.png, Wildfly2.png, WildflyVerify1.png, WildflyVerify2.png, WildflyVerify3.png, WildflyVerify4.png, WildflyVerify5.png, WildflyVerify6.png
>
>
> *Installing Wildfly on IBM Cloud*
>
> This document will describe how to install Wildfly on IBM Cloud using Kubernetes Service.
>
> *+Contents+*
> # Introduction
> # Provision Kubernetes Cluster
> # Deploy IBM Cloud Block-Storage Plugin
> # Deploy Wildfly
> # Verifying the Wildfly Installation
> *Introduction*
> To complete this tutorial, you should have an IBM Cloud account, if you do not have one, please [register/signup|https://cloud.ibm.com/registration] here.
> For installing Wildfly, we have used the Kubernetes cluster, and used the IBM Cloud Block-Storage plugin for our persistent volume. Upon the completion of this tutorial, you would have the Wildfly up and running on the Kubernetes cluster.
> # Provision the Kubernetes cluster, if you have already setup one, skip to step 2.
> # Deploy the IBM Cloud Block-Storage Plugin to the created cluster, if you have already done this, skip to step 3.
> # Deploy the Wildfly.
> *Provision Kubernetes Cluster*
> * Click on the *Catalog* button on top center. Open [Catalog|https://cloud.ibm.com/catalog]. !Kubernetes1.png!
> * In search catalog box, search for *Kubernetes Service* and click on it. !Kubernetes2.png!
> * You are now at Create Kubernetes Cluster page, there you have the two plans to create the Kubernetes cluster, either using free plan or standard plan.
>
> *Option1- Using Free Plan:*
> * Select Pricing Plan as “*Free*”.
> * Click on *Create*. !Kubernetes3.png!
> * Wait a few minutes, and then your Cloud would be ready.
>
> *_Note_*_: Please be careful when choosing free cluster, as your pods could be stuck at pending state due to insufficient compute and memory resources, if you face such kind of issue please increase your resource by creating them choosing the standard plan._
>
> *Option2- Using Standard Plan:*
> * Select Pricing Plan as “*Standard*”
> * Select your Kubernetes Version as latest available or desired one by application. In our example we have set it to be ‘*1.18.14*’.
> * !Kubernetes4.png!
> * Select Infrastructure as “*Classic*”
> * Leave Resource Group to “*Default*”
> * Select Geography as “*Asia*” or your desired one.
> * Select Availability as “*Single Zone*”.
> _This option allows you to create the resources in either single or multi availability zones. Multi availability zone provides you the option to create the resources in more than one availability zones so in case of catastrophe it could sustain the disaster and continues to work._
> * Select Worker Zone as *Chennai 01. !Kubernetes5.png!*
> * In Worker Pool, input your desired number of nodes as “*2*”
> * Leave the Encrypt Local Disk option to “*On*”
> * Select Master Service Endpoint to “*Both private and public endpoints*” !Kubernetes6.png!
> * Give your cluster-name as “*Wildfly-Cluster*”
> * Provide *tags* to your cluster and click on *Create*.
> * Wait a few minutes, and then your Cloud would be ready. !Kubernetes7.png!
> *Deploy IBM Cloud Block-Storage Plugin*
> * Click on the *Catalog* button on top center.
> * In search catalog box, search for *IBM Cloud Block Storage Plug-in* and click on it !Storage1.png!
> * Select your cluster as "*Wildfly-Cluster*"
> * Provide *Target Namespace* as “*wildfly-storage*”, leave *name* and *resource group* to *default*
> * Click on *Install !Storage2.png!*
>
> *Deploy Wildfly*
> * Again go to the *Catalog* and search for Wildfly. !Wildfly1.png!
> * Provide the details as below. !Wildfly2.png!
> * Target: *IBM Kubernetes Service*
> * Method: *Helm chart*
> * Kubernetes cluster: *Wildfly-Cluster*(jp-tok)
> * Target namespace: *wildfly*
> * Workspace: *wildfly-01-13-2021*
> * Resource group: *Default*
> * Click on *Parameters with Default Values*, you can set the deployment values or use the default ones, we have used the default ones in this example.
> * Click on *Install*.
> *Verifying the Wildfly Installation*
> * Go to the *Resources List* in the Left Navigation Menu and click on ** *Kubernetes* and then *Clusters. !WildflyVerify1.png!*
> * Click on your created *Wildfly-Cluster.*
> * A screen would come up for your created cluster, click on *Actions,* and then *Web Terminal !WildflyVerify2.png!*
> * A warning will appear asking you to install the Web Terminal, click on *Install*
> * When the terminal is installed, click on the action button again and click on web terminal and type the following command in below command window. It will show you the workspaces of your cluster, you can see *Wildfly* active.
> {code:java}
> $ kubectl get ns{code}
> !WildflyVerify3.png!
> {code:java}
> $ kubectl get pod –n Namespace –o wide {code}
> !WildflyVerify4.png!
> {code:java}
> $ kubectl get service –n Namespace {code}
> !WildflyVerify5.png!
> Note the IP address and put it into your browser and you would see the Wildfly console would open.
> !WildflyVerify6.png!
>
> The installation is done. Enjoy!
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months