[
https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979041#comment-16979041
]
Geert Graat commented on QPID-8381:
-----------------------------------
I can verify that the issue is fixed in BDB JE release 7.5.11. I just ran Qpid
with this version instead of the included 7.4.5 with Zulu community edition and
the error no longer appears in the log. Also, {{JVMSystemUtils.java}} now
contains this comment:
{quote}final String vendor = System.getProperty("java.vendor");
final String vmName = System.getProperty("java.vm.name");
/*
* Check java.vm.name to distinguish Zing from Zulu, as recommended
* by Azul.
*/
ZING_JVM = vendor != null && vmName != null &&
vendor.equals("Azul Systems, Inc.") && vmName.contains("Zing");
{quote}
This is exactly where the problem was, so the issue that Robbie pointed out is
actually the issue that I ran into.
I also tried to run Qpid with an initial configuration that sets the message
store type to DERBY instead of the default BDB, and this also fixes the issue.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
