Russell Bateman created NIFI-2993:
-------------------------------------
Summary: Issue clearer message when debug port conflicts
Key: NIFI-2993
URL: https://issues.apache.org/jira/browse/NIFI-2993
Project: Apache NiFi
Issue Type: Improvement
Components: Configuration
Affects Versions: 0.7.1, 1.0.0
Environment: Any hosting NiFi.
Reporter: Russell Bateman
Priority: Minor
When launching NiFi with remote debugging enabled in conf/bootstrap.conf, but
with a conflicting port, the messages given in logs/nifi-bootstrap.log aren't
as clear as they might be leading one to check and recheck the port setting in
conf/nifi.properties without realizing that remote debug is enabled and also
uses a port (and that it's this port that conflicts).
Sample message excerpt:
2016-11-04 11:32:35,747 ERROR [NiFi logging handler] org.apache.nifi.StdErr
ERROR: transport error 202: bind failed: Address already in use
2016-11-04 11:32:35,747 ERROR [NiFi logging handler] org.apache.nifi.StdErr
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
2016-11-04 11:32:35,747 ERROR [NiFi logging handler] org.apache.nifi.StdErr
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized
[debugInit.c:750]
2016-11-04 11:32:35,747 INFO [NiFi logging handler] org.apache.nifi.StdOut
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
2016-11-04 11:32:36,739 INFO [main] org.apache.nifi.bootstrap.RunNiFi NiFi
never started. Will not restart NiFi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
