Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Labels:
      None

      Description

      Possibility for metadata in JMS API. Ex. retrieving Queue depth.
      Although providers will probably not be able to supply real-time accurate readings, it can be very handy to read out the current depth even if not 100% accurate.
      Currently the only way is to browse a queue and count messages (or use provider specific commands).
      Other suggestions are: max queue depth, max queue message size and so forth

      Management like moving data between objects or deleting messages in one time.
      The latter one has currently be accomplished by doing (destructive) reads which is of course not not performant.
      (alternatives are provider custom commands, which we would like to avoid for very basic management things like described)

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              koen.serneels
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: