Mantis - Resin
Viewing Issue Advanced Details
4159 minor always 08-04-10 02:08 08-04-10 11:53
hans  
alex  
normal  
closed 4.0.9  
fixed  
none    
none 4.0.10  
0004159: Windows - looks for 64-bit DLLs in resin\win32\
On Windows 2008 R2 64-bit + Resin 4.0.9 Pro

Everything seems fine until I add the license file.

Then I get:

[10-08-03 13:47:25.752] {main} Windows Server 2008 R2 6.1 amd64
[10-08-03 13:47:25.752] {main} Java(TM) SE Runtime Environment 1.6.0_21-b07,
Cp1252, da
[10-08-03 13:47:25.752] {main} Java HotSpot(TM) 64-Bit Server VM 17.0-b17,
64, mixed mode, Sun Microsystems Inc.
[10-08-03 13:47:25.752] {main}
[10-08-03 13:47:25.752] {main} user.name = Administrator
[10-08-03 13:47:25.799] {main}
[10-08-03 13:47:25.799] {main} server listening to 127.0.0.1:6800
[10-08-03 13:47:25.815] {main}
[10-08-03 13:47:25.986] {main} Found library 'resin' as
'D:\resin\win64\resin.dll', but the load failed. The JVM exception was:
java.lang.UnsatisfiedLinkError: D:\resin\win32\resin.dll: Can't load IA
32-bit .dll on a AMD 64-bit platform

+ later

[10-08-03 13:47:27.655] {main} JNI file: Found library 'resin' as
'D:\resin\win64\resin.dll', but the load failed. The JVM exception was:
java.lang.UnsatisfiedLinkError: D:\resin\win32\resin.dll: Can't load IA
32-bit .dll on a AMD 64-bit platform

[10-08-03 13:47:27.655] {main} JNI keepalive: Found library 'resin' as
'D:\resin\win64\resin.dll', but the load failed. The JVM exception was:
java.lang.UnsatisfiedLinkError: D:\resin\win32\resin.dll: Can't load IA
32-bit .dll on a AMD 64-bit platform

[10-08-03 13:47:27.655] {main} JNI socket: Found library 'resin_os' as
'D:\resin\win64\resin_os.dll', but the load failed. The JVM exception was:
java.lang.UnsatisfiedLinkError: D:\resin\win32\resin_os.dll: Can't load IA
32-bit .dll on a AMD 64-bit platform

I notice that the first reference is to D:\resin\win64\ the next to
D:\resin\win32\

Workaround: If you overwrite the DLLs in win32 with the DLLs in win64 it starts without the JNI-errors. I do get this one in the log during start:

[10-08-04 11:04:58.206] {main} JNI keepalive: disabled for unknown reasons

But that is perhaps a config issue on my part?

There are no notes attached to this issue.