February 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-13828) remote+tls is not supported by EJBClient and remote-outbound-connection

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13828?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-13828: -------------------------------------------- Hello [~mgrossmann] Sorry, I was busy with some other issues. Currently, I'm working on it. This is the first feature request of mine, there are many steps to follow before doing the coding part, will take some time. > remote+tls is not supported by EJBClient and remote-outbound-connection > ----------------------------------------------------------------------- > > Key: WFLY-13828 > URL: https://issues.redhat.com/browse/WFLY-13828 > Project: WildFly > Issue Type: Feature Request > Components: Remoting > Affects Versions: 20.0.1.Final > Reporter: Matthias Großmann > Assignee: Ranabir Chakraborty > Priority: Major > > Hi, > in our company we would like to use the newest Wildfly together with legacy servers like JBoss AS 7 over SSL. > This is possible with the Uri scheme "remote+tls" provided by jboss-remoting > https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav... > {code:java} > final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory(); > ... > endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE)); > {code} > But that uri scheme is not supported by the jboss-ejb-client in current version > https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org... > {code} > public boolean supportsProtocol(final String uriScheme) { > switch (uriScheme) { > case "remote": > case "remote+http": > case "remote+https": > // compatibility > case "remoting": > case "http-remoting": > case "https-remoting": { > return true; > } > default: { > return false; > } > } > } > {code} > and also the remote-outbound-connection does not allow that protocol: > https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr... > {code} > public enum Protocol { > REMOTE("remote"), > REMOTE_HTTP("remote+http"), > HTTP_REMOTING("http-remoting"), > HTTPS_REMOTING("https-remoting"), > REMOTE_HTTPS("remote+https"); > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-13828) remote+tls is not supported by EJBClient and remote-outbound-connection

by Matthias Großmann (Jira)

[ https://issues.redhat.com/browse/WFLY-13828?page=com.atlassian.jira.plugi... ] Matthias Großmann commented on WFLY-13828: ------------------------------------------ Hi [~rchakrab], ist there a chance that the issue can be integrated? Regards Matthias > remote+tls is not supported by EJBClient and remote-outbound-connection > ----------------------------------------------------------------------- > > Key: WFLY-13828 > URL: https://issues.redhat.com/browse/WFLY-13828 > Project: WildFly > Issue Type: Feature Request > Components: Remoting > Affects Versions: 20.0.1.Final > Reporter: Matthias Großmann > Assignee: Ranabir Chakraborty > Priority: Major > > Hi, > in our company we would like to use the newest Wildfly together with legacy servers like JBoss AS 7 over SSL. > This is possible with the Uri scheme "remote+tls" provided by jboss-remoting > https://github.com/jboss-remoting/jboss-remoting/blob/master/src/main/jav... > {code:java} > final RemoteConnectionProviderFactory remoteConnectionProviderFactory = new RemoteConnectionProviderFactory(); > ... > endpoint.addConnectionProvider("remote+tls", remoteConnectionProviderFactory, OptionMap.create(Options.SECURE, Boolean.TRUE)); > {code} > But that uri scheme is not supported by the jboss-ejb-client in current version > https://github.com/wildfly/jboss-ejb-client/blob/master/src/main/java/org... > {code} > public boolean supportsProtocol(final String uriScheme) { > switch (uriScheme) { > case "remote": > case "remote+http": > case "remote+https": > // compatibility > case "remoting": > case "http-remoting": > case "https-remoting": { > return true; > } > default: { > return false; > } > } > } > {code} > and also the remote-outbound-connection does not allow that protocol: > https://github.com/wildfly/wildfly-core/blob/master/remoting/subsystem/sr... > {code} > public enum Protocol { > REMOTE("remote"), > REMOTE_HTTP("remote+http"), > HTTP_REMOTING("http-remoting"), > HTTPS_REMOTING("https-remoting"), > REMOTE_HTTPS("remote+https"); > {code} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6034) Unable to build project inserting and updating a fact of same rule running with an executable model

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-6034?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-6034: --------------------------------- Sprint: 2021 Week 07-09 (from Feb 15) > Unable to build project inserting and updating a fact of same rule running with an executable model > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-6034 > URL: https://issues.redhat.com/browse/DROOLS-6034 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Attachments: RuleIssue_02864136.zip, pom.xml > > > Customer has rule which look like as: > > ~~~ > rule "Testrule" > dialect "mvel" > when > then > com.Employee e = new Employee(); > e.setId("1"); > insert( e ); > e.setName("abc"); > update( e ); > end > ~~~ > > If we try to build project it fails with below exception: > ~~~ > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel (default-generateModel) on project RuleIssue_02864136: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel failed.: RuntimeException -> [Help 1] > [ERROR] > ~~~ > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6029) Unable to build project inserting and updating a fact of same rule running with an executable model

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-6029?page=com.atlassian.jira.plug... ] Luca Molteni deleted DROOLS-6029: --------------------------------- > Unable to build project inserting and updating a fact of same rule running with an executable model > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-6029 > URL: https://issues.redhat.com/browse/DROOLS-6029 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.49.0.Final > Reporter: Abhijit Humbe > Assignee: Luca Molteni > Priority: Major > > Customer has rule which look like as: > > ~~~ > rule "Testrule" > dialect "mvel" > when > then > com.Employee e = new Employee(); > e.setId("1"); > insert( e ); > e.setName("abc"); > update( e ); > end > ~~~ > > If we try to build project it fails with below exception: > ~~~ > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel (default-generateModel) on project RuleIssue_02864136: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel failed.: RuntimeException -> [Help 1] > [ERROR] > ~~~ > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6021) Migrate standalone Business Central from Thorntail to EAP Bootable Jar

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-6021?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-6021: --------------------------------- Story Points: 5 (was: 3) > Migrate standalone Business Central from Thorntail to EAP Bootable Jar > ---------------------------------------------------------------------- > > Key: DROOLS-6021 > URL: https://issues.redhat.com/browse/DROOLS-6021 > Project: Drools > Issue Type: Task > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6021) Migrate standalone Business Central from Thorntail to EAP Bootable Jar

by Marek Novotny (Jira)

[ https://issues.redhat.com/browse/DROOLS-6021?page=com.atlassian.jira.plug... ] Marek Novotny commented on DROOLS-6021: --------------------------------------- inserting for correct relation link > Migrate standalone Business Central from Thorntail to EAP Bootable Jar > ---------------------------------------------------------------------- > > Key: DROOLS-6021 > URL: https://issues.redhat.com/browse/DROOLS-6021 > Project: Drools > Issue Type: Task > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6010) Not able to use a space within quotes in guided DecisionTable.

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-6010?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-6010: --------------------------------- Story Points: 1 > Not able to use a space within quotes in guided DecisionTable. > -------------------------------------------------------------- > > Key: DROOLS-6010 > URL: https://issues.redhat.com/browse/DROOLS-6010 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor, Guided Rule Editor, Guided Template Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFLY-13548) Implementation of XAResourceWrapper to allow Narayana resolve in-doubt transaction assume complete situation

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13548?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet reassigned WFLY-13548: ---------------------------------------- Assignee: Emmanuel Hugonnet (was: Jeff Mesnil) > Implementation of XAResourceWrapper to allow Narayana resolve in-doubt transaction assume complete situation > ------------------------------------------------------------------------------------------------------------ > > Key: WFLY-13548 > URL: https://issues.redhat.com/browse/WFLY-13548 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 13.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Emmanuel Hugonnet > Priority: Major > > With fix of the https://issues.jboss.org/browse/JBTM-860 there was added method {{getJndiName}} for {{XAResourceWrapper}}: https://github.com/jbosstm/jboss-transaction-spi/blob/master/src/main/jav... > which Narayana uses to resolve situation when there is in-doubt record at the side of resource manager (message broker) but Narayana does not have corresponding record in its log store. This could mean the transaction was already committed. But Narayana needs to pair the in-doubt transaction with existing RM to assume so. > This capability would be fine to be provided by generic jms ra too. -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (DROOLS-6029) Unable to build project inserting and updating a fact of same rule running with an executable model

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-6029?page=com.atlassian.jira.plug... ] Toni Rikkola reassigned DROOLS-6029: ------------------------------------ Assignee: Luca Molteni (was: Toni Rikkola) > Unable to build project inserting and updating a fact of same rule running with an executable model > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-6029 > URL: https://issues.redhat.com/browse/DROOLS-6029 > Project: Drools > Issue Type: Bug > Components: core engine, executable model > Affects Versions: 7.49.0.Final > Reporter: Abhijit Humbe > Assignee: Luca Molteni > Priority: Major > > Customer has rule which look like as: > > ~~~ > rule "Testrule" > dialect "mvel" > when > then > com.Employee e = new Employee(); > e.setId("1"); > insert( e ); > e.setName("abc"); > update( e ); > end > ~~~ > > If we try to build project it fails with below exception: > ~~~ > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel (default-generateModel) on project RuleIssue_02864136: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.44.0.Final-redhat-00003:generateModel failed.: RuntimeException -> [Help 1] > [ERROR] > ~~~ > -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

[Red Hat JIRA] (WFCORE-4970) Changing the JVM settings at host level does not put the servers in restart-required

by Parul Sharma (Jira)

[ https://issues.redhat.com/browse/WFCORE-4970?page=com.atlassian.jira.plug... ] Parul Sharma commented on WFCORE-4970: -------------------------------------- [~yersan] [~brian.stansberry] Can you please elaborate on how I can do further analysis? As per Brian's comment what I understood is AbstractAttributeDefinitionBuilder.addArbitraryDescriptor operation is using jvmAttributes, is this mean we have to run something on CLI to see which resources are able to use those attributes, and then we need to analyze if Restart_JVM actually required or not. Please correct me if my understanding is wrong. > Changing the JVM settings at host level does not put the servers in restart-required > ------------------------------------------------------------------------------------ > > Key: WFCORE-4970 > URL: https://issues.redhat.com/browse/WFCORE-4970 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 12.0.0.Beta2 > Reporter: Yeray Borges Santana > Assignee: Parul Sharma > Priority: Major > > Operations like the following one should put the servers in restart required to indicate the user changes will be applied after restarting the servers: > {noformat} > [domain@localhost:9990 /] /host=master/jvm=default:write-attribute(name=heap-size, value=256m) > { > "outcome" => "success", > "result" => undefined, > "server-groups" => undefined > } > {noformat} -- This message was sent by Atlassian Jira (v8.13.1#813001)

5 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2021