You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Tom Jordahl (Jira)" <ji...@apache.org> on 2021/05/11 14:59:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=17342619#comment-17342619 ]
Tom Jordahl commented on QPID-8381:
-----------------------------------
We are attempting to update to the Azul Java 11 OpenJDK and this is a showstopper for my team. See QPID-8524 .
We are stuck in a awkward place: we need to update to BDB 7.5.11 but would very much like to continue using the 'vanilla' Qpid distro tarball for easy updates in the future. Also, while we expect to never have to upgrade from an existing data store, it make me nervous to use a version of the library that the project doesn't use/test. I think in the short term we will probably update the jar file ourselves to work around this problem, but I am looking for a way out of doing that.
Any thoughts/advice here?
> [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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org