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 » JVM Port Debugging Issue

Post new topic  Reply to topic
 JVM Port Debugging Issue « View previous topic :: View next topic » 
Author Message
swaugh
PostPosted: Tue Dec 16, 2008 11:54 pm    Post subject: JVM Port Debugging Issue Reply with quote

Apprentice

Joined: 15 Jun 2006
Posts: 37

Hello,
I am having issues with the flow debugger using WMB toolkit version 6.1. We are currently running the WMB version of 6.0.2. Since i am using the 6.1 toolkit to access the version 6.0 broker, when i try to attach the flow debugger, its expecting a value of JVM port to be set. Further my message flow doesn't use any JCN node.

going thru the forum and documentation, i used the mqsichangeproperties command to set the jvm port to the Execution group and also recycled the broker, but still i am not able to see the JVM port value on my toolkit. I get an error message on the flow debugger perspective saying that Engine Id is empty.I have recyled the RAC too, but no luck. When i run the mqsireportproperties command , i am able to see the port that i set at the AIX level, but on my toolkit i am not able to see the JVM value as well as i am unable to attach the flow engine.

any help in this area is greatly appreciated.

Thanks,
Swaugh
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Dec 17, 2008 11:47 am    Post subject: Re: JVM Port Debugging Issue Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

swaugh wrote:
Hello,
I am having issues with the flow debugger using WMB toolkit version 6.1. We are currently running the WMB version of 6.0.2. Since i am using the 6.1 toolkit to access the version 6.0 broker, when i try to attach the flow debugger, its expecting a value of JVM port to be set. Further my message flow doesn't use any JCN node.

going thru the forum and documentation, i used the mqsichangeproperties command to set the jvm port to the Execution group and also recycled the broker, but still i am not able to see the JVM port value on my toolkit. I get an error message on the flow debugger perspective saying that Engine Id is empty.I have recyled the RAC too, but no luck. When i run the mqsireportproperties command , i am able to see the port that i set at the AIX level, but on my toolkit i am not able to see the JVM value as well as i am unable to attach the flow engine.

any help in this area is greatly appreciated.

Thanks,
Swaugh
you guessed it: To debug a 6.0 broker you need a 6.0 toolkit... have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » JVM Port Debugging Issue
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.