[
https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-8381:
-----------------------------
Fix Version/s: (was: qpid-java-broker-7.1.6)
(was: qpid-java-broker-8.0.0)
Future
Rescheduling the corresponding upgrade for Future. The BDB JE version 7.5.11
has an issue with start-up when the number of store files drops to one. It
seems it is by design, but, I am not sure what conditions can cause store to
reduce to a single BDB JE file. The BDB JE Environment cannot be created after
that. The issue manifests on upgrade. Though, it can potentially manifest in
other conditions. Thus, reverting the changes...
> [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]
