On Tue, Oct 18, 2016 at 12:45 PM, Quinn Stevenson
wrote:
> Clebert -
>
> Thank you for your input!
>
> I try and avoid XA transactions whenever possible as well. I do have a few
> customers that insist on transactions when they do JMS->JMS routes (the JMS
> destination are in different brokers/
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.
Clebert -
Thank you for your input!
I try and avoid XA transactions whenever possible as well. I do have a few
customers that insist on transactions when they do JMS->JMS routes (the JMS
destination are in different brokers/servers - hence the need for XA).
This is really the last piece I n
Most of the usecases around XA are around an application server, and
hence around MDBs, And JMS.
ClientSession extends XAResource so you should be able to use / enlist
on a Transaction Manager, or if you really wanted (I'm not advising
you) you could play the TransactionManager on some fakes (for
Is there an example of using the Artemis Core APIs with XA? It appears that
all of the XA examples use JMS. Am I missing something?
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:
