Hi,

I've read those before already and I have slf4j dependency in my module. In my pom I have:

<Import-Package>org.slf4j; provider=paxlogging,*;resolution:=optional</Import-Package>

and in manifest imports.

org.slf4j;provider=paxlogging;version="[1.5,2)"

And if there is uncaught exception, it is ?consumed? and never displayed/logged. Just

org.osgi.framework.BundleException: Activator start error in bundle network [90].

in console. When I log explicitly in code it works, I have problem with losing information about uncaught exceptions.

An ideas? Is there possibly a configuration needed to allow this? I'm sure this must be some bug in my configuration (karaf 2.2.5 from tarball) or bundle content.

Thanks & regards,

Marek

On 04/03/2012 01:00 PM, Reuben Garrett wrote:
i use SLF4J and it seems to automagically connect with Karaf's pax logging. from there, you would use Karaf's log:set and log:display commands (log:tail if you want to be "notified". check out [1] for more details on Karaf logging.

[1]: http://karaf.apache.org/manual/2.2.5/users-guide/logging-system.html

~ Reuben

On Monday, April 2, 2012, Marek Šabo wrote:

    I would like to ask how can I be notified/log/see uncaught
    exceptions that originate from my bundle.

    Is there any way to log uncaught exception from bundles? I don't
    know if all the code I use won't let one slip through.

Reply via email to