[
https://issues.apache.org/jira/browse/AMQ-4961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864819#comment-13864819
]
Ulrich Romahn commented on AMQ-4961:
------------------------------------
Unfortunately, the leveldbjni-all does not contain the platform-specific
libraries (.so or .dll). The only option, which seems to work just fine, is to
copy the leveldbjn-1.8.jar over to the lib/optional of the 5.9.0 instance, then
remove the "old" leveldbjni-1.7.jar and finally copy the
leveldbjni-<platform>-1.8.jar.
I have a native leveldb v 1.7 installed and the v1.8 jni libraries seem to work
just fine with it - I ran some simple smoke-tests against it and things seem to
work just fine.
However, on a different note: the performance of the Java implementation seems
very close to the native implementation, at least in a non-high-concurrency
environment, and hence the potential gain may not warrant the increased
complexity of having an external native component.
I guess I should close this issue then since it is not really an issue anymore.
> leveldbjni platform jars not included in binary release
> -------------------------------------------------------
>
> Key: AMQ-4961
> URL: https://issues.apache.org/jira/browse/AMQ-4961
> Project: ActiveMQ
> Issue Type: Bug
> Components: activemq-leveldb-store
> Affects Versions: 5.9.0
> Environment: all
> Reporter: Ulrich Romahn
> Priority: Critical
>
> It appears that the binary release of ActiveMQ 5.9.0 is missing all the
> platform-specific leveldbjni files in lib/optional. Those files are all
> present in ActiveMQ 5.8.0 binary release.
> Reason: AMQ 5.9.0 depends on leveldbjni-1.7.0 which would then also require
> all the platform-specific jni jars of version 1.7.0. Unfortunately it appears
> that all public maven repos (specifically on repo1.maven.org) do not contain
> version 1.7 of those jars. The public maven repo contains version 1.5 and
> then 1.8.
> This is not specific an issue of ActiveMQ, but I still wanted the ActiveMQ
> team make aware of this issue.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
