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
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
