Posted: Wed Mar 26, 2014 10:00 pm Post subject: deployment failed with Heap dumps
Voyager
Joined: 01 Dec 2010 Posts: 76
hi All,
i am trying to deploy 131 flows listening over MQInput and my bar file size is around 5.7 MB and when i try to deploy on 7 PROD servers it was successfully deployed on 6 servers but failed on 1 server with heap dumps and "OutOfMemory" errors. Then I splitted the bar file into 2 bars one 3 MB and another 2.6 MB , then it got deployed successfully. I have 2GB of heap memory allocated to my EG.
Also there is one more case where the EG is having 512 MB of memory and bar file size is 8 MB and no issues deploying the bar file, however it contains 40 msg flows and lot of message sets.
I want some help to know on what factors is the mqsideploy command works and how much memory it nees is dependent on what factors?
Posted: Thu Mar 27, 2014 4:23 am Post subject: Re: deployment failed with Heap dumps
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
dosttumhara1810 wrote:
I want some help to know on what factors is the mqsideploy command works and how much memory it nees is dependent on what factors?
It's all the usual stuff; the bigger the data the more memory you need. Think about what the deploy command is actually doing, what it needs to be parsing and how 131 flows would be represented within the bar file.
Then ask yourself why you'd want 131 flows in a single bar file anyway. What advantages does this give you, especially when you can (with apparent ease) split it up. What disadvantages (aside from memory consumption) could this method offer you? _________________ Honesty is the best policy.
Insanity is the best defence.
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