Thread safety guarentees, or lack thereof, are usually part of the JavaDoc API documentation of such frameworks. At least that's how it should be.
For instance, if you browse the
API documentation for the IBM MQ classes for Java you'll find:
An MQQueueManager object (and any queues or processes accessed through it) can be shared between multiple threads, but be aware that access to the WebSphere MQ queue manager itself is synchronized, so that only one thread can communicate with it at any one time.
Similarly for JMS in
its API documentation:
A Session object is a single-threaded context for producing and consuming messages.
Build a man a fire, and he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life.