|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| Kill Process on Integration Bus 10 | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | ccarrillo | 
			  
				|  Posted: Tue Jul 18, 2017 12:58 pm    Post subject: Kill Process on Integration Bus 10 |   |  |  
		  | Newbie
 
 
 Joined: 28 Oct 2016Posts: 9
 
 
 | 
			  
				| Hi guys, i have an integration bus 10, i have  a question, about when i kill a execution group process. Is necesary restart the  broker?  Excuse me but i'm new on this.  Thanks. |  |  
		  | Back to top |  |  
		  |  |  
		  | rammer | 
			  
				|  Posted: Tue Jul 18, 2017 10:21 pm    Post subject: |   |  |  
		  | Partisan
 
 
 Joined: 02 May 2002Posts: 359
 Location: England
 
 | 
			  
				| Hi - Ive only ever done it on 8 and then just restarted the execution group, not sure on 10 nor if its the best way of doing it.   Only time Ive done it is when its been last resort. |  |  
		  | Back to top |  |  
		  |  |  
		  | zpat | 
			  
				|  Posted: Wed Jul 19, 2017 12:16 am    Post subject: |   |  |  
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| If you can't deal with this any other way (and there is now a forceexecutiongrouprestart option on the stop message flow command), then the EG will auto-restart (assuming you kill the EG and not the EG start process). 
 No need to restart the broker.
 
 Killing an EG indicates that you have a underlying issue that needs resolving - don't just hope it won't happen again.
 _________________
 Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | mrSatendraNegi | 
			  
				|  Posted: Sat Jul 29, 2017 11:50 pm    Post subject: |   |  |  
		  | Newbie
 
 
 Joined: 29 Jul 2017Posts: 4
 
 
 | 
			  
				| You can use the 
 ps -ef|grep <EG name >
 
 kill -9 <process id EG from above command> on AIX
 
 Wait for few minutes , EG will restart automatically but again make sure you find the root cause of EG becoming unresponsive and take the action accordingly.
 
 That's on IIB9 , should be same on IIB10 run time as well.
 |  |  
		  | 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
 
 |  |  |  |