[
https://issues.apache.org/jira/browse/NIFI-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14242109#comment-14242109
]
Joseph Witt commented on NIFI-145:
----------------------------------
The startup prints this:
...
Apache NiFi now running and listening for requests on port 59865
That should likely be updated to indicate that it is the boostrap process or
the nfi side of listening to such commands. It could easily be interpreted by
a user as-is that this is the port to send http requests to i think.
Also i see this:
Starting Apache NiFi...
....
Dnifi.bootstrap.listen.port=49950 -Dapp=NiFi org.apache.nifi.NiFi
Apache NiFi now running and listening for requests on port 59865
It perhaps should be clarified what the difference is betweeen boostrap
listening port and the request listening port on the nifi process side.
Last comment for now :-)
- We seem to have lost the arguments which addressed the java code cache
handling bug that kills performance at high sustained rates.
Thanks
Joe
> Develop Bootstrap module
> ------------------------
>
> Key: NIFI-145
> URL: https://issues.apache.org/jira/browse/NIFI-145
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
> Affects Versions: 0.0.1
> Reporter: Mark Payne
> Assignee: Mark Payne
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> We need a module that can parse a configuration file in order to determine
> runtime parameters to run the Java executable for NiFi.
> This should include JVM args, such as agentlib, Xmx, Xms, etc., as well as
> indicating where the NiFi properties file can be found and what the Java
> command should be (java vs. $JAVA_HOME/bin/java, etc.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
