uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lou DeGenaro (JIRA)" <...@uima.apache.org>
Subject [jira] [Created] (UIMA-5099) DUCC Service Manager (SM) pinger message not clear when incorrect JMX has been port specified
Date Thu, 01 Sep 2016 18:09:20 GMT
Lou DeGenaro created UIMA-5099:
----------------------------------

             Summary: DUCC Service Manager (SM) pinger message not clear when incorrect JMX
has been port specified
                 Key: UIMA-5099
                 URL: https://issues.apache.org/jira/browse/UIMA-5099
             Project: UIMA
          Issue Type: Bug
          Components: DUCC
            Reporter: Lou DeGenaro
            Assignee: Jerry Cwiklik
            Priority: Minor
             Fix For: future-DUCC


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message