Currently we are having a doubt in our mind regarding using the OTMQ together with a JCA component. We are building in our architecture a component in order to call, by a java bean deployed inside a WL server, an OTMQ instance running in the same machine. This OTMQ instance is the OTMQ standalone platform (not Tuxedo + OTMQ) and we would use, on the Java side, a mix of JCA and, if necessary, JNI calls to make a connection between both these components.
My doubt here is, since WL will have many instances of this bean, is there any issues I should be aware regarding using multiple threads in this kind of component? I believe we shouldn't have any issues with that, since OTMQ work similar as the Tuxedo /Q, but I was just wondering if there's something we are missing here.
If you could just help me understand if I will have trouble with this architecture, I would be very grateful.
The JCA adapter is thread safe and if you find any threading problems related to the JCA adapter, please report them to Oracle Support. Regarding OTMQ, I believe those libraries are thread safe as you can build a multi-threaded OTMQ server, but we don't support using JNI to call any of our libraries. Why would you want to use JNI? You can simply use the JCA adapter to enqueue/dequeue messages.
Oracle Tuxedo Chief Architect