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 » The broker is not running

Post new topic  Reply to topic
 The broker is not running « View previous topic :: View next topic » 
Author Message
integrated
PostPosted: Fri Dec 18, 2009 2:12 am    Post subject: The broker is not running Reply with quote

Newbie

Joined: 15 Oct 2009
Posts: 6
We had broker and config manager running on aix box on 2 different q managers. Everything was working fine till today when tried to set debug port to 80 and change it back to 0 and disabled. After that when connected to config manager from toolkit, always alert is shown, "The broker is not running" and also all the flows underneath it not running.

Channels between config manager q manager and broker q manager are running fine. restarted both q managers as well as config manager and broker.

in aix everything shows running and see 4 process 2 for config manager and 2 for broker but when connected to config manager, still shows broker is not running and not able to deploy and perform any actions on broker.

appreciate help
Back to top
View user's profile Send private message
integrated
PostPosted: Fri Dec 18, 2009 2:57 am    Post subject: Reply with quote

Newbie

Joined: 15 Oct 2009
Posts: 6
getting below error

2009-12-18 10:06:22.006853 Execution group started. UUID is: '3aadfb39-2401-0000-0080-a3545619c978'. Broker is: EBRK1
ERROR: transport error 202: bind failed: The file access permissions do not allow the specified action. ["transport.c",L70]
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) ["debugInit.c",L547]
JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
Fatal error: JDWP No transports initialized, jvmtiError=JVMTI_ERROR_INTERNAL(113)

tried to change back port to other than 80 but not able to by below command

mqsichangeproperties EBRK1 -e default -o ComIbmJVMManager -n jvmDebugPort -v 7575

as broker might not be in running state

is there any other way of updating debug port number directly
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 » The broker is not running
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.