CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer on Documentation - V2

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Classpath entry cannot be resolved

Mon, 01 Jan 0001 00:00:00 +0000

Description

The page provides you with the information about the warning “classpath entry can not be resolved” and the procedure to counter the warnings.

Observed in CAST Extension

Release	Yes/No
JEE 1.1.x	(coche)
JEE 1.0.x	(coche)

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	(coche)
CSS2	✅
CSS1	❌

Step by Step Scenario

Discover the source.
Accept delivery and run the analysis.
Open logs and observe that you have following warnings in the logs.

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Extension jaxws has encountered an issue with get annotations

Mon, 01 Jan 0001 00:00:00 +0000

Purpose (problem description)

This page helps with the issue of the following warning during a JEE analysis with the jaxws extension:
- Extension com.castsoftware.jaxws has encountered an issue
  - Last line of the traceback is AttributeError: ‘Parenthesis’ object has no attribute ‘get_annotations’ or AttributeError: ‘CurlyBracket’ object has no attribute ‘get_annotations’
An example of the full traceback is below:
- 2019-12-19 15:19:59.435365 Warning MODULMSG ; Job execution Extension com.castsoftware.jaxws has encountered an issue :
  During on
  Traceback (most recent call last):
  File “C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\cast\analysers\internal\plugin.py”, line 123, in call_extensions2
  plugin._call_extension2(className, methodName, parameter)
  File “C:\Program Files\CAST\8.3\ThirdParty\Python34\lib\site-packages\cast\__init__.py”, line 95, in _call_extension2
  method(parameter)
  File “C:\ProgramData\CAST\CAST\Extensions\com.castsoftware.jaxws.1.0.10-funcrel\apache_cxf_analyser.py”, line 169, in start_type
  if self.is_endpoint(_type):
  File “C:\ProgramData\CAST\CAST\Extensions\com.castsoftware.jaxws.1.0.10-funcrel\apache_cxf_analyser.py”, line 305, in is_endpoint
  for annotation in ast.get_annotations():
  AttributeError: ‘Parenthesis’ object has no attribute ‘get_annotations’

CAST Extension Version

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Failed to analyze configuration file

Mon, 01 Jan 0001 00:00:00 +0000

Problem

This page describes the solution to the following warnings that you might encounter,when analyzing java source with hibernate framework.

Failed to analyze configuration file ‘C:\CASTMS\LTSA\LTSA\ccd746b326c643d19fa431c8487b3196/Scr14750\JavaTemp\Test.hbm-7-8.xml’\n Queries files ‘C:\Program Files\CAST\7.3\EnvProf\J2EE\Hibernate*cast-hibernate-config-3-2.xml*’ not found.
�Failed to analyze configuration file ‘C:\CASTMS\LTSA\LTSA\ccd746b326c643d19fa431c8487b3196/Scr14750\JavaTemp\Test1.hbm-9-10.xml’\n Queries files ‘C:\Program Files\CAST\7.3\EnvProf\J2EE\Hibernate*cast-hibernate-config-3-2.xml*’ not found.�

Observed in CAST Extension

Release	Yes/No
JEE 1.1.x	(coche)
JEE 1.0.x	(coche)

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	(coche)
CSS2	✅

Step by Step Scenario

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - File is not a valid java source

Mon, 01 Jan 0001 00:00:00 +0000

Problem

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

Information MODULMSG ; Job execution Starting processing of JEE analysis
Warning MODULMSG ; Job execution JAVA047: File is not a valid java source
Warning MODULMSG ; Job execution JAVA047: File is not a valid java source
Information MODULMSG ; Job execution JEE025: Processing application properties files …

Observed in CAST Extension

Release	Yes/No
JEE 1.1.x	(coche)
JEE 1.0.x	(coche)

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - FilePath has been selected for analysis but is not handled by any of the environment profiles you selected

Mon, 01 Jan 0001 00:00:00 +0000

Problem

When analyzing the java source you may find the warnings for the XML file inside the JARs.

Observed in CAST AIP

Release	Yes/No
8.3.x	(coche)
8.2.x	✅
8.1.x	✅
8.0.x	✅
7.3.x	✅
7.2.x	✅
7.0.x	❌

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	(coche)
CSS2	✅
CSS1	❌

Step by Step Scenario

Analyze java files
Open logs
See the warnings for the XML files inside the JARS

Solution

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - JAVA044 Syntax not recognized or JEE052 Syntax not recognized

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

This page describes how to deal with the warning JAVA044: Syntax not recognized or JAVA052: Syntax not recognized while performing a Java analysis.

2018-11-15 13:23:15.935923	Warning	MODULMSG ; Job execution	JAVA044: Syntax not recognized :

			finally {

				if (rs!=null) {

					rs.close;

-------------^

				}

				if (is!=null) {

					is.close;
S:\Sources\Analyzed\Some.java

For more information refer to JEE - Analysis messages

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - JAVA128 Annotations are not managed in Environment Profiles

Mon, 01 Jan 0001 00:00:00 +0000

Description

While running JEE analysis using JEE analyzer you may get warnings related toAnnotation ‘xx.xx.xx.xxx’ is not managed in Environment Profiles as shown below:

2018-11-08 06:56:49.758242	 Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.xml.bind.annotation.XmlType' is not managed in Environment Profiles		
2018-11-08 06:56:49.759243	 Warning	MODULMSG ; Job execution	JAVA128: Annotation 'com.google.common.annotations.TestWS' is not managed in Environment Profiles		
2018-11-08 06:56:49.760244	 Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.jws.soap.SOAPBinding' is not managed in Environment Profiles		
2018-11-08 06:56:49.760244	 Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.xml.bind.annotation.XmlRootElement' is not managed in Environment Profiles		
2018-11-08 06:56:49.760244	 Warning	MODULMSG ; Job execution	JAVA128: Annotation 'javax.xml.ws.BindingType' is not managed in Environment Profiles

Observed in CAST Extension

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Log the exception information Exception EXCEPTION ACCESS VIOLATION

Mon, 01 Jan 0001 00:00:00 +0000

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	✅
JEE 1.1.0	✅
JEE 1.0.x (x >=4)	✅
JEE 1.0.x (x < 4)	❌

Observed on RDBMS

RDBMS	Yes/No
CSS	✅

Step by Step scenario

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

Action Plan

To troubleshoot this issue, you need the Relevant Input

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

Mon, 01 Jan 0001 00:00:00 +0000

Purpose

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.

Analysis log file

Warning� MODULMSG ; Job execution� Log the exception information: Unknown Exception

Observed in

Release	Yes/No
JEE 1.2.x	✅
JEE 1.1.x	✅
JEE 1.0.x (x >=4)	✅
JEE 1.0.x (x < 4)	❌

Observed on RDBMS

RDBMS	Yes/No
Oracle Server	✅
Microsoft SQL Server	✅
CSS3	✅
CSS2	✅

Step by Step scenario

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Spring bean has an empty name in

Mon, 01 Jan 0001 00:00:00 +0000

Problem

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

Information MODULMSG ; Job execution JEE028: Analyzing configuration file ‘S:\Sources\Test_app\Analyzed\test\src\main\webapp\WEB-INF\applicationContext-ibatis.xml’ …
Information MODULMSG ; Job execution [com.castsoftware.struts] File S:\Sources\Test_app\Analyzed\test\src\main\webapp\WEB-INF\applicationContext-ibatis.xml received.
Information MODULMSG ; Job execution [com.castsoftware.labs.spring.integration] Scanning XML test file :
Information MODULMSG ; Job execution running extension SPRING3
Information MODULMSG ; Job execution Parsing Java file (phase 2) : [S:\ProgramData\CAST\CAST\Extensions\com.castsoftware.mqe.1.0.0-funcrel\jars\RabbitMQ_jars\spring-context-5.0.3.RELEASE.jar]\org\springframework\jndi\JndiObjectFactoryBean.class
Information MODULMSG ; Job execution Parsing Java file (phase 2) : [S:\ProgramData\CAST\CAST\Extensions\com.castsoftware.mqe.1.0.0-funcrel\jars\RabbitMQ_jars\spring-context-5.0.3.RELEASE.jar]\org\springframework\jndi\JndiObjectLocator.class
Information MODULMSG ; Job execution Parsing Java file (phase 2) : [S:\ProgramData\CAST\CAST\Extensions\com.castsoftware.mqe.1.0.0-funcrel\jars\RabbitMQ_jars\spring-context-5.0.3.RELEASE.jar]\org\springframework\jndi\JndiLocatorSupport.class
Information MODULMSG ; Job execution Parsing Java file (phase 1) : [S:\ProgramData\CAST\CAST\Extensions\com.castsoftware.mqe.1.0.0-funcrel\jars\RabbitMQ_jars\spring-context-5.0.3.RELEASE.jar]\org\springframework\jndi\JndiAccessor.class
Information MODULMSG ; Job execution Parsing Java file (phase 2) : [S:\ProgramData\CAST\CAST\Extensions\com.castsoftware.mqe.1.0.0-funcrel\jars\RabbitMQ_jars\spring-beans-5.0.4.RELEASE.jar]\org\springframework\beans\factory\BeanClassLoaderAware.class
Warning MODULMSG ; Job execution   JEE070: ** has an empty name in ’ ‘.**There are maybe other cases, like <%NAME2 %> will be ignored

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - The attribute maxlength for the tag textfield is not defined in the TLD - struts-tags tld

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

While analyzing a J2ee application, we may encounter this warning in the log regarding the ‘maxleangth’ not defined in the TLD.

Note:There is no impact on your analysis as long it is a new attribute which is not analyzed by cast.

Observed in CAST Extension

Release	Yes/No
JEE 1.1.x	(coche)
JEE 1.0.x	(coche)

Action Plan

This warning means that there is a difference between the TLD used for writing the application and the TLD CAST uses for the analysis.
Such warnings are encountered very often when you analyze with a CAST environment profile, an application written with a newer version of the framework.

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Unable to decompile class file

Mon, 01 Jan 0001 00:00:00 +0000

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

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Unable to find or to use archive

Mon, 01 Jan 0001 00:00:00 +0000

Problem

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

Warning MODULMSG ; Job execution JAVA142: unable to find or to use archive “S:\Sources\JAVA_CODE\maven-buildcentral\org\java_test\javatest-complete\1.4.0JTEST\jtest-complete-1.4.0JTEST.jar”. Archive ‘S:\Sources\JAVA_CODE\maven-buildcentral\org\java_test\javatest-complete\1.4.0JTEST\jtest-complete-1.4.0JTEST.jar’ is not in .ZIP format.

Observed in CAST Extension

Release	Yes/No
JEE 1.1.x	✅
JEE 1.0.x	✅

Observed on RDBMS

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - Unable to identify the mapped files of the application that are referenced in the hibernate config xml

Mon, 01 Jan 0001 00:00:00 +0000

Problem Description

This page explains about the following warning you may get while analysing hibernate xml file - hibernate-config.xml

“Unable to add ‘XXX/config/data/model/CategorieDataObj.hbm.xml’ (relative path) referenced in ‘XXX\WEB-INF\hibernate-config.xml’”

Observed in CAST Extension

Release	Yes/No
JEE 1.1.x	(coche)
JEE 1.0.x	(coche)

Impact on the Analysis

The warning have no impacts on the analyzes job or on function point computation.

Details

The warning message “Unable to add ‘XXX/config/data/model/CategorieDataObj.hbm.xml’ (relative path) referenced in ‘XXX\WEB-INF\hibernate-config.xml’” means that CAST is unable to identify the mapped files of the application that are referenced in the hibernate-config.xml (or hibernate.cfg.xml).

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - JAVA124: Cannot resolve 'XXX' as type

Mon, 01 Jan 0001 00:00:00 +0000

Description

While running the analysis you may get warnings related to unresolved objects in the analysis log file. It means that the analyzer is unable to resolve the objects, either because of an ambiguity, or because the object cannot be found.

The purpose of this page is to distinguish the different cases and offer an action plan to remedy them.

There are different variants of this message :

Analysis log file

CMS Snapshot Analysis - Run Analyzer - Warnings - JEE with extension - JEE Analyzer - JAVA068: Duplicate class declaration

Mon, 01 Jan 0001 00:00:00 +0000

Description

When you get warnings related to duplicate class declarations like below, then it means that the same class has been found more than once in the source files.

2018-10-22 04:06:10.897295    Information    MODULMSG ; Job execution    Parsing Java file (phase 1) : S:\Sources\MYAPP\Analyzed\my_package\WEB-INF\classes\com\mycompany\SomeClass.java  
2018-10-22 04:06:10.899248    Warning    MODULMSG ; Job execution    JAVA068: Duplicate class declaration : com.mycompany.SomeClass S:\Sources\MYAPP\Analyzed\my_package\WEB-INF\classes\com\mycompany\SomeClass.java

Observed in CAST Extension

Release	Yes/No
JEE 1.0.x	✅
JEE 1.1.x	✅
JEE 1.2.x	✅

Observed on RDBMS