| Author | 
		  Message
		 | 
		
		  | wyatt | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 6:55 am    Post subject: Configuration Manager Fails to start - V6 | 
				     | 
			   
			 
		   | 
		
		
		   Voyager
 
 Joined: 28 Nov 2004 Posts: 76
  
  | 
		  
		    
			  
				After making changes to CLASSPATH, our V6 configuration manager does not start  The following message is posted to the windows log (event viewer):
 
 
"
 
Unexpected exception in ConfigurationManager class 'initialize' method; exception text: ''java.lang.NoSuchFieldError: msgToken'', ''msgToken''.   
 
 
An exception was caught by the ConfigurationManager class 'initialize' method while the Configuration Manager was being started or stopped. The exception text is: 'java.lang.NoSuchFieldError: msgToken', 'msgToken'.   
 
"
 
 
The CLASSPATH contains:
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;
 
C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqetclient.jar;
 
C:\PROGRA~1\IBM\SQLLIB\java\db2java.zip;
 
C:\PROGRA~1\IBM\SQLLIB\java\db2jcc.jar;
 
C:\PROGRA~1\IBM\SQLLIB\java\db2jcc_license_cisuz.jar;
 
C:\PROGRA~1\IBM\SQLLIB\java\db2jcc_license_cu.jar;
 
 
Any suggestions? | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 6:59 am    Post subject: Re: Configuration Manager Fails to start - V6 | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| wyatt wrote: | 
   
  
	| After making changes to CLASSPATH, our V6 configuration manager does not start   | 
   
 
 
 
What was the change? Have you tried reversing it to see if that resolves the problem (and hence point to some conflict within the order of the CLASSPATH)? _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | wyatt | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 7:10 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Voyager
 
 Joined: 28 Nov 2004 Posts: 76
  
  | 
		  
		    
			  
				| ...stating the problem exposed the error.  File db2jcc_license_cu.jar was incorrectly specified | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Vitor | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 7:12 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				
   
	| wyatt wrote: | 
   
  
	| ...stating the problem exposed the error.  File db2jcc_license_cu.jar was incorrectly specified | 
   
 
 
 
Weird how often that happens......    
 
 
Glad you've got it sorted. _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | mqmatt | 
		  
		    
			  
				 Posted: Thu Sep 07, 2006 9:22 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Grand Master
 
 Joined: 04 Aug 2004 Posts: 1213 Location: Hursley, UK 
  | 
		  
		    
			  
				
   
	| wyatt wrote: | 
   
  
	| ...stating the problem exposed the error.  File db2jcc_license_cu.jar was incorrectly specified | 
   
 
 
That would have been the cause, but the problem you saw was not because of DB2.
 
I suspect that incorrectly specifying that JAR would have caused a problem with the CLASSPATH as a whole, which would have caused the MQ Java Client JAR not to be accessible.
 
It is a missing MQ v6 com.ibm.mq.jar that causes the problem described in the original post. See http://www.mqseries.net/phpBB2/viewtopic.php?t=27869 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |