[
https://issues.apache.org/jira/browse/QPID-8381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16981761#comment-16981761
]
Alex Rudyy commented on QPID-8381:
----------------------------------
The BDB JE upgrade to version 7.5.11 caused the failure of upgrade test
{{BDBUpgradeTest#testBindingAndMessageDurability}}. It seems that environment
cannot start, when the number of store files drops to one. I never seen the
manifestation of the same issue when environment is created from scratch. The
BDB JE seems always keeping at least 2 files on the disk. Though, in order to
avoid any surprises in production environments, I think it would be better to
revert the changes from both master and branch and exclude this change from
version 7.1.6
I raise the issue on Oracle BDB JE forum
[https://community.oracle.com/message/15504459#15504459]. Though, that forum
is not very active.
> [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: qpid-java-broker-8.0.0, qpid-java-broker-7.1.6
>
> 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
