Application issues
Always look at the logfiles for identifying the error messages. Logfiles should be observed to identify issues and error messages to identify the root cause. Use the logfile status as info for collecting more data. You must know the location of all the logfiles. You have domain, managed server, application, and container and JVM logs to help for troubleshooting.
Some of the most re-occurring issues with SOA Suite application are as follows:
ClassNotFoundException errors: This can be caused by either filesystem corruption or if one fails to load the jar needed for newly-added features for your SOA composite application. In the case of filesystem corruptions, restore it from the backup or perform a green field install. On the other hand, while adding new features simply ensure that you got all the jar libraries needed with this release. Usually, if the deployment steps failed to mention all the jar files added during the design and development it gets caught while deploying...