You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JMSToolBox throws an error when trying to view a queue and won't let me view any messages on the queue with that delivery mode.
Steps to Reproduce the Problem
Install/setup Tibco queues
Post a message to the queue with Delivery mode 22
Try to view message on that queue and get a java.lang.IllegalArgumentException due to JTBDeliveryMode being coded to throw that exception when any delivery mode other than 1 or 2 is used.
The text was updated successfully, but these errors were encountered:
cabellouarkbluecross
changed the title
JMSToolbox doesn't support TibcoEMS Delivery mode 22
JMSToolbox doesn't support Tibco Delivery mode 22
Aug 18, 2023
I understand the usecase
However, this delivery mode is a Tibco proprietary JMS extension and JMSToolBox is based on the standard JMS 2.x, capable to handle JMS messages in a generic way
The delivery mode could be added to JTB with the 2 standard modes but it will be seen and used by all other QM and obvisoulu cause exceptions
Maybe there is a way to make it to be only visible to Tibco sessions, but in that case, how to handle the errors when someone will try to copy messages (D&D, via templates, via export/import...) from a Tibco QM to another kind of QM?
I will have to think about it and evaluate where and how the DeliveryMode is used in JTB
Specifications
Expected Behavior
I should be able to post a message from my application with Delivery mode 22 and view it in JMSToolbox
AKA, JTBDeliveryMode should support delivery mode of 22 as per the [Tibco documentation] (https://docs.tibco.com/pub/api-exchange-gateway/2.2.0/doc/html/GUID-7547554A-3CF8-49D0-A8C7-62ACD63A09C6.html) :
Actual Behavior
JMSToolBox throws an error when trying to view a queue and won't let me view any messages on the queue with that delivery mode.
Steps to Reproduce the Problem
Logs
JTB_20235918_1108215_jmstoolbox.log
JTB_20235918_1108215_eclipse.log
The text was updated successfully, but these errors were encountered: