[
https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17342656#comment-17342656
]
Robbie Gemmell commented on QPID-8381:
--------------------------------------
Not really. The older BDB doesnt work on Azul's OpenJDK 11 specifically due to
a BDB bug (but does I believe work on other OpenJDK 11 variants), and whilst a
newer BDB fixed that it introduced another issue that would likely break people
upgrading existing broker installs on any JDK. A choice was made to avoid the
latter which seems reasonable, its a more severe issue potentially affecting
more people.
Essentially for now you can have Azuls OpenJDK with your own change, or a
'vanilla' install with another JDK.
> [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
> Fix For: Future
>
> 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]
