You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Jira)" <ji...@apache.org> on 2019/11/23 23:37:00 UTC
[jira] [Updated] (QPID-8381) [Broker-J] Cannot run Qpid Broker-J
with Azul Zulu JRE 11
[ https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Rudyy updated QPID-8381:
-----------------------------
Status: Reviewable (was: In Progress)
> [Broker-J] Cannot run Qpid Broker-J with Azul Zulu JRE 11
> ---------------------------------------------------------
>
> Key: QPID-8381
> URL: https://issues.apache.org/jira/browse/QPID-8381
> Project: Qpid
> Issue Type: Bug
> Environment: * Qpid Broker-J 7.1.5
> * Java Zulu Community 11.0.4+11 LTS
> * Windows 10
> Reporter: Geert Graat
> Assignee: Alex Rudyy
> Priority: Major
> Attachments: log.txt
>
>
> When running the Qpid Java broker with Zulu Community JRE, I get an error on startup when my configured virtual node is validated. The maximum amount of runtime memory needs to be computed, and specifically for the Zulu runtime the class {{com.azul.zing.management.ManagementFactory}} is needed, which is not part of the Zulu Community. It seems to be part of the (commercial) Zing JVM, which is also developed by Azul systems.
> The problem seems to be in the {{com.sleepycat.je.utilint.JVMSystemUtils}} class in the dependencies of Qpid, which checks the {{java.vendor}}, which is apparently the same for the Zulu Community and Zing.
> When using the Oracle JDK, this problem does not occur.
> Attached is the stacktrace in the log.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org