You should not call it before FreeLibrary(). Try calling it after.
Best Regards,
Igor
On Tue, Jan 29, 2019 at 5:02 PM F.D. wrote:
> Hi Igor,
>
> thanks for your reply, I've added this code:
>
> Snippet
>
> void Ignition::DestroyJVM()
> {
>factoryLock.Enter();
>
>
Hi Igor,
thanks for your reply, I've added this code:
Snippet
void Ignition::DestroyJVM()
{
factoryLock.Enter();
JniErrorInfo jniErr;
SharedPointer ctx(JniContext::Create(0, 0,
JniHandlers(), ));
IgniteError err;
IgniteError::SetError(jniErr.code,
Hi,
Currently, Ignite on start creates JVM instance internally, but
it never stops it. Also, it currently can not work with already started
JVM.
So when you start Ignite the first time, it loads JVM, when you stop
and unload it, the JVM remains loaded in process memory. When
you start Ignite
Hi Igniters,
I'm trying to use Ignite in a dll (using c++) that is dinamically loaded. I
wrapped the method start/end/... bihind a "c" pure interface that I export.
It works quite well. I can call the LoadLibrary and start a Ignite node. I
can stop it and restart it again smoothly.
I've the
