Possible causes of the Throwable com.jniwrapper.n

[Kai Windmöller]

Hello *,

a customer of our product is running into trouble with the JNIWrapper during the start of our product on a Windows system.

The Stacktrace

java.lang.reflect.InvocationTargetException
   ... lines removed ...
Caused by: java.lang.ExceptionInInitializerError
   ... lines removed ...
Caused by: com.jniwrapper.n
    at com.jniwrapper.H.b(SourceFile:144)
    at com.jniwrapper.H.<init>(SourceFile:32)
    at com.jniwrapper.Parameter.<clinit>(SourceFile:22)

The customer tried jniwrapper version 3.3 and 3.8.4.

What can be the causes of the Throwable?


Any pointer to what the meaning and possible causes are, are appreciated.

Thanks
Kai

[Sergei Piletsky]

Hi,

One of the possible reasons could be a license validation issue. If my guess is correct, you can add -Dteamdev.license.info=true VM parameter to the startup parameters of your Java application, re-run the application and JNIWrapper should print out the detailed license diagnostic information to Java console.   

-

Sergei

--
You received this message because you are subscribed to the Google Groups "JNIWrapper Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jniwrapper-for...@teamdev.com.
To post to this group, send email to jniwrapp...@teamdev.com.
Visit this group at http://groups.google.com/a/teamdev.com/group/jniwrapper-forum/.
For more options, visit https://groups.google.com/a/teamdev.com/groups/opt_out.

[kai.win...@softproject.de]

Hi Sergei,

thanks for the hint. The cause is that the customer system is a 64bit system.

Whom do I have to contact to get a corrected license file?

Thanks,
Kai

PS.: I believe it would help if the Exception has a better name and a message indicating the cause of the problem.

[Sergei Piletsky]

Hi Kai,

If you need to run your Java application using 64-bit JVMs, then you may need to upgrade your existing JNIWrapper license (that currently supports 32-bit mode only) to 64-bit one. On the other hand, if your application should not be running in 64-bit mode (on 64-bit operating systems), you can still run it using a 32-bit JVM, and in this case the license update will not be required. You can contact our Sales team (sa...@teamdev.com) regarding the upgrade. 

Thanks for your suggestion about the exception name, we will correct it to be more informative.

-Sergei

--