[prev in list] [next in list] [prev in thread] [next in thread]
List: esb-java-dev
Subject: Re: [Dev] How to resolve SVN errors of worker nodes at server startup
From: Evanthika Amarasiri <evanthika () wso2 ! com>
Date: 2015-05-30 13:49:40
Message-ID: CAA=mr52Qq5m6qvmEYXb9zOT5SnTGVj4Orn9CcLmNNhhgjbOSCw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi all,
For products like ESB/API-M when we are replacing the packs with new ones,
we continuously see this behaviour while starting up the worker nodes. The
solution we have given is to clean the repo, start the server once, when
you get the exception '*The synapse.xml location
././repository/deployment/server/synapse-configs/default doesn't
exist*', restart
the server once again. I'm wondering whether this the correct solution?
Also, will we be seeing the same behaviour with Carbon 4.3.0 products as
well?
Regards,
Evanthika
On Thu, Dec 4, 2014 at 11:23 AM, Samuel Gnaniah <samuel@wso2.com> wrote:
> Updated the note for API-M [1] and ESB [2] to include instructions to
> restart the server once again.
>
> [1] - https://docs.wso2.com/display/CLUSTER420/Clustering+the+Gateway
> [2] - https://docs.wso2.com/display/CLUSTER420/Clustering+ESB
>
> *Samuel Gnaniah*
> Senior Technical Writer
>
> WSO2 (pvt.) Ltd.
> Colombo, Sri Lanka
> (+94) 773131798
>
> On Wed, Dec 3, 2014 at 12:03 PM, Evanthika Amarasiri <evanthika@wso2.com>
> wrote:
>
> > This note is applicable for products like AS/BPS/etc. But for products
> > like API-M & ESB, the first time you restart the server after cleaning the
> > *server* folder will throw the exception - '*The synapse.xml location
> > ././repository/deployment/server/synapse-configs/default doesn't exist*'.
> >
> > So to resolve that, you have to restart the server once again. We need to
> > find a proper solution for that.
> >
> > Regards,
> > Evanthika Amarasiri
> > Senior Technical Lead - Quality Assurance
> > Mobile: +94773125935
> > Blog: evanthika.blogspot.com
> >
> > wso2.com lean.enterprise.middleware
> >
> > On Wed, Dec 3, 2014 at 11:53 AM, Samuel Gnaniah <samuel@wso2.com> wrote:
> >
> > > Added a small note on this in [1], [2] and [3]. Thanks for bringing this
> > > up!
> > >
> > > [1] -
> > > https://docs.wso2.com/display/CLUSTER420/Configuring+the+Worker+Node
> > > [2] -
> > > https://docs.wso2.com/display/CLUSTER420/Clustering+WSO2+Products+without+WSO2+ELB
> > > [3] - https://docs.wso2.com/display/CLUSTER420/Clustering+the+Gateway
> > >
> > > Thanks,
> > > Sam
> > >
> > > *Samuel Gnaniah*
> > > Senior Technical Writer
> > >
> > > WSO2 (pvt.) Ltd.
> > > Colombo, Sri Lanka
> > > (+94) 773131798
> > >
> > > On Wed, Dec 3, 2014 at 11:35 AM, Evanthika Amarasiri <evanthika@wso2.com
> > > > wrote:
> > >
> > > > Yes. This is only for worker nodes.
> > > >
> > > > Regards,
> > > > Evanthika
> > > >
> > > > On Wed, Dec 3, 2014 at 9:39 AM, Samuel Gnaniah <samuel@wso2.com> wrote:
> > > >
> > > > > Just to confirm, are we recommending this only in the worker nodes?
> > > > >
> > > > > *Samuel Gnaniah*
> > > > > Senior Technical Writer
> > > > >
> > > > > WSO2 (pvt.) Ltd.
> > > > > Colombo, Sri Lanka
> > > > > (+94) 773131798
> > > > >
> > > > > On Wed, Dec 3, 2014 at 8:34 AM, Sameera Jayasoma <sameera@wso2.com>
> > > > > wrote:
> > > > >
> > > > > > Even for Carbon 4.3.0 testing, we followed the same method. We will
> > > > > > try to fix these errors during the AS 6.0.0 release. But for 4.2.0 based
> > > > > > products, lets document this step.
> > > > > >
> > > > > > Thanks,
> > > > > > Sameera.
> > > > > >
> > > > > >
> > > > > > On Wed, Dec 3, 2014 at 7:47 AM, Evanthika Amarasiri <
> > > > > > evanthika@wso2.com> wrote:
> > > > > >
> > > > > > > Yes Sameera, I got this continuously on
> > > > > > >
> > > > > > > API-M worker nodes yesterday. So, after this SVN error, I see
> > > > > > > another exception with regard to service initialisation due to a \
> > > > > > > missing module as below.
> > > > > > >
> > > > > > > So I suppose there are can be functionality breaks once you get this
> > > > > > > svn issue. Anyhow, throwing such ERRORs at startup is not right. So if
> > > > > > > these are harmless errors we can make them warnings instead without
> > > > > > > printing a whole stack trace like this?
> > > > > > >
> > > > > > > However, in this case, what I feel is that there can be
> > > > > > > functionality issues. I will investigate on this further.
> > > > > > >
> > > > > > > Also, if this is what we recommend to users (removing the content
> > > > > > > inside the server folder before starting worker nodes), shall we add \
> > > > > > > this to our documentation?
> > > > > > >
> > > > > > >
> > > > > > > TID: [0] [AM] [2014-12-02 06:30:15,390] ERROR
> > > > > > > {org.wso2.carbon.core.persistence.AbstractPersistenceManager} - Unable \
> > > > > > > to handle service initialization. Service: WSRegistryService
> > > > > > > {org.wso2.carbon.core.persistence.AbstractPersistenceManager}
> > > > > > > org.wso2.carbon.CarbonException: *Axis Module not found for :
> > > > > > > addressing-4.2.0*
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.AbstractPersistenceManager.getExistingAxisModule(AbstractPersistenceManager.java:583)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:469)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.file.deployer.PersistenceMetaDataDeployer.deploy(PersistenceMetaDataDeployer.java:96)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
> > > > > > > at
> > > > > > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > > > > > > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> > > > > > > at
> > > > > > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> > > > > > > at
> > > > > > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> > > > > > > at
> > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > > > > > > at
> > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > > > > > at java.lang.Thread.run(Thread.java:745)
> > > > > > > TID: [0] [AM] [2014-12-02 06:30:15,391] ERROR
> > > > > > > {org.wso2.carbon.core.persistence.file.deployer.PersistenceMetaDataDeployer}
> > > > > > >
> > > > > > > - Unable to handle service initialization. Service: WSRegistryService
> > > > > > > {org.wso2.carbon.core.persistence.file.deployer.PersistenceMetaDataDeployer}
> > > > > > >
> > > > > > > org.wso2.carbon.core.persistence.PersistenceException: Unable to
> > > > > > > handle service initialization. Service: WSRegistryService
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.AbstractPersistenceManager.handleExceptionWithRollback(AbstractPersistenceManager.java:603)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:744)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.file.deployer.PersistenceMetaDataDeployer.deploy(PersistenceMetaDataDeployer.java:96)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)
> > > > > > > at
> > > > > > > org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)
> > > > > > > at
> > > > > > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > > > > > > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> > > > > > > at
> > > > > > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> > > > > > > at
> > > > > > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> > > > > > > at
> > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > > > > > > at
> > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > > > > > at java.lang.Thread.run(Thread.java:745)
> > > > > > > Caused by: org.wso2.carbon.CarbonException: Axis Module not found
> > > > > > > for : addressing-4.2.0
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.AbstractPersistenceManager.getExistingAxisModule(AbstractPersistenceManager.java:583)
> > > > > > > at
> > > > > > > org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:469)
> > > > > > >
> > > > > > > ... 18 more
> > > > > > >
> > > > > > > Regards,
> > > > > > > Evanthika
> > > > > > >
> > > > > > >
> > > > > > > On Tuesday, December 2, 2014, Sameera Jayasoma <sameera@wso2.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > If you unzip a fresh pack and configure svn depsync with an already
> > > > > > > > populated svn repository, then you will see such errors. I believe \
> > > > > > > > these are harmless errors. Evanthika, do you get these errors every \
> > > > > > > > time you restart? Also does this break any functionality?
> > > > > > > >
> > > > > > > > Our recommendation is to delete the repository/deployment/server
> > > > > > > > directory and create an empty server directory. This way we can avoid \
> > > > > > > > svn conflicts etc. We've been recommending this approach to users.
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Sameera.
> > > > > > > >
> > > > > > > > On Tue, Dec 2, 2014 at 6:17 PM, Evanthika Amarasiri <
> > > > > > > > evanthika@wso2.com> wrote:
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > While testing API-M 1.8.0, I noticed the following exception on
> > > > > > > > > all gateway worker nodes.
> > > > > > > > >
> > > > > > > > > TID: [0] [AM] [2014-12-02 07:02:05,108] ERROR
> > > > > > > > > {org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository}
> > > > > > > > >
> > > > > > > > > - Error while checking out or updating artifacts from the SVN \
> > > > > > > > > repository \
> > > > > > > > > {org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository}
> > > > > > > > > org.tigris.subversion.svnclientadapter.SVNClientException:
> > > > > > > > > org.tigris.subversion.javahl.ClientException: svn: Failed to add \
> > > > > > > > > directory 'modulemetafiles': an unversioned directory of the same \
> > > > > > > > > name already exists at
> > > > > > > > > org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.checkout(AbstractJhlClientAdapter.java:297)
> > > > > > > > > at
> > > > > > > > > org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.checkout(SVNBasedArtifactRepository.java:419)
> > > > > > > > > at
> > > > > > > > > org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizer.checkout(DeploymentSynchronizer.java:181)
> > > > > > > > > at
> > > > > > > > > org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:87)
> > > > > > > > > at
> > > > > > > > > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:165)
> > > > > > > > > at
> > > > > > > > > org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:123)
> > > > > > > > > at
> > > > > > > > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> > > > > > > > > at \
> > > > > > > > > java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at
> > > > > > > > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> > > > > > > > > at
> > > > > > > > > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> > > > > > > > > at
> > > > > > > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> > > > > > > > > at
> > > > > > > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> > > > > > > > > at java.lang.Thread.run(Thread.java:745)
> > > > > > > > > Caused by: org.tigris.subversion.javahl.ClientException: svn:
> > > > > > > > > Failed to add directory 'modulemetafiles': an unversioned directory \
> > > > > > > > > of the same name already exists
> > > > > > > > > at
> > > > > > > > > org.tigris.subversion.javahl.JavaHLObjectFactory.throwException(JavaHLObjectFactory.java:777)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.javahl.SVNClientImpl.throwException(SVNClientImpl.java:1850)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.javahl.SVNClientImpl.checkout(SVNClientImpl.java:1976)
> > > > > > > > > at
> > > > > > > > > org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.checkout(AbstractJhlClientAdapter.java:287)
> > > > > > > > >
> > > > > > > > > ... 12 more
> > > > > > > > > Caused by: org.tmatesoft.svn.core.SVNException: svn: Failed to add
> > > > > > > > > directory 'modulemetafiles': an unversioned directory of the same \
> > > > > > > > > name already exists
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:623)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:274)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:262)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:266)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1261)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:818)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:558)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:934)
> > > > > > > > > at
> > > > > > > > > org.tmatesoft.svn.core.javahl.SVNClientImpl.checkout(SVNClientImpl.java:1973)
> > > > > > > > >
> > > > > > > > > ... 13 more
> > > > > > > > >
> > > > > > > > > After discussing with the Carbon team, found out that the solution
> > > > > > > > > is to delete the *$API_HOME/repository/deployment/server* folder
> > > > > > > > > the first time you start the server. This works for products like
> > > > > > > > > AS/DSS/BPS,etc.
> > > > > > > > >
> > > > > > > > > However, for products like API-M, ESB, the first time you start
> > > > > > > > > the server, it will throw the exception '*The synapse.xml
> > > > > > > > > location ././repository/deployment/server/synapse-configs/default \
> > > > > > > > > doesn't exist*'. The solution right now is to restart the server \
> > > > > > > > > which IMO is not a correct solution and should be handled in some \
> > > > > > > > > other way.
> > > > > > > > > We have come across this issue with almost all the products and
> > > > > > > > > have reported the same many times. So I suppose it's time we \
> > > > > > > > > finalize on this solution and document it.
> > > > > > > > >
> > > > > > > > > @Sameera, appreciate your feedback on this.
> > > > > > > > >
> > > > > > > > > Regards,
> > > > > > > > > Evanthika Amarasiri
> > > > > > > > > Senior Technical Lead - Quality Assurance
> > > > > > > > > Mobile: +94773125935
> > > > > > > > > Blog: evanthika.blogspot.com
> > > > > > > > >
> > > > > > > > > wso2.com lean.enterprise.middleware
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Sameera Jayasoma,
> > > > > > > > Software Architect,
> > > > > > > >
> > > > > > > > WSO2, Inc. (http://wso2.com)
> > > > > > > > email: sameera@wso2.com
> > > > > > > > blog: http://sameera.adahas.org
> > > > > > > > twitter: https://twitter.com/sameerajayasoma
> > > > > > > > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> > > > > > > > Mobile: 0094776364456
> > > > > > > >
> > > > > > > > Lean . Enterprise . Middleware
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sameera Jayasoma,
> > > > > > Software Architect,
> > > > > >
> > > > > > WSO2, Inc. (http://wso2.com)
> > > > > > email: sameera@wso2.com
> > > > > > blog: http://sameera.adahas.org
> > > > > > twitter: https://twitter.com/sameerajayasoma
> > > > > > flickr: http://www.flickr.com/photos/sameera-jayasoma/collections
> > > > > > Mobile: 0094776364456
> > > > > >
> > > > > > Lean . Enterprise . Middleware
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > Dev mailing list
> > > > > > Dev@wso2.org
> > > > > > http://wso2.org/cgi-bin/mailman/listinfo/dev
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
[Attachment #5 (text/html)]
<div dir="ltr"><div class="gmail_default" style="font-family:'trebuchet \
ms',sans-serif">Hi all,</div><div class="gmail_default" \
style="font-family:'trebuchet ms',sans-serif"><br></div><div \
class="gmail_default" style="font-family:'trebuchet ms',sans-serif">For \
products like ESB/API-M when we are replacing the packs with new ones, we \
continuously see this behaviour while starting up the worker nodes. The solution we \
have given is to clean the repo, start the server once, when you get the exception \
<span style="font-size:13px">'</span><i style="font-size:13px">The synapse.xml \
location ././repository/deployment/server/synapse-configs/default doesn't \
exist</i><span style="font-size:13px">', </span>restart the server once again. \
I'm wondering whether this the correct solution?</div><div class="gmail_default" \
style="font-family:'trebuchet ms',sans-serif"><br></div><div \
class="gmail_default" style="font-family:'trebuchet ms',sans-serif">Also, \
will we be seeing the same behaviour with Carbon 4.3.0 products as well? \
<br></div><div class="gmail_default" style="font-family:'trebuchet \
ms',sans-serif"><br></div><div class="gmail_default" \
style="font-family:'trebuchet ms',sans-serif">Regards,</div><div \
class="gmail_default" style="font-family:'trebuchet \
ms',sans-serif">Evanthika</div><div class="gmail_extra"> <br><div \
class="gmail_quote">On Thu, Dec 4, 2014 at 11:23 AM, Samuel Gnaniah <span \
dir="ltr"><<a href="mailto:samuel@wso2.com" \
target="_blank">samuel@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div style="font-size:small">Updated the note for API-M [1] and ESB [2] to \
include instructions to restart the server once again.</div><div \
style="font-size:small"><br></div><div>[1] - <a \
href="https://docs.wso2.com/display/CLUSTER420/Clustering+the+Gateway" \
target="_blank">https://docs.wso2.com/display/CLUSTER420/Clustering+the+Gateway</a><br></div><div>[2] \
- <a href="https://docs.wso2.com/display/CLUSTER420/Clustering+ESB" \
target="_blank">https://docs.wso2.com/display/CLUSTER420/Clustering+ESB</a><br></div></div><div \
class="gmail_extra"><span><br clear="all"><div><div><div dir="ltr"><b>Samuel \
Gnaniah</b><div>Senior Technical Writer</div><div><br></div><div><font size="1">WSO2 \
(pvt.) Ltd.</font></div><div><span \
style="color:rgb(67,67,67);font-family:Arial,Helvetica,Verdana,monospace,san-serif;line-height:20px;background-color:rgb(230,230,230)"><font \
size="1">Colombo, Sri Lanka</font></span><font size="1"><br></font></div><div><span \
style="color:rgb(67,67,67);font-family:Arial,Helvetica,Verdana,monospace,san-serif;line-height:20px;background-color:rgb(230,230,230)"><font \
size="1"><a href="tel:%28%2B94%29%20773131798" value="+94773131798" \
target="_blank">(+94) 773131798</a></font></span></div></div></div></div> \
<br></span><div><div><div class="gmail_quote">On Wed, Dec 3, 2014 at 12:03 PM, \
Evanthika Amarasiri <span dir="ltr"><<a href="mailto:evanthika@wso2.com" \
target="_blank">evanthika@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div style="font-family:'trebuchet ms',sans-serif">This note is \
applicable for products like AS/BPS/etc. But for products like API-M & ESB, the \
first time you restart the server after cleaning the <i>server</i> folder will throw \
the exception - <span style="font-size:13px">'</span><i \
style="font-size:13px">The synapse.xml location \
././repository/deployment/server/synapse-configs/default doesn't exist</i><span \
style="font-size:13px">'</span>.</div><div style="font-family:'trebuchet \
ms',sans-serif"><br></div><div style="font-family:'trebuchet \
ms',sans-serif">So to resolve that, you have to restart the server once again. We \
need to find a proper solution for that.</div><div style="font-family:'trebuchet \
ms',sans-serif"><br></div><div class="gmail_extra"><span><div><div><div \
dir="ltr"><div><div dir="ltr"><div><font face="trebuchet ms, sans-serif" \
size="1">Regards,</font></div><font face="trebuchet ms, sans-serif" \
size="1">Evanthika Amarasiri<br>Senior Technical Lead - Quality \
Assurance<br></font><div><font face="trebuchet ms, sans-serif" size="1">Mobile: <a \
href="tel:%2B94773125935" value="+94773125935" \
target="_blank">+94773125935</a></font></div><div><font face="trebuchet ms, \
sans-serif" size="1">Blog: <a href="http://evanthika.blogspot.com" \
target="_blank">evanthika.blogspot.com</a></font></div><div><span \
style="color:rgb(153,153,153)"><font color="#000000" face="trebuchet ms, sans-serif" \
size="1"><strong><br></strong></font></span></div><div><font color="#000000" \
face="trebuchet ms, sans-serif" size="1"><a href="http://wso2.com" \
target="_blank">wso2.com</a> \
lean.enterprise.middleware</font></div></div></div></div></div></div> \
<br></span><div><div><div class="gmail_quote">On Wed, Dec 3, 2014 at 11:53 AM, Samuel \
Gnaniah <span dir="ltr"><<a href="mailto:samuel@wso2.com" \
target="_blank">samuel@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div style="font-size:small">Added a small note on this in [1], [2] and \
[3]. Thanks for bringing this up!</div><div style="font-size:small"><br></div><div \
style="font-size:small">[1] - <a \
href="https://docs.wso2.com/display/CLUSTER420/Configuring+the+Worker+Node" \
target="_blank">https://docs.wso2.com/display/CLUSTER420/Configuring+the+Worker+Node</a></div><div \
style="font-size:small">[2] - <a \
href="https://docs.wso2.com/display/CLUSTER420/Clustering+WSO2+Products+without+WSO2+ELB" \
target="_blank">https://docs.wso2.com/display/CLUSTER420/Clustering+WSO2+Products+without+WSO2+ELB</a></div><div \
style="font-size:small">[3] - <a \
href="https://docs.wso2.com/display/CLUSTER420/Clustering+the+Gateway" \
target="_blank">https://docs.wso2.com/display/CLUSTER420/Clustering+the+Gateway</a></div><div \
style="font-size:small"><br></div><div style="font-size:small">Thanks,</div><div \
style="font-size:small">Sam</div></div><div class="gmail_extra"><span><br \
clear="all"><div><div><div dir="ltr"><b>Samuel Gnaniah</b><div>Senior Technical \
Writer</div><div><br></div><div><font size="1">WSO2 (pvt.) \
Ltd.</font></div><div><span \
style="color:rgb(67,67,67);font-family:Arial,Helvetica,Verdana,monospace,san-serif;line-height:20px;background-color:rgb(230,230,230)"><font \
size="1">Colombo, Sri Lanka</font></span><font size="1"><br></font></div><div><span \
style="color:rgb(67,67,67);font-family:Arial,Helvetica,Verdana,monospace,san-serif;line-height:20px;background-color:rgb(230,230,230)"><font \
size="1"><a href="tel:%28%2B94%29%20773131798" value="+94773131798" \
target="_blank">(+94) 773131798</a></font></span></div></div></div></div> \
<br></span><div><div><div class="gmail_quote">On Wed, Dec 3, 2014 at 11:35 AM, \
Evanthika Amarasiri <span dir="ltr"><<a href="mailto:evanthika@wso2.com" \
target="_blank">evanthika@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div style="font-family:'trebuchet ms',sans-serif">Yes. This is \
only for worker nodes.</div><div class="gmail_extra"><br clear="all"><div><div><div \
dir="ltr"><div dir="ltr"><div><font face="trebuchet ms, sans-serif" \
size="1">Regards,</font></div><font face="trebuchet ms, sans-serif" \
size="1">Evanthika<br></font></div></div></div></div><div><div> <br><div \
class="gmail_quote">On Wed, Dec 3, 2014 at 9:39 AM, Samuel Gnaniah <span \
dir="ltr"><<a href="mailto:samuel@wso2.com" \
target="_blank">samuel@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div style="font-size:small">Just to confirm, are we recommending this only \
in the worker nodes?</div></div><div class="gmail_extra"><br \
clear="all"><div><div><div dir="ltr"><b>Samuel Gnaniah</b><div>Senior Technical \
Writer</div><div><br></div><div><font size="1">WSO2 (pvt.) \
Ltd.</font></div><div><span \
style="color:rgb(67,67,67);font-family:Arial,Helvetica,Verdana,monospace,san-serif;line-height:20px;background-color:rgb(230,230,230)"><font \
size="1">Colombo, Sri Lanka</font></span><font size="1"><br></font></div><div><span \
style="color:rgb(67,67,67);font-family:Arial,Helvetica,Verdana,monospace,san-serif;line-height:20px;background-color:rgb(230,230,230)"><font \
size="1"><a href="tel:%28%2B94%29%20773131798" value="+94773131798" \
target="_blank">(+94) 773131798</a></font></span></div></div></div></div> <br><div \
class="gmail_quote"><div><div>On Wed, Dec 3, 2014 at 8:34 AM, Sameera Jayasoma <span \
dir="ltr"><<a href="mailto:sameera@wso2.com" \
target="_blank">sameera@wso2.com</a>></span> wrote:<br></div></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div \
dir="ltr">Even for Carbon 4.3.0 testing, we followed the same method. We will try to \
fix these errors during the AS 6.0.0 release. But for 4.2.0 based products, lets \
document this step.<div><br></div><div>Thanks,</div><div>Sameera.<div><div><br><div \
class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 3, 2014 at 7:47 AM, \
Evanthika Amarasiri <span dir="ltr"><<a href="mailto:evanthika@wso2.com" \
target="_blank">evanthika@wso2.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div style="font-family:'trebuchet \
ms',sans-serif;display:inline">Yes Sameera, I got this continuously on</div> \
<div style="font-family:'trebuchet ms',sans-serif;display:inline">API-M \
worker nodes yesterday. So, after this SVN error, I see another exception with \
regard to service initialisation due to a missing module as below. </div><div><div \
style="font-family:'trebuchet \
ms',sans-serif;display:inline"><br></div></div><div><div \
style="font-family:'trebuchet ms',sans-serif;display:inline">So I suppose \
there are can be functionality breaks once you get this svn issue. Anyhow, throwing \
such ERRORs at startup is not right. So if these are harmless errors we can make them \
warnings instead without printing a whole stack trace like this? </div><div><font \
face="trebuchet ms, sans-serif"><br></font></div><div><font face="trebuchet ms, \
sans-serif"><div style="font-family:'trebuchet \
ms',sans-serif;display:inline">However, in this case, what I feel is that \
there can be functionality issues. I will investigate on this \
further.</div></font></div><div><font face="trebuchet ms, \
sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif"><div \
style="font-family:'trebuchet ms',sans-serif;display:inline">Also, if this \
is what we recommend to users (removing the content inside the server folder before \
starting worker nodes), shall we add this to our \
documentation?</div><br></font><div><font face="trebuchet ms, \
sans-serif"><br></font></div><div><font face="trebuchet ms, sans-serif"><div><font \
size="1">TID: [0] [AM] [2014-12-02 06:30:15,390] ERROR \
{org.wso2.carbon.core.persistence.AbstractPersistenceManager} - Unable to handle \
service initialization. Service: WSRegistryService \
{org.wso2.carbon.core.persistence.AbstractPersistenceManager}</font></div><div><font \
size="1">org.wso2.carbon.CarbonException: <font color="#ff0000"><b>Axis Module not \
found for : addressing-4.2.0</b></font></font></div><div><font size="1"><span \
style="white-space:pre-wrap"> </span>at \
org.wso2.carbon.core.persistence.AbstractPersistenceManager.getExistingAxisModule(AbstractPersistenceManager.java:583)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.wso2.carbon.core.persistence.ServicePersistenceManager.handleExistingServiceInit(ServicePersistenceManager.java:469)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.wso2.carbon.core.persistence.file.deployer.PersistenceMetaDataDeployer.deploy(PersistenceMetaDataDeployer.java:96)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:807)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:377)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:254)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:371)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:59)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:67)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:79)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:124)</font></div><span><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)</font></div><div><font \
size="1"><span style="white-space:pre-wrap"> </span>at \
java.lang.Thread.run(Thread.java:745)</font></div></span><div><font size="1">TID: [0] \
[AM] [2014-12-02 06:30:15,391] ERROR \
{org.wso2.carbon.core.persistence.file.deployer.PersistenceMetaDataDeployer} - \
</div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div \
dir="ltr"><font color="#336666">Sameera Jayasoma,<br>Software \
Architect,</font><div><span style="color:rgb(51,102,102)"><br></span></div><div><span \
style="color:rgb(51,102,102)">WSO2, Inc. (</span><a href="http://wso2.com" \
target="_blank">http://wso2.com</a><span style="color:rgb(51,102,102)">)</span><font \
color="#336666"><br>email: <a>sameera@wso2.com</a><br>blog: </font><a \
href="http://sameera.adahas.org" \
target="_blank">http://sameera.adahas.org</a><div>twitter: <a \
href="https://twitter.com/sameerajayasoma" \
target="_blank">https://twitter.com/sameerajayasoma</a></div><div>flickr: <a \
href="http://www.flickr.com/photos/sameera-jayasoma/collections" \
target="_blank">http://www.flickr.com/photos/sameera-jayasoma/collections</a></div><div><span \
style="color:rgb(136,136,136)">Mobile: 0094776364456</span><br><br><font \
color="#336666">Lean . Enterprise . Middleware</font></div><div><font \
color="#336666"><br></font></div><div><font color="#336666"><img \
src="http://c.content.wso2.com/signatures/general.png" width="420" \
height="54"></font></div></div></div></div> </div></div>
</blockquote>
</div></div></div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div \
dir="ltr"><font color="#336666">Sameera Jayasoma,<br>Software \
Architect,</font><div><span style="color:rgb(51,102,102)"><br></span></div><div><span \
style="color:rgb(51,102,102)">WSO2, Inc. (</span><a href="http://wso2.com" \
target="_blank">http://wso2.com</a><span style="color:rgb(51,102,102)">)</span><font \
color="#336666"><br>email: <a href="mailto:sameera@wso2.com" \
target="_blank">sameera@wso2.com</a><br>blog: </font><a \
href="http://sameera.adahas.org" \
target="_blank">http://sameera.adahas.org</a><div>twitter: <a \
href="https://twitter.com/sameerajayasoma" \
target="_blank">https://twitter.com/sameerajayasoma</a></div><div>flickr: <a \
href="http://www.flickr.com/photos/sameera-jayasoma/collections" \
target="_blank">http://www.flickr.com/photos/sameera-jayasoma/collections</a></div><div><span \
style="color:rgb(136,136,136)">Mobile: 0094776364456</span><br><br><font \
color="#336666">Lean . Enterprise . Middleware</font></div><div><font \
color="#336666"><br></font></div><div><font color="#336666"><img \
src="http://c.content.wso2.com/signatures/general.png" width="420" \
height="54"></font></div></div></div></div> </div></div></div></div></div>
<br></div></div><span>_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@wso2.org" target="_blank">Dev@wso2.org</a><br>
<a href="http://wso2.org/cgi-bin/mailman/listinfo/dev" \
target="_blank">http://wso2.org/cgi-bin/mailman/listinfo/dev</a><br> \
<br></span></blockquote></div><br></div> \
</blockquote></div><br></div></div></div></div> \
</blockquote></div><br></div></div></div> \
</blockquote></div><br></div></div></div></div> \
</blockquote></div><br></div></div></div> </blockquote></div><br></div></div>
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic