Hi @TomF ,
Thanks for your continued support. I used a timeout to try and connect to Solace VM on port 55555 from the Boomi Atom. It looks like that was successful.
BoomiAtom$ timeout 1 bash -c 'cat < /dev/null > /dev/tcp/SOLACEVM/55555'
$ echo $?
0
What’s happening here is that timeout will run the subcommand and kill it if it doesn’t exit within the specified timeout (1 second in the above example). In this case bash is the subcommand and uses its special /dev/tcp handling to try and open a connection to the server and port specified. If bash can open the connection within the timeout, cat will just close it immediately (since it’s reading from /dev/null) and exit with a status code of 0 which will propagate through bash and then timeout. If bash gets a connection failure prior to the specified timeout, then bash will exit with an exit code of 1 which timeout will also return. And if bash isn’t able to establish a connection and the specified timeout expires, then timeout will kill bash and exit with a status of 124.
Interestingly, Boomi Support has asked me upload JAR files in order to be able to use Solace connector; which I think is wrong. I do not intend to use the JMS connector and hence shouldn’t need the JAR files in question? “”)
https://help.boomi.com/bundle/connectors/page/int-JMS_connection_Solace.html