Getting error "332:Internal error: Subscription context is null" on using AppManage to deploy or undeploy

Getting error "332:Internal error: Subscription context is null" on using AppManage to deploy or undeploy

book

Article ID: KB0091875

calendar_today

Updated On:

Products Versions
TIBCO Administrator -
Not Applicable -

Description

Resolution:
Problem description:
When deploying/undeploying applications via AppManage, following error occurs:
ERROR 2008/01/19 18:45:50.499 332: Internal error: Subscription context is null..

It happens randomly, and is usually associated with delay(10+ minutes). Also, most of these cases are reported on multi-CPU machines.

Solution:
Please note a known issue in the previous versions of TRA.
=========
1-6Z04Z0 Appmanage -deploy and -undeploy would take an excessive amount of time to complete.
A new "-serialize" option has been added to AppManage that allows you to explicitly choose to serialize deployment.
=========

If using TRA 5.5.x and above, add -serialize to the Appmanage command.  

For example:
AppManage -deploy -ear d:\deploy\temp\test.ear -deployconfig
d:\deploy\temp\test_config.xml -app TEST/test -domain test -user
admin -pw admin -nostart -serialize

When -serialize is specified, deploy/undeploy of the service instances is performed serially instead of using multiple threads.

Issue/Introduction

Getting error "332:Internal error: Subscription context is null" on using AppManage to deploy or undeploy