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

HornetQ HTTP transport over netty-servlet does not work as expected

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: EAP_EWP 5.2.0
    • Fix Version/s: None
    • Component/s: HornetQ
    • Labels:
    • Environment:

      JBoss-EAP-5.2, HornetQ-2.2.24_10858 (HQ_2_2_24_EAP_JBPAPP_10858)

    • Steps to Reproduce:
      Hide
      • Install JBoss-EAP-5.2 with HornetQ and then apply JBPAPP-10858 patch
      • Configure the netty servlet, a connector, acceptor and a connection factory, which would use the configured netty-servlet
      • The netty-servlet configuration can be found in the attached reproducer/configs/messaging.war/WEB-INF/web.xml file
      • The HornetQ configuration used in the tests can be found at reproducer/configs/hornetq directory
      • Start the server
      • Start the consumer HTTPQueueConsumer.java
      • Run the message sender(HornetQueueSender.java) and send a single message
      • The HTTPQueueConsumer would consume this message and prints the time stamp
      • Wait for an 1.5 to 2 hours
      • Send another message to this destination
      • The consumer would not consume this message
      • The JMX console would confirm that there's an active consumer but it would not consume the messages

      PS :
      I have configured connection-ttl to -1 and the servlet session the same way but with the same result

      Show
      Install JBoss-EAP-5.2 with HornetQ and then apply JBPAPP-10858 patch Configure the netty servlet, a connector, acceptor and a connection factory, which would use the configured netty-servlet The netty-servlet configuration can be found in the attached reproducer/configs/messaging.war/WEB-INF/web.xml file The HornetQ configuration used in the tests can be found at reproducer/configs/hornetq directory Start the server Start the consumer HTTPQueueConsumer.java Run the message sender(HornetQueueSender.java) and send a single message The HTTPQueueConsumer would consume this message and prints the time stamp Wait for an 1.5 to 2 hours Send another message to this destination The consumer would not consume this message The JMX console would confirm that there's an active consumer but it would not consume the messages PS : I have configured connection-ttl to -1 and the servlet session the same way but with the same result
    • Docs QE Status:
      NEW

      Description

      Netty-servelet transport stalls JMS connections, leaving remote JMS clients in stale/limbo state if a client idles for a period of time.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                clebert.suconic Clebert Suconic
                Reporter:
                bershath27 Tyronne Wickramarathne
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: