+46Currently doing some testing after upgrading FMEFlow to 2025.2.1
It appears that the validate button on the JMS trigger now just returns an ‘Invalid Parameter’ message
Previously it produced something slightly more descriptive.
i.e. Failed to find JMS object / Realm is currently not reachable
Is a more detailed message available in a log somewhere, if so where should i look?
I have it all set up and working correctly in 2025.2.1, this is just for future reference.
Best answer by merlinegeorge
Hello,
I checked with the dev team and can confirm this is a bug . I have filled a ticket for validation check to continue to return a more descriptive status message [FMEFLOW-27537].
+69do the jms logs in core/current/subscribers or core/current/publishers show anything?
+6Hello, As mentioned by
Could you please confirm the previous Flow version that has the more descriptive logging ?
+46Previous flow version was 2024.1
I've looked in the publisher/subscriber logs and couldn't see that there was anything there
+46When the automation is turned on these errors end up in \logs\core\current\publishers\*_jms.log
I’m specifically interested if anything ends up logged when you press the validate button when the automation is switched off.
+6Hello,
I checked with the dev team and can confirm this is a bug . I have filled a ticket for validation check to continue to return a more descriptive status message [FMEFLOW-27537].
