SAP Basis Tech Supports

Misleading log error messages “Cannot get aliases for …”

June 26, 2009 at 9:32 pm

[engine] [error log] [error log is full] [J2EE] [navigation] [NWA] [php error log] [var log messages] [webcontainer]

Misleading log error messages “Client certificate error.”Symptom In the default trace files the following error messages...
Hom./Het.System Copy SAP Web AS 6.40 SR1 JavaSymptom *********************************************************************** * Homogeneous and Heterogeneous System Copy * for...
FAQ XI 3.0/ PI 7.0/ PI 7.1/ PI 7.11/ PI 7.2 RFC AdapterSymptom FAQ XI 3.0 RFC Adapter, PI 7.0 RFC Adapter,...
SAP NetWeaver AS Java 6.40 SP24 – List of correctionsSymptom You want to know which changes have been done...
SAP NetWeaver AS Java 7.01 (EhP1) SP04- List of correctionsSymptom List of Corrections for SP04 of the NW701 (EhP1)...
SAP NetWeaver 7.01 SPS03: Release Information JSPMSymptom This SAP Note describes all changes and fixes for...
Incosistent Configuration after System CopySymptom During the Config Tool startup a Configuration Inconsistency warning...
Central Note for SAP NetWeaver Java Server 04/2004sSymptom This note lists some important and mostly used notes...

Symptom

In the default trace files the following error messages appear even when there is no real error observed:
Cannot get aliases for [] application.
The error is: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5005] Application is not deployed on cluster element get its aliases and it is not possible to {2}.
at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.getAliases(DeployCommunicatorImpl.java:513)
at com.sap.engine.services.servlets_jsp.server.DeployContext.getAliases(DeployContext.java:153)
at com.sap.engine.services.servlets_jsp.server.DeployContext.getAliasesCanonicalized(DeployContext.java:170)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.WebContainerExtensionContext.getMyWebModules(WebContainerExtensi onContext.java:152)
#

Other terms

j2ee engine, webcontainer, nwa navigation

Reason and Prerequisites

The above errors can be written to the default traces for example after signing in the NWA even though NWA behaves correctly. The reason for this is that NWA checks which applications are deployed in order to show them in the navigation and WebContainer logs this error message while performing the check.

Solution

In versions 710 SP7 and later, the log severity of this message is decreased to warning and is not written by default in the trace files.