MQSeries.net :: View topic

venkataramanan · Posted: Fri Jan 17, 2003 5:46 pm Post subject:

HI all,

I face a strange problem with the config manager. I moved a msg flow ARIV from an EG EG_SL to the other newly created EG SL_FINAL. i forgot to deploy the EG EG_SL after removing the msg flow ARIV. immediately i moved the msg flow ARIV to the new EG SL_FINAL. i deployed the EG SL_FINAL.

The one mistake i did was i should have deployed my old EG EG_SL before moving the msg flow ARIV to the EG SL_FINAL but by mistake i deployed the new EG SL_FINAL.

But i get the following error when i do the deployment.

BIP1502S: Unexpected exception in Configuration Manager BrokerManager class processDeploy method; exception ext: 'java.lang.NullPointerException'.
An exception was caught by the Configuration Manager BrokerManager class processDeploy method. The exception text is: java.lang.NullPointerException. The current operation will end.
Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception and contact your IBM support center.

Now I deleted the EG SL_FINAL. Now i dont have the EG SL_FINAL and i removed all the flows from the EG EG_SL. when i deploy i get different error now

SQL0973N Not enough storage is available in the "APP_CTL_HEAP" heap to process the statement. SQLSTATE=57011 '.
While attempting a database operation on the configuration repository, a SQL exception was caught by the Configuration Manager. The database operation did not complete successfully. If this message was issued by the Configuration Manager, then it will continue if it is safe to do so. The exception text is: [IBM][CLI Driver][DB2/NT] SQL0973N Not enough storage is available in the "APP_CTL_HEAP" heap to process the statement. SQLSTATE=57011 .
For more information on this error refer to the relevant documentation for the database manager you are using for the configuration repository (for example, for DB2 refer to the DB2 SQL Reference manual).

I stopped and restarted the broker and i also did forced deployment. but nothing works. in the operation tab the broker still holds the handle towards that exception. I specifically deployed the broker. I dont see any change still the EG SL_FINAL is there and all the removed MSG flows are still there in the other EG EG_SL. In assignment TAB the changes are reflected but in the opertaions broker still holds the same config. Even I increased my DB2 database HEAP SIZE.

Hope iam not confusing infact iam confused

could anybody help me in soving out this problem.

with regards
venkat