August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-338) Bootable JAR - Cloud - Enable json logging

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-338: ------------------------------------------ Summary: Bootable JAR - Cloud - Enable json logging Key: WFWIP-338 URL: https://issues.redhat.com/browse/WFWIP-338 Project: WildFly WIP Issue Type: Enhancement Reporter: Jean Francois Denise Assignee: Jean Francois Denise In an openshift context it would be interesting to enable json logging. For Bootable JAR we would evolve the <cloud> element with <enable-json-logging>true|false</enable-json-logging>. Logging subsystem and logging.properties would have to be updated during packaging. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5605) [DMN Designer] Enabled elements in Read Only Mode

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5605: ----------------------------------- Summary: [DMN Designer] Enabled elements in Read Only Mode Key: DROOLS-5605 URL: https://issues.redhat.com/browse/DROOLS-5605 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.43.0.Final Reporter: Jozef Marko Assignee: Guilherme Gomes Attachments: Screenshot from 2020-08-27 15-45-51.png, Screenshot from 2020-08-27 15-46-21.png This issue is related to KOGITO-543. There are still two places to disable for Read Only mode. h1. Navigate To Expression Editor Currently an exception is thrown if user tries to open an expression editor for DMN node in read only mode. !Screenshot from 2020-08-27 15-45-51.png|thumbnail! h1. Import Data Object There is button to generate DMN data type according to a java class. This button should be disabled in Read Only mode. !Screenshot from 2020-08-27 15-46-21.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13804) Upgrade smallrye-open-api to 2.0.8

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13804: ----------------------------------- Summary: Upgrade smallrye-open-api to 2.0.8 Key: WFLY-13804 URL: https://issues.redhat.com/browse/WFLY-13804 Project: WildFly Issue Type: Component Upgrade Components: MP OpenAPI Affects Versions: 20.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.7] https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.8 -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5604) Implement IsMissing, IsNotMissing inside KiePMMLSimplePredicate

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5604?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5604: ------------------------------------- Summary: Implement IsMissing, IsNotMissing inside KiePMMLSimplePredicate (was: Implement IsMissing, IsNotMissing inside KiePMMLSimplePRedicate) > Implement IsMissing, IsNotMissing inside KiePMMLSimplePredicate > --------------------------------------------------------------- > > Key: DROOLS-5604 > URL: https://issues.redhat.com/browse/DROOLS-5604 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Implement IsMissing/IsNotMissing management inside KiePMMLSimplePredicate -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-337) Bootable JAR - Cloud - Add bindall interface, http(s) bound to bindall itf.

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-337: ------------------------------------------ Summary: Bootable JAR - Cloud - Add bindall interface, http(s) bound to bindall itf. Key: WFWIP-337 URL: https://issues.redhat.com/browse/WFWIP-337 Project: WildFly WIP Issue Type: Bug Reporter: Jean Francois Denise Assignee: Jean Francois Denise In S2i, the http socket binding is bound to 0.0.0.0. Currently in Bootable JAR it is bound to HOSTENV (if defined) and fallback to 127.0.0.1. We should align to S2I builder image by introducing the bindall interface and have http and https to use it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5604) Implement IsMissing, IsNotMissing inside KiePMMLSimplePRedicate

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5604: ---------------------------------------- Summary: Implement IsMissing, IsNotMissing inside KiePMMLSimplePRedicate Key: DROOLS-5604 URL: https://issues.redhat.com/browse/DROOLS-5604 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Implement IsMissing/IsNotMissing management inside KiePMMLSimplePredicate -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-336) Bootable JAR - Cloud - Set proxy address forwarding

by Jean Francois Denise (Jira)

Jean Francois Denise created WFWIP-336: ------------------------------------------ Summary: Bootable JAR - Cloud - Set proxy address forwarding Key: WFWIP-336 URL: https://issues.redhat.com/browse/WFWIP-336 Project: WildFly WIP Issue Type: Bug Reporter: Jean Francois Denise Assignee: Jean Francois Denise That is required when running on Openshift, the details in this JIRA: [https://issues.redhat.com/browse/CLOUD-2055|https://www.google.com... -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Nicolas De Amicis (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Nicolas De Amicis edited comment on WFLY-13793 at 8/27/20 5:20 AM: ------------------------------------------------------------------- Thanks for the PR and the workaround. The workaround adds to the standalone-full.xml the expected attribute: {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/jms/artemisConnectionFactory" connectors="remote-artemis" enable-amq1-prefix="false"/>}} {quote} But wildfly is listen always on the wrong queue. In my case, I would like that use the queue named toPrinter, but wildfly is listen on the queue named jms.queue.toPrinter. It's seems that enable-amq1-prefix=false has no effect. The version of my remote ActiveMQ Artemis is 2.10.1 A snippet from my MDB: {quote}{{@MessageDriven(name = "PrinterMDB", activationConfig = {}} @ActivationConfigProperty(propertyName = "destinationLookup", propertyValue = "toPrinter"), @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge")}) {{@ResourceAdapter(value = "remote-artemis")}} {{public class PrinterMDB implements MessageListener}} {{...}} {quote} And the parameters from my standalone-full.xml about remote-artemis: {quote}{{<remote-connector name="remote-artemis" socket-binding="remote-artemis"/>}} {{<pooled-connection-factory name="remote-artemis" entries="java:/jms/artemisConnectionFactory" connectors="remote-artemis" enable-amq1-prefix="false"/>}} {{<outbound-socket-binding name="remote-artemis">}} {{ <remote-destination host="testserver" port="61616"/>}} {{</outbound-socket-binding>}} {quote} was (Author: deamn): Thanks for the PR and the workaround. The workaround adds to the standalone-full.xml the expected attribute: {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/jms/artemisConnectionFactory" connectors="remote-artemis" enable-amq1-prefix="false"/>}} {quote} But wildfly is listen always on the wrong queue. In my case, I would like that use the queue named toPrinter, but wildfly is listen on the queue named jms.queue.toPrinter. It's seems that enable-amq1-prefix=false has no effect. The version of my remote ActiveMQ Artemis is 2.10.1 A snippet from my MDB: {quote}{{@MessageDriven(name = "PrinterMDB", activationConfig = {}} {{ @ActivationConfigProperty(propertyName = "destinationLookup", propertyValue = "toPrinter"),}} {{ @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),}} {{ @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge")})}} {{@ResourceAdapter(value = "remote-artemis")}} {{public class PrinterMDB implements MessageListener}} {{...}} {quote} And the parameters from my standalone-full.xml about remote-artemis: {quote}{{<remote-connector name="remote-artemis" socket-binding="remote-artemis"/>}} {{<pooled-connection-factory name="remote-artemis" entries="java:/jms/artemisConnectionFactory" connectors="remote-artemis" enable-amq1-prefix="false"/>}} {{<outbound-socket-binding name="remote-artemis">}} {{ <remote-destination host="testserver" port="61616"/>}} {{</outbound-socket-binding>}} {quote} > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Brian Stansberry > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13793) Attribute enable-amq1-prefix doesn't work (remote artemis)

by Nicolas De Amicis (Jira)

[ https://issues.redhat.com/browse/WFLY-13793?page=com.atlassian.jira.plugi... ] Nicolas De Amicis commented on WFLY-13793: ------------------------------------------ Thanks for the PR and the workaround. The workaround adds to the standalone-full.xml the expected attribute: {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/jms/artemisConnectionFactory" connectors="remote-artemis" enable-amq1-prefix="false"/>}} {quote} But wildfly is listen always on the wrong queue. In my case, I would like that use the queue named toPrinter, but wildfly is listen on the queue named jms.queue.toPrinter. It's seems that enable-amq1-prefix=false has no effect. The version of my remote ActiveMQ Artemis is 2.10.1 A snippet from my MDB: {quote}{{@MessageDriven(name = "PrinterMDB", activationConfig = {}} {{ @ActivationConfigProperty(propertyName = "destinationLookup", propertyValue = "toPrinter"),}} {{ @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),}} {{ @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge")})}} {{@ResourceAdapter(value = "remote-artemis")}} {{public class PrinterMDB implements MessageListener}} {{...}} {quote} And the parameters from my standalone-full.xml about remote-artemis: {quote}{{<remote-connector name="remote-artemis" socket-binding="remote-artemis"/>}} {{<pooled-connection-factory name="remote-artemis" entries="java:/jms/artemisConnectionFactory" connectors="remote-artemis" enable-amq1-prefix="false"/>}} {{<outbound-socket-binding name="remote-artemis">}} {{ <remote-destination host="testserver" port="61616"/>}} {{</outbound-socket-binding>}} {quote} > Attribute enable-amq1-prefix doesn't work (remote artemis) > ---------------------------------------------------------- > > Key: WFLY-13793 > URL: https://issues.redhat.com/browse/WFLY-13793 > Project: WildFly > Issue Type: Bug > Affects Versions: 17.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Brian Stansberry > Priority: Major > > I need to connect Wildfly 17.0.1 to a remote Artemis server. I follow the doc here: [https://docs.wildfly.org/17/Admin_Guide.html#Messaging_Connect_a_pooled-c...] No problem for point 1 to 3. But when I follow the instruction for disabling the compatibility mode (enable-amq1-prefix) I have this error: > {quote}{{[standalone@localhost:9990 /] /subsystem=messaging-activemq/pooled-connection-factory=remote-artemis:write-attribute(name="enable-amq1-prefix", value="false")}} > \{{{}} > \{{ "outcome" => "failed",}} > \{{ "failure-description" => "WFLYCTL0248: Invalid value false for enable-amq1-prefix; legal values are [XA_GENERIC, GENERIC, XA_T}} > {{OPIC, TOPIC, QUEUE, XA_QUEUE]",}} > \{{ "rolled-back" => true}} > {{}}} > {quote} > If I deploy my MDB that connects to queue myqueue, I see in artemis console my MDB is connected to jms.queue.myqueue. > I also tried to add the attribute manually but it seems it doesn't work: > {quote}{{<pooled-connection-factory name="remote-artemis" entries="java:/}}{{jms/remoteCF}}{{" connectors="remote-artemis" enable-amq1-prefix="false"/>}} > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5603) Refactor super invocation setting

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-5603: ---------------------------------------- Summary: Refactor super invocation setting Key: DROOLS-5603 URL: https://issues.redhat.com/browse/DROOLS-5603 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Currently in sources generation the super invocation is managed by field index {code:java} // Some comments here ExplicitConstructorInvocationStmt superStatement = (ExplicitConstructorInvocationStmt) statement; NameExpr algorithmNameExpr = (NameExpr) superStatement.getArgument(2); algorithmNameExpr.setName(String.format("\"%s\"", treeModel.getAlgorithmName())); {code} This must be changed so that field to be set is looked for by name and - if not found, an exception must be thrown (as for the AssignExpr) -- This message was sent by Atlassian Jira (v7.13.8#713008)

3 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2020