Eclipse Community Forums: Virgo » How to implement catch all type exception handler

Help

Home

Home » Eclipse Projects » Virgo » How to implement catch all type exception handler

Show: Today's Messages :: Show Polls :: Message Navigator

How to implement catch all type exception handler [message #695771]

Tue, 12 July 2011 14:12

Barbara Rosi-Schwartz

Messages: 448
Registered: July 2009

Senior Member

Hello.

In my OSGi based application, I would like to apply the pattern of a last ditch "catch all" Exception handler which appropriately and gracefully handles any really unexpected exception that may be thrown and not caught anywhere.

In a normal Java application, I would implement such a patter in the app's main() method. Since an OSGi application does not have such a thing as a main() method, how would I go about doing this?

Any suggestions would be very appreciated.

TIA,
B.

Report message to a moderator

Re: How to implement catch all type exception handler [message #695784 is a reply to message #695771]

Tue, 12 July 2011 14:42

Glyn Normington

Messages: 1222
Registered: July 2009

Senior Member

I think a nice solution would require some support in Virgo. Virgo would probably need to set an uncaught exception handler on threads that can run application code. I think it could probably manage that before calling Bundle.start and in the executor which is used to spawn Spring DM worker threads. Then Virgo could generate a dump whenever an uncaught exception surfaced. Your "last ditch" bundle could then register a DumpContributor and hook in to the generation of the dump. It would be able to gather additional diagnostics and include them in the dump directory, for instance. The bundle could potentially do some application specific clean up, but I'm not sure it could be made as graceful as you would like.

If that sounds useful, please raise an enhancement bugzilla. If you can provide a patch too, so much the better.

Meanwhile, you could set an uncaught exception handler from your application, but there might be issues getting this to work nicely across bundles, although I can't think of any such issues immediately.

Alternatively, you'd need to make any external "entry point" in a bundle handle its own graceful cleanup before "percolating" the unexpected exception to its caller.

Report message to a moderator