What is the content of your zip ? It needs to be a JBI artifact, so the jbi descriptor is a requirement for components, shared libraries and service assemblies. It is not required for service units, but service units must be wrapped in service assemblies.
On Tue, Apr 29, 2008 at 12:46 AM, Daniel_Bruessler <[EMAIL PROTECTED]> wrote: > > Hello, > > > > gnodet wrote: > > > > You should have something more explicit in the console or the log file, > > like a stack trace exception or something like that. > > > > today I started all with > ------- > bin/hotdeploy > ------- > > with just having this in the hotdeploy-folder: bean, jms, lwcontainer, > shared, truezip > > When SM has started, not just these, all components got loaded (why?) and > then when ready I added just the iqtestcontainer-3.2.1-src.zip > > the error-message is "Unable to find jbi descriptor" - but I think I don't > need a jbi.xml, do I? > > -------- > INFO | Timer-5 | AutoDeploymentService | > ramework.AutoDeploymentService 646 | Directory: hotdeploy: Archive changed: > processing iqtestcontainer-3.2.1-src.zip ... > > WARN | Timer-5 | AutoDeploymentService | > ramework.AutoDeploymentService 650 | Directory: hotdeploy: Automatic > install of > C:\Programme\ApacheServiceMix321\hotdeploy\iqtestcontainer-3.2.1-src.zip > failed > javax.jbi.management.DeploymentException: <?xml version="1.0" > encoding="UTF-8"?> > <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message"; > version="1.0"> > <jbi-task-result> > <frmwk-task-result> > <frmwk-task-result-details> > <task-result-details> > <task-id>deploy</task-id> > <task-result>FAILED</task-result> > <message-type>ERROR</message-type> > <task-status-msg> > <msg-loc-info> > <loc-token/> > <loc-message>Unable to find jbi descriptor: > > C:\Programme\ApacheServiceMix321\hotdeploy\iqtestcontainer-3.2.1-src.zip</loc-message> > </msg-loc-info> > </task-status-msg> > </task-result-details> > </frmwk-task-result-details> > </frmwk-task-result> > </jbi-task-result> > </jbi-task> > > at > > org.apache.servicemix.jbi.framework.AutoDeploymentService.failure(AutoDeploymentService.java:384) > at > > org.apache.servicemix.jbi.framework.AutoDeploymentService.failure(AutoDeploymentService.java:370) > at > > org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:234) > at > > org.apache.servicemix.jbi.framework.AutoDeploymentService.monitorDirectory(AutoDeploymentService.java:647) > at > > org.apache.servicemix.jbi.framework.AutoDeploymentService.access$800(AutoDeploymentService.java:60) > at > > org.apache.servicemix.jbi.framework.AutoDeploymentService$1.run(AutoDeploymentService.java:611) > at java.util.TimerThread.mainLoop(Timer.java:512) > at java.util.TimerThread.run(Timer.java:462) > -------- > -- > View this message in context: > http://www.nabble.com/pure-container-running-endlessly-tp16917660p16945970.html > > > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
