[UIMA-5099] DUCC Service Manager (SM) pinger message not clear when incorrect JMX has been port specified

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Abandoned
• Fix Version/s: future-DUCC
• Component/s: DUCC
• Assignee: Jaroslaw Cwiklik
• Reporter: Lou DeGenaro
• Created: 01/Sep/16 18:08
• Updated: 12/Jan/23 15:25
• Resolved: 12/Jan/23 15:25

Description

Service was configured with:

service_ping_arguments broker-jmx-port=1100

After starting service, message in registry was:

=====
meta.service-statistics JMX Failure[Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: broker1; nested exception is: java.net.ConnectException: Connection refused]]] MetaNode[192.168.2.120] MetaPid[13647:76
=====

Problem was that port should have been 1099.

More clarity is desirable, such as: unable to connect to broker1 on port 1100.