July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12129) The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12129?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12129: ----------------------------------------- [~terryyrliang] You put a 'regression' label on this. What's the latest WildFly version where you have not seen this problem? If that's not WildFly 16.0.0.Final and if you've tried with any others prior to 17.0.0.Beta1 please let us know as that might help narrow down the problem. Thanks! > The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory > -------------------------------------------------------------------------------------------------- > > Key: WFLY-12129 > URL: https://issues.jboss.org/browse/WFLY-12129 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Alpha1, 17.0.0.Beta1 > Reporter: terry liang > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: regression > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12129) The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12129?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12129: ------------------------------------ Steps to Reproduce: 1. Setup below configuration in wildfly {code} <subsystem xmlns="urn:jboss:domain:messaging-activemq:5.0"> <server name="default"> <security enabled="false"/> <management jmx-enabled="true" address="jms.queue.activemq.management" jmx-domain="org.activemq" /> <security-setting name="activemq.management"> <role name="admin"/> </security-setting> <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760000" page-size-bytes="2097152" message-counter-history-day-limit="10"/> <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/> <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput"> <param name="batch-delay" value="50"/> </http-connector> <remote-connector name="legacy-messaging-connector" socket-binding="legacy-messaging"/> <in-vm-connector name="in-vm" server-id="0"> <param name="buffer-pooling" value="false"/> </in-vm-connector> <http-acceptor name="http-acceptor" http-listener="default"/> <http-acceptor name="http-acceptor-throughput" http-listener="default"> <param name="batch-delay" value="50"/> <param name="direct-deliver" value="false"/> </http-acceptor> <remote-acceptor name="legacy-messaging-acceptor" socket-binding="legacy-messaging"/> <in-vm-acceptor name="in-vm" server-id="0"> <param name="buffer-pooling" value="false"/> </in-vm-acceptor> <jms-topic name="testTopic" entries="topic/newTestTopic java:jboss/exported/topic/newTestTopic" legacy-entries="topic/testTopic jms/topic/testTopic java:jboss/exported/topic/testTopic"/> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory java:jboss/exported/ConnectionFactory" connectors="in-vm"/> <connection-factory name="NewRemoteConnectionFactory" entries="java:jboss/exported/jms/NewRemoteConnectionFactory" connectors="http-connector"/> <legacy-connection-factory name="legacy-discovery" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="legacy-messaging-connector"/> <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> </server> </subsystem> <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <connector name="legacy-remoting-connector" socket-binding="legacy-remoting"/> <http-connector name="http-remoting-connector" connector-ref="default"/> </subsystem> <interfaces> <interface name="management"> <any-address/> </interface> <interface name="public"> <any-address/> </interface> <interface name="messaging-interface"> <any-address/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${my.jboss.port.offset:0}"> <socket-binding name="legacy-remoting" port="4447"/> <socket-binding name="legacy-messaging" interface="messaging-interface" port="5445"/> </socket-binding-group> {code} 2. Use JMS client tool such as JMSToolBox to connect to wildfly messaging system with Apache Active MQ Artemis v2.x and port 5445 3. Subscribe the topic testTopic 4. Disconnect to wildfly messaging system 5. Wait for 30 seconds 6. Reconnect to wildfly messaging system again 7. The topic testTopic disappear. was: 1. Setup below configuration in wildfly <subsystem xmlns="urn:jboss:domain:messaging-activemq:5.0"> <server name="default"> <security enabled="false"/> <management jmx-enabled="true" address="jms.queue.activemq.management" jmx-domain="org.activemq" /> <security-setting name="activemq.management"> <role name="admin"/> </security-setting> <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760000" page-size-bytes="2097152" message-counter-history-day-limit="10"/> <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/> <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput"> <param name="batch-delay" value="50"/> </http-connector> <remote-connector name="legacy-messaging-connector" socket-binding="legacy-messaging"/> <in-vm-connector name="in-vm" server-id="0"> <param name="buffer-pooling" value="false"/> </in-vm-connector> <http-acceptor name="http-acceptor" http-listener="default"/> <http-acceptor name="http-acceptor-throughput" http-listener="default"> <param name="batch-delay" value="50"/> <param name="direct-deliver" value="false"/> </http-acceptor> <remote-acceptor name="legacy-messaging-acceptor" socket-binding="legacy-messaging"/> <in-vm-acceptor name="in-vm" server-id="0"> <param name="buffer-pooling" value="false"/> </in-vm-acceptor> <jms-topic name="testTopic" entries="topic/newTestTopic java:jboss/exported/topic/newTestTopic" legacy-entries="topic/testTopic jms/topic/testTopic java:jboss/exported/topic/testTopic"/> <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory java:jboss/exported/ConnectionFactory" connectors="in-vm"/> <connection-factory name="NewRemoteConnectionFactory" entries="java:jboss/exported/jms/NewRemoteConnectionFactory" connectors="http-connector"/> <legacy-connection-factory name="legacy-discovery" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="legacy-messaging-connector"/> <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> </server> </subsystem> <subsystem xmlns="urn:jboss:domain:remoting:4.0"> <connector name="legacy-remoting-connector" socket-binding="legacy-remoting"/> <http-connector name="http-remoting-connector" connector-ref="default"/> </subsystem> <interfaces> <interface name="management"> <any-address/> </interface> <interface name="public"> <any-address/> </interface> <interface name="messaging-interface"> <any-address/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${my.jboss.port.offset:0}"> <socket-binding name="legacy-remoting" port="4447"/> <socket-binding name="legacy-messaging" interface="messaging-interface" port="5445"/> </socket-binding-group> 2. Use JMS client tool such as JMSToolBox to connect to wildfly messaging system with Apache Active MQ Artemis v2.x and port 5445 3. Subscribe the topic testTopic 4. Disconnect to wildfly messaging system 5. Wait for 30 seconds 6. Reconnect to wildfly messaging system again 7. The topic testTopic disappear. > The subscribed topic is removed if reconnecting to messaging system with legacy-connection-factory > -------------------------------------------------------------------------------------------------- > > Key: WFLY-12129 > URL: https://issues.jboss.org/browse/WFLY-12129 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Alpha1, 17.0.0.Beta1 > Reporter: terry liang > Assignee: Emmanuel Hugonnet > Priority: Blocker > Labels: regression > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12297) Jakarta EE 8 Certification for WildFly

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12297: --------------------------------------- Summary: Jakarta EE 8 Certification for WildFly Key: WFLY-12297 URL: https://issues.jboss.org/browse/WFLY-12297 Project: WildFly Issue Type: Task Components: Server Reporter: Brian Stansberry Assignee: Scott Marlow Certify WildFly 18 as Jakarta EE 8 compatible. Publish the certification results on https://github.com/wildfly/certifications -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2362) Providing logical member name in JDBC_PING

by S Pokutniy (Jira)

S Pokutniy created JGRP-2362: -------------------------------- Summary: Providing logical member name in JDBC_PING Key: JGRP-2362 URL: https://issues.jboss.org/browse/JGRP-2362 Project: JGroups Issue Type: Feature Request Affects Versions: 4.0.20, 4.1.0, 4.0.19, 4.0.18, 4.0.17 Reporter: S Pokutniy Assignee: Bela Ban When using JDBC_PING and logical names instead of UUIDs and one of the cluster member crashes or get killed and this member is not coordinator then its database set still remains in the database as long as coordinator changes (independently from remove_old_coords_on_view_change /remove_all_data_on_view_change). If the the cluster is then restarted the old dataset makes connect() much slower (+30 seconds), as the members seem to be tryting to connect to it. Parameter remove_all_data_on_view_change seems to be the solution but it does not work as long as coordinator does not change, so practically the same as remove_old_coords_on_view_change. The only solution seems to be to provide an appropriate delete statement in parameter initialize_sql, which would delete old entry, for example like this: delete from JGROUPSPING where ping_data like '%logical name%'. However, this is neither really quick nor the ideal solution, as ping_data's datatype is bytea or bit varying. It would be great to have also logical name in JGROUPSPING, which is instead per default in insert(). This is also easy to implement as there is access to this information in PingData. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-824) UI Automations - Fix random failures for OCP4

by Hayk Hovsepyan (Jira)

[ https://issues.jboss.org/browse/SWSQE-824?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan closed SWSQE-824. -------------------------------- Resolution: Done > UI Automations - Fix random failures for OCP4 > --------------------------------------------- > > Key: SWSQE-824 > URL: https://issues.jboss.org/browse/SWSQE-824 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Critical > Labels: automation > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4315) [DMN Designer] Documentation - Download buttons UX

by Tiago Dolphine (Jira)

[ https://issues.jboss.org/browse/DROOLS-4315?page=com.atlassian.jira.plugi... ] Tiago Dolphine commented on DROOLS-4315: ---------------------------------------- Hi [~roger600] the print button on the Documentation Tab it not generic now, I mean it is not shared among all Documentation Views (BPMN, DMN, ...) this could be refactored to have some common component. [~karreiro] probably have created a print button on the dmn view similar we've done on the view for bpmn. > [DMN Designer] Documentation - Download buttons UX > -------------------------------------------------- > > Key: DROOLS-4315 > URL: https://issues.jboss.org/browse/DROOLS-4315 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: component-1.png, component-2.png, component-3.png > > > h3. Context: > Today users can: > 1) Download the diagram picture by using this component: > !component-1.png|thumbnail! > 2) Download the DMN file by using this component: > !component-2.png|thumbnail! > 3) Print or Download the documentation as PDF by using the *Print* button (into the Documentation tab): > !component-3.png|thumbnail! > 4) Download the documentation as DOC by using the *Download .doc file* button (into the Documentation tab): > !component-3.png|thumbnail! > ---- > h3. Problem: > The "Download" concept is getting confusing for users. > As a user, I want to be able to: > - Download the documentation as a .PDF file > - Download the documentation as a .DOC file > - Print the documentation > ---- > h3. Notice: > This component can be removed (if UX considers that it's necessary): > !component-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-813) Maistra - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-813?page=com.atlassian.jira.plugin.... ] Sunil Kondkar commented on SWSQE-813: ------------------------------------- There is no missing data for Maistra project in audit report: https://polarion.engineering.redhat.com/polarion/#/project/pylarion/wiki/... Test run statistics: https://polarion.engineering.redhat.com/polarion/#/project/MaistraIstio/w... PQI Metrics: https://polarion.engineering.redhat.com/polarion/#/project/MaistraIstio/w... > Maistra - Create TP12 Polarion PQI reports > ------------------------------------------ > > Key: SWSQE-813 > URL: https://issues.jboss.org/browse/SWSQE-813 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Priority: Major > Labels: pqi > > et PQI reports for Maistra: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Maistra TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-813) Maistra - Create TP12 Polarion PQI reports

by Sunil Kondkar (Jira)

[ https://issues.jboss.org/browse/SWSQE-813?page=com.atlassian.jira.plugin.... ] Sunil Kondkar resolved SWSQE-813. --------------------------------- Resolution: Done > Maistra - Create TP12 Polarion PQI reports > ------------------------------------------ > > Key: SWSQE-813 > URL: https://issues.jboss.org/browse/SWSQE-813 > Project: Kiali QE > Issue Type: QE Task > Reporter: Sunil Kondkar > Priority: Major > Labels: pqi > > et PQI reports for Maistra: > 1) Check Test case Quality Audit report(No missing data) > 2) PQI reports - Create TP12 test iteration, link this iteration to Maistra TP12 test runs -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4332) Disable PMML parsing via kie-pmml if jPMML is in the classpath

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-4332: ------------------------------------- Summary: Disable PMML parsing via kie-pmml if jPMML is in the classpath Key: DROOLS-4332 URL: https://issues.jboss.org/browse/DROOLS-4332 Project: Drools Issue Type: Task Components: PMML Reporter: Daniele Zonca Assignee: Vladimir Blagojevic When user add in the classpath jPMML integration jars, kie-pmml should be disabled because otherwise it could generate parsing errors in case of unsupported model. We need to disable it in {{PMMLAssembler}} and in {{ApplyPmmlModelCommand}} and add a log info about that -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12221) Integrate mod_cluster subsystem with WildFly Discovery SPI

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12221?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12221: ---------------------------------- Description: The discovery can be generalized using WildFly Discovery SPI. Currently, it can essentially replace static proxies list. Once discovery providers can be supplied by subsystems a general multicast or cloud based discovery can be used. (was: The discovery can be generalized with WildFly Discovery SPI. Currently, it can essentially replace static proxies list. Once discovery providers can be supplied by subsystems a general multicast or cloud based discovery can be used.) > Integrate mod_cluster subsystem with WildFly Discovery SPI > ---------------------------------------------------------- > > Key: WFLY-12221 > URL: https://issues.jboss.org/browse/WFLY-12221 > Project: WildFly > Issue Type: Feature Request > Components: mod_cluster > Affects Versions: 17.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > The discovery can be generalized using WildFly Discovery SPI. Currently, it can essentially replace static proxies list. Once discovery providers can be supplied by subsystems a general multicast or cloud based discovery can be used. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years

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 2019