| Author | 
		  Message
		 | 
		
		  | jsware | 
		  
		    
			  
				 Posted: Tue Apr 01, 2014 11:55 pm    Post subject: LOCAL_TIMEZONE hangs in Debugger | 
				     | 
			   
			 
		   | 
		
		
		    Chevalier
 
 Joined: 17 May 2001 Posts: 455
  
  | 
		  
		    
			  
				Hi,
 
 
Has anybody experienced a problem debugging ESQL which uses the LOCAL_TIMEZONE keyword?  When you step through the ESQL code, the debugger hangs when stepping over a line of code with this keyword.
 
 
It seems to work fine when running at full speed.
 
 
For example, the code:
 
 
SET OutputRoot.XMLNSC.LocalTimeZone = LOCAL_TIMEZONE;
 
 
seems to hang in a compute node. _________________ Regards
 
John
 
The pain of low quaility far outlasts the joy of low price. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Esa | 
		  
		    
			  
				 Posted: Wed Apr 02, 2014 12:53 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 22 May 2008 Posts: 1387 Location: Finland 
  | 
		  
		    
			  
				| I just ran a brief test and can confirm that this is what happens. WMB and Toolkit version 8.0.0.2. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Esa | 
		  
		    
			  
				 Posted: Wed Apr 02, 2014 1:14 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 22 May 2008 Posts: 1387 Location: Finland 
  | 
		  
		    
			  
				An interesting observation:
 
 
if you terminate the debug session after it has hanged with LOCAL_TIMEZONE and start it again, you must send several test messages before the debugger wakes up and stops at a breakpoint.
 
The messages that you send before the debugger woke up will vanish without a trace, they cannot be found in the input queue, output queue or the dead letter queue.
 
If you send more messages while the debugger is hanging, they also disappear without a trace.
 
 
I guess this may not have to do with LOCAL_TIMEZONE, it may even be a well-known feature of the  debugger? Nothing serious, nobody should debug in production anyway. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | McueMart | 
		  
		    
			  
				 Posted: Wed Apr 02, 2014 1:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Chevalier
 
 Joined: 29 Nov 2011 Posts: 490 Location: UK...somewhere 
  | 
		  
		    
			  
				| The debugger crashing when stepping over the INTERVAL keyword was fixed in 8.0.0.4. Possibly they fixed LOCAL_TIMEZONE too? Give it a test! | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Dave Ziegler | 
		  
		    
			  
				 Posted: Mon Nov 03, 2014 6:56 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 15 Apr 2014 Posts: 118
  
  | 
		  
		    
			  
				| I have this problem in V9, is there a resolution? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | jsware | 
		  
		    
			  
				 Posted: Thu Nov 06, 2014 5:02 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Chevalier
 
 Joined: 17 May 2001 Posts: 455
  
  | 
		  
		    
			  
				I think this may be fixed in v9.0.0.2.  You'll have to test it. _________________ Regards
 
John
 
The pain of low quaility far outlasts the joy of low price. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Dave Ziegler | 
		  
		    
			  
				 Posted: Thu Nov 06, 2014 6:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 15 Apr 2014 Posts: 118
  
  | 
		  
		    
			  
				
   
	| jsware wrote: | 
   
  
	| I think this may be fixed in v9.0.0.2.  You'll have to test it. | 
   
 
 
 
You are correct, I installed the update just now and LOCAL_TIMEZONE is no longer hanging the debugger.
 
 
Thanks! | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |