[
https://issues.apache.org/jira/browse/SOLR-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey updated SOLR-11645:
--------------------------------
Attachment: SOLR-11645.patch
Patch (without CHANGES.txt) that appears to fix the issue, after dealing with
browser caching.
Would appreciate a review from those who really know the UI code, and would
also like to know if we can avoid sorting the commandline arguments, so we can
show them in the order they actually appear on the commandline.
> When there are duplicate java commandline arguments, the Solr UI dashboard
> doesn't show Args at all
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-11645
> URL: https://issues.apache.org/jira/browse/SOLR-11645
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: 7.1
> Reporter: Shawn Heisey
> Priority: Minor
> Attachments: SOLR-11645.patch
>
>
> A user couldn't get the "Args" to display in the admin UI.
> Ultimately it was determined that they had duplicate arguments on their
> commandline, and this was resulting in an error in the browser:
> {code}
> Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use
> 'track by' expression to specify unique keys. Repeater: arg in
> commandLineArgs, Duplicate key: string:-XX:+UseGCLogFileRotation, Duplicate
> value: -XX:+UseGCLogFileRotation
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
