| Author | 
		  Message
		 | 
		
		  | WLeideckDC | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 3:53 am    Post subject: runmqchl stop working after some time | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 25 Aug 2004 Posts: 21 Location: Ludwigshafen, Germany 
  | 
		  
		    
			  
				Hello,
 
we are using MQ V5.3 CSD07 on HPUX 11.11.
 
 
We defined a sender channel with parameter discint(6000). It is default.
 
We the channel with 'runmqchl -c <this channel> -m <QM> &'.
 
If no message arrived on the transmission queue the channel stops working
 
after the defined range of 6000 sec.  After that we couldn't send any message only a restart of the channel with runmqchl works.
 
Could we avoid this behaviour?
 
 
Thanks in advance
 
Wolfgang | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | JasonE | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 4:02 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 03 Nov 2003 Posts: 1220 Location: Hursley 
  | 
		  
		    
			  
				| Look up channel triggering in the intercomms guide, or change the discint parm if you really, really, really need to run the runmqchl command manually. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | WLeideckDC | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 4:55 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 25 Aug 2004 Posts: 21 Location: Ludwigshafen, Germany 
  | 
		  
		    
			  
				Triggering is enabled as mentioned in the intercomm guide but it isn't working as expected.
 
 
Putting a message of the remote queue doesn't  deliver the message of
 
the local queue of the other qm, which is defined by the remote queue.
 
 
Wolfgang | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | JasonE | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 5:46 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Grand Master
 
 Joined: 03 Nov 2003 Posts: 1220 Location: Hursley 
  | 
		  
		    
			  
				So the question is not how to keep the runmqchl running, but why your channel triggering isnt working.
 
 
Are you running a channel initiator (runmqchi - usually started by strmqm)
 
What is your channel, xmitq (and process, if you do it that way) definitions? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | WLeideckDC | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 6:10 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 25 Aug 2004 Posts: 21 Location: Ludwigshafen, Germany 
  | 
		  
		    
			  
				Ok, the channel initiator is running on both QM's.
 
 
Here the definition of the xmit queue:
 
DEFINE QLOCAL(MOBILIX.XMIT) TRIGGER +
 
INITQ(SYSTEM.CHANNEL.INITQ) +
 
TRIGDATA(MOBILIX.TEST1.CH) +
 
TRIGTYPE(FIRST) +
 
USAGE(XMITQ) +
 
REPLACE
 
 
Channeldefinition
 
DEFINE CHANNEL(MOBILIX.TEST1.CH) +
 
CHLTYPE(SDR) +
 
CONNAME('mobilix(9001)') +
 
XMITQ(MOBILIX.XMIT) +
 
REPLACE
 
 
Remotequeue definition
 
DEFINE QREMOTE(MOBILIX.TEST1_LQ) +
 
RNAME(TEST1.LQ) +
 
RQMNAME(QM.TEST1) +
 
XMITQ(MOBILIX.XMIT) +
 
REPLACE
 
 
The definitions on QM.TEST1 are similiar. Also runmqlsr is running on both QM's.
 
 
The messages are only delivered if i run runmqchl.
 
 
Thanks | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vennela | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 10:26 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India 
  | 
		  
		    
			  
				You definitions look OK. 
 
 
Do not run runmqchl
 
 
Start the Queue Manager. Look for a process called runmqchi  after the QMGR is started. 
 
 
Now if you put a message to a remote queue then the channel will start automatically. 
 
Do 
 
 to find the channel status. Let us know if you have problems. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | gunter | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 11:46 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Partisan
 
 Joined: 21 Jan 2004 Posts: 307 Location: Germany, Frankfurt 
  | 
		  
		    
			  
				
   
	| Quote: | 
   
  
	DEFINE CHANNEL(MOBILIX.TEST1.CH) +
 
CHLTYPE(SDR) +
 
CONNAME('mobilix(9001)') + # ?????
 
XMITQ(MOBILIX.XMIT) +
 
REPLACE
 
 | 
   
 
 
 
It's a channel to mobilix ?  
 
 
   
	| Quote: | 
   
  
	DEFINE QREMOTE(MOBILIX.TEST1_LQ) +
 
RNAME(TEST1.LQ) +
 
RQMNAME(QM.TEST1) +  # ?????
 
XMITQ(MOBILIX.XMIT) +
 
REPLACE  | 
   
 
 
 
Is QM.TEST1 on mobilix ? 
 
 
Please describe the architecture. What are the names of the queuemanager. At which host they are. Where are the objects located? _________________ Gunter Jeschawitz
 
IBM Certified System Administrator - Websphere MQ, 5.3 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | PeterPotkay | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 2:21 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Poobah
 
 Joined: 15 May 2001 Posts: 7723
  
  | 
		  
		    
			  
				The definitions look OK, if a bit unconventional in their naming.
 
 
You show that the XMITQ has a trigger type of first, but you are not showing if trigger control is ON of OFF. Make sure its ON.
 
 
Once the QM is up, do a Queue Usuage on the init queue. It should have an IPROCS of 1, showing that the cannel init has it open and ready to process trigger messages to start up channels. _________________ Peter Potkay
 
Keep Calm and MQ On | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | WLeideckDC | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 11:06 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Novice
 
 Joined: 25 Aug 2004 Posts: 21 Location: Ludwigshafen, Germany 
  | 
		  
		    
			  
				Just for clarify,
 
 
mobilix is a test machine. Both QM's are running on the same machine.
 
 
After playing with the reordering  with the define statements, triggering works.
 
I don't know why but it works. 
 
Is the order of parameters in a definition important?
 
 
Thanks for your assistance.
 
 
Wolfgang | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | vennela | 
		  
		    
			  
				 Posted: Wed Aug 25, 2004 11:14 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Knight
 
 Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India 
  | 
		  
		    
			  
				
   
	| Quote: | 
   
  
	| Is the order of parameters in a definition important? | 
   
 
 
AFAIK
 
NO 
 
If the order matters then runmqsc would error out. But if the runmqsc has not given a syntax error then the order should not matter. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | zlf | 
		  
		    
			  
				 Posted: Thu Sep 08, 2005 11:43 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 08 Sep 2005 Posts: 15
  
  | 
		  
		    
			  
				I encounter the same problem now. My runmqchi process always stops after one hour around after starting it.
 
I wonder does this problem get solved now.
 
thx | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | EddieA | 
		  
		    
			  
				 Posted: Fri Sep 09, 2005 9:21 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi
 
 Joined: 28 Jun 2001 Posts: 2453 Location: Los Angeles 
  | 
		  
		    
			  
				
   
	| Quote: | 
   
  
	| I wonder does this problem get solved now | 
   
 
 
What problem.  Did you actually read this thread.
 
 
Cheers, _________________ Eddie Atherton
 
IBM Certified Solution Developer - WebSphere Message Broker V6.1
 
IBM Certified Solution Developer - WebSphere Message Broker V7.0 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |