Network Deployment (Distributed operating systems), v8.0 > Reference > Troubleshoot tips > Troubleshoot OSGi applications
OSGi Applications: Messages
When you use the OSGi Applications component, you might encounter system messages. Each message has a unique message identifier, and includes an explanation of the problem, and details of any action that you can take to resolve the problem.
WAS system messages are logged from a variety of sources, including application server components and applications. For OSGi Applications, the message identifier is 10 characters in length and has the following form:
CWS??1234Xwhere:
The Troubleshooter reference: Messages topic contains information about all WAS messages, indexed by message prefix. For each message there is an explanation of the problem, and details of any action that you can take to resolve the problem.
The alphabetic prefixes for OSGi Applications are as follows:
| OSGi Applications message prefix | OSGi Applications component |
|---|---|
| CWSAA | Launcher. |
| CWSAB | Kernel; declarative transactions. |
| CWSAC | OSGi application processing. |
| CWSAF | Java Persistence API (JPA) container. |
| CWSAG | Java Naming and Directory Interface (JNDI). |
| CWSAH | Web application archive (WAR) processing project. |
| CWSAI | Tr.error() calls in OSGi applications. |
| CWSAJ | Administrative messages. |
| CWSAK | Asynchronous bundle download. |
| CWSAL | Business-level applications. |
| CWSAN | Application utilities; parsing resource references. |
| CWSAO | Bundle provisioning. |
| CWSAP | Class loading. |
Related concepts:
About OSGi Applications
Related tasks:
Secure OSGi Applications
Administer OSGi Applications
Related reference:
OSGi Applications: Troubleshooting tips
Reference topic
Feedback
Copyright IBM Corporation 2009, 2011. All Rights Reserved.
This information center is powered by Eclipse technology.