| Author | 
		  Message
		 | 
		
		  | mca | 
		  
		    
			  
				 Posted: Thu Jul 12, 2007 12:57 pm    Post subject: Listener for WBRK6_DEFAULT_QUEUE_MANAGER on port 2414 failed | 
				     | 
			   
			 
		   | 
		
		
		   Disciple
 
 Joined: 09 Mar 2005 Posts: 196
  
  | 
		  
		    
			  
				When i am trying to create the default Config Manager and Broker on my Windows system, its failing because of this error. This is the first QM that i created and i made sure this port is not being used. 
 
 
Task: Creating a listener for queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] on port 2414. failed
 
If you can manually fix the issues that caused this task to fail, do so and then click Yes.
 
If you click Yes, the wizard starts the task again.
 
 
Log File:
 
 
Creating a listener for queue manager [WBRK6_DEFAULT_QUEUE_MANAGER] on port 2414.
 
Status ERROR: com.ibm.etools.mft.eou code=0 Could not create the listener.
 
 
Collected output from task > Stdout: Listener creation no longer supported
 
 
Active Connections
 
 
  Proto  Local Address          Foreign Address        State
 
  TCP    s056816:epmap          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:microsoft-ds   s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:523            s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:6789           s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:9495           s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:10002          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:10005          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:23781          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:26214          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:26470          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:db2c_DB2       s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:57961          s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:DB2_DB2_1      s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:1051           s056816.ho.nmfco.com:0  LISTENING
 
  TCP    s056816:1252           localhost:26470        ESTABLISHED
 
  TCP    s056816:26470          localhost:1252         ESTABLISHED
 
  TCP    s056816:netbios-ssn    s056816.ho.nmfco.com:0  LISTENING]
 
 
 Stderr: [WebSphere MQ queue manager running.] null
 
 
Please advice | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | shrek | 
		  
		    
			  
				 Posted: Thu Jul 12, 2007 6:39 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Acolyte
 
 Joined: 19 Feb 2005 Posts: 61 Location: Gudivada,India 
  | 
		  
		    
			  
				| Is there a specific reason that you are using 2414? Have you tried creating listener on some other port(1414 is default). | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mca | 
		  
		    
			  
				 Posted: Thu Jul 12, 2007 7:47 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Disciple
 
 Joined: 09 Mar 2005 Posts: 196
  
  | 
		  
		    
			  
				| I am trying to create this default configuration creation from MB Tool kit. So, all this is being done in the background with out manual interference. And this default configuration wizard is selecting this port #. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Thu Jul 12, 2007 10:58 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| shrek wrote: | 
   
  
	| Is there a specific reason that you are using 2414 | 
   
 
 
 
It is indeed the port used by the MB wizard. Go figure.
 
 
mca - which version of MBv6 are you trying to use? If it's the plain 6.0.0 you may want to move up some versions; the wizard's kinda funky in the early itterations.
 
 
The alternative is to follow the instructions in the manual & issue the commands from the v6 prompt. Slightly tedious, but my experience is that the problem tends to be with the wizard rather than the software. You might have more luck the long way round. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mca | 
		  
		    
			  
				 Posted: Fri Jul 13, 2007 6:21 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Disciple
 
 Joined: 09 Mar 2005 Posts: 196
  
  | 
		  
		    
			  
				| The version of MB is Version: 6.0.2. May be i should install some latest fix packs to solve the issue | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kbogan | 
		  
		    
			  
				 Posted: Wed Jul 25, 2007 10:26 am    Post subject: Port 2414 | 
				     | 
			   
			 
		   | 
		
		
		   Newbie
 
 Joined: 25 Jul 2007 Posts: 1
  
  | 
		  
		    
			  
				| I had the same problem - the way I fixed it was I changed a line in c:\program files\ibm\mqsi\6.0\bin\mqsicfgutil.ini from port=2414 to port=1414 and all is well. The Default Configuration completed. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mca | 
		  
		    
			  
				 Posted: Wed Jul 25, 2007 11:42 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Disciple
 
 Joined: 09 Mar 2005 Posts: 196
  
  | 
		  
		    
			  
				| That helps. But i already configured this from command prompt. Thanks a lot for your valuable advice. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |