September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5621) KieComponentFactory should not declare non static logger field

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5621?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5621: -------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > KieComponentFactory should not declare non static logger field > -------------------------------------------------------------- > > Key: DROOLS-5621 > URL: https://issues.redhat.com/browse/DROOLS-5621 > Project: Drools > Issue Type: Bug > Affects Versions: 7.42.0.Final > Reporter: Christian Martensen > Assignee: Mario Fusco > Priority: Major > > h3. Description > The serializable class org.drools.core.reteoo.KieComponentFactory declares a non static logger field (currently unused). > {code:java} > Logger logger = LoggerFactory.getLogger(KieComponentFactory.class); > {code} > When serializing the object this causes problems if the used slf4j logger is not serializable. This will also cause problems if the used logger is not available during deserialization. > h3. Desired solution > Either declare the logger field as static or remove it since it is unused. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 updated WFLY-13793: ------------------------------------- Affects Version/s: 20.0.1.Final (was: 17.0.1.Final) > 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 > Components: JMS, Management > Affects Versions: 20.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Beta1 > > > 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13825) The 'microprofile.surefire' execution doesn't run microprofile tests at all due to wrong package name include

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13825: ------------------------------------- Summary: The 'microprofile.surefire' execution doesn't run microprofile tests at all due to wrong package name include Key: WFLY-13825 URL: https://issues.redhat.com/browse/WFLY-13825 Project: WildFly Issue Type: Bug Affects Versions: 20.0.0.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Fix For: 21.0.0.Beta1 This is because the package name is actually "org/wildfly/test/integration/microprofile/**/*TestCase.java" and not "org/jboss/as/test/integration/microprofile/**/*TestCase.java". Issue introduced in https://github.com/wildfly/wildfly/commit/1226bd825d0271fa72e7280257c85dc... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 reopened WFLY-13793: -------------------------------------- With Wildfly 20, the attribute enable-amq1-prefix=false is functional with the MDB (to receive a message). Now I'm trying to publish a message, but the prefix jms.queue is added to my queue name. I define a queue named TEST with jndi name queue/test: {quote}{{<external-jms-queue name="TEST" entries="queue/test"/>}}{quote} Here a snippet from my publisher (an ejb): {quote}{{@Resource(lookup = "java:/queue/test")}} {{ private Queue testQueue;}}{{...}}{quote} The message is published on the queue jms.queue.TEST on the remote artemis server. I will provide a testcase > 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 > Components: JMS, Management > Affects Versions: 17.0.1.Final > Reporter: Nicolas De Amicis > Assignee: Chao Wang > Priority: Major > Fix For: 21.0.0.Beta1 > > > 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)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1215) Update upstream-pipeline

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1215: ------------------------------------ Summary: Update upstream-pipeline Key: SWSQE-1215 URL: https://issues.redhat.com/browse/SWSQE-1215 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta We need to make [https://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8443/view/main-pipelines...] work with SM 2.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1214) Update pipelines for SM 2.0

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1214: ------------------------------------ Summary: Update pipelines for SM 2.0 Key: SWSQE-1214 URL: https://issues.redhat.com/browse/SWSQE-1214 Project: Kiali QE Issue Type: Story Reporter: Filip Brychta Assignee: Filip Brychta -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5621) KieComponentFactory should not declare non static logger field

by Christian Martensen (Jira)

Christian Martensen created DROOLS-5621: ------------------------------------------- Summary: KieComponentFactory should not declare non static logger field Key: DROOLS-5621 URL: https://issues.redhat.com/browse/DROOLS-5621 Project: Drools Issue Type: Bug Affects Versions: 7.42.0.Final Reporter: Christian Martensen Assignee: Mario Fusco h3. Description The serializable class org.drools.core.reteoo.KieComponentFactory declares a non static logger field (currently unused). {code:java} Logger logger = LoggerFactory.getLogger(KieComponentFactory.class); {code} When serializing the object this causes problems if the used slf4j logger is not serializable. This will also cause problems if the used logger is not available during deserialization. h3. Desired solution Either declare the logger field as static or remove it since it is unused. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-339) OpenSSL security provider seems to be used when not defined with JDK8 now

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/WFWIP-339?page=com.atlassian.jira.plugin... ] Jan Stourac commented on WFWIP-339: ----------------------------------- [~fjuma], thank you for the explanation and for the fix! I understand now. I've also tested your changes and re-run our pipeline and all looks okay now! I'm gonna resolve this one. Thank you again! > OpenSSL security provider seems to be used when not defined with JDK8 now > ------------------------------------------------------------------------- > > Key: WFWIP-339 > URL: https://issues.redhat.com/browse/WFWIP-339 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Jan Stourac > Assignee: Farah Juma > Priority: Major > Attachments: client.jks, server.jks, standalone-full.xml > > > It looks like the OpenSSL security provider is now used as a default when I configure reverse-proxy feature on the server. Not sure what is the root-cause for this change of behavior. I also see this change of behavior only with JDK8. JDK11 works as expected! > Attaching relevant configuration. There can be also seen that during the startup, relevant log message about OpenSSL provider is logged during the server boot, e.g.: > {quote} > 16:44:42,676 INFO [org.wildfly.openssl.SSL] (MSC service thread 1-3) WFOPENSSL0002 OpenSSL Version OpenSSL 1.0.2h-fips 3 May 2016 > {quote} > This INFO message starts to occur in the server log since 'server-ssl-context' or 'client-ssl-contexts' are added into the server configuration and server is started with JDK8: > {code} > <server-ssl-contexts> > <server-ssl-context name="server-ssl-context" need-client-auth="true" key-manager="server-ssl-contextKM" trust-manager="server-ssl-contextTM"/> > </server-ssl-contexts> > <client-ssl-contexts> > <client-ssl-context name="proxy-ssl-context" key-manager="proxy-ssl-contextKM" trust-manager="proxy-ssl-contextTM"/> > </client-ssl-contexts> > {code} > There are two questions from this: > # Is this change of OpenSSL provider being initialized during the boot in this configuration case expected? > # I believe that even in case that answer to question above is `yes`, then we should not change default security provider, which in this case it should be JSSE. Not to mention that we don't want to behave differently for JDK8 and JDK11. > Hope I don't have any misconfiguration in the configuration itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-339) OpenSSL security provider seems to be used when not defined with JDK8 now

by Jan Stourac (Jira)

[ https://issues.redhat.com/browse/WFWIP-339?page=com.atlassian.jira.plugin... ] Jan Stourac resolved WFWIP-339. ------------------------------- Resolution: Done > OpenSSL security provider seems to be used when not defined with JDK8 now > ------------------------------------------------------------------------- > > Key: WFWIP-339 > URL: https://issues.redhat.com/browse/WFWIP-339 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Reporter: Jan Stourac > Assignee: Farah Juma > Priority: Major > Attachments: client.jks, server.jks, standalone-full.xml > > > It looks like the OpenSSL security provider is now used as a default when I configure reverse-proxy feature on the server. Not sure what is the root-cause for this change of behavior. I also see this change of behavior only with JDK8. JDK11 works as expected! > Attaching relevant configuration. There can be also seen that during the startup, relevant log message about OpenSSL provider is logged during the server boot, e.g.: > {quote} > 16:44:42,676 INFO [org.wildfly.openssl.SSL] (MSC service thread 1-3) WFOPENSSL0002 OpenSSL Version OpenSSL 1.0.2h-fips 3 May 2016 > {quote} > This INFO message starts to occur in the server log since 'server-ssl-context' or 'client-ssl-contexts' are added into the server configuration and server is started with JDK8: > {code} > <server-ssl-contexts> > <server-ssl-context name="server-ssl-context" need-client-auth="true" key-manager="server-ssl-contextKM" trust-manager="server-ssl-contextTM"/> > </server-ssl-contexts> > <client-ssl-contexts> > <client-ssl-context name="proxy-ssl-context" key-manager="proxy-ssl-contextKM" trust-manager="proxy-ssl-contextTM"/> > </client-ssl-contexts> > {code} > There are two questions from this: > # Is this change of OpenSSL provider being initialized during the boot in this configuration case expected? > # I believe that even in case that answer to question above is `yes`, then we should not change default security provider, which in this case it should be JSSE. Not to mention that we don't want to behave differently for JDK8 and JDK11. > Hope I don't have any misconfiguration in the configuration itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2374) TCP/TCP_NIO2/GossipRouter: add TLS

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2374?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2374. ---------------------------- Resolution: Duplicate Issue Dupl of JGRP-2487 > TCP/TCP_NIO2/GossipRouter: add TLS > ---------------------------------- > > Key: JGRP-2374 > URL: https://issues.redhat.com/browse/JGRP-2374 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.1 > > > Add TLS to the TCP and TCP_NIO2 transports. Look into wildfly-openssl [1] for the impl. > [1] https://github.com/wildfly-security/wildfly-openssl -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 September 2020