Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-5970

Plain JMS clients don't fallback

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • 9.0.2.Final, 10.0.0.Final
    • EE
    • None
    • Hide

      Steps to Reproduce:
      1. Configure a live-backup pair on the same machine with a shared store in standalone mode
      2. Please change the default cluster configuration to use netty connectors instead of the default UDP
      3. Start the live node then the backup node
      4. Start a plain JMS consumer and a producer
      5. Please configure the producer to send 20,000 messages at 1.5 second intervals
      6. Stop the live server using Ctrl + C
      7. The clients would fail over to the backup node (the new active node)
      8. Please wait about 20 seconds
      9. Start the live server.
      10. The live server becomes active and the backup node goes back to the passive mode
      11. The clients would not failback to the live node.
      12. The JMS clients remain in hung state indefinitely

      Show
      Steps to Reproduce: 1. Configure a live-backup pair on the same machine with a shared store in standalone mode 2. Please change the default cluster configuration to use netty connectors instead of the default UDP 3. Start the live node then the backup node 4. Start a plain JMS consumer and a producer 5. Please configure the producer to send 20,000 messages at 1.5 second intervals 6. Stop the live server using Ctrl + C 7. The clients would fail over to the backup node (the new active node) 8. Please wait about 20 seconds 9. Start the live server. 10. The live server becomes active and the backup node goes back to the passive mode 11. The clients would not failback to the live node. 12. The JMS clients remain in hung state indefinitely

    Description

      Plain JMS clients don't fallback when the Live server takes over

      Version-Release number of selected component
      messaging subsystem 1.4

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. WFLY-5394 Generic acceptor/connector is ignoring its socket-binding

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4477 Plain JMS clients don't fallback

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              gaohoward Howard Gao
              gaohoward Howard Gao
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: