Windows client unable to connect to MRG3 broker without authentication

Solution Verified - Updated -

Issue

When trying to connect to a MRG3 broker, the Windows clients presents a authentication error, even if if the broker is configured to not use authentication.

A sample error message:

[INIT_SUITE] core_middleware_connector Cannot connect, error: connection-forced: Not authenticated!
2015-05-25 09:56:05 [Client] warning Broker closed connection: 320, connection-forced: Not authenticated! Cannot connect, error: connection-forced: Not authenticated!

Environment

  • Red Hat Enterprise Linux 6 or 7
  • Red Hat MRG Messaging 3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content