| Author |
Message |
 Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
 Forum: IBM MQ Installation/Configuration Support Posted: Thu Jul 01, 2010 6:23 pm Subject: High Memory Usage After Migrating to v7.0 |
Finally its fixed,  after a long wait.
Here are the details below if someone is interested:
IBM have provided a ifix APAR IZ70032, when the kpiMQGETM function has been modified to free the ... |
| Topic: WMQ 7.0.1.2 upgrade from WMQ 6.0.2.8 |
nallabalu
Replies: 11
Views: 9072
|
Forum: IBM MQ Installation/Configuration Support Posted: Mon Jun 21, 2010 6:08 am Subject: WMQ 7.0.1.2 upgrade from WMQ 6.0.2.8 |
has anyone gone directly from 5.3 to 7.0 please?
Yes we did migrated from 5.3 to 7.0 with out any MQ issues(particularly with qmgr or channels), But we are currently experiencing memory leak [url=htt ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Fri Jun 18, 2010 7:40 am Subject: High Memory Usage After Migrating to v7.0 |
So, you/they went ahead with an upgrade without a plan, OR not following a plan to have the prerequisite
WMQ 7.0 :
Storage requirements for WebSphere MQ server
You require up to 600 MB to fully in ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Fri Jun 18, 2010 5:39 am Subject: High Memory Usage After Migrating to v7.0 |
| I think Yes, but not schedule at this moment as far i know. |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Thu Jun 17, 2010 5:42 pm Subject: High Memory Usage After Migrating to v7.0 |
| Yes, Most of the FDC's recorded mq was unable to obtain enough storage, and few of them recorded AMQ6118: An internal WebSphere MQ error has occurred ' i did a search on the probe ID but no hits foun ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Thu Jun 17, 2010 2:58 pm Subject: High Memory Usage After Migrating to v7.0 |
| Yes, i do agree with you vitor. Infact i even suggested it a long back about having few queue managers per server with lot of queues would be more effecient, than having more queue managers with only ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Thu Jun 17, 2010 1:42 pm Subject: High Memory Usage After Migrating to v7.0 |
stack limitation on Windows that you could not run more than 9 qmgrs simultaneously?
Is it something new in WMq 7.0, as this has been migrated, the same number of queue managers were running in mq 6. ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Thu Jun 17, 2010 1:03 pm Subject: High Memory Usage After Migrating to v7.0 |
Thanks for your responses.
What is the type of logging used at all 10 qmgrs?
Circular
is there any FDC reported?
Yes there are lot of FDC's
An old one, but one that may still be pertinent HERE ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Thu Jun 17, 2010 12:02 pm Subject: High Memory Usage After Migrating to v7.0 |
Thanks for your response.
Have you bounced the server and checked the results?
I Have bounced the server and the memory usage is the same(at high) after a period of time.
Which MQ process is i ... |
| Topic: High Memory Usage After Migrating to v7.0 |
nallabalu
Replies: 23
Views: 19415
|
Forum: IBM MQ Installation/Configuration Support Posted: Thu Jun 17, 2010 11:03 am Subject: High Memory Usage After Migrating to v7.0 |
Hi,
I have upgraded my Production queue managers from Wmq 6.0.2.8 and v5.3 to WMQ 7.0.1.1 2 days ago. Every thing migrated fine and saw all the queue managers started fine and processing messages( ... |
| Topic: Error Publishing msg to MQ After migration to V 7.0.1.1 |
nallabalu
Replies: 4
Views: 8533
|
Forum: IBM MQ Java / JMS Posted: Wed May 12, 2010 5:02 am Subject: Error Publishing msg to MQ After migration to V 7.0.1.1 |
| No application changes were made before or after MQ upgrade. Guess MQ should have went wrong, because the same application was working fine with v6.0 until the migration. This is the new error we noti ... |
| Topic: Error Publishing msg to MQ After migration to V 7.0.1.1 |
nallabalu
Replies: 4
Views: 8533
|
Forum: IBM MQ Java / JMS Posted: Tue May 11, 2010 8:32 am Subject: Error Publishing msg to MQ After migration to V 7.0.1.1 |
| We have noticed an application error, unable to create a session when connecting to Migrated MQ in our Test environment. The JMS pub/sub application connection is from Weblogic and current version of ... |
| Topic: Automatic re-creation of deleted subscriptions? |
nallabalu
Replies: 15
Views: 14510
|
Forum: General IBM MQ Support Posted: Fri May 07, 2010 6:06 am Subject: Automatic re-creation of deleted subscriptions? |
| I am sure, its your application recreating the durable subscriptions. Stop your app's connecting the Qmgr, delete the subscriptions and restart your Qmgr(don't start your App's). you will see no sub's ... |
| Topic: ms03 (SAVEQMGR) ok with MQ5.3? |
nallabalu
Replies: 10
Views: 6782
|
Forum: IBM MQ Installation/Configuration Support Posted: Wed May 05, 2010 5:00 am Subject: ms03 (SAVEQMGR) ok with MQ5.3? |
You have to save your OAM definitions seperately for a v5.3 Queue Manager. |
| Topic: How to integrate MQ Series with Tomcat application server |
nallabalu
Replies: 5
Views: 12263
|
Forum: IBM MQ Java / JMS Posted: Sun May 02, 2010 2:29 pm Subject: How to integrate MQ Series with Tomcat application server |
| Ask the MQSeries Administrator to provide the userid in the MCAUSER on the queue manager to which your application is connecting, through the server-conn channel. I am not sure if this works..but seem ... |
