This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

JMS Active MQ - Failed to validate account

Go to solution
avinashpatil
New Contributor

‎07-22-2021 10:42 PM

Hello Friends,
Need a help configuring JMS ActiveMQ account.
After trying multiple configuration settings still not able to validate account.
Please suggest solution. Find the attached configuration.
image

JMS_MQ
TCP connectivity test.
image

0 Kudos
1 ACCEPTED SOLUTION

Go to solution
mbowen
Employee
Employee
In response to avinashpatil

‎07-30-2021 03:34 PM

Ok. There are limitations with a trial account. A Groundplex isn’t available, which means to access your Active MQ instance, your machine needs to be accessible over the Internet!

A Groundplex is a plex that is customer-managed, and so you could install other software on it, such as Active MQ. The Groundplex can be an on-premise instance or cloud-based instance. Cloudplexes, by contrast, are cloud-based and managed by SnapLogic.

It sounds like your experimenting with Active MQ. Many of the cloud providers allow you to spin up this service. I think Amazon’s MQ wraps Apache Active MQ.

I don’t want this to tarnish your impression of SnapLogic, because we really do have a big offering. I didn’t realize you were on a trial account.

View solution in original post

0 Kudos
9 REPLIES 9

Go to solution
mbowen
Employee
Employee

‎07-23-2021 11:21 AM

It seems there is an issue with name resolution. I’m not familiar with the Test-NetConnection script. It looks like you’re on Windows. As an experiment, does it work if you replace the hostname in the provider url with the IP address ?

java.naming.provider.url = tcp://192.168.0.12:61616

Alternatively, you could define a mapping for this hostname in your Windows host file. Not sure what versions of Windows you are running; maybe in C:\Windows\System32\drivers\etc\hosts

192.168.0.12 PC1J57TA
0 Kudos

Go to solution
avinashpatil
New Contributor
In response to mbowen

‎07-26-2021 10:38 PM

Thanks for update, I have already tried with replacing machine name with IP address/localhost/127.0.0.1 but its throwing same exception. Yes, I am trying on Window 10.
As suggested, I have tried DNS mapping option but it did not work.

0 Kudos

Go to solution
mbowen
Employee
Employee
In response to avinashpatil

‎07-27-2021 12:44 PM

Bummer. Definitely something to do with name resolution. If broker was down, or or port invalid, you would get a ConnectionException. Similarly, a SocketException would be raised if bad ip.

I’m able to reproduce locally if I use an invalid hostname. A valid hostname successfully validates (Linux).

jms-active-mq-bogus-hostname

jms-active-mq-good-hostname

You may want to file a support ticket. We have a lot of in-house expertise with Windows, just I don’t.

0 Kudos

Go to solution
mbowen
Employee
Employee
In response to mbowen

‎07-27-2021 02:37 PM

Hi Avinash:

Another thing to note is the IP address in your tcp connection test is a private non-routable address. I’m not sure of your SnapLogic configuration, but the Snaplex needs to be able to talk to this Active MQ broker. So, maybe that’s the issue. It looks like you ran the test on the same machine which isn’t a snaplex.

0 Kudos