Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] java.lang.IllegalArgumentException: cannot add context to list #637

Closed
etgraylog opened this issue Mar 18, 2024 · 2 comments
Closed
Labels
bug Something isn't working

Comments

@etgraylog
Copy link

What is the bug?
The performance-analyzer-agent-cli generates the following exception during startup in OpenSearch 2.12.0:

user@ip-10-1-1-2:~$ sudo systemctl status --full --no-pager opensearch-performance-analyzer
● opensearch-performance-analyzer.service - OpenSearch Performance Analyzer
     Loaded: loaded (/lib/systemd/system/opensearch-performance-analyzer.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-03-13 20:54:46 UTC; 9min ago
   Main PID: 1735 (java)
      Tasks: 17 (limit: 9252)
     Memory: 80.3M
     CGroup: /system.slice/opensearch-performance-analyzer.service
             └─1735 /usr/share/opensearch/jdk/bin/java -Xshare:auto -Xms4m -Xmx64m -XX:+UseSerialGC -Dlog4j.configurationFile=/etc/opensearch/opensearch-performance-analyzer/log4j2.xml -Xms64M -Xmx64M -XX:+UseSerialGC -XX:CICompilerCount=1 -XX:-TieredCompilation -XX:InitialCodeCacheSize=4096 -XX:MaxRAM=400m -Dopensearch.path.home=/usr/share/opensearch -Dopensearch.path.conf=/etc/opensearch -Dopensearch.distribution.type=deb -cp /usr/share/opensearch/lib/*:/usr/share/opensearch/performance-analyzer-rca/lib/* org.opensearch.performanceanalyzer.PerformanceAnalyzerApp

Mar 13 20:54:46 ip-10-1-1-2 systemd[1]: Started OpenSearch Performance Analyzer.
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]: Exception in thread "main" java.lang.IllegalArgumentException: cannot add context to list
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at jdk.httpserver/sun.net.httpserver.ContextList.add(ContextList.java:37)
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at jdk.httpserver/sun.net.httpserver.ServerImpl.createContext(ServerImpl.java:276)
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at jdk.httpserver/sun.net.httpserver.HttpServerImpl.createContext(HttpServerImpl.java:74)
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at jdk.httpserver/sun.net.httpserver.HttpServerImpl.createContext(HttpServerImpl.java:39)
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at org.opensearch.performanceanalyzer.PerformanceAnalyzerApp.createClientServers(PerformanceAnalyzerApp.java:354)
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at org.opensearch.performanceanalyzer.PerformanceAnalyzerApp.createClientServers(PerformanceAnalyzerApp.java:319)
Mar 13 20:54:48 ip-10-1-1-2 performance-analyzer-agent-cli[1735]:         at org.opensearch.performanceanalyzer.PerformanceAnalyzerApp.main(PerformanceAnalyzerApp.java:112)
user@ip-10-1-1-2:~$

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Install OpenSearch 2.12.0 via DEB package on a Debian/Ubuntu host.
  2. Evaluate status of the opensearch-performance-analyzer.service.

What is the expected behavior?
The opensearch-performance-analyzer.service (opensearch-performance-analyzer-cli process) to start successfully without exception & ultimately respond to HTTP requests sent to its default socket-listener on port 9600.

What is your host/environment?

  • OS: Ubuntu 20.0.4.6 LTS
  • Version 2.12.0
  • Plugins
    • Nothing 'extra' was installed, only the plug-ins enabled by default with 2.12.0.

OS:

Do you have any screenshots?
N/A, see output from systemctl in Description.

Do you have any additional context?
This problem does not seem to exist in versions before 2.12.0 (ex: 2.11.1), as the opensearch-performance-analyzer.service functions as expected & is responsive to requests to its default socket-listener on Port 9600 in older versions.

@etgraylog etgraylog added bug Something isn't working untriaged labels Mar 18, 2024
@dblock dblock removed the untriaged label Jun 17, 2024
@dblock
Copy link
Member

dblock commented Jun 17, 2024

Catch All Triage - 1 2 3 4 5

@etgraylog
Copy link
Author

Closing this as a duplicate of opensearch-project/performance-analyzer-rca issue #545.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants