Uploaded image for project: 'AMQ Clients'
  1. AMQ Clients
  2. ENTMQCL-418

[dotnet] Support intercepting rejection of sent messages

XMLWordPrintable

    • Release Notes
    • Hide
      It was found that in earlier releases of the product, the error indication status of rejected messages was not being passed between the broker and the client program. This could create a situation wherein a client was not aware that the broker had rejected a message and would subsequently take no action to recover from the error.

      In this release, the broker signals the error through AMQP mechanisms as expected and clients can take appropriate action to recover.
      Show
      It was found that in earlier releases of the product, the error indication status of rejected messages was not being passed between the broker and the client program. This could create a situation wherein a client was not aware that the broker had rejected a message and would subsequently take no action to recover from the error. In this release, the broker signals the error through AMQP mechanisms as expected and clients can take appropriate action to recover.
    • Documented as Resolved Issue

      User without "send" permition (nobody in this case) can send a message to the broker.

      Steps to reproduce:
      1. Configure the broker according to attached configuration.
      2. Create a queue (send a message under a user with permition to create a queue, f.e. admin): Interop.Spout.exe --broker amqp://admin:admin@<hostname>:5672 --address jms.queue.myQ
      3. Try to send a message under a user without sending permission (nobody):
      Interop.Spout.exe --broker amqp://nobody:nobody@<hostname>:5672 --address jms.queue.myQ

      Expected results:
      The message should not be delivered, SecurityException should be raised.

      Current results:
      The message is delivered into the queue on the broker.

      Note:
      This issue occurs also with qpid-cpp client.
      The broker behaves as expected with qpid-jms and openwire-jms clients (nobody user cannot send messages, the exception is raised).
      Nobody user cannot send messages, but the broker hangs with python-qpid client.

        3. entmqcl-374-sender.patch
          3 kB
          Petra Svobodova

              crolke@redhat.com Chuck Rolke (Inactive)
              psvobodo@redhat.com Petra Svobodova (Inactive)
              Chuck Rolke (Inactive)
              Petra Svobodova Petra Svobodova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: