SOI Manager is not starting after upgrade from 3.3 to 4.0 CU1

Document ID : KB000045690
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptom:

SOI Manager does not start up after upgrading from 3.3 to 4.0.

The soimgr-debug.log contains the following errors

2016-08-10 11:26:03,717 ERROR [http-bio-0.0.0.0-7090-exec-1] logging.DirectJDKLog.log(185) - Servlet.service() for servlet [jsp] in context with path [/sam] threw exception [Unable to compile class for JSP:
An error occurred at line: [1] in the generated java file: [D:\CA\SOI\tomcat\work\Catalina\localhost\sam\org\apache\jsp\debug\allpools_jsp.java]
The type java.util.Map$Entry cannot be resolved. It is indirectly referenced from required .class files

Environment:

SOI 4.0 CU1 + T6CP047 upgraded from SOI 3.3

Cause:

An obsolete ecj-3.7.2.jar file was present in the ..\tomcat\lib folder.

Resolution:

The SOI Manager started correctly after removing the ecj-3.7.2.jar file from the ..\tomcat\lib folder. This file is for use with the SOI 3.3 Apache Tomcat Version 6.0.36.

The ecj-4.4.2.jar is used with the SOI 4.0 Apache Tomcat Version 7.0.62