After an upgrade, it is possible that the class cache's are still holding onto previous versions of classes. It is also possible that the caches became corrupted.
Please remember there are two caches that will need to be cleared, the JVM's cache and the OSGi cache. The MDM server has to be stopped before clearing the cache.
To clear the OSGi class cache:
To clear the JVM's class cache
- For UNIX platforms, run the following script in each profile:
For Windows platforms, run the following script in each profile:
(Linux, AIX, z/OS and Windows) :
- For UNIX and z/OS platforms, run the following script:
For Windows platforms, run the following script:
And clear the following directory contents:
where WinUsers_home is either C:\Documents and Settings\DefaultUser OR C:\Users depending on your current version of Windows.
1. You should not delete the cache while any of the JVM's are running and using the cache. The server has to be stopped before clearing the cache.
2. You must be logged in as the user who started WebSphere Application Server.
3. For Windows the clearClassCache.bat may not work if you are using Windows Services. Please follow these steps:
Clear the following directory contents:
For Windows XP/Windows 2003:
C:\Documents and Settings\DefaultUser\Local Settings\ ApplicationData\javasharedresources\
For Window Vista/Windows 7/Windows 2008: