[ https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16982372#comment-16982372 ]
ASF subversion and git services commented on QPID-8381: ------------------------------------------------------- Commit 5faf99120d2356ff4468db641c54d995c00bc8b0 in qpid-broker-j's branch refs/heads/master from Alex Rudyy [ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=5faf991 ] Revert "QPID-8381: [Broker-J] Upgrade Oracle BDB JE dependency to version 7.5.11" This reverts commit d5ae00b256914fb8af0ead9a2362f9476c59218c. > [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-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org