Skip to main content
  • EN

Recently upgraded our Dev environment to FME Flow 2024.1 (in situ)

Previously we were connecting to WebMethods using Software AG(Nirvana)

After installation, relevant .jar files have been added to the jms directory on the server

However, there is no connectivity.

The error received is

OM.safe.fmeserver.plugin.jms.JMSClientException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsps:REDACTED [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - 0]

This doesn’t appear to be hugely helpful as you get the exact same error if you use an incorrect provider URL. I can’t see anything in the logs that provides any additional information

All evidence points to the location being reachable (testnet connection in powershell from the server)

 

@steveatsafe - any ideas?

Just to update this, in case anyone stumbles across a similar problem.

 

We got this working eventually in both FME Form 2024.1 and FME Flow 2024.1

 

It required some newer JAR files sourced from a later version of Universal Messenger, and an additional jar file that wasn’t required for our 2021 FME Server installation (jakarta.jms-api-2.0.3) along with installation of certificates to the relevant cacerts file.

 

And to get workspaces using JMSReceivers/Senders working, the jar files had to also go in the plugins directory and a different cacerts file updated...

Reply


Community Stats

30,351
Posts
115,336
Replies
38,078
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.