ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ?????Help Please

Post new topic  Reply to topic
 ?????Help Please « View previous topic :: View next topic » 
Author Message
sam_mq
PostPosted: Mon Sep 09, 2002 11:53 am    Post subject: ?????Help Please Reply with quote

Novice

Joined: 22 Aug 2002
Posts: 24

hye kiran,
thanks for ur response... sorry, to ask you ... i'm new to MQ...
How to find what's my current JVMHeapSize? and what is the MaxHeapSize i can increase? why i'm unable to deploy my broker when i'm using debugger? what is ?(marked yellow) means in the operations view? i searched lot of documents they have given meaning only for red, green and yellow . once again thanks for ur patience...
Back to top
View user's profile Send private message
kirani
PostPosted: Mon Sep 09, 2002 5:05 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Sam,

Sorry for late reply!
There is no direct command, which will display MaxJVMHeapSize for Configuration Manager. I know how to check this value using regedit. Run regedit command from ConfigMgr server and go to following value.
HKEY_LOCAL_MACHINE->SOFTWARE->IBM->WebSphereMQIntegrator->2->ConfigMgr

I am not sure about the maximum size you can set here. Minimum is 64MB and the default value is 128MB.

When debugging a message flow, a debug copy of message flow is deployed to your broker. Are you facing this problem while debugging the message flow? Does your normal deploy go thru?

One of the reason you get ? status in operations panel for MessageFlow/Execution group is because of inconsistency between your view and repository.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
sam_mq
PostPosted: Tue Sep 10, 2002 7:30 am    Post subject: Reply with quote

Novice

Joined: 22 Aug 2002
Posts: 24

once again thanks kiran, you are right i'm facing problems while i start debugging my msg flow, it is not deploying. then i delete csection = depling in the DB. my normal deploy is working fine.

infact, i have created new DBs, config mgr and broker even then i'm unable to debug my msg flow. same problem...

please, let me know what else can i do to make by debugger work and how can i remove incosistency between my view and repositroy?

HKEY_LOCAL_MACHINE->SOFTWARE->IBM->WebSphereMQIntegrator->2->ConfigMgr in this folder i dont find any name where i can set the value only name i feel i can set is Default, but in LOCALBR(my local br) i can find ConfigurationDelayTimeout set 60 and ConfigurationTimeout 300. do i have to change ConfigurationDelayTimeout.... to say 192

Thanks
Sam
Back to top
View user's profile Send private message
maxis
PostPosted: Tue Sep 10, 2002 9:12 am    Post subject: Reply with quote

Centurion

Joined: 25 Jun 2002
Posts: 144

hi sam,
i took liberty to share my experience.

Many times we faced similar problem, we adopted trial & error method. And make sure no other memory consuming applications are running on cofig box.
Back to top
View user's profile Send private message
kirani
PostPosted: Tue Sep 10, 2002 9:42 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Hi sam,

Are you sure you are looking at registry on Configuration Manager server? If you don't see MaxJVMHeapSize key in the registry, you can create one by running mqsichangeconfigmgr -j command.

ConfigurationTimeout and ConfigurationDelayTimeout parameters are used by the Broker. You could use mqsichangebroker command to set these parameters. Try changing ConfigurationDelayTimeout property value to higher number (192 secs is fine).

As pvmk said, make sure you have minimal applications running on your WMQI server.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
sam_mq
PostPosted: Tue Sep 10, 2002 10:32 am    Post subject: Reply with quote

Novice

Joined: 22 Aug 2002
Posts: 24

thanks a lot guys!!! sam as u said i created MaxJVMHeapSize and now i'm able to debug... once again thanks for ur patience...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » ?????Help Please
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.