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

Logstash error "Microsystems was unexpected at this time." #11729

Open
pankaj-k opened this issue Mar 30, 2020 · 2 comments · May be fixed by #15479
Open

Logstash error "Microsystems was unexpected at this time." #11729

pankaj-k opened this issue Mar 30, 2020 · 2 comments · May be fixed by #15479

Comments

@pankaj-k
Copy link

  • Version: 7.6.1
  • Operating System: Windows 10, ver 1709
  • Config File (if you have sensitive info, please remove it):
  • Sample Data:
  • Steps to Reproduce:
  1. Install java.
> java -version
Picked up JAVA_TOOL_OPTIONS: -Djava.vendor="Sun Microsystems Inc."
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10)
OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode)
  1. Extract the logstash zip.
  2. Open a command line window.
  3. Move to bin folder and run logstash.
  4. Error shown: Microsystems was unexpected at this time.

This issue is similar to 26261.

Workaround as of now to make it logstash start:
Comment out the block in setup.bat in bin folder.

rem do not let JAVA_TOOL_OPTIONS slip in (as the JVM does by default)
if not "%JAVA_TOOL_OPTIONS%" == "" (
  echo "warning: ignoring JAVA_TOOL_OPTIONS=$JAVA_TOOL_OPTIONS"
  set JAVA_TOOL_OPTIONS=
)

and add just set the env variable to empty. As below.

rem do not let JAVA_TOOL_OPTIONS slip in (as the JVM does by default)
rem if not "%JAVA_TOOL_OPTIONS%" == "" (
rem   echo "warning: ignoring JAVA_TOOL_OPTIONS=$JAVA_TOOL_OPTIONS"
rem   set JAVA_TOOL_OPTIONS=
rem )
set JAVA_TOOL_OPTIONS=
@deepankarmalhan
Copy link

Running into this same issue right now, the issue linked fixes it for elasticsearch but can I get confirmation that the fix is present in Logstash codebase as well?

@kares
Copy link
Contributor

kares commented Dec 30, 2021

the .bat scripts could use the same work-around as Elasticsearch did

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants