On Wed, Mar 26, 2008 at 2:05 PM, raulvk <[EMAIL PROTECTED]> wrote:
>
> Hi everyone,
>
> I tried deploying a service assembly and the deployment failed due to some
> namespace clash. That is not the problem. The problem is that when I fix the
> problem and try to deploy the service assembly again, I get the following
> error for the servicemix-http service unit that it carries inside.
>
> java.lang.Exception: <?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-result-details>
> </frmwk-task-result-details>
> </frmwk-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
> <component-name>servicemix-http</component-name>
> <component-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>Service Unit 'prueba-http-listener' is already
> deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
> </task-result-details>
> </component-task-result-details>
> </component-task-result>
> ...
> </jbi-task>
>
> The other service units within the service assembly are deployed OK for the
> second time, its just this http service unit that fails. It seems that the
> previous failed deployment stuck around as a "ghost" service unit.
>
> I have checked via JMX that the DeploymentService doesn't think the service
> unit is deployed already (invoking the getDeployedServiceUnit method passing
> in the parameter "servicemix-http").
>
> Also, the Registry doesnt show the service unit inside the attribute
> "serviceUnitNames".
>
> And of course, as the service assembly wasn't deployed the first time, it's
> impossible to undeploy the conflictive service unit.
>
> Has anyone come across this problem before? It seems that it only affects
> servicemix-http service units............ could it be a bug?
>
> Thanks a lot,
>
> Raul.
>
> P.S.: I am a beginner, and due to that I think I have posted at least 4
> times today. Please, please bear with me. With your help I will become a
> ServiceMix expert and hopefully a committer at some point ;)
Most of the time this is a stale reference or something wonky in the
data directory. The easiest thing to do is to shut down SMX, remove
the data directory entirely, start up SMX and deploy the SA again.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/