The above happened this morning on a live site (we had moved to 3.0.2 because of an issue with Jetty and certs in 3.0.0) but after restarting hasn't happened again. OTOH there has been very light load this afternoon, I mean in the range of 2-3 external users all afternoon. Right now it's being used as a demo tool by some salepeople and that's all - no paying customers yet.
So since it hasn't happened again, maybe it's a one-time fluke, but I'm very suspicious. It seems like something that could happen if one classloader in one thread loaded the DLL and then another one wanted to also. But maybe we haven't needed two simultaneous threads since the first crash.
In any event, I'd really like to be able to move the JNI jar back to default/lib if only it would be loaded from there.