July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2656: ------------------------------------- [~mstevens1] Any updates on resources for this task? I ask because it was pulled into the current sprint, so I believe that'll give Brian about 5 days to create the icons once he's back. Not sure if that's ok or do-able for him. Wdyt? > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10663) Upgrade mod_cluster to 1.3.10.Final

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10663?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10663: --------------------------------------- [~jamezp] Right, it's just needed to sync with downstream. Otherwise the target is 1.4.x (WFLY-10440) which is currently held up by QE (WFLY-6803). > Upgrade mod_cluster to 1.3.10.Final > ----------------------------------- > > Key: WFLY-10663 > URL: https://issues.jboss.org/browse/WFLY-10663 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10663) Upgrade mod_cluster to 1.3.10.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10663?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10663: -------------------------------------- Diff seems to be minor https://github.com/modcluster/mod_cluster/compare/1.3.9.Final...1.3.10.Final. > Upgrade mod_cluster to 1.3.10.Final > ----------------------------------- > > Key: WFLY-10663 > URL: https://issues.jboss.org/browse/WFLY-10663 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3953) JBoss CLI doesn't work on OpenShift

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3953?page=com.atlassian.jira.plugi... ] Jean-Francois Denise moved WFLY-10664 to WFCORE-3953: ----------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-3953 (was: WFLY-10664) Component/s: CLI (was: CLI) > JBoss CLI doesn't work on OpenShift > ----------------------------------- > > Key: WFCORE-3953 > URL: https://issues.jboss.org/browse/WFCORE-3953 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Environment: OpenShift/MiniShift > * minishift v1.15.1+f19ac09 > * CDK v3.4.0-2 > EAP CD12 > * Registry registry.access.redhat.com > * Namespace/Repository jboss-eap-7-tech-preview/eap-cd-openshift > * Tag 12.0-14 > Reporter: Martin Styk > Assignee: Jean-Francois Denise > Priority: Critical > > I am unable to access JBoss CLI console running EAP CD12 on OpenShift. > On OS webconsole terminal: > {code} > cd $JBOSS_HOME/bin > sh jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > {code} > No new line appears and I am not able to enter any character, thus I can not connect. I can only exit JBoss CLI console with Ctrl + C. > With CD12 it doesn't work neither with terminal session on web console, nor with {{oc rsh <pod>}} from local terminal. > This doesn't happen with EAP 7.0 and EAP 7.1 openshift images. EAP CD12 distribution (not the OpenShift image) is also not affected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10664) JBoss CLI doesn't work on OpenShift

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFLY-10664?page=com.atlassian.jira.plugin... ] Jean-Francois Denise commented on WFLY-10664: --------------------------------------------- [~mstyk], if you could: 1) call stty -a and provide the output 2) tty and provide the output 3) Enable all traces and provide the output 4) Value of TERM 5) Ideally the value of System.getProperty("os.name") Thank-you. JF > JBoss CLI doesn't work on OpenShift > ----------------------------------- > > Key: WFLY-10664 > URL: https://issues.jboss.org/browse/WFLY-10664 > Project: WildFly > Issue Type: Bug > Components: CLI > Environment: OpenShift/MiniShift > * minishift v1.15.1+f19ac09 > * CDK v3.4.0-2 > EAP CD12 > * Registry registry.access.redhat.com > * Namespace/Repository jboss-eap-7-tech-preview/eap-cd-openshift > * Tag 12.0-14 > Reporter: Martin Styk > Assignee: Jean-Francois Denise > Priority: Critical > > I am unable to access JBoss CLI console running EAP CD12 on OpenShift. > On OS webconsole terminal: > {code} > cd $JBOSS_HOME/bin > sh jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > {code} > No new line appears and I am not able to enter any character, thus I can not connect. I can only exit JBoss CLI console with Ctrl + C. > With CD12 it doesn't work neither with terminal session on web console, nor with {{oc rsh <pod>}} from local terminal. > This doesn't happen with EAP 7.0 and EAP 7.1 openshift images. EAP CD12 distribution (not the OpenShift image) is also not affected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3952) Unable to run -DallTests -Delytron builds

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-3952: ---------------------------------------- Summary: Unable to run -DallTests -Delytron builds Key: WFCORE-3952 URL: https://issues.jboss.org/browse/WFCORE-3952 Project: WildFly Core Issue Type: Bug Components: Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 6.0.0.Alpha3 Attempting to use -DallTests -Delytron results in the following error: - {noformat} [ERROR] } [ERROR] Cannot start embedded Host Controller: WFLYEMB0022: Cannot invoke 'start' on embedded process: WFLYHC0097: Domain base directory does not exist: /home/darranl/src/wildfly13/wildfly-core/testsuite/standalone/target/wildfly-core/domain {noformat} I believe this is actually caused by WFCORE-3769 which provisions a standalone server only. We don't currently run -Delytron jobs for WildFly Core but this bug causes problems with experimental builds where we may want to use -Delytron. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-10665) XTS .NET async feature should be enalbled with system property as it's way how it's done in 7.1.0

by Francesco Marchioni (JIRA)

[ https://issues.jboss.org/browse/WFLY-10665?page=com.atlassian.jira.plugin... ] Francesco Marchioni commented on WFLY-10665: -------------------------------------------- Ack [~ochaloup] > XTS .NET async feature should be enalbled with system property as it's way how it's done in 7.1.0 > ------------------------------------------------------------------------------------------------- > > Key: WFLY-10665 > URL: https://issues.jboss.org/browse/WFLY-10665 > Project: WildFly > Issue Type: Bug > Components: XTS > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > > This is follow-up to issue: https://issues.jboss.org/browse/WFLY-9818 where XTS subsystem was enriched with attribute {{<async-registration enabled="true" />}} to enable XTS async registration needed to work fine with .NET. > In JBoss EAP 7.1 there is change to enable the feature with system property {{wsat.async.registration}}. > The possibility to enable the feature with the system property should be available in the master (WFLY14) too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-23) [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster

by Michal Toth (JIRA)

[ https://issues.jboss.org/browse/WFWIP-23?page=com.atlassian.jira.plugin.s... ] Michal Toth edited comment on WFWIP-23 at 7/3/18 11:21 AM: ----------------------------------------------------------- I am checking this one using EAP QE test suite again. Make it running 20 times. My further tests shown error in our QE Core client, needing to handle Exception during failover. This has been resolved. Used {{https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/528/artifact/jboss-eap.zip}} and our build with latest master {[https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/121/}}. {noformat} $ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster ... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s] [INFO] tooling ............................................ SUCCESS [ 8.128 s] [INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s] [INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s] [INFO] common-tests ....................................... SUCCESS [15:20 min] [INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s] [INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s] [INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15:55 min [INFO] Finished at: 2018-07-02T16:39:28+02:00 [INFO] Final Memory: 72M/1146M [INFO] ------------------------------------------------------------------------ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase {noformat} was (Author: mtoth): I am checking this one using EAP QE test suite again. Make it running 20 times. My further tests shown error in our QE Core client, needing to handle Exception during failover. This has been resolved. Used {{https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/528/artifact/jboss-eap.zip}} {noformat} $ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster ... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s] [INFO] tooling ............................................ SUCCESS [ 8.128 s] [INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s] [INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s] [INFO] common-tests ....................................... SUCCESS [15:20 min] [INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s] [INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s] [INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15:55 min [INFO] Finished at: 2018-07-02T16:39:28+02:00 [INFO] Final Memory: 72M/1146M [INFO] ------------------------------------------------------------------------ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase {noformat} > [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster > ----------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-23 > URL: https://issues.jboss.org/browse/WFWIP-23 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Jiri Ondrusek > Priority: Blocker > Labels: activemq, feature-branch-blocker > Attachments: journal-node-2.txt > > > There are lost messages in scenario where nodes in cluster are cleanly stopped and started again. This issue was hit with Artemis 2.5.0.Final and WF Jeff's integration branch WFLY-9407_upgrade_artemis_2.4.0_with_prefix. > Test Scenario: > * start two servers in cluster (JGroups used for discovery) > * send messages to testQueue0 on node-1 and node-2 > * wait until consumers on both nodes receive 300 messages > * cleanly shut down 1st and then 2nd server > * leave servers shut down for one minute > * start both servers > * wait until both consumers receive 500 messages > * stop sending messages and receive all remaining messages > Pass Criteria: All send messages are received by consumer > Actual Result: There are lost messages. > Investigation: > There are lost messages which were sent to 2nd node. However they got stuck in queue {{.artemis.internal.sf.my-cluster.8a7e9e98-2c36-11e8-9737-fa163ea20b26}} during load balancing to 1st server. > I'm attaching trace logs from client and servers and content of journal from 2nd server. > This is regression against Artemis 1.5.5 thus setting blocker priority. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFWIP-23) [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster

by Michal Toth (JIRA)

[ https://issues.jboss.org/browse/WFWIP-23?page=com.atlassian.jira.plugin.s... ] Michal Toth edited comment on WFWIP-23 at 7/3/18 11:21 AM: ----------------------------------------------------------- I am checking this one using EAP QE test suite again. Make it running 20 times. My further tests shown error in our QE Core client, needing to handle Exception during failover. This has been resolved. Used {{https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/528/artifact/jboss-eap.zip}} and our build with latest master {{https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/121/}}. {noformat} $ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster ... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s] [INFO] tooling ............................................ SUCCESS [ 8.128 s] [INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s] [INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s] [INFO] common-tests ....................................... SUCCESS [15:20 min] [INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s] [INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s] [INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15:55 min [INFO] Finished at: 2018-07-02T16:39:28+02:00 [INFO] Final Memory: 72M/1146M [INFO] ------------------------------------------------------------------------ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase {noformat} was (Author: mtoth): I am checking this one using EAP QE test suite again. Make it running 20 times. My further tests shown error in our QE Core client, needing to handle Exception during failover. This has been resolved. Used {{https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/528/artifact/jboss-eap.zip}} and our build with latest master {[https://mw-messaging-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/early-testing-messaging-prepare/121/}}. {noformat} $ ./repeat_test_until_fail.sh ClusterTestCase#testStopStartCluster ... [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] jboss-hornetq-testsuite ............................ SUCCESS [ 12.403 s] [INFO] tooling ............................................ SUCCESS [ 8.128 s] [INFO] apps-jms11-jdk6 .................................... SUCCESS [ 1.568 s] [INFO] tooling-eap7 ....................................... SUCCESS [ 3.895 s] [INFO] common-tests ....................................... SUCCESS [15:20 min] [INFO] apps-jms2 .......................................... SUCCESS [ 1.498 s] [INFO] tests-eap7 ......................................... SUCCESS [ 7.706 s] [INFO] apps-jms11-jdk8 .................................... SUCCESS [ 0.062 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 15:55 min [INFO] Finished at: 2018-07-02T16:39:28+02:00 [INFO] Final Memory: 72M/1146M [INFO] ------------------------------------------------------------------------ Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 317.251 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 338.664 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 339.027 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 348.038 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 283.612 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 308.667 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 371.996 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 278.644 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 454.23 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 320.277 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 341.886 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 312.079 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 291.723 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 444.321 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,718.165 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1,001.854 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 955.398 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 928.888 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 913.361 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 910.408 sec - in org.jboss.qa.hornetq.test.cluster.ClusterTestCase {noformat} > [Artemis 2.x upgrade] Stuck messages in artemis.internal.sf.my-cluster... queue after restarting nodes in cluster > ----------------------------------------------------------------------------------------------------------------- > > Key: WFWIP-23 > URL: https://issues.jboss.org/browse/WFWIP-23 > Project: WildFly WIP > Issue Type: Bug > Components: Artemis > Reporter: Miroslav Novak > Assignee: Jiri Ondrusek > Priority: Blocker > Labels: activemq, feature-branch-blocker > Attachments: journal-node-2.txt > > > There are lost messages in scenario where nodes in cluster are cleanly stopped and started again. This issue was hit with Artemis 2.5.0.Final and WF Jeff's integration branch WFLY-9407_upgrade_artemis_2.4.0_with_prefix. > Test Scenario: > * start two servers in cluster (JGroups used for discovery) > * send messages to testQueue0 on node-1 and node-2 > * wait until consumers on both nodes receive 300 messages > * cleanly shut down 1st and then 2nd server > * leave servers shut down for one minute > * start both servers > * wait until both consumers receive 500 messages > * stop sending messages and receive all remaining messages > Pass Criteria: All send messages are received by consumer > Actual Result: There are lost messages. > Investigation: > There are lost messages which were sent to 2nd node. However they got stuck in queue {{.artemis.internal.sf.my-cluster.8a7e9e98-2c36-11e8-9737-fa163ea20b26}} during load balancing to 1st server. > I'm attaching trace logs from client and servers and content of journal from 2nd server. > This is regression against Artemis 1.5.5 thus setting blocker priority. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3951) Upgrade jboss-logmanager from 2.1.2.Final to 2.1.3.Final

by James Perkins (JIRA)

James Perkins created WFCORE-3951: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.2.Final to 2.1.3.Final Key: WFCORE-3951 URL: https://issues.jboss.org/browse/WFCORE-3951 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.2.Final to 2.1.3.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018