July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13546) Upgrade smallrye-open-api to 2.0.3

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13546?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13546: -------------------------------- Summary: Upgrade smallrye-open-api to 2.0.3 (was: Upgrade smallrye-open-api to 1.2.5) > Upgrade smallrye-open-api to 2.0.3 > ---------------------------------- > > Key: WFLY-13546 > URL: https://issues.redhat.com/browse/WFLY-13546 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenAPI > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Fixes: > [https://github.com/smallrye/smallrye-open-api/issues/349] > [https://github.com/smallrye/smallrye-open-api/issues/353] > [https://github.com/smallrye/smallrye-open-api/issues/359] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11999) WildFly creates too many instances of all web service classes

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-11999?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-11999: ---------------------------------- Summary: WildFly creates too many instances of all web service classes (was: Wildfly creates to many instances of all web service classes) > WildFly creates too many instances of all web service classes > ------------------------------------------------------------- > > Key: WFLY-11999 > URL: https://issues.redhat.com/browse/WFLY-11999 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 8.0.0.Final, 16.0.0.Final, 19.0.0.Final > Environment: Ubuntu 18.10 64bit, Open JDK 8 or Open JDK 11 > Reporter: Stefan Frings > Assignee: Parul Sharma > Priority: Minor > Attachments: Test-1.0-SNAPSHOT.war, Test.zip, standalone.xml > > > 1) My @Webservice classes are all constructed multiple times (3x - 4x) but I expected only one instance. > 2) Only the second instance receives a call to the observer method for initialization. I expect that this method is called in each instance. > The issue can be reproduced with the attached minimum project on Wildfly 8 with JDK 8 as well as Wildfly 16 with JDK 11. > Complete source code of the whole application: > {code} > package com.mvneco.test; > import javax.enterprise.context.ApplicationScoped; > import javax.enterprise.context.Initialized; > import javax.enterprise.event.Observes; > import javax.jws.WebMethod; > import javax.jws.WebService; > import org.apache.commons.logging.Log; > import org.apache.commons.logging.LogFactory; > @ApplicationScoped > @WebService > public class SoapService > { > private Log log = LogFactory.getLog(SoapService.class); > public SoapService() > { > log.debug("Init SoapService 1"); > } > @WebMethod(exclude = true) > public void init(@Observes @Initialized(ApplicationScoped.class) Object init) > { > log.debug("Init SoapService 2"); > } > @WebMethod > public String test(String payload) > { > log.debug("Start test(). payload="+payload); > return "OK"; > } > } > {code} > Extract from Log messages that show the issue (the complete log is in the attached ZIP): > {code} > 2019-04-17 13:12:21,399 DEBUG [com.mvneco.test.SoapService] (MSC service thread 1-2) Init SoapService 1 > 2019-04-17 13:12:23,068 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 1 > 2019-04-17 13:12:23,070 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 2 > 2019-04-17 13:12:23,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started in 10514ms - Started 510 of 699 services (337 services are lazy, passive or on-demand) > 2019-04-17 13:12:28,920 INFO [org.apache.cxf.services.SoapService.REQ_IN] (default task-1) REQ_IN > Address: http://localhost:8080/Test-1.0-SNAPSHOT/SoapService > ... > 2019-04-17 13:12:28,932 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1 > 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1 > 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Start test(). payload=? > 2019-04-17 13:12:28,969 INFO [org.apache.cxf.services.SoapService.RESP_OUT] (default task-1) RESP_OUT > Content-Type: text/xml > ... > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13673) Some kind if layer test that verifies legacy security is not included.

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13673: --------------------------------------- Summary: Some kind if layer test that verifies legacy security is not included. Key: WFLY-13673 URL: https://issues.redhat.com/browse/WFLY-13673 Project: WildFly Issue Type: Task Components: Security, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 21.0.0.Beta1 I am currently looking at changes needed to prevent legacy security / PicketBox from being accidentally provisioned with Elytron security. We should likely have a test that PicketBox is not present so if any future changes accidentally added a dependency this would be flagged quickly in CI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2

by Janardhan Naidu (Jira)

[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ] Janardhan Naidu commented on JGRP-2485: --------------------------------------- Hi [~belaban] I was trying to execute the demo chat application, In RHEL it worked even without passing udp.xml as input. But when i tried the same in Windows, It is not working. I am attaching udp.xml from v3.6.9 where there is no option to add bind_addr and mcast_addr. I tried adding it in udp.xml itself after mcast_port and it too didn't help. Also I had one more question, How do we provide TCPPING list to this demo chat application? I was going through one of your article and found another way to test to run mcast sender in one node and mcast receiver in another node. and this test passed in both rhel and win for me. *In Node1:* java -cp jgroups-3.6.19.Final.jar org.jgroups.tests.McastSenderTest -bind_addr bdc-node1IP -mcast_addr 239.255.166.17 -port 49080 -ttl 9 *In Node2:* java -cp jgroups-3.6.19.Final.jar org.jgroups.tests.McastReceiverTest -bind_addr bdc-node2IP -mcast_addr 239.255.166.17 -port 49080 Need your help in running demoChat application with the parameters you suggested. Thanks in Advance!. Regards, Janardhan > UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2 > -------------------------------------------------------------------- > > Key: JGRP-2485 > URL: https://issues.redhat.com/browse/JGRP-2485 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.19 > Reporter: Janardhan Naidu > Assignee: Bela Ban > Priority: Major > Attachments: noapp.log.D20200619.T053202_NODE1, udp.xml > > > Hi Team, > > we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working. > after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP. > *Warnings:* > *WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead* > [2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField > *WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored* > [2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init > *WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false* > > To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar: > and now our properties looks like: > *property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2) > > > With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP. > Please help me in resolving the same > > Thank > Janardhan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2485) UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2

by Janardhan Naidu (Jira)

[ https://issues.redhat.com/browse/JGRP-2485?page=com.atlassian.jira.plugin... ] Janardhan Naidu updated JGRP-2485: ---------------------------------- Attachment: udp.xml > UDP is not working after upgarde to 3_6_19 from jgroups-3.4.0.Alpha2 > -------------------------------------------------------------------- > > Key: JGRP-2485 > URL: https://issues.redhat.com/browse/JGRP-2485 > Project: JGroups > Issue Type: Bug > Affects Versions: 3.6.19 > Reporter: Janardhan Naidu > Assignee: Bela Ban > Priority: Major > Attachments: noapp.log.D20200619.T053202_NODE1, udp.xml > > > Hi Team, > > we just upgraded from jgroups-3.4.0.Alpha2 to 3_6_19. post the UDP cluster communication is not working. > after upgrade, we were hitting some warning as below and we solved those by changing property_string of UDP. > *Warnings:* > *WARNING: JGRP000014: Discovery.timeout has been deprecated: GMS.join_timeout should be used instead* > [2020-06-17 14:05:49.271] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.stack.Configurator resolveAndAssignField > *WARNING: JGRP000014: Discovery.num_initial_members has been deprecated: will be ignored* > [2020-06-17 14:05:49.396] ALL 000000000000 GLOBAL_SCOPE Jun 17, 2020 2:05:49 PM org.jgroups.protocols.pbcast.NAKACK init > *WARNING: use_mcast_xmit should not be used because the transport (TCP) does not support IP multicasting; setting use_mcast_xmit to false* > > To solve above warnings, we went through tcp.xml which was shipped using in 3_6_19 jar: > and now our properties looks like: > *property_string=UDP*(bind_addr=*hostIP*;bind_port=39061;mcast_addr=239.255.166.17;mcast_port=39060;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800;discard_delivered_msgs=true):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *distribution_property_string=TCP*(bind_port=39060;thread_pool_rejection_policy=run):TCPPING(async_discovery=true;initial_hosts=*hostIP*[39060];port_range=0;):MERGE2(min_interval=3000;max_interval=5000):FD_SOCK:FD(timeout=5000;max_tries=48):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=false;discard_delivered_msgs=true;):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;max_bytes=0):pbcast.GMS(join_timeout=5000;print_local_addr=true) > > *lock.protocolStack=UDP*(bind_addr=*hostIP*;bind_port=39062;mcast_addr=239.255.166.17;mcast_port=39069;ip_ttl=32;mcast_send_buf_size=150000;mcast_recv_buf_size=80000):PING:MERGE2(min_interval=5000;max_interval=10000):FD_ALL(interval=5000;timeout=20000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(use_mcast_xmit=true;retransmit_timeout=300,600,1200,2400,4800):UNICAST:pbcast.STABLE(desired_avg_gossip=20000):FRAG(frag_size=8096):pbcast.GMS(join_timeout=5000;print_local_addr=true):CENTRAL_LOCK(num_backups=2) > > > With above properties, we are not seeing any warning or error. But still cluster communication is not working with UDP. > Please help me in resolving the same > > Thank > Janardhan -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5511) Grid keyboard control after collection editor in use

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5511: ----------------------------------- Summary: Grid keyboard control after collection editor in use Key: DROOLS-5511 URL: https://issues.redhat.com/browse/DROOLS-5511 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Affects Versions: 7.41.0.Final Reporter: Jozef Marko Assignee: Jozef Marko The Test scenario has a a collection editor popup to facilitate providing list of values. The issue is once provided values are saved, the popup disappear however test scenario grid lost focus and user can not control it by keyboard. For comparison, if user decides to discard changes in collection editor popup, and click just close, the grid does not lost focus and is still interactive. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5286) [Sceim Editor] If you select a fact with context type then it is not selects in test tools

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5286?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5286: ------------------------------- Priority: Minor (was: Major) > [Sceim Editor] If you select a fact with context type then it is not selects in test tools > ------------------------------------------------------------------------------------------- > > Key: DROOLS-5286 > URL: https://issues.redhat.com/browse/DROOLS-5286 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools, kogito-tooling > Attachments: TestPossible types.dmn, image-2020-04-30-15-44-13-859.png > > > Test tools Pannel has a defect - it does not highlighting the right context nested node if that was just initialized. See [1] > Workaround: remove fact and add again > [1] > !image-2020-04-30-15-44-13-859.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5287) [Scenario Editor] Context type could be added twice

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5287?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5287: ------------------------------- Priority: Minor (was: Major) > [Scenario Editor] Context type could be added twice > --------------------------------------------------- > > Key: DROOLS-5287 > URL: https://issues.redhat.com/browse/DROOLS-5287 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.36.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools, kogito-tooling > Attachments: TestPossible types.dmn > > > There is a DMN type called Context > User can add context type as a fact in Scenario Simullation Table . > Defect: user can do that twice -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13620) jaxrs-jwt: The parameters 'mainClass' are missing or invalid

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13620?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-13620: -------------------------------------------- [~mayerw01] Hello, Can you please change your java version to 1.8.0_232 and check if is it working fine or not? > jaxrs-jwt: The parameters 'mainClass' are missing or invalid > ------------------------------------------------------------- > > Key: WFLY-13620 > URL: https://issues.redhat.com/browse/WFLY-13620 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final > Reporter: Wolfgang Mayer > Assignee: Ranabir Chakraborty > Priority: Minor > > mvn exec:java fails > [INFO] Reactor Summary for Quickstart: jaxrs-jwt 20.0.0.Final: > [INFO] > [INFO] Quickstart: jaxrs-jwt .............................. FAILURE [ 0.361 s] > [INFO] Quickstart: jaxrs-jwt - client ..................... SKIPPED > [INFO] Quickstart: jaxrs-jwt - service .................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 1.056 s > [INFO] Finished at: 2020-06-27T13:39:17+02:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project jaxrs-jwt: The parameters 'mainClass' for goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java are missing or invalid -> [Help 1] > [ERROR] > mvn -v > Apache Maven 3.6.3 > Maven home: /usr/share/maven > Java version: 14.0.1, vendor: Private Build, runtime: /usr/lib/jvm/java-14-openjdk-amd64 > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-39-generic", arch: "amd64", family: "unix" > Executing the clent directly via: > $JAVA_HOME/bin/java -classpath $CLASSPATH org.jboss.quickstarts.jaxrsjwt.client.JwtRestClient > Euns successfully indeed. So this seems to be an issue with the pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5510) GDST Verifier throws an error for BRL column

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5510?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5510: -------------------------------- Workaround Description: Turn off V&V feature by: {{-Dorg.kie.verification.disable-dtable-realtime-verification}} (was: Turn off V&V feature by: {-Dorg.kie.verification.disable-dtable-realtime-verification}) > GDST Verifier throws an error for BRL column > -------------------------------------------- > > Key: DROOLS-5510 > URL: https://issues.redhat.com/browse/DROOLS-5510 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.41.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2020-07-16 10-56-24.png, Screenshot from 2020-07-16 10-56-34.png, Screenshot from 2020-07-16 10-56-52.png, bpms_vv-reproducer.zip > > > There is an issue when user adds a first rown into guided decision table with specific BRL column. > !Screenshot from 2020-07-16 10-56-52.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

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 July 2020