[
https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16978570#comment-16978570
]
Robbie Gemmell commented on QPID-8381:
--------------------------------------
https://community.oracle.com/thread/4040318 indicates the issue was fixed
'after 7.5'. It is noted in the 7.5.11 changes at
https://docs.oracle.com/cd/E17277_02/html/changelog.html as being fixed as of
7.5.3. I dont know if the newer release would work with 7.1.5 if you were to
override the version locally, but I was able to build master and run all the
tests with the java-bdb.1-0 test profile against 7.5.11 (not on Zulu, to be
clear).
> 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]
