You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the com4j.jar file is located on an UNC path (for example: \host\share\foo\lib\com4j-20120426-2.jar), it will cause an ExceptionInInitializerError with root cause:
Caused by: java.lang.NullPointerException
at com4j.COM4J.loadNativeLibrary(COM4J.java:567)
at com4j.COM4J.(COM4J.java:522)
... 7 more
First the NPE is caused by using LOGGER before it's initialized (since both are part of the class's static init code and the LOGGER part is a the end) in the IOException catch block. The real root cause is a bug in the file path parsing code, causing the process that copies the DLL file to the filesystem to throw an IOException.
When the com4j.jar file is located on an UNC path (for example: \host\share\foo\lib\com4j-20120426-2.jar), it will cause an ExceptionInInitializerError with root cause:
Caused by: java.lang.NullPointerException
at com4j.COM4J.loadNativeLibrary(COM4J.java:567)
at com4j.COM4J.(COM4J.java:522)
... 7 more
First the NPE is caused by using LOGGER before it's initialized (since both are part of the class's static init code and the LOGGER part is a the end) in the IOException catch block. The real root cause is a bug in the file path parsing code, causing the process that copies the DLL file to the filesystem to throw an IOException.
Found that if the COM4J.class URL is:
The dllFile will be:
which is invalid. It should be:
The text was updated successfully, but these errors were encountered: