Changing the Messaging Bus using CLI failed with ERROR "ERROR - TIBCO-AMX-CLI-000019: Error invoking action set on MessagingBus: TIBCO-AMX-ADMIN-020040: Failed the connection test to 'tcp://localhost:7223' in non-SSL mode."

Changing the Messaging Bus using CLI failed with ERROR "ERROR - TIBCO-AMX-CLI-000019: Error invoking action set on MessagingBus: TIBCO-AMX-ADMIN-020040: Failed the connection test to 'tcp://localhost:7223' in non-SSL mode."

book

Article ID: KB0071102

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Service Grid 3.3,3.4

Description

Changing the Messaging bus using the CLI ant script throws an ERROR that it failed to connect to the EMS Server.
This is because the default ant script environment_data.xml doesn't have the username and password property and therefore the CLI script failed to connect to the EMS server and the update of Messaging bus failed.

And the SystemNode will have the below ERROR :
===================================================
02 Jul 2021 15:17:10,535 [amxAdminDefaultHttpConnector_8] [ERROR] [] com.tibco.amx.admin.user.action.log - TIBCO-AMX-ADMIN-005399: User 'admin' failed to perform 'EnvService.setServiceVirtualizationConfigWithContext' in 4ms. Context [(TIBCO-AMX-ADMIN-020050: Environment id 'DevEnvironment (internal id: '3324')', Environment name 'DevEnvironment', emsserverurl  'null', connectionUsername 'false', isSslDebugTrace '{4}')].
02 Jul 2021 15:17:10,535 [amxAdminDefaultHttpConnector_8] [ERROR] [] com.tibco.amx.admin.server - TIBCO-AMX-ADMIN-004204: Error occured in Administrator... about to throw AxisFault for this exception
com.tibco.amf.admin.api.core.exception.AdminException
summary = TIBCO-AMX-ADMIN-020040: Failed the connection test to 'tcp://ompatil-t14:7223/admin' in non-SSL mode. 
faultDetail:  detail = 
  cause = com.tibco.amf.admin.api.core.exception.AdminException: TIBCO-AMX-ADMIN-020040: Failed the connection test to 'tcp://ompatil-t14:7223/admin' in non-SSL mode. 

===================================================

Issue/Introduction

Changing the Messaging Bus using CLI failed with ERROR "ERROR - TIBCO-AMX-CLI-000019: Error invoking action set on MessagingBus: TIBCO-AMX-ADMIN-020040: Failed the connection test to 'tcp://localhost:7223' in non-SSL mode."

Environment

All Supported OS Platforms

Resolution

After adding the username and password property in the Tag of MessagingBus we can overcome this ERROR and Messaging bus URL is updated successfully.

Below are the username and password property which is needed to be added in the MessagingBus Tag:

  • emsConnectionUsername="admin"
  •  emsConnectionPassword="" 

 

CLI Script Example:

=====================================================

<Environment xsi:type="amxdata:Environment" name="SystemEnvironment" description="environment for administrator" contact="TIBCO" autoDeployProductApps="true" noMessagingBus="false">

<Host name="Host" />

<MessagingBus emsServerURL="tcp://ompatil-t14:7222" emsConnectionUsername="admin" emsConnectionPassword="" outboundSessionPoolSize="24" connectionPoolSize="18" emsReconnectAttemptCount="600" emsReconnectAttemptDelay="600"/>

</Environment>

=====================================================

Log entry for

successful update:

======================================================
Jul 2021 15:19:04,800 [amxAdminDefaultHttpConnector_7] [DEBUG] [] com.tibco.amx.admin.user.action.log.internal - TIBCO-AMX-ADMIN-005393: User 'admin' is starting to perform 'test ems configuration ' with details 'DevEnvironment (internal id: '3324'),name:  ,id: 0 ,description:  ,outbound session pool size: 24 ,connection pool size: 12 ,ems connection identity:  ,ems reconnect attempt count: 600 ,ems reconnect attempt delay: 500 ,ems server URL: tcp://ompatil-t14:7223 ,ssl ems server URL:  ,use XA: false ,use SSL for Out: false ,ssl verify host: false ,ssl expected host name:  ,ssl vendor:  ,ssl trace: false ,ssl debug trace: false ,connection username: admin ,ssl client provider: '
02 Jul 2021 15:19:04,813 [amxAdminDefaultHttpConnector_7] [INFO ] [] com.tibco.tibems.qin - Trying to create notification (QIN) connection for member: 'EMSGMS.TestGroupConnection.TestGroupConnectionMember', attempt no.: 1 of 50. [Initial connect attempt delay is 500 milli secs.]
02 Jul 2021 15:19:04,813 [amxAdminDefaultHttpConnector_7] [INFO ] [] stdout - Trying to create notification (QIN) connection for member: 'EMSGMS.TestGroupConnection.TestGroupConnectionMember', attempt no.: 1 of 50. [Initial connect attempt delay is 500 milli secs.]
02 Jul 2021 15:19:04,827 [amxAdminDefaultHttpConnector_7] [INFO ] [] com.tibco.tibems.qin - Creating TibJmsConnectionFactory with clientId: EMSGMS.TestGroupConnection.PARTICIPANT.TestGroupConnectionMember and server URL : tcp://ompatil-t14:7223
02 Jul 2021 15:19:04,845 [amxAdminDefaultHttpConnector_7] [INFO ] [] com.tibco.tibems.qin - Got initial notification (QIN) connection for member: 'EMSGMS.TestGroupConnection.TestGroupConnectionMember', in 1 attempts.
02 Jul 2021 15:19:04,845 [amxAdminDefaultHttpConnector_7] [INFO ] [] stdout - Got initial notification (QIN) connection for member: 'EMSGMS.TestGroupConnection.TestGroupConnectionMember', in 1 attempts.
02 Jul 2021 15:19:04,854 [amxAdminDefaultHttpConnector_7] [INFO ] [] com.tibco.amx.admin.user.action.log - TIBCO-AMX-ADMIN-005395: User 'admin' successfully completed 'test ems configuration ' in 56ms. Context [(TIBCO-AMX-ADMIN-020050: Environment id 'DevEnvironment (internal id: '3324')', Environment name 'DevEnvironment', emsserverurl  'admin', connectionUsername 'false', isSslDebugTrace '{4}')].

=====================================================================

Additional Information

TAP-12928