Toni Serbanescu Posted January 6, 2022 Share Posted January 6, 2022 Hello, I have seen multiple threads regarding the below error but 0 solutions. We are encountering it on the whole environment. We've tried to restart the appspace, EMS, TEA, appnodes multiple times but nothing worked. {"@timestamp":"2022-01-06T07:03:13.016Z","loglevel":"INFO","logger":"bw.audit","message":"application operation [create] with arguments { profileName=null appSpaceName=TOM1-AS profileFile=/tmp/deploy.tea3836464690804159779/default.substvar-1.2 domainName=OrchestrationDomain replace=true description=https://confluence.rbro.rbg.cc/display/MW/deal-classifier earFileName=deal-classifier_1.2.3.ear user=admin autoStart=true earFilePath= } failed with [WARNING: exception with message ***Error starting application [deal-classifier:1.2]*** has not been localized: TIBCO-BW-ADMIN-500417: Error encountered starting application on AppNode [TOM1-AS-N3]: com.tibco.bw.thor.management.client.ClientException: Not Found (404)WARNING: exception with message ***Error starting application [deal-classifier:1.2]*** has not been localized: TIBCO-BW-ADMIN-500417: Error encountered starting application on AppNode [TOM1-AS-N4]: com.tibco.bw.thor.management.client.ClientException: Not Found (404)WARNING: exception with message ***Error starting application [deal-classifier:1.2]*** has not been localized: TIBCO-BW-ADMIN-500417: Error encountered starting application on AppNode [TOM1-AS-N2]: com.tibco.bw.thor.management.client.ClientException: Not Found (404)WARNING: exception with message ***Error starting application [deal-classifier:1.2]*** has not been localized: TIBCO-BW-ADMIN-500417: Error encountered starting application on AppNode [TOM1-AS-N1]: com.tibco.bw.thor.management.client.ClientException: Not Found (404)]","operationID":"b366b414-2d41-4196-b066-a9fbe97c0166","correlationId":"5056ad5651-17e253fe280-6619"} We have TIBCO 6.7. Can someone suggest a solution to this issue Thank you very much! Link to comment Share on other sites More sharing options...
Emmanuel Marchiset 2 Posted January 10, 2022 Share Posted January 10, 2022 I would recommend to delete the content of the config directory of the appnode (TOM1-AS-N1) while this is a possible explanation to the issue. This can be automated using the following property in the config.ini file of the appnode : bw.appnode.clean.config.folder.on.startup=true If this doesn't solve the issue you would need to check the appnode log file to understand what is going on at this level. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now