Purpose

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

Analysis log file
Warning�    MODULMSG ; Job execution�    Log the exception information: 
EXCEPTION_ACCESS_VIOLATION...
Observed in

Release

Yes/No

JEE 1.2.0 (tick)
JEE 1.1.0 (tick)
JEE 1.0.x (x >=4)(tick)
JEE 1.0.x (x < 4)(error)
Observed on RDBMS
RDBMS
Yes/No
CSS(tick) 

Step by Step scenario

  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.

Action Plan

To troubleshoot this issue, you need the Relevant Input

This warning is logged by the analyzer when it catches the exception formerly leading to Fatal Error : Unable to process JEE analysis.

For this reason, the Action Plan is:

  • If you are using JEE extension < 1.0.26, this then is exactly the same as in the Fatal Error page
  • If you are using JEE extension > = 1.0.26, then the functionality for this has changed and now the exception is handled and the analysis proceeds to the previously unanalyzed files.  This normally is a minor issue where the few files that have this exception are not analyzed.  For improvement of the analyzer, please provide the source files to support that are causing these warnings.  The source files are required for proper identification and resolution of this issue.
Notes/comments


Related Pages