Uploaded image for project: 'IronJacamar'
  1. IronJacamar
  2. JBJCA-17

JMS Message Inflow

    XMLWordPrintable

Details

    • Task
    • Resolution: Won't Do
    • Major
    • None
    • None
    • JMS
    • None

    Description

      Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672

      The JMS message inflow in the JMS resource adapter needs properly testing.
      There are basic tests, but the following are missing:

      1) Complete tests of edge cases for each configuration parameter in the activation spec
      2) Failure tests to confirm the implementation handles error gracefully
      3) Stress tests to make sure there the implementation is stable
      4) Performance tests to optimize the implementation

      Additionally, we need to confirm that it is possible to use this implementation for EJB2.0
      style deployments and hence as the default configuration.
      This should be possible provided the user has not created their own
      container configuration that uses the old JMSContainerInvoker explicitly.

      Attachments

        Issue Links

          blocks

          Task - Represents a small unit of work that is not end-user facing. JBAS-58 Complete testing of JMS Message Inflow

          • 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
          is blocked by

          Sub-task - The sub-task of the issue JBAS-2409 EJB3 JMS Integration

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBAS-2486 setupDLQConnection() uses incorrect class type for Util.lookup()

          • 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. JBAS-2487 Incorrect acknowledge mode returned by JmsActivationSpec

          • 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

              jpederse@redhat.com Jesper Pedersen
              adrian.brock Adrian Brock (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: