I was having a similar issue on windows, and here's what helped me:

In case the problem is triggered by JNA's UnsatisfiedLinkError on a library, say, "kernel.32.dll" I suggest checking that the jnidispatch.dll that is being linked is the one from JNA, not from any other location in Path.

Debugging java.exe with a simple test case that loads the problematic library using JNA's Native.loadLibrary (say, kernel32.dll) in Visual Studio (I suggest checking all the exceptions) will show you which library was actually used.

That helped me, and I hope will helps this issue too.

In case it doesn't I would recommend checking jnidispatch.dll from JNA's jar (choose the appropriate .dll for you 32-bit or 64-bit platform) and check that there are no errors or missing libraries.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to