com.ibm.wps.app.exceptions.CompositeApplicationException: com.ibm.rcp.portal.app.internal.exceptions.NotFoundException: 404
at com.ibm.rcp.portal.app.internal.loader.internal.CAXmlProcessor.bringUpToDate(Unknown Source)
at com.ibm.rcp.portal.app.internal.loader.internal.CAXmlProcessor.provisionAndParseApplication(Unknown Source)
at com.ibm.rcp.portal.app.internal.loader.CaXmlLoader.loadCA(Unknown Source)
The difference from most Java stack traces is that the line numbers are missing. This is done intentionally for performance reasons, but can be a problem for a developer or anyone (IBM support) who needs the line numbers to review source code. The simple solution is to update the jvm.properties file by commenting out two properties:
The latter property disables the shared classes cache. If the class had previously been cached without line numbers, you'll need to remove the class from the cache. The only way to do this is by deleting the shared classes cache file from disk. Delete the file located in <workspace>\.config\org.eclipse.osgi. You should have a ~40MB file, which has as part of its name the xpdplat_.jvm name value seen in the vmarg.Dshare property. To prevent future development issues, it's suggested to disable the shared classes file altogether.
If at a future date you want to re-enable the cache, simply uncomment the vmarg.Dshare property and launch the client. For more information on the shared classes cache, see the developerWorks article Java technology, IBM style: Class sharing.