Problem

This page describes the solution to the following warnings that you may encounter when analyzing java source.

2020-04-24 12:14:07.003474 Warning MODULMSG ; Job execution JAVA151: unable to decompile class file "org\apache\spark\SparkConf.class" from archive "C:\WEBI\AipNode\data\deploy\maven-pkg\.m2\repository\org\apache\spark\spark-core_2.11\2.0.2\spark-core_2.11-2.0.2.jar" compiled from "SparkConf.scala"RDBMS


2020-04-24 12:14:07.003474 Warning MODULMSG ; Job execution JAVA124:Cannot resolve 'SparkConf' as type in package 'org.apache.spark' from package 'com.edelia.bc.elec.cost.targets.consumption.calculation' C:\WEBI\AipNode\data\deploy\main_sources\home-bc-elec-code\bc-elec\bc-elec\bc-elec-cost-target-consumption-calculation\src\main\java\com\bc\elec\cost\targets\consumption\calculation\BatchEntry.java


2020-04-24 12:14:07.050351 Warning MODULMSG ; Job execution JAVA151: unable to decompile class file "org\apache\spark\SparkContext.class" from archive "C:\WEBI\AipNode\data\deploy\maven-pkg\.m2\repository\org\apache\spark\spark-core_2.11\2.0.2\spark-core_2.11-2.0.2.jar" compiled from "SparkContext.scala"RDBMS


2020-04-24 12:14:07.050351 Warning MODULMSG ; Job execution JAVA124:Cannot resolve 'SparkContext' as type in package 'org.apache.spark' from package 'com.edelia.bc.elec.cost.targets.consumption.calculation' C:\WEBI\AipNode\data\deploy\main_sources\home-bc-elec-code\bc-elec\bc-elec\bc-elec-cost-target-consumption-calculation\src\main\java\com\bc\elec\cost\targets\consumption\calculation\BatchEntry.java

Observed in CAST Extension

Release

Yes/No

JEE 1.2.x(tick)
JEE 1.1.x(tick)
JEE 1.0.x(tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server(tick)
Microsoft SQL Server(tick)
CSS3(tick)
CSS2(tick)
Step by Step Scenario
  1. Package the Java source code.
  2. Deliver and accept the delivery.
  3. Run the analysis, validate the analysis log.
Impact on Analysis Results and Dashboard

The jar files may not be de-compiled in the LISA and hence the object resolution may not be proper which may lead to missing links. 

Action Plan
Based on the Warnings in the log file follow the below steps :
  1. Open the analysis log.
  2. Go to the warning and see which .jar file it is referring to and navigate to the .jar file.
  3. Check if the .jar file is corrupt or fine by unzipping the jar file using 7z.
    a. While unzipping the jar file, if you get the below error, the jar file is corrupt and the user has to get a good jar file:

    b. If the .jar file is corrupt check if the jar is an application-related jar or a third-party open-source jar. If it is a third-party open-source jar you can download the jar from the internet and run the analysis. If the jar is application related ask the user to get a good jar and then replace it and run the analysis.
  4. Check if the jar file is compiled by JDK 11. To check open the jar file with the 7z tools. Navigate to the META-INF folder and open MANIFEST.MF file and see if this JDK has been used. See the screenshot below:

    If the jar is built by JDK 11, then this issue has been fixed in JEE 1.2.12 funcrel. Run the analysis using this JEE version.
  5. If you are getting a warning message like below:

    unable to decompile class file "com\fasterxml\jackson\module\kotlin\KotlinModule.class" from archive "C:\WEBI\AipNode\data\deploy\CORE\mavenHttpPck\com\fasterxml\jack\module\jack-module-kotlin\2.11.2\jackson-module-kotlin-2.11.2.jar" compiled from "KotlinModule.kt" unable to decompile class file "com\fasterxml\jackson\module\kotlin\KotlinModule.class" from archive "C:\WEBI\AipNode\data\deploy\CORE\mavenHttpPck\com\fasterxml\jack\module\jack-module-kotlin\2.11.2\jackson-module-kotlin-2.11.2.jar" compiled from "KotlinModule.kt"

    The above warnings are coming for the compilation done by KOTLIN *.kt which is not yet supported by the JEE analyzer. Our decompiler does not support Kotlin or scala jars yet but supports Java jars.

  6. Sometimes when the size of the jar is huge and if the system does not have enough memory we get these warnings so, the solution is to add memory or run the analysis in the machine where we have a good memory
  7. If the jar file is unzipped without any error and upgrading to JEE 1.2.12 funcrel did not help then contact CAST Technical Support with the Relevant Input to reproduce the issue.

Relevant Input

  1. Sherlock (CAST Support Tool (CST) - alias Sherlock) : Export Cast Database (Management Base and Local Base only), Export logs, Export Configuration Files, Export source code
  2. Explanation about the problem and supporting screenshots
Impact of the Solution

No Impact on the analysis and the dashboard.