Note that there are some explanatory texts on larger screens.

plurals
  1. POWSO2 ESB Deployment Synchronizer stuck (can't gracefully shutdown or deploy services)
    text
    copied!<p>We are facing some issues with WSO2 ESB sincronizer, since we have a clustered configuration, we are using svn to store the content of "repository/deployment/server". The carbon.xml configuration is the following:</p> <pre><code>&lt;DeploymentSynchronizer&gt; &lt;Enabled&gt;true&lt;/Enabled&gt; &lt;AutoCommit&gt;false&lt;/AutoCommit&gt;&lt;!--true for the mgt node--&gt; &lt;AutoCheckout&gt;true&lt;/AutoCheckout&gt; &lt;RepositoryType&gt;svn&lt;/RepositoryType&gt; &lt;SvnUrl&gt;https://svn/x/trunk/serverESB/desenv/&lt;/SvnUrl&gt; &lt;SvnUser&gt;user&lt;/SvnUser&gt; &lt;SvnPassword&gt;password&lt;/SvnPassword&gt; &lt;SvnUrlAppendTenantId&gt;false&lt;/SvnUrlAppendTenantId&gt; &lt;/DeploymentSynchronizer&gt; </code></pre> <p>It works correctly for some time, but after some deploys and undeploys it stops working. Although it still gives the message that it is going to sincronize and the svn update seems to be corectly performed, the esb does not load the newly deployed XMLs:</p> <pre><code>TID: [0] [ESB] INFO {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Received [SynchronizeRepositoryRequest{tenantId=-1234, tenantDomain='carbon.super', messageId=f9b51e23-8a3c-4f08-acb0-5a1f0f4590b2}] {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} TID: [0] [ESB] INFO {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} - Going to synchronse artefacts. {org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest} </code></pre> <p>Normally after this message it prints INFO saying that new services where deployed, but it does no occour.</p> <p>When i try to shutdown the server it gives me the message "Waiting for deployment completion...", and gets stuck (so i have to kill using "kill -9"):</p> <pre><code>TID: [0] [ESB] INFO {org.wso2.carbon.core.ServerManagement} - Waiting for deployment completion... {org.wso2.carbon.core.ServerManagement} </code></pre> <p>If I manually restarts it, all the deployments will work fine, and the sincronizer will start to work fine again (for some time).</p> <p>p.s: I've tryed to use the OS's svn (SuSe) and also the SVNKit module. Our svn repository version is 1.5.1.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload