|Timeout when starting Blueprint Bundle in Virgo 3.5.0.RELEASE [message #902315]
||Thu, 16 August 2012 22:47
| William Curtis
Registered: August 2012
I created a new bundle project using maven-bundle-plugin. This plugin wraps log4j-1.2.17 and exposes the internal workings of log4j to other bundles that use too much of log4j that I can't control. (It actually "inlines" the log4j classes)|
This works well.
I defined a service interface and implementation in the bundle as well that could be used to control the log appenders and levels for loggers. (The final goal was to add a console interface to allow OSGi console level manipulation of log4j)
I went to define that service interface in the "/OSGI-INF/blueprint/blueprint.xml" and the whole bundle fails to start. It times out and never starts and the bundle "un-resolves" and uninstalls.
I took the definitions of the service and interface out of the .xml and re-deployed. So now, the XML just has the "blueprint" begin and end tags and it still will not start. It just hangs.
<?xml version="1.0" encoding="UTF-8"?>
I don't know where to start debugging this. I can try to start the bundle from the osgi console, but still no help.
Thanks for any help in advance...
Powered by FUDForum
. Page generated in 0.01484 seconds