|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	     | 
	 | 
   
 
  
	|  MQJE001: Completion Code 2, Reason 2085 | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | sshaker | 
		  
		    
			  
				 Posted: Mon May 12, 2003 11:15 am    Post subject: MQJE001: Completion Code 2, Reason 2085 | 
				     | 
			   
			 
		   | 
		 
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				Hi
 
 
I am trying to put a message to a cluster queue and getting the following error. Can somebody tell me what can be the reason?
 
 
TEST queue is hosted on a remote queue manager and i am trying to put message on a second queue manager which is part of the same cluster.
 
QM1 is on myHost
 
QM2 is on myComputer
 
client application is on myClient
 
 
The error message is:
 
 
*** Client Connection ***
 
hostname = myHost
 
channel = JAVA.CHANNEL
 
port = 1414
 
Connection to QM successful.
 
Accessing queue TEST
 
MQJE001: Completion Code 2, Reason 2085
 
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085
 
        at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1391)
 
        at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:1436)
 
        at mqTestPut.initialize(mqTestPut.java:91)
 
        at mqTestPut.main(mqTestPut.java:101)
 
Queue Manager disconnect.
 
 
The relevant reason from 2085 explanation is:
 
 
The object being opened is a cluster queue that is
 
hosted on a remote queue manager, but the local
 
queue manager does not have a defined route to the
 
remote queue manager.
 
 
thnx in advance
 
 
shaker _________________ shaker | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | mqonnet | 
		  
		    
			  
				 Posted: Mon May 12, 2003 11:37 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Grand Master
 
 Joined: 18 Feb 2002 Posts: 1114 Location: Boston, Ma, Usa. 
  | 
		  
		    
			  
				First thing to do is to check if the queue TEST shows up in the cluster.  From your local queue manager issue... dis qcluster(*) and see if TEST shows up in there.  
 
 
If it doesnt, then it could mean many things.
 
 
1) The queue is not a clustered queue.
 
2) IT has not been published in the cluster yet.  
 
3) Your cluster may not be set right.  Check to see the outputs from dis clusqmgr(*).
 
4) Cluster channels may not be running.
 
 
How many full repos do you have and which one is it.  Is the clustered queue hosted on the partial or the full repos.
 
 
Cheers
 
Kumar _________________ IBM Certified WebSphere MQ V5.3 Developer
 
IBM Certified WebSphere MQ V5.3 Solution Designer
 
IBM Certified WebSphere MQ V5.3 System Administrator | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | sshaker | 
		  
		    
			  
				 Posted: Mon May 12, 2003 1:29 pm    Post subject: closed | 
				     | 
			   
			 
		   | 
		 
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				thnx for ur help. i refreshed the cluster and it started working. 
 
 
regards
 
shaker _________________ shaker | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | 
		    
		   | 
		 
	   
	 | 
   
 
  
	     | 
	 | 
	Page 1 of 1 | 
   
 
 
 
  
  	
	  
		
		  
 
  | 
		  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
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |