[ 
https://issues.apache.org/activemq/browse/SM-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56637#action_56637
 ] 

Sergiy Mamitko commented on SM-1920:
------------------------------------

Hi Freeman,

The situation is not exactly in xbean.xml but in implementation of Deployer 
interface and class BaseServiceUnitManager. Why last one asks Deployer for 
possibility to deploy when really going to perform undeploy? Maybe Deployer 
interface need method canUndeploy()?

Yes, it is possible to remove data folder, but it will not clean up some 
registries without restarting servicemix. Restart of SMX is not accepted in our 
scenarious.
That is why during next deployment (Now I copy SA *.zip to install or hotdeploy 
folder) SA will not be installed successfully because it is already registered 
(or some SU already registered).

So, question is how to successfully undeploy or redeploy SA without restart of 
SMX if some registries were not cleaned up successfully?

Sergiy M

> Deployment/Undeployment troubles if one of already deployed SU doesn't 
> contain xbean.xml file in serviceUnitRootPath
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: SM-1920
>                 URL: https://issues.apache.org/activemq/browse/SM-1920
>             Project: ServiceMix
>          Issue Type: Bug
>          Components: servicemix-core
>    Affects Versions: 3.3.1
>            Reporter: Sergiy Mamitko
>            Assignee: Freeman Fang
>
> If for some unknown reasons file xbean.xml was removed from deployed SU (from 
> serviceUnitRootPath) then it is impossible to remove a whole SA without 
> forther troubles.
> Looking into sources there is Deployer.canDeploy method which is used in 
> implementations for doDeploy and for doUndeploy. But if xbean.xml is 
> necessary for deployment why it is need for undeployment process. 
> Moreover if xbean is absent, then SU will not be unregistered from component 
> and it will be impossible to redeploy the same SA.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to