|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
ConfigMgr :: Deployment Issue |
« View previous topic :: View next topic » |
Author |
Message
|
Devine1990 |
Posted: Fri Mar 13, 2015 6:42 am Post subject: ConfigMgr :: Deployment Issue |
|
|
Newbie
Joined: 20 Feb 2015 Posts: 4
|
Hi Guys ,
Getting below error , while deploying the message flows to EG , please can you help ??
( ConfigMgr ) The response received by the Configuration Manager on input queue ''SYSTEM.BROKER.ADMIN.REPLY'' could not be processed.
A message was received by the Configuration Manager on input queue ''SYSTEM.BROKER.ADMIN.REPLY'', but the message was not a response to an outstanding broker request. This message has arrived, in error, on queue ''SYSTEM.BROKER.ADMIN.REPLY''.
The message has been written to the WebSphere MQ dead letter queue. Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deployment operation was subsequently cancelled, then it can be ignored. If this is not the case, correct the the application.
 |
|
Back to top |
|
 |
mqjeff |
Posted: Fri Mar 13, 2015 6:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
|
Back to top |
|
 |
Devine1990 |
Posted: Fri Mar 13, 2015 6:56 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2015 Posts: 4
|
Thank you grand master for the quick reply . Is there any other temporary solution apart from raising PMR ??
 |
|
Back to top |
|
 |
Vitor |
Posted: Fri Mar 13, 2015 7:01 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Devine1990 wrote: |
Is there any other temporary solution apart from raising PMR ?? |
Devine1990 wrote: |
The message has been written to the WebSphere MQ dead letter queue. Look at the message on the dead letter queue to establish which application sent the message. If the message was a reply from a broker to which a deployment operation was subsequently cancelled, then it can be ignored. If this is not the case, correct the the application. |
You could try following the advice.... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
Devine1990 |
Posted: Mon Mar 16, 2015 6:54 am Post subject: |
|
|
Newbie
Joined: 20 Feb 2015 Posts: 4
|
Thanks a lot guys , issue is resolved now . It was the problem with barfile size. The bar file that we deployed was of 4 MB in size, we removed few unused resources from it and deployed (the bar file size reduced to 0.6 MB). It got deployed successfully.  |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|