App TIBCOServers ignoring order because ConfiguredServiceArchive could not be loaded

App TIBCOServers ignoring order because ConfiguredServiceArchive could not be loaded

book

Article ID: KB0084062

calendar_today

Updated On:

Products Versions
TIBCO Administrator all
TIBCO Enterprise Message Service all

Description

Users may see many lines like the following in the Administrator.log:
<----in Administrator.log ---
2013 Dec 04 10:24:37:444 GMT -8 Debug [DeploymentConfiguration] AESDKJ-0000 [http-48530-Processor13]  App TIBCOServers ignoring order because ConfiguredServiceArchive could not be loaded. java.lang.IllegalArgumentException: Could not find an application archive associated with a deployment configuration for ApplicationConfiguration: TIBCO Servers
---->

Issue/Introduction

Administrator.log has entries such as "App TIBCOServers ignoring order because ConfiguredServiceArchive could not be loaded. ..."

Environment

OS: All

Resolution

These are normal debug messages which only appear when LogDebug is set to true domain's properties files (AdministrationDomain.properties and AuthorizationDomain.properties). Unlike BW and Adapter applications, TIBCOServers like EMS plugins do not have associated ConfiguredServiceArchive objects. 
It can be safely ignored.