Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8153

Upgrade HornetQ for EAP 5.2.0

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • EAP_EWP 5.2.0 ER5
    • EAP_EWP 5.1.2
    • HornetQ
    • None
    • Not Required
    • NEW

    Description

      • HornetQ 2.2.16

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-7218 Track component upgrades - EAP 5.2.0

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          clones

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-9739 Upgrade HornetQ for EAP 5.2.1

          • 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.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. JBPAPP-9875 CLONE - Upgrade HornetQ for EAP 5.2.0 (HornetQ 2.2.20.EAP.GA.build2)

          • 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
          incorporates

          Sub-task - The sub-task of the issue JBPAPP-8377 Duplicate Resource Recovery entries may fire JBTM-842

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-8769 Sending Extreme Large Messages may lock the queue while transmission or copy is done causing timeouts on clients

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-9603 Non Durable Subscription is leaking on paging if not properly closed

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10387 CLONE - Duplicate message detection causes message loss in cluster

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBPAPP-10388 CLONE - Messages are hidden after restart when ACKs are done out of order on paging

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          1.
          		 CLONE - createQueue not idempotent Sub-task Closed Major Justin Bertram
          2.
          		 HornetQ page files not deleted on rollback Sub-task Closed Major Justin Bertram
          3.
          		 Rollback for crashed client not updating delivery count properly Sub-task Closed Major Justin Bertram
          4.
          		 Duplicate Resource Recovery entries may fire JBTM-842 Sub-task Closed Major Clebert Suconic
          5.
          		 Message lost when using message selector Sub-task Closed Major Justin Bertram
          6.
          		 NullPointerException in ClusterManagerImpl.destroyBridge Sub-task Closed Major Justin Bertram
          7.
          		 Re-implement XML export/import tool Sub-task Closed Major Justin Bertram
          8.
          		 HornetQ deletes JNDI bindings during a server restart Sub-task Closed Major Clebert Suconic
          9.
          		 When one ManagedConnection is destroyed the pool's ServerLocator gets destroyed as well Sub-task Closed Major Justin Bertram
          10.
          		 Discovery group binds to 0.0.0.0 on all OSs even though local-bind-address is set Sub-task Closed Major Justin Bertram
          11.
          		 IllegalStateException: Cannot access JMS Server, core server is not yet active during shutting down of backup server Sub-task Closed Major Justin Bertram
          12.
          		 CLONE - HornetQ cluster with collocated backup serve cannot be shutdown gracefully Sub-task Closed Major Justin Bertram
          13.
          		 possible deadlock in resource adapter Sub-task Closed Minor Andy Taylor
          14.
          		 CLONE - Paging won't expire messages unless there's an active consumer Sub-task Closed Minor Clebert Suconic
          15.
          		 Singleton MDB won't failover as expected on a HornetQ cluster Sub-task Closed Major Clebert Suconic
          16.
          		 applying JBPAPP-7655 correctly Sub-task Closed Minor Clebert Suconic
          17.
          		 CLONE : HornetQ leaks socket connections over long period of time eventually leading - to java.net.SocketException: Too many open files - exception Sub-task Closed Major Clebert Suconic
          18.
          		 back port AS7-4548/HORNETQ-913 Sub-task Closed Major Clebert Suconic
          19.
          		 CLONE - Repetitive logging from BroadcastGroupImpl broadcastConnectors Sub-task Closed Major Justin Bertram
          20.
          		 CLONE - cannot getObject when sending java.lang.reflect.Proxy object Sub-task Closed Major Justin Bertram
          21.
          		 CLONE - JMX Topic Attributes Not Available in Cluster Sub-task Closed Major Justin Bertram
          22.
          		 When binding AS7 to 0.0.0.0 remote HornetQ clients fail Sub-task Closed Major Justin Bertram
          23.
          		 CLONE - Fix NPE in journal importer Sub-task Closed Major Justin Bertram
          24.
          		 CLONE - Message body is null when imported from XML Sub-task Closed Major Justin Bertram

          Activity

            People

              permaine Permaine Cheung
              rhn-support-jbertram Justin Bertram
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: