For anyone running AwareIM as a windows service with Java 64bit you may receive the following error in the Tomcat log:
STATUS | wrapper | 2012/03/08 16:44:44 | --> Wrapper Started as Service
STATUS | wrapper | 2012/03/08 16:44:44 | Launching a JVM...
INFO | jvm 1 | 2012/03/08 16:44:44 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org
INFO | jvm 1 | 2012/03/08 16:44:44 |
INFO | jvm 1 | 2012/03/08 16:44:44 |
INFO | jvm 1 | 2012/03/08 16:44:44 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO | jvm 1 | 2012/03/08 16:44:44 | The file is located on the path at the following location but
INFO | jvm 1 | 2012/03/08 16:44:44 | could not be loaded:
INFO | jvm 1 | 2012/03/08 16:44:44 | C:\AwareIM\bin..\Tomcat\lib\wrapper.dll
INFO | jvm 1 | 2012/03/08 16:44:44 | Please verify that the file is readable by the current user
INFO | jvm 1 | 2012/03/08 16:44:44 | and that the file has not been corrupted in any way.
INFO | jvm 1 | 2012/03/08 16:44:44 | One common cause of this problem is running a 32-bit version
INFO | jvm 1 | 2012/03/08 16:44:44 | of the Wrapper with a 64-bit version of Java, or vica versa.
INFO | jvm 1 | 2012/03/08 16:44:44 | This is a 64-bit JVM.
INFO | jvm 1 | 2012/03/08 16:44:44 | System signals will not be handled correctly.
I found an update for a 64bit version of the tanukisoftware wrapper here:
http://www.krenger.ch/blog/java-service-wrapper-3-5-7-for-windows-x64/
as the current version http://wrapper.tanukisoftware.com/doc/english/download.jsp#stable is not currently being made available in the Community Edition.
To implement the new wrapper I renamed the following:
C:\AwareIM\Tomcat\lib\wrapper.dll to wrapper32.dll
C:\AwareIM\Tomcat\lib\wrapper.jar to wrapper32.jar
C:\AwareIM\bin\wrapper.exe to wrapper32.exe
And copied the files (wrapper.dll, wrapper.jar, wrapper.exe) from the zip to the above locations.
I also had to create a logs directory under AwareIM as it was giving an error in the logs, it creates another wrapper.log file now in C:\AwareIM\logs, I think this is due to the location in the .conf files.
Everything is working fine now with Java 64bit.
Regards
Chris