I did a bit more troubleshooting. I confirmed that the rdrand engine
loads natively on Mac High Sierra by running the below test program in
XCode. I believe the issue is one of the commons-crypto build, not
openssl itself. Hopefully, someone more familiar with the codebase
will pick this up and
I think it is best you direct your tomcat pool related questions and comments
about their documentation to the tomcat mailing lists. (On the other hand the
tomcat documentation on their own pool including a description why they don't
use dbcp 1.x looks rather comprehensive to me:
On 3/23/2018 5:19 PM, Phil Steitz wrote:
> That's the documentation for the alternative pool. Use this instead:
> https://tomcat.apache.org/tomcat-7.0-doc/jndi-datasource-examples-howto.html#Database_Connection_Pool_(DBCP)_Configurations
This does not really explain how to configure Tomcat. It
On 3/22/18 6:14 PM, Shawn Heisey wrote:
> First thing to do is thank you again for taking the time to help me.
> Apache has great communities.
>
> On 3/22/2018 5:38 PM, Phil Steitz wrote:
>> You must be looking at documentation describing how to use the
>> alternative pool mentioned above
Maybe I was misunderstood, each line ends with two newlines not just the
end of the file...
So there's a gap of one empty line between every two lines...
Thanks
GBa.
On Thu, Mar 22, 2018, 23:32 Gil Baruch wrote:
> I'm using the daemon to wrap my Jetty based service.
Yes, I can reproduce this error on the Mac running under:
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T14:49:05-05:00)
Maven home: /usr/local/Cellar/maven/3.5.3/libexec
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home:
Hello Alex,
I haven’t spent much time working with [crypto], but I recall seeing something
like this when building from a Mac. In fact, my error is upstream to yours:
--
[INFO] Executing tasks
make:
[exec]
Sending again, this time with a subject line.
I’m building Apache Commons Crypto from source on Mac OS HighSierra
(10.13.3) and the CryptoRandom tests fail, apparently because of
failure to load the underlying random number generation library. All
other tests pass. I successfully built and