Informix - Problem description
Problem IT42749 | Status: Closed |
TRAILING BLANKS AFTER SSL.ENABLE=TRUE ARE NOT REMOVED, LEADING TO CRYPTIC ERROR MESSAGES, AS CONNECTION WILL NOT USE SSL | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
If there is an extra blank in the hqagent properties file after the setting for ssl.enable=true this will lead to a failure in setting up the connection to the server, as SSL is not enabled. the agent.log will show this: 2022-12-08 14:41:17 [main] INFO com.informix.hq.agent.MetricMonitorApplication - Starting InformixHQ Monitoring Agent, version 2.2.0 (build date: 2022-09-15T06:52:03-0500) 2022-12-08 14:41:17 [main] INFO com.informix.hq.agent.MetricMonitorApplication - InformixHQ Monitoring Agent configuration: {pool.connectionTimeout=5000, ssl.keystore.file=*keystore*, server.host=*hostname*, ssl.keystore.password=********, pool.idleTimeout=60000, server.port=p*portnumber*, pool.minimumIdle=0, ssl.keystore.type=PKCS12, pool.maximumPoolSize=3, target.ping.frequency=1, dataSource.IFX_ISOLATION_LEVEL=1, informixServer.id=4, ssl.enable=true } 2022-12-08 14:41:17 [main] INFO com.informix.hq.agent.MetricMonitorApplication - Agent running on AIX 2022-12-08 14:41:17 [main] INFO com.informix.hq.agent.MetricMonitorApplication - Starting Monitor 2022-12-08 14:41:17 [main] ERROR com.informix.hq.agent.WebSocketManager - Attempting to connect with InformixHQ Server at ws://*hostname*:*portnumber*/ws/4 2022-12-08 14:41:20 [WebSocketConnectReadThread-49] TRACE com.informix.hq.agent.WebSocketManager - Retrying in 2,000 ms 2022-12-08 14:41:20 [WebSocketConnectReadThread-49] ERROR com.informix.hq.agent.WebSocketManager - WebSocket Connection Exception A remote host refused an attempted connect operation. (Connection refused). Agent will retry to connect with InformixHQ Server for (informixServer.id = 4) in background. If still unsuccessful, next connection failure log will be printed after an hour Instead of the secure connection, an normal websocket connection (ws instead of wss) will be tried and fails. This can be identified as there is an extra blank before the closing bracket of the configuration, but that is not easy to spot. Instead of the secure connection, an normla websocket connection will be tried and fails. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of InformixHQ prior to 2.3.0. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to InformixHQ 2.3.0. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of InformixHQ prior to 2.3.0. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to InformixHQ 2.3.0. * **************************************************************** | |
Comment | |
Fixed in InformixHQ 2.3.0. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.12.2022 17.02.2023 17.02.2023 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |