Connection: improve validation and more verbose error log

[assimbly]

Specifications

• JMSToolBox version: 5.6.0
• OS (Name, version, 32/64bits): Windows 10 64
• Q provider (kind, version) : ActiveMQ Artemis v2 (AMQ 7.2)

Actual Behavior

Currently I am trying to connect a ActiveMQ Artemis v2. This broker is running on a Red Hat Linux server and has SSL enabled. Both
AMQP and JMS are enabled. I am trying to reach the connection with SSL enabled. I may have something wrong in my connection settings, but this is very hard to tell based on the connectin error which says "Connect unsuccesful tried with all available server(s)"

Expected Behavior

Some questions I have

Can JMSToolbox reach the server with the given?

I assume yes:
a) Check the broker.xml (this is configured according the JMSToolbox wiki), port 61616
b) The broker is running (Camel running on the same server can send message to it and I can use the CLI and Hawt.io)
c) telenet to server with port 61616 is working

Question I have: Is the server reachable? Is the port OK? Is a jar file missing/correct? Is SSL required ? Is the truststorepath/password OK? Is user/password OK

As a feature request there could be more validation on the entered connection parameters and the error log could be more verbose. This would make connecting to a broker more dummy proof. It should be clear for the end user:

What are the steps taken in the background?
At which step does it go wrong?
What exactly is wrong?
How should I fix it?

An example when I put the SSL enable to true and the connect it does not say I need TrusthPath and TrustPassword as required. What if I forget a required field? What if the password is wrong?

Now it only gives the general message is: Connection failed and in the details as much as possible information. The stacktrace in the details would already be nice.

[assimbly]

JMSToolbox_Connections.zip

[assimbly]

Attached zip with logs and screenshots

[assimbly]

Unfortunately you are also dependent on the MQ provider. The general message of Artemis make it extra difficult. I'll check this article: https://developer.jboss.org/thread/267476. Maybe something with socket binding or NAT.

[eric-creekside]

I'm also searching for logs or more details when connecting, in my case to an ActiveMQ broker I know is running on my corporate VPN. Apps running locally can connect but JMSToolbox only gives me the generic and useless message

java.lang.Exception: Failed to connect to a 'master' ActiveMQ broker with the information set in the session definition

Where can I find more details about the underlying connection error so I can troubleshoot?

[titou10titou10]

What is displayed by JTB in the UI and in the logs is what is returned by the Artemis java client...
I do not know if there is a way to augment the logging on the client side
Maybe the logs on the server side could give a clue on what's going wrong