Take a look on QueueControl::browse
It would be easy to patch it to look at the ScheduledDeliveries. I
could even guide you around it if you are interested.
On Tue, Oct 18, 2016 at 2:36 PM, abhijith wrote:
> I am assuming you are referring to JMSBrowser.
>
> We have locked down Queues and Top
I am assuming you are referring to JMSBrowser.
We have locked down Queues and Topics with authentication and authorization.
We would have to create a management role just for browsing which I am
trying to avoid. Also, this user would be super user who could essentially
read from everywhere.
Why don't you simply use Browser? why use Management for that?
On Tue, Oct 18, 2016 at 9:20 AM, abhijith wrote:
> Thanks, our requirement is not really performance intensive. It's only done
> on critical issues which needs immediate support.
>
> On another note, what is the best way to read mess
Thanks, our requirement is not really performance intensive. It's only done
on critical issues which needs immediate support.
On another note, what is the best way to read messages with body?
listMessages() operation does not retrieve body contents.
~Abhi
--
View this message in context:
The management method browse won't go through the list of Scheduled
References. but it would be an easy patch.
You must be careful though as such method will be competing for
resources with Queue deliveries. It's an anti-pattern as I see it.
(Unless you don't need any real performance out of the
