You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Barrie Treloar <ba...@gmail.com> on 2009/10/06 00:54:57 UTC

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Repost after 2 weeks, hoping someone can provide some enlightenment.
Thanks.

On Wed, Sep 23, 2009 at 5:03 PM, Barrie Treloar <ba...@gmail.com> wrote:
> Firstly apologies for the length of this post, Google hasn't been
> helpful when trying to resolve this.
> I'm hoping I've only included the relevant bits of the error output
> that are useful.
>
> I am getting deployment errors with ServiceMix 3.3.1 on Windows XP sp2.
>
> I have three scenarios:
> (fails)  Scenario 1: ServiceMix freshly started, SA is deployed and
> started, deploy new version of SA
> (pass) Scenario 2: After Scenario 1, re-run deployment
> (fails)  Scenario 3: Rebuilding SA and redploying.
>
> I get errors at Scenario 1 and 3 where I dont expect any errors,
> especially since Scenario 2 just re-runs the deployment step straight
> after the failure from 1.
>
> Details of what I am doing and the output follows.
> Suggestions, pointers, hints all gratefully accepted.
>
> Thanks.
> Barrie
>
> ===
> Scenario 1: ServiceMix freshly started, SA is deployed and started,
> deploy new version of SA
>
> Trying to install new version os SA via
> mvn jbi:projectDeploy -DforceUpdate=true
>
> Gives
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to deploy project, Error accessing ServiceMix administration
>
> org/apache/servicemix/common/ManagementSupport$Message
>
> With ServiceMix console output:
> WARN  - InstallationService            - Failed to delete old
> installation directory:
> D:\apache-servicemix\apache-servicemix-3.3.1\data\smx\components\servicemix-jms\version_17
> INFO  - ComponentMBeanImpl             - Starting component: servicemix-jms
> WARN  - InstallationService            - Failed to delete old
> installation directory:
> D:\apache-servicemix\apache-servicemix-3.3.1\data\smx\components\servicemix-file\version_11
> INFO  - ComponentMBeanImpl             - Starting component: servicemix-file
> WARN  - InstallationService            - Failed to delete old
> installation directory:
> D:\apache-servicemix\apache-servicemix-3.3.1\data\smx\components\servicemix-camel\version_16
> INFO  - ComponentMBeanImpl             - Starting component: servicemix-camel
> INFO  - ServiceAssemblyLifeCycle       - Shutting down service assembly: mcp-sa
> INFO  - ServiceAssemblyLifeCycle       - Stopping service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-jms-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-jms-su
> INFO  - ServiceAssemblyLifeCycle       - Shutting down service assembly: mcp-sa
> INFO  - ServiceAssemblyLifeCycle       - Stopping service assembly: mcp-sa
>
> But no further information as to why this failed.
>
> ===
> Scenario 2: After Scenario 1, re-run deployment
>
> If I re-run the same command
> mvn jbi:projectDeploy -DforceUpdate=true
>
> Then the deployment is successful.
>
> ===
> Scenario 3: Rebuilding SA and redploying.
>
> Same mvn command:
> mvn jbi:projectDeploy -DforceUpdate=true
>
> Gives error:
> [INFO] Unable to deploy project, Error accessing ServiceMix administration
>
> <?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>shutDown</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
> And the console gives:
> INFO  - ServiceAssemblyLifeCycle       - Stopping service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-jms-su
> INFO  - ServiceAssemblyLifeCycle       - Shutting down service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-jms-su
> INFO  - JBIContainer                   - Deactivating component servicemix-jms
> WARN  - EnvironmentContext             - Failed to remove directory
> structure for component [version]: servicemix-jms [s
> ervicemix-jms]
> WARN  - InstallationService            - Failed to delete old
> installation directory: D:\apache-servicemix\apache-servic
> emix-3.3.1\data\smx\components\servicemix-jms\version_17
> INFO  - ComponentMBeanImpl             - Starting component: servicemix-jms
> INFO  - ComponentMBeanImpl             - Initializing component: servicemix-jms
> INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Initializing service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Initializing service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Initializing service unit: mcp-jms-su
> INFO  - JBIContainer                   - Deactivating component servicemix-file
> WARN  - EnvironmentContext             - Failed to remove directory
> structure for component [version]: servicemix-file [
> servicemix-file]
> WARN  - InstallationService            - Failed to delete old
> installation directory: D:\apache-servicemix\apache-servic
> emix-3.3.1\data\smx\components\servicemix-file\version_11
> INFO  - ComponentMBeanImpl             - Starting component: servicemix-file
> INFO  - ComponentMBeanImpl             - Initializing component: servicemix-file
> INFO  - JBIContainer                   - Deactivating component servicemix-camel
> WARN  - EnvironmentContext             - Failed to remove directory
> structure for component [version]: servicemix-camel
> [servicemix-camel]
> WARN  - InstallationService            - Failed to delete old
> installation directory: D:\apache-servicemix\apache-servic
> emix-3.3.1\data\smx\components\servicemix-camel\version_16
> INFO  - ComponentMBeanImpl             - Starting component: servicemix-camel
> INFO  - ComponentMBeanImpl             - Initializing component:
> servicemix-camel
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-jms-su
> ERROR - Registry                       - Error trying to restore
> service assembly state
> 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>start</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:111)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:168)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:364)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:353)
>        at org.apache.servicemix.jbi.framework.Registry.startPendingAssemblies(Registry.java:864)
>        at org.apache.servicemix.jbi.framework.Registry$1.run(Registry.java:840)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>        at java.lang.Thread.run(Thread.java:595)
> INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-file-su
> ERROR - Registry                       - Error trying to restore
> service assembly state
> 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>start</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:111)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:168)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:364)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:353)
>        at org.apache.servicemix.jbi.framework.Registry.startPendingAssemblies(Registry.java:864)
>        at org.apache.servicemix.jbi.framework.Registry$1.run(Registry.java:840)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>        at java.lang.Thread.run(Thread.java:595)
> INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Starting service unit: mcp-file-su
> ERROR - Registry                       - Error trying to restore
> service assembly state
> 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>start</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:111)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:168)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:364)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(ServiceAssemblyLifeCycle.java:353)
>        at org.apache.servicemix.jbi.framework.Registry.startPendingAssemblies(Registry.java:864)
>        at org.apache.servicemix.jbi.framework.Registry$1.run(Registry.java:840)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>        at java.lang.Thread.run(Thread.java:595)
> INFO  - ServiceAssemblyLifeCycle       - Shutting down service assembly: mcp-sa
> INFO  - ServiceAssemblyLifeCycle       - Stopping service assembly: mcp-sa
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: mcp-jms-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-eip-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-file-su
> INFO  - ServiceUnitLifeCycle           - Shutting down service unit: mcp-jms-su
> INFO  - DeploymentService              - Error in shutDown
> 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>shutDown</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:111)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.shutDown(ServiceAssemblyLifeCycle.java:260)
>        at org.apache.servicemix.jbi.framework.DeploymentService.shutDown(DeploymentService.java:426)
>        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:32
> 8)
>        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:255)
>        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateExternalArchive(AutoDeploymentService.java:20
> 5)
>        at org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive(JBIContainer.java:494)
>        at org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive(JBIContainer.java:504)
>        at org.apache.servicemix.jbi.framework.AdminCommandsService.deployServiceAssembly(AdminCommandsService.java:209)
>
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
>        at org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStandardMBean.java:323)
>        at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
>        at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
>        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>        at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
>        at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
>        at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350)
>        at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>        at sun.rmi.transport.Transport$1.run(Transport.java:153)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>        at java.lang.Thread.run(Thread.java:595)
> ERROR - AutoDeploymentService          - Failed to update Service
> Assembly: mcp-sa
> 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>shutDown</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> <component-task-result
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message>
> </msg-loc-info>
> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details>
> </component-task-result>
> </jbi-task-result>
> </jbi-task>
>
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:125)
>        at org.apache.servicemix.jbi.framework.ManagementSupport.failure(ManagementSupport.java:111)
>        at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.shutDown(ServiceAssemblyLifeCycle.java:260)
>        at org.apache.servicemix.jbi.framework.DeploymentService.shutDown(DeploymentService.java:426)
>        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServiceAssembly(AutoDeploymentService.java:32
> 8)
>        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchive(AutoDeploymentService.java:255)
>        at org.apache.servicemix.jbi.framework.AutoDeploymentService.updateExternalArchive(AutoDeploymentService.java:20
> 5)
>        at org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive(JBIContainer.java:494)
>        at org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive(JBIContainer.java:504)
>        at org.apache.servicemix.jbi.framework.AdminCommandsService.deployServiceAssembly(AdminCommandsService.java:209)
>
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java:216)
>        at org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStandardMBean.java:323)
>        at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
>        at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
>        at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>        at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1410)
>        at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
>        at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1247)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1350)
>        at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:784)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>        at sun.rmi.transport.Transport$1.run(Transport.java:153)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
>        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
>        at java.lang.Thread.run(Thread.java:595)
>
>
> At this point I have to restart ServiceMix. Which takes me back
> through the Scenario 1, then Scenario 2 cycle.
>

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by loboEsa <la...@gmail.com>.
Hi baerrach

I have the same problem. I find that the problem is not redeploy my SA the
problem become with -DforceUpdate=true because try to restart all
dependencies and fail to redeploy other components (SE per example,
including ServiceMix components). I didn't waste more time with this problem
and choose to use hotdeploy instead maven and all be fine.


baerrach wrote:
> 
> Ok here are the results of the suggestions.
> 
> Stuart Roe:
> Try: If you stop SMX can you delete the data folder in the SMX
> installation?
> Result: Success
> Selected "data" directory in ${SMX_HOME} and successfully deleted
> directory via Windows Explorer > Delete
> 
> Gert Vanthienen:
> virus scanners - Not tried.
> 
> Gert Vanthienen:
> Try: Use hotdeploy instead of the jbi maven plugin.
> Result: Success.
> Fresh SMX start, copy the <installer>.zip created
> INFO  - AutoDeploymentService          - Directory: hotdeploy:
> Finished installation of archive:  mcp-sa-1.0-SNAPSHOT.zip
> 
> Even tried deleting the hotdeploy archive and that uninstalls correctly as
> well.
> Also rebuilt sa and re-hotdeployed and that works with no errors.
> 
> Barrie:
> Stop SMX
> Delete data directory
> Start SMX
> Wait for re-installation of data/ directory.
> Restart SMX to avoid any re-installation potential issues.
> Searched for "mcp" in ${SMX_HOME} - found nothing.
> Hotdeploy
> Searched for "mcp" in ${SMX_HOME}
> - found in data\smx\service-assemblies\mcp-sa\...
> - found in data\amq\kr-store\data (hash index files)
> - found in hotdeploy\ (obviously)
> Hotundeploy
> Searched for "mcp" in ${SMX_HOME}
> - found in data\smx\service-assemblies\mcp-sa\...
> - found in data\amq\kr-store\data (hash index files)
> Delete directory
> - Fails because java has the locks on the files - specifically the
> libraries in one of my service-units.
> 
> My code is pretty dumb (its only a proof of concept) and I can't see
> anything that would be left in memory after an un-install.
> I thought perhaps it was Log4J and the static Loggers holding
> references to classes, but I've removed that code and it still
> happens.
> 
> I was just about to remove the guts of my code thinking something like
> XStream might be holding onto classes, when I realized that I am not
> actually running the service-unit.
> I'm just installing/uninstalling which therefore should not create any
> locks.
> I suspect that SMX is not unloading classes correctly then.
> 
> So doing a full thread dump I can see that there are threads blocked
> on waiting condition - which is probably why the classes are not being
> released.
> 
> So the problem appears to be uninstall does not stop running threads
> created during the install.
> Scanning JIRA on "thread waiting" shows
> http://issues.apache.org/activemq/browse/SM-1807 "Classes, Objects and
> Threads still alive after Undeploying a servicemix component"
> http://issues.apache.org/activemq/browse/SM-1578 "When shutting down
> endpoints, the component should wait for all exchanges to be
> completely processed before unregistering the endpoint"
> 
> Does this sound familiar to anyone? Have I identified the correct defects?
> Cheers
> 
> "QueueThread:queue://org.apache.servicemix.jca.{urn:mcp:testing}file:sender"
> daemon prio=6 tid=0x00a39090 nid=0x172c waiting on condition
> [0x3088f000..0x3088fa98]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 
> "QueueThread:queue://org.apache.servicemix.jca.{urn:mcp}incoming:endpoint"
> daemon prio=6 tid=0x2af22d58 nid=0x11d8 waiting on condition
> [0x307cf000..0x307cfb18]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 
> "QueueThread:queue://org.apache.servicemix.jms.{urn:mcp}incoming:endpoint"
> daemon prio=6 tid=0x28fbfc18 nid=0xce4 waiting on condition
> [0x3078f000..0x3078fd98]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 		
> "QueueThread:queue://org.apache.servicemix.jms.{urn:mcp:testing}file:sender"
> daemon prio=6 tid=0x2b898db0 nid=0x1420 waiting on condition
> [0x3068f000..0x3068fb18]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)		
> 		
> "QueueThread:queue://org.apache.servicemix.jms.{http://activemq.apache.org/camel/schema/jbi}provider:camel:mcp-eip-su-controlBus"
> daemon prio=6 tid=0x28b90638 nid=0xb50 waiting on condition
> [0x304cf000..0x304cfb18]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 		
> "QueueThread:queue://org.apache.servicemix.jca.{http://activemq.apache.org/camel/schema/jbi}provider:camel:mcp-eip-su-controlBus"
> daemon prio=6 tid=0x28f6d408 nid=0x7e0 waiting on condition
> [0x3040f000..0x3040fc18]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 		
> "QueueThread:queue://org.apache.servicemix.jca.{urn:mcp}outgoing:endpoint"
> daemon prio=6 tid=0x2878b390 nid=0x828 waiting on condition
> [0x3038f000..0x3038fb18]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 
> "QueueThread:queue://org.apache.servicemix.jms.{urn:mcp}outgoing:endpoint"
> daemon prio=6 tid=0x2bc35408 nid=0x14e4 waiting on condition
> [0x300df000..0x300dfa18]
>         at sun.misc.Unsafe.park(Native Method)
>         at
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>         at
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>         at
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>         at java.lang.Thread.run(Thread.java:595)
> 
> 

-- 
View this message in context: http://www.nabble.com/Deployment-errors-with-ServiceMix-3.3.1-on-Windows-XP-sp2-tp25572000p25961660.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Gert Vanthienen <ge...@gmail.com>.
Barrie,

To disable those flows, you can just comment out the JMS and JCA flow
elements in conf/servicemix.xml.  This is unrelated to using a JMS
endpoint in your flow -- you can still have JMS endpoints when using
the SedaFlow internally to send exchanges between components.  Using
the JMS/JCA flow will use JMS queues under the covers to transfer
exchanges, but it's usually a better idea to use explicit jms
endpoints like you are doing because then you have control yourself of
when things are getting queued.

Could you give it another go with both flows disabled to see if that's
where the problems are coming from?

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/10/21 Barrie Treloar <ba...@gmail.com>:
> On Wed, Oct 21, 2009 at 6:14 AM, Gert Vanthienen
> <ge...@gmail.com> wrote:
>> Barrie,
>>
>> It looks like those are all JMS/JCA flow threads.  Could you try
>> disabling those two flows in conf/servicemix.xml and see if that fixes
>> the issue?  It might only be a workaround if you're not using those
>> flows, but it will also give us a clue where to look for solving this
>> issue.
>
> My Proof of Concept uses JMS but not JCA.
>
> Request: File Poller -> ESB -> JMS Q
> Response: JMS Topic -> ESB -> File Sender
>
> I'm happy to give this a go, this is the only bit I can find referencing jms/jca
>
> ${SMX_HOME}/conf/servicemix.xml
>    <!-- Use a secured broker (see security.xml)
>         and define the 3 standard flows -->
>    <sm:broker>
>      <sm:securedBroker authorizationMap="#authorizationMap">
>        <sm:flows>
>          <sm:sedaFlow />
>          <sm:jmsFlow jmsURL="${activemq.url}" />
>          <sm:jcaFlow connectionManager="#connectionManager"
>                      jmsURL="${activemq.url}" />
>        </sm:flows>
>      </sm:securedBroker>
>    </sm:broker>
>
> How do I disable these flows?
>
> I'm attempting to remove the jms-su from my sa and see whether that
> still has an issue.
>

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Oct 21, 2009 at 9:43 AM, Barrie Treloar <ba...@gmail.com> wrote:
> I'm attempting to remove the jms-su from my sa and see whether that
> still has an issue.

After taking out the jms-su and restarting SMX and then using the
maven plugin to install I get this error the first time:
INFO  - ComponentMBeanImpl             - Starting component: servicemix-camel
ERROR - CamelJbiComponent              -
java.lang.NoClassDefFoundError:
org/apache/servicemix/common/xbean/ClassLoaderXmlPreprocessor

But after that it installs/uninstalls fine. So I will ignore
NoClassDefFoundError for now.

I must assume there is something in my jms-su that is not uninstalling properly.

I have in my xbeans.xml:
* jms:provider
* jms:consumer
* bean for Marshaling
* bean for Unmarshaling
* connectionFactory (Spring JndiObjectFactoryBean)
* destinationResolver (Spring JndiDestinationResolver)
* jndiTemplate (Spring JndiTemplate)

Since I am just installing/uninstalling the su and not pushing any
messages through this has to be the culprit.

I've tried with an empty xbean.xml, not surprisingly this complains
about no endpoints.

I ripped everything out and replaced it with a single AMQ endpoint
instead of the weblogic one.

After fiddling taking things and out, sometimes it creates a lock and
sometimes it doesn't.
I'm kinda stuck at this point and going to give up.

Cheers.

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Oct 21, 2009 at 6:14 AM, Gert Vanthienen
<ge...@gmail.com> wrote:
> Barrie,
>
> It looks like those are all JMS/JCA flow threads.  Could you try
> disabling those two flows in conf/servicemix.xml and see if that fixes
> the issue?  It might only be a workaround if you're not using those
> flows, but it will also give us a clue where to look for solving this
> issue.

My Proof of Concept uses JMS but not JCA.

Request: File Poller -> ESB -> JMS Q
Response: JMS Topic -> ESB -> File Sender

I'm happy to give this a go, this is the only bit I can find referencing jms/jca

${SMX_HOME}/conf/servicemix.xml
    <!-- Use a secured broker (see security.xml)
         and define the 3 standard flows -->
    <sm:broker>
      <sm:securedBroker authorizationMap="#authorizationMap">
        <sm:flows>
          <sm:sedaFlow />
          <sm:jmsFlow jmsURL="${activemq.url}" />
          <sm:jcaFlow connectionManager="#connectionManager"
                      jmsURL="${activemq.url}" />
        </sm:flows>
      </sm:securedBroker>
    </sm:broker>

How do I disable these flows?

I'm attempting to remove the jms-su from my sa and see whether that
still has an issue.

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Gert Vanthienen <ge...@gmail.com>.
Barrie,

It looks like those are all JMS/JCA flow threads.  Could you try
disabling those two flows in conf/servicemix.xml and see if that fixes
the issue?  It might only be a workaround if you're not using those
flows, but it will also give us a clue where to look for solving this
issue.

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/10/19 Barrie Treloar <ba...@gmail.com>:
> Ok here are the results of the suggestions.
>
> Stuart Roe:
> Try: If you stop SMX can you delete the data folder in the SMX installation?
> Result: Success
> Selected "data" directory in ${SMX_HOME} and successfully deleted
> directory via Windows Explorer > Delete
>
> Gert Vanthienen:
> virus scanners - Not tried.
>
> Gert Vanthienen:
> Try: Use hotdeploy instead of the jbi maven plugin.
> Result: Success.
> Fresh SMX start, copy the <installer>.zip created
> INFO  - AutoDeploymentService          - Directory: hotdeploy:
> Finished installation of archive:  mcp-sa-1.0-SNAPSHOT.zip
>
> Even tried deleting the hotdeploy archive and that uninstalls correctly as well.
> Also rebuilt sa and re-hotdeployed and that works with no errors.
>
> Barrie:
> Stop SMX
> Delete data directory
> Start SMX
> Wait for re-installation of data/ directory.
> Restart SMX to avoid any re-installation potential issues.
> Searched for "mcp" in ${SMX_HOME} - found nothing.
> Hotdeploy
> Searched for "mcp" in ${SMX_HOME}
> - found in data\smx\service-assemblies\mcp-sa\...
> - found in data\amq\kr-store\data (hash index files)
> - found in hotdeploy\ (obviously)
> Hotundeploy
> Searched for "mcp" in ${SMX_HOME}
> - found in data\smx\service-assemblies\mcp-sa\...
> - found in data\amq\kr-store\data (hash index files)
> Delete directory
> - Fails because java has the locks on the files - specifically the
> libraries in one of my service-units.
>
> My code is pretty dumb (its only a proof of concept) and I can't see
> anything that would be left in memory after an un-install.
> I thought perhaps it was Log4J and the static Loggers holding
> references to classes, but I've removed that code and it still
> happens.
>
> I was just about to remove the guts of my code thinking something like
> XStream might be holding onto classes, when I realized that I am not
> actually running the service-unit.
> I'm just installing/uninstalling which therefore should not create any locks.
> I suspect that SMX is not unloading classes correctly then.
>
> So doing a full thread dump I can see that there are threads blocked
> on waiting condition - which is probably why the classes are not being
> released.
>
> So the problem appears to be uninstall does not stop running threads
> created during the install.
> Scanning JIRA on "thread waiting" shows
> http://issues.apache.org/activemq/browse/SM-1807 "Classes, Objects and
> Threads still alive after Undeploying a servicemix component"
> http://issues.apache.org/activemq/browse/SM-1578 "When shutting down
> endpoints, the component should wait for all exchanges to be
> completely processed before unregistering the endpoint"
>
> Does this sound familiar to anyone? Have I identified the correct defects?
> Cheers
>
> "QueueThread:queue://org.apache.servicemix.jca.{urn:mcp:testing}file:sender"
> daemon prio=6 tid=0x00a39090 nid=0x172c waiting on condition
> [0x3088f000..0x3088fa98]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jca.{urn:mcp}incoming:endpoint"
> daemon prio=6 tid=0x2af22d58 nid=0x11d8 waiting on condition
> [0x307cf000..0x307cfb18]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jms.{urn:mcp}incoming:endpoint"
> daemon prio=6 tid=0x28fbfc18 nid=0xce4 waiting on condition
> [0x3078f000..0x3078fd98]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jms.{urn:mcp:testing}file:sender"
> daemon prio=6 tid=0x2b898db0 nid=0x1420 waiting on condition
> [0x3068f000..0x3068fb18]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jms.{http://activemq.apache.org/camel/schema/jbi}provider:camel:mcp-eip-su-controlBus"
> daemon prio=6 tid=0x28b90638 nid=0xb50 waiting on condition
> [0x304cf000..0x304cfb18]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jca.{http://activemq.apache.org/camel/schema/jbi}provider:camel:mcp-eip-su-controlBus"
> daemon prio=6 tid=0x28f6d408 nid=0x7e0 waiting on condition
> [0x3040f000..0x3040fc18]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jca.{urn:mcp}outgoing:endpoint"
> daemon prio=6 tid=0x2878b390 nid=0x828 waiting on condition
> [0x3038f000..0x3038fb18]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>
> "QueueThread:queue://org.apache.servicemix.jms.{urn:mcp}outgoing:endpoint"
> daemon prio=6 tid=0x2bc35408 nid=0x14e4 waiting on condition
> [0x300df000..0x300dfa18]
>        at sun.misc.Unsafe.park(Native Method)
>        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
>        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
>        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
>        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
>        at java.lang.Thread.run(Thread.java:595)
>

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Barrie Treloar <ba...@gmail.com>.
Ok here are the results of the suggestions.

Stuart Roe:
Try: If you stop SMX can you delete the data folder in the SMX installation?
Result: Success
Selected "data" directory in ${SMX_HOME} and successfully deleted
directory via Windows Explorer > Delete

Gert Vanthienen:
virus scanners - Not tried.

Gert Vanthienen:
Try: Use hotdeploy instead of the jbi maven plugin.
Result: Success.
Fresh SMX start, copy the <installer>.zip created
INFO  - AutoDeploymentService          - Directory: hotdeploy:
Finished installation of archive:  mcp-sa-1.0-SNAPSHOT.zip

Even tried deleting the hotdeploy archive and that uninstalls correctly as well.
Also rebuilt sa and re-hotdeployed and that works with no errors.

Barrie:
Stop SMX
Delete data directory
Start SMX
Wait for re-installation of data/ directory.
Restart SMX to avoid any re-installation potential issues.
Searched for "mcp" in ${SMX_HOME} - found nothing.
Hotdeploy
Searched for "mcp" in ${SMX_HOME}
- found in data\smx\service-assemblies\mcp-sa\...
- found in data\amq\kr-store\data (hash index files)
- found in hotdeploy\ (obviously)
Hotundeploy
Searched for "mcp" in ${SMX_HOME}
- found in data\smx\service-assemblies\mcp-sa\...
- found in data\amq\kr-store\data (hash index files)
Delete directory
- Fails because java has the locks on the files - specifically the
libraries in one of my service-units.

My code is pretty dumb (its only a proof of concept) and I can't see
anything that would be left in memory after an un-install.
I thought perhaps it was Log4J and the static Loggers holding
references to classes, but I've removed that code and it still
happens.

I was just about to remove the guts of my code thinking something like
XStream might be holding onto classes, when I realized that I am not
actually running the service-unit.
I'm just installing/uninstalling which therefore should not create any locks.
I suspect that SMX is not unloading classes correctly then.

So doing a full thread dump I can see that there are threads blocked
on waiting condition - which is probably why the classes are not being
released.

So the problem appears to be uninstall does not stop running threads
created during the install.
Scanning JIRA on "thread waiting" shows
http://issues.apache.org/activemq/browse/SM-1807 "Classes, Objects and
Threads still alive after Undeploying a servicemix component"
http://issues.apache.org/activemq/browse/SM-1578 "When shutting down
endpoints, the component should wait for all exchanges to be
completely processed before unregistering the endpoint"

Does this sound familiar to anyone? Have I identified the correct defects?
Cheers

"QueueThread:queue://org.apache.servicemix.jca.{urn:mcp:testing}file:sender"
daemon prio=6 tid=0x00a39090 nid=0x172c waiting on condition
[0x3088f000..0x3088fa98]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)

"QueueThread:queue://org.apache.servicemix.jca.{urn:mcp}incoming:endpoint"
daemon prio=6 tid=0x2af22d58 nid=0x11d8 waiting on condition
[0x307cf000..0x307cfb18]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)

"QueueThread:queue://org.apache.servicemix.jms.{urn:mcp}incoming:endpoint"
daemon prio=6 tid=0x28fbfc18 nid=0xce4 waiting on condition
[0x3078f000..0x3078fd98]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)
		
"QueueThread:queue://org.apache.servicemix.jms.{urn:mcp:testing}file:sender"
daemon prio=6 tid=0x2b898db0 nid=0x1420 waiting on condition
[0x3068f000..0x3068fb18]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)		
		
"QueueThread:queue://org.apache.servicemix.jms.{http://activemq.apache.org/camel/schema/jbi}provider:camel:mcp-eip-su-controlBus"
daemon prio=6 tid=0x28b90638 nid=0xb50 waiting on condition
[0x304cf000..0x304cfb18]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)
		
"QueueThread:queue://org.apache.servicemix.jca.{http://activemq.apache.org/camel/schema/jbi}provider:camel:mcp-eip-su-controlBus"
daemon prio=6 tid=0x28f6d408 nid=0x7e0 waiting on condition
[0x3040f000..0x3040fc18]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)
		
"QueueThread:queue://org.apache.servicemix.jca.{urn:mcp}outgoing:endpoint"
daemon prio=6 tid=0x2878b390 nid=0x828 waiting on condition
[0x3038f000..0x3038fb18]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)

"QueueThread:queue://org.apache.servicemix.jms.{urn:mcp}outgoing:endpoint"
daemon prio=6 tid=0x2bc35408 nid=0x14e4 waiting on condition
[0x300df000..0x300dfa18]
        at sun.misc.Unsafe.park(Native Method)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:118)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1841)
        at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:359)
        at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:470)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:674)
        at java.lang.Thread.run(Thread.java:595)

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Gert Vanthienen <ge...@gmail.com>.
Barrie,

Could you also try that with hotdeploy instead of using the jbi maven
plugin to deploy these artifacts to see if that improves the
situation?

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/10/7 Barrie Treloar <ba...@gmail.com>:
> On Wed, Oct 7, 2009 at 6:09 AM, Gert Vanthienen
> <ge...@gmail.com> wrote:
>> Barrie,
>>
>> I was going to suggest looking at virus scanners for the same reason
>> -- they tend to look into zip/jar files and keeping them locked,
>> preventing deletion from disk.  You'll probably notice that as well in
>> unlocker though if that's the case...
>
> Could be that as well, will try it.
> I dont have enough priveleges to tell the virus scanner not to check
> SMX directories.
>
> However, failing to delete the old directory should not cause me to
> fail to deploy a new version.
> Isn't the new version placed into a new directory?
>
> As discussed in the first post a fresh SMX start fails to deploy my
> app, but it works if I re-run the deploy command again.
> Then if I want to deploy another time, I have to restart SMX, and go
> through the above again (failed deploy, working deploy).
> Not sure if files being locked would be the cause of this...
>

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Barrie Treloar <ba...@gmail.com>.
On Wed, Oct 7, 2009 at 6:09 AM, Gert Vanthienen
<ge...@gmail.com> wrote:
> Barrie,
>
> I was going to suggest looking at virus scanners for the same reason
> -- they tend to look into zip/jar files and keeping them locked,
> preventing deletion from disk.  You'll probably notice that as well in
> unlocker though if that's the case...

Could be that as well, will try it.
I dont have enough priveleges to tell the virus scanner not to check
SMX directories.

However, failing to delete the old directory should not cause me to
fail to deploy a new version.
Isn't the new version placed into a new directory?

As discussed in the first post a fresh SMX start fails to deploy my
app, but it works if I re-run the deploy command again.
Then if I want to deploy another time, I have to restart SMX, and go
through the above again (failed deploy, working deploy).
Not sure if files being locked would be the cause of this...

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Gert Vanthienen <ge...@gmail.com>.
Barrie,

I was going to suggest looking at virus scanners for the same reason
-- they tend to look into zip/jar files and keeping them locked,
preventing deletion from disk.  You'll probably notice that as well in
unlocker though if that's the case...

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/10/6 Barrie Treloar <ba...@gmail.com>:
> On Tue, Oct 6, 2009 at 6:23 PM, Stuart Roe <st...@ovic.co.uk> wrote:
>> Barry,
>>
>> If you stop SMX can you delete the data folder in the SMX installation?
>>
>> I have previously had a problem where the Windows Content Index Service
>> (cisvc.exe) was processing file in the data folder and the deletion
>> operation failed. It interferred with the undeployment and redeployment of
>> SA to SMX.
>>
>> I stopped SMX and tried to delete the data folder and found that files were
>> still in use. Using the Process Explorer (after of the Sysinternals toolkit)
>> I found that the indexing service had a file open within the folder. Killing
>> the process fixed the issue.
>>
>> Not sure if this will help, but it's worth checking.
>
> Yes, it is worth checking. I'm fairly sure I have indexer turned off -
> waste of cpus.
>
> I also use unlocker which can tell me what process has lock files open as well.
>
> Will find out tomorrow at work.
> Cheers
>

Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Barrie Treloar <ba...@gmail.com>.
On Tue, Oct 6, 2009 at 6:23 PM, Stuart Roe <st...@ovic.co.uk> wrote:
> Barry,
>
> If you stop SMX can you delete the data folder in the SMX installation?
>
> I have previously had a problem where the Windows Content Index Service
> (cisvc.exe) was processing file in the data folder and the deletion
> operation failed. It interferred with the undeployment and redeployment of
> SA to SMX.
>
> I stopped SMX and tried to delete the data folder and found that files were
> still in use. Using the Process Explorer (after of the Sysinternals toolkit)
> I found that the indexing service had a file open within the folder. Killing
> the process fixed the issue.
>
> Not sure if this will help, but it's worth checking.

Yes, it is worth checking. I'm fairly sure I have indexer turned off -
waste of cpus.

I also use unlocker which can tell me what process has lock files open as well.

Will find out tomorrow at work.
Cheers

RE: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Posted by Stuart Roe <st...@ovic.co.uk>.
Barry,

If you stop SMX can you delete the data folder in the SMX installation?

I have previously had a problem where the Windows Content Index Service
(cisvc.exe) was processing file in the data folder and the deletion
operation failed. It interferred with the undeployment and redeployment of
SA to SMX.

I stopped SMX and tried to delete the data folder and found that files were
still in use. Using the Process Explorer (after of the Sysinternals toolkit)
I found that the indexing service had a file open within the folder. Killing
the process fixed the issue.

Not sure if this will help, but it's worth checking.

Stuart.

-----Original Message-----
From: Barrie Treloar [mailto:baerrach@gmail.com] 
Sent: 05 October 2009 23:55
To: users@servicemix.apache.org
Subject: Re: Deployment errors with ServiceMix 3.3.1 on Windows XP sp2

Repost after 2 weeks, hoping someone can provide some enlightenment.
Thanks.

On Wed, Sep 23, 2009 at 5:03 PM, Barrie Treloar <ba...@gmail.com> wrote:
> Firstly apologies for the length of this post, Google hasn't been 
> helpful when trying to resolve this.
> I'm hoping I've only included the relevant bits of the error output 
> that are useful.
>
> I am getting deployment errors with ServiceMix 3.3.1 on Windows XP sp2.
>
> I have three scenarios:
> (fails)  Scenario 1: ServiceMix freshly started, SA is deployed and 
> started, deploy new version of SA
> (pass) Scenario 2: After Scenario 1, re-run deployment
> (fails)  Scenario 3: Rebuilding SA and redploying.
>
> I get errors at Scenario 1 and 3 where I dont expect any errors, 
> especially since Scenario 2 just re-runs the deployment step straight 
> after the failure from 1.
>
> Details of what I am doing and the output follows.
> Suggestions, pointers, hints all gratefully accepted.
>
> Thanks.
> Barrie
>
> ===
> Scenario 1: ServiceMix freshly started, SA is deployed and started, 
> deploy new version of SA
>
> Trying to install new version os SA via mvn jbi:projectDeploy 
> -DforceUpdate=true
>
> Gives
> [ERROR] BUILD ERROR
> [INFO] 
> ----------------------------------------------------------------------
> -- [INFO] Unable to deploy project, Error accessing ServiceMix 
> administration
>
> org/apache/servicemix/common/ManagementSupport$Message
>
> With ServiceMix console output:
> WARN  - InstallationService            - Failed to delete old 
> installation directory:
> D:\apache-servicemix\apache-servicemix-3.3.1\data\smx\components\servi
> cemix-jms\version_17 INFO  - ComponentMBeanImpl             - Starting 
> component: servicemix-jms WARN  - InstallationService            - 
> Failed to delete old installation directory:
> D:\apache-servicemix\apache-servicemix-3.3.1\data\smx\components\servi
> cemix-file\version_11 INFO  - ComponentMBeanImpl             - 
> Starting component: servicemix-file WARN  - InstallationService          
 
> - Failed to delete old installation directory:
> D:\apache-servicemix\apache-servicemix-3.3.1\data\smx\components\servi
> cemix-camel\version_16 INFO  - ComponentMBeanImpl             - 
> Starting component: servicemix-camel INFO  - ServiceAssemblyLifeCycle    
  
> - Shutting down service assembly: mcp-sa INFO  - 
> ServiceAssemblyLifeCycle       - Stopping service assembly: mcp-sa 
> INFO  - ServiceUnitLifeCycle           - Stopping service unit: 
> mcp-eip-su INFO  - ServiceUnitLifeCycle           - Stopping service 
> unit: mcp-file-su INFO  - ServiceUnitLifeCycle           - Stopping 
> service unit: mcp-jms-su INFO  - ServiceUnitLifeCycle           - 
> Shutting down service unit: mcp-eip-su INFO  - ServiceUnitLifeCycle      
    
> - Shutting down service unit: mcp-file-su INFO  - ServiceUnitLifeCycle    
      
> - Shutting down service unit: mcp-jms-su INFO  - 
> ServiceAssemblyLifeCycle       - Shutting down service assembly: 
> mcp-sa INFO  - ServiceAssemblyLifeCycle       - Stopping service 
> assembly: mcp-sa
>
> But no further information as to why this failed.
>
> ===
> Scenario 2: After Scenario 1, re-run deployment
>
> If I re-run the same command
> mvn jbi:projectDeploy -DforceUpdate=true
>
> Then the deployment is successful.
>
> ===
> Scenario 3: Rebuilding SA and redploying.
>
> Same mvn command:
> mvn jbi:projectDeploy -DforceUpdate=true
>
> Gives error:
> [INFO] Unable to deploy project, Error accessing ServiceMix 
> administration
>
> <?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>shutDown</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> <component-task-result 
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> </jbi-task-result> </jbi-task>
>
> And the console gives:
> INFO  - ServiceAssemblyLifeCycle       - Stopping service assembly: 
> mcp-sa INFO  - ServiceUnitLifeCycle           - Stopping service unit: 
> mcp-eip-su INFO  - ServiceUnitLifeCycle           - Stopping service 
> unit: mcp-file-su INFO  - ServiceUnitLifeCycle           - Stopping 
> service unit: mcp-jms-su INFO  - ServiceAssemblyLifeCycle       - 
> Shutting down service assembly: mcp-sa INFO  - ServiceUnitLifeCycle      
    
> - Shutting down service unit: mcp-eip-su INFO  - ServiceUnitLifeCycle    
      
> - Shutting down service unit: mcp-file-su INFO  - ServiceUnitLifeCycle    
      
> - Shutting down service unit: mcp-jms-su INFO  - JBIContainer            
      
> - Deactivating component servicemix-jms WARN  - EnvironmentContext        
    
> - Failed to remove directory structure for component [version]: 
> servicemix-jms [s ervicemix-jms] WARN  - InstallationService            
> - Failed to delete old installation directory: 
> D:\apache-servicemix\apache-servic
> emix-3.3.1\data\smx\components\servicemix-jms\version_17
> INFO  - ComponentMBeanImpl             - Starting component: 
> servicemix-jms INFO  - ComponentMBeanImpl             - Initializing 
> component: servicemix-jms INFO  - ServiceAssemblyLifeCycle       - 
> Starting service assembly: mcp-sa INFO  - ServiceUnitLifeCycle           
> - Initializing service unit: mcp-eip-su INFO  - ServiceUnitLifeCycle      
    
> - Initializing service unit: mcp-file-su INFO  - ServiceUnitLifeCycle    
      
> - Initializing service unit: mcp-jms-su INFO  - JBIContainer              
    
> - Deactivating component servicemix-file WARN  - EnvironmentContext      
      
> - Failed to remove directory structure for component [version]: 
> servicemix-file [ servicemix-file] WARN  - InstallationService            
> - Failed to delete old installation directory: 
> D:\apache-servicemix\apache-servic
> emix-3.3.1\data\smx\components\servicemix-file\version_11
> INFO  - ComponentMBeanImpl             - Starting component: 
> servicemix-file INFO  - ComponentMBeanImpl             - Initializing 
> component: servicemix-file INFO  - JBIContainer                   - 
> Deactivating component servicemix-camel WARN  - EnvironmentContext        
    
> - Failed to remove directory structure for component [version]: 
> servicemix-camel [servicemix-camel] WARN  - InstallationService          
 
> - Failed to delete old installation directory: 
> D:\apache-servicemix\apache-servic
> emix-3.3.1\data\smx\components\servicemix-camel\version_16
> INFO  - ComponentMBeanImpl             - Starting component: 
> servicemix-camel INFO  - ComponentMBeanImpl             - Initializing
component:
> servicemix-camel
> INFO  - ServiceUnitLifeCycle           - Starting service unit: 
> mcp-eip-su INFO  - ServiceUnitLifeCycle           - Starting service 
> unit: mcp-file-su INFO  - ServiceUnitLifeCycle           - Starting 
> service unit: mcp-jms-su ERROR - Registry                       - 
> Error trying to restore service assembly state
> 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>start</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> <component-task-result 
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> </jbi-task-result> </jbi-task>
>
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:125)
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:111)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Ser
> viceAssemblyLifeCycle.java:168)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(S
> erviceAssemblyLifeCycle.java:364)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(S
> erviceAssemblyLifeCycle.java:353)
>        at 
> org.apache.servicemix.jbi.framework.Registry.startPendingAssemblies(Re
> gistry.java:864)
>        at 
> org.apache.servicemix.jbi.framework.Registry$1.run(Registry.java:840)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> tor.java:650)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:675)
>        at java.lang.Thread.run(Thread.java:595)
> INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: 
> mcp-sa INFO  - ServiceUnitLifeCycle           - Starting service unit: 
> mcp-eip-su INFO  - ServiceUnitLifeCycle           - Starting service 
> unit: mcp-file-su ERROR - Registry                       - Error 
> trying to restore service assembly state
> 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>start</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> <component-task-result 
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> </jbi-task-result> </jbi-task>
>
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:125)
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:111)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Ser
> viceAssemblyLifeCycle.java:168)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(S
> erviceAssemblyLifeCycle.java:364)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(S
> erviceAssemblyLifeCycle.java:353)
>        at 
> org.apache.servicemix.jbi.framework.Registry.startPendingAssemblies(Re
> gistry.java:864)
>        at 
> org.apache.servicemix.jbi.framework.Registry$1.run(Registry.java:840)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> tor.java:650)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:675)
>        at java.lang.Thread.run(Thread.java:595)
> INFO  - ServiceAssemblyLifeCycle       - Starting service assembly: 
> mcp-sa INFO  - ServiceUnitLifeCycle           - Starting service unit: 
> mcp-eip-su INFO  - ServiceUnitLifeCycle           - Starting service 
> unit: mcp-file-su ERROR - Registry                       - Error 
> trying to restore service assembly state
> 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>start</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> <component-task-result 
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>start</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> </jbi-task-result> </jbi-task>
>
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:125)
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:111)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(Ser
> viceAssemblyLifeCycle.java:168)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(S
> erviceAssemblyLifeCycle.java:364)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.restore(S
> erviceAssemblyLifeCycle.java:353)
>        at 
> org.apache.servicemix.jbi.framework.Registry.startPendingAssemblies(Re
> gistry.java:864)
>        at 
> org.apache.servicemix.jbi.framework.Registry$1.run(Registry.java:840)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecu
> tor.java:650)
>        at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
> java:675)
>        at java.lang.Thread.run(Thread.java:595)
> INFO  - ServiceAssemblyLifeCycle       - Shutting down service 
> assembly: mcp-sa INFO  - ServiceAssemblyLifeCycle       - Stopping 
> service assembly: mcp-sa INFO  - ServiceUnitLifeCycle           - 
> Stopping service unit: mcp-jms-su INFO  - ServiceUnitLifeCycle           
> - Shutting down service unit: mcp-eip-su INFO  - ServiceUnitLifeCycle    
      
> - Shutting down service unit: mcp-file-su INFO  - ServiceUnitLifeCycle    
      
> - Shutting down service unit: mcp-jms-su INFO  - DeploymentService        
     
> - Error in shutDown
> 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>shutDown</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> <component-task-result 
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> </jbi-task-result> </jbi-task>
>
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:125)
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:111)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.shutDown(
> ServiceAssemblyLifeCycle.java:260)
>        at 
> org.apache.servicemix.jbi.framework.DeploymentService.shutDown(Deploym
> entService.java:426)
>        at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServic
> eAssembly(AutoDeploymentService.java:32
> 8)
>        at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchiv
> e(AutoDeploymentService.java:255)
>        at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateExtern
> alArchive(AutoDeploymentService.java:20
> 5)
>        at 
> org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive
> (JBIContainer.java:494)
>        at 
> org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive
> (JBIContainer.java:504)
>        at 
> org.apache.servicemix.jbi.framework.AdminCommandsService.deployService
> Assembly(AdminCommandsService.java:209)
>
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39)
>        at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at 
> org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java
> :216)
>        at 
> org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStan
> dardMBean.java:323)
>        at 
> com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl
> .java:213)
>        at 
> com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>        at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMB
> eanServerInterceptor.java:815)
>        at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectio
> nImpl.java:1410)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnection
> Impl.java:81)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(
> RMIConnectionImpl.java:1247)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RM
> IConnectionImpl.java:1350)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl
> .java:784)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39)
>        at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>        at sun.rmi.transport.Transport$1.run(Transport.java:153)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>        at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:46
> 6)
>        at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.
> java:707)
>        at java.lang.Thread.run(Thread.java:595)
> ERROR - AutoDeploymentService          - Failed to update Service
> Assembly: mcp-sa
> 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>shutDown</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-camel</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-eip-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> <component-task-result 
> xmlns="http://java.sun.com/xml/ns/jbi/management-message">
>        <component-name>servicemix-file</component-name>
>        <component-task-result-details>
>                <task-result-details>
>                        <task-id>shutDown</task-id>
>                        <task-result>FAILED</task-result>
>                        <message-type>ERROR</message-type>
>                        <task-status-msg> <msg-loc-info> <loc-token/> 
> <loc-message>Service Unit 'mcp-file-su' is not deployed</loc-message> 
> </msg-loc-info> </task-status-msg>
>                </task-result-details>
>        </component-task-result-details> </component-task-result> 
> </jbi-task-result> </jbi-task>
>
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:125)
>        at 
> org.apache.servicemix.jbi.framework.ManagementSupport.failure(Manageme
> ntSupport.java:111)
>        at 
> org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.shutDown(
> ServiceAssemblyLifeCycle.java:260)
>        at 
> org.apache.servicemix.jbi.framework.DeploymentService.shutDown(Deploym
> entService.java:426)
>        at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateServic
> eAssembly(AutoDeploymentService.java:32
> 8)
>        at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateArchiv
> e(AutoDeploymentService.java:255)
>        at 
> org.apache.servicemix.jbi.framework.AutoDeploymentService.updateExtern
> alArchive(AutoDeploymentService.java:20
> 5)
>        at 
> org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive
> (JBIContainer.java:494)
>        at 
> org.apache.servicemix.jbi.container.JBIContainer.updateExternalArchive
> (JBIContainer.java:504)
>        at 
> org.apache.servicemix.jbi.framework.AdminCommandsService.deployService
> Assembly(AdminCommandsService.java:209)
>
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39)
>        at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at 
> org.apache.commons.beanutils.MethodUtils.invokeMethod(MethodUtils.java
> :216)
>        at 
> org.apache.servicemix.jbi.management.BaseStandardMBean.invoke(BaseStan
> dardMBean.java:323)
>        at 
> com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl
> .java:213)
>        at 
> com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
>        at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMB
> eanServerInterceptor.java:815)
>        at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectio
> nImpl.java:1410)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnection
> Impl.java:81)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(
> RMIConnectionImpl.java:1247)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RM
> IConnectionImpl.java:1350)
>        at 
> javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl
> .java:784)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:39)
>        at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccess
> orImpl.java:25)
>        at java.lang.reflect.Method.invoke(Method.java:585)
>        at 
> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
>        at sun.rmi.transport.Transport$1.run(Transport.java:153)
>        at java.security.AccessController.doPrivileged(Native Method)
>        at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
>        at 
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:46
> 6)
>        at 
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.
> java:707)
>        at java.lang.Thread.run(Thread.java:595)
>
>
> At this point I have to restart ServiceMix. Which takes me back 
> through the Scenario 1, then Scenario 2 cycle.
>