CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Log the exception information Unknown Exception

This page will help you to troubleshoot, the below warning that you may encounter in the analysis log file, while running the analysis using the JEE Analyzer extension.

1. Package and deliver the J2EE application.
2. Set as current version.
3. Run the analysis.
4. Open the Analysis Log file and check for the warning.

The Parsing Step is interrupted by the exception (which formerly was a Fatal Error). The Saving Step will now take place since the exception is caught, but many objects may be missing and analysis results will be incomplete.

1. Make sure that this is the proper page for checking this situation.  Some of the information below may look similar to cases with other exceptions, but make sure that it says 'Unknown Exception' in the message warning.
2. Check if it is an Open JDK issue-

   JEE extension version less than 1.0.18 are not able to analyze the open JDK jars.

   In order to solve this, we need to remove from the analysis,  JDK jar files from the application source-code .

   There is no impact on analysis result because CAST provides the required JDK and the other related .class files in environment profile.

   This issue is resolved in JEE 1.0.18 extension

3. Check in the log if you have something like below:

   2020-06-26 12:53:26.503818    Information    MODULMSG ; Job execution    [CIL] setting project Source SOLDE : Librairie d'accès aux données HR Access_daf5e0b2    0 ; 0    0        0    [Module name]    0    0        
    2020-06-26 12:53:27.956936    Warning    MODULMSG ; Job execution    Log the exception information: 
   Unknown Exception...
   
   ------------------------------------------------------------------
   
   Function : RaiseException
   
       [Source File : UnkownFile]
       [Source Line : 0
   Function : CxxThrowException

   See the line above the warning "Source SOLDE : Librairie d'accès aux données HR Access_daf5e0b2"
   The solution would be to edit the pom.xml file for the project and remove the apostrophe. Then redeliver the source code and run the analysis.

4. This warning may be logged by the analyzer when it catches an exception which formerly led to a Fatal Error, but this exception now is unknown. For this reason, the Action Plan should be the same as in the generic Fatal Error page
5. If you are unable to find a solution to the issue then contact CAST Technical Support with the Relevant Input to reproduce the issue.

#17681- For open JDK issue