[
https://issues.apache.org/jira/browse/NIFI-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10017:
-------------------------------
Affects Version/s: 1.20.0
Status: Patch Available (was: In Progress)
> TLS-Toolkit standalone gives "Java heap space" error
> ----------------------------------------------------
>
> Key: NIFI-10017
> URL: https://issues.apache.org/jira/browse/NIFI-10017
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management, Tools and Build
> Affects Versions: 1.20.0, 1.16.1
> Environment: CentOS server, Java 11
> Reporter: Daniel Salwerowicz
> Assignee: Kevin Doran
> Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When I invoked tls-toolkit during installation of a new (1.16.1) NiFi
> instance on server I got following error from toolkit.
> {noformat}
> nifi-toolkit-1.16.1/bin/tls-toolkit.sh standalone \
> -C "..." \
> -K "..." \
> -S "..." \
> -P "..." \
> -f "/disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties" \
> -o ./certificate \
> -n "..." \
> -O
> [main] INFO
> org.apache.nifi.toolkit.tls.standalone.TlsToolkitStandaloneCommandLine -
> Using /disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties as template.
> Service standalone error: Java heap space{noformat}
> Upon reading the script I noticed a small problem on line 114 of the
> "tls-toolkit.sh" file:
> {noformat}
> exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m}
> org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"
> {noformat}
> If you look at the {{JAVA_OPTS}} it assigns only 12 and 24 Mb as min and max
> heap size available to the java process it executes. I think this causes the
> java process to run out of heap space, when I increased it to 128 and 256 Mb
> like in "encrypt-config.sh" then it worked alright.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
