Status: Closed (View Workflow)
Resolution: Migrated to another ITS
Affects Version/s: EWS 1.0.2
Fix Version/s: TBD EWS
Security Level: Public (Everyone can see)
Environment:Tomcat 6, Windows 2008 64x
Similar Issues:Show 6 results
JBEWS-52 EWS on Windows - Tomcat SSL doesn't work when started as a service JBEWS-308 EWS - tomcat6 with a SSL accelerator JBEWS-338 EWS on Windows: Tomcat5 service start command missing the path (has only "tomcat5.exe ..." JBEWS-312 EWS 2.0.0 ER9 postinstall script doesn't work as expected JBEWS-233 EWS on Windows: Reorganize directory structure. JBEWS-122 EWS on Windows: Create installation script
1) Install OpenSSL from http://www.openssl.org/related/binaries.html
Make sure to do this on a disposable Windows installation (virtualized)
2) Configure EWS's Tomcat 6 to use SSL, e.g.:
3) Start Tomcat. For simplicity, use startup.bat.
4) With this, Tomcat will show no error anywhere (Event log, console, or tomcat logs), only Tomcat console window flashes, then disappears.
After consultation with Mladen, we revealed that:
A) The error can be only seen if you run `catalina.bat run`, which will show you this:
B) It's caused by garbage DLL's in c:\windows\system32 - libeay32.dll, libssl32.dll, ssleay32.dll
For the record (and searchability), after removing libeay32, APR did not load at all and the error was:
This potential gotcha should be documented - users should be advised to check c:\windows\system32 for files overriding EWS's DLL's.
This is especially important because Tomcat doesn't log any error and the poor user is left in chaos.
Maybe EWS could also have a script for this - just something which would list potential troublemakers if present there.