Hhm, rather strange. What version of the SMX4 kernel do you use?
I have built a quick OSGI bundle testcase with an Activator that uses java.util.logging and can see the logging working fine and written correctly.
Is your org.ops4j.pax.logging.cfg config different from the default?
Btw, pax logging will register a JdkHandler that redirects any java.util.logging to its own logging (which in ServiceMix4 is done via log4j).
Edited by: tmielke on Apr 2, 2009 2:40 PM
Thanks for the response. I'm using version 220.127.116.11 of SMX.
I'm still climbing the familiarity curve with OSGi. It turns out that some of the 3rd party Jars (geotools) I am linking with are split into multiple modules, some of which are meant to share the same singleton instances (causes somewhat unpredictable behavior when deployed as separate bundles). The modules also have some sort of logging layer and try to do clever things with class loading.
When I integrated the geotools modules into my application bundle so they share the same class loader, the error went away.
Thanks for doing the test ... Sorry for the false alarm!