You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alex Rudyy (Jira)" <ji...@apache.org> on 2019/11/20 16:13:00 UTC
[jira] [Comment Edited] (QPID-8381) 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=16978555#comment-16978555 ]
Alex Rudyy edited comment on QPID-8381 at 11/20/19 4:12 PM:
------------------------------------------------------------
Hi [~g.graat],
As you correctly stated out in JIRA description, the problem originates from Oracle Berkeley DB library class {{com.sleepycat.je.utilint.JVMSystemUtils}}. Thus, you need to raise this issue with Oracle who develops this library. For example, you can try to report the issue via BDB JE forum at [https://community.oracle.com/community/groundbreakers/database/berkeley_db_family/berkeley_db_java_edition].
By default, Qpid Broker is configured to use Berkeley DB based message store to store persistent messages and queue entries.
There are several alternatives to Berkeley DB based store you can use with Qpid broker. For example, you can start broker with Derby or JDBC stores.
When broker is started for a first time you need to override context variable "qpid.initial_config_virtualhost_config" to instruct the broker to use different type of message store. By default, it is set to "\{ \"type\" : \"BDB\" \}". You can change it to "\{ \"type\" : \"DERBY\" \}" to use embedded DERBY message store. For example, you can do it as follows
{noformat}
$ export QPID_OPTS="-Dqpid.initial_config_virtualhost_config={\"type\":\"DERBY\"}"
$ ./bin/qpid-server
{noformat}
If virtual host message store does not exist in broker work directory, the new one will be created on broker start-up.
You can also utilize JDBC message store. In order to do so, you need to provide JDBC URL and username/password in initial configuration. For example,
{noformat}
$ export QPID_OPTS="-Dqpid.initial_config_virtualhost_config={\"type\":\"JDBC\",\"connectionUrl\":\"jdbc:mysql://localhost:3306/mydb\", \"username\":\"foo\",\"password\":\"bar\"}"
$ ./bin/qpid-server
{noformat}
Please, do not forget to drop jdbc driver into broker lib folder.
Please note that you can override broker initial configuration and provide the virtual host initial settings directly in initial configuration. Please check qpid broker documentation at [https://qpid.apache.org/releases/qpid-broker-j-7.1.5/book/Java-Broker-Initial-Configuration-Create-Initial-Config.html] for more details.
was (Author: alex.rufous):
Hi [~g.graat],
As you correctly stated out in JIRA description, the problem originates from Oracle Berkeley DB library class {{com.sleepycat.je.utilint.JVMSystemUtils}}. Thus, you need to raise this issue with Oracle who develops this library. For example, you can try to report the issue via BDB JE forum at [https://community.oracle.com/community/groundbreakers/database/berkeley_db_family/berkeley_db_java_edition].
By default, Qpid Broker is configured to use Berkeley DB based message store to store persistent messages and queue entries.
There are several alternatives to Berkeley DB based store you can use with Qpid broker. For example, you can start broker with Derby or JDBC stores.
When broker is started for a first time you need to override context variable "qpid.initial_config_virtualhost_config" to instruct the broker to use different type of message store. By default, it is set to "{ \"type\" : \"BDB\" }". You can change it to "{ \"type\" : \"DERBY\" }" to use embedded DERBY message store. For example, you can do it as follows
{noformat}
$ export QPID_OPTS="-Dqpid.initial_config_virtualhost_config={\"type\":\"DERBY\"}"
$ ./bin/qpid-server
{noformat}
If virtual host message store does not exist in broker work directory, the new one will be created on broker start-up.
You can also utilize JDBC message store. In order to do so, you need to provide JDBC URL and username/password in initial configuration. For example,
{noformat}
$ export QPID_OPTS="-Dqpid.initial_config_virtualhost_config={\"type\":\"JDBC\",\"connectionUrl\":\"jdbc:mysql://localhost:3306/mydb\", \"username\":\"foo\",\"password\":\"bar\"}"
$ ./bin/qpid-server
{noformat}
Please, do not forget to drop jdbc driver into broker lib folder.
Please note that you can override broker initial configuration and provide the virtual host initial settings directly in initial configuration. Please check qpid broker documentation at [https://qpid.apache.org/releases/qpid-broker-j-7.1.5/book/Java-Broker-Initial-Configuration-Create-Initial-Config.html] for more details.
> 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
> Priority: Major
> 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