Chapter 8. Debugging applications
This chapter covers
- Debugging bundles using jdb
- Debugging bundles using Eclipse
- Understanding and solving class-loading issues
- Tracking down memory leaks and dangling service references
You just learned how to test individual bundles and application deployments in OSGi, but what should you do when an integration test unexpectedly fails with a class-loading exception or a load test runs out of memory? If you were working on a classic Java application, you’d break out the debugger, start adding or enabling instrumentation, and capture various diagnostic dumps. Well, an OSGi application is still a Java application, so you can continue to use many of your well-honed debugging techniques. The key area to watch ...
Get OSGi in Action now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
