Found out that this is because of the corrupted deployment folder. This was
caused because the svnClientBundle jar was missing when the server was
first started up.

Removing all the .svn folders in repository/deployment directory will solve
the issue.

Thanks
Manisha

On Fri, Sep 6, 2013 at 12:05 PM, Manisha Gayathri <[email protected]> wrote:

>
> Hi Kasun,
>>
>> Followed the guide given in [1] to configure WSO2 AS 5.1.0. I have set up
>> the MULTICAST clustering and I have copied the svnClientBundle-1.0.0.jar to
>> AS_HOME/repository/components/dropins as well.
>>
>> But when starting the server, I get the following error. (Observed the
>> same in both worker and manager nodes)
>>
>> ERROR {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
>>  Error while running deployment scheduler..
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.Arrays.copyOf(Arrays.java:2882)
>> at
>> java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
>>  at
>> java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
>> at java.lang.StringBuffer.append(StringBuffer.java:224)
>>  at
>> org.tmatesoft.svn.core.SVNErrorMessage.getFullMessage(SVNErrorMessage.java:257)
>> at
>> org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:58)
>>  at
>> org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.open(SVNAdminAreaFactory.java:163)
>> at
>> org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.doOpen(SVNWCAccess.java:364)
>>  at
>> org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:272)
>> at
>> org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:265)
>>  at
>> org.tmatesoft.svn.core.internal.wc.admin.SVNWCAccess.open(SVNWCAccess.java:261)
>> at
>> org.tmatesoft.svn.core.wc.SVNStatusClient.doStatus(SVNStatusClient.java:316)
>>  at
>> org.tmatesoft.svn.core.javahl.SVNClientImpl.status(SVNClientImpl.java:296)
>> at
>> org.tmatesoft.svn.core.javahl.SVNClientImpl.status(SVNClientImpl.java:278)
>>  at
>> org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:542)
>> at
>> org.tigris.subversion.svnclientadapter.svnkit.SvnKitClientAdapter.getStatus(SvnKitClientAdapter.java:144)
>>  at
>> org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:528)
>> at
>> org.tigris.subversion.svnclientadapter.javahl.AbstractJhlClientAdapter.getStatus(AbstractJhlClientAdapter.java:521)
>>  at
>> org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.cleanupDeletedFiles(SVNBasedArtifactRepository.java:486)
>> at
>> org.wso2.carbon.deployment.synchronizer.subversion.SVNBasedArtifactRepository.checkout(SVNBasedArtifactRepository.java:352)
>>  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:146)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:111)
>>  at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>> at
>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>  at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205)
>>  at
>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>>
>> Any idea what causes this?
>> When I tried the same configs with BPS 3.0.0, it did not give me such an
>> error.
>>
>> [1]. http://docs.wso2.org/display/AS510/Clustered+Deployment
>>
>> Thanks
>> Manisha
>> <http://docs.wso2.org/display/AS510/Clustered+Deployment>--
>> ~Regards
>> *Manisha Eleperuma*
>> Software Engineer
>> WSO2, Inc.: http://wso2.com
>> lean.enterprise.middleware
>>
>> *blog:      http://manisha-eleperuma.blogspot.com/*
>> *
>> *
>>
>
>
> *
> *
>



-- 
~Regards
*Manisha Eleperuma*
Software Engineer
WSO2, Inc.: http://wso2.com
lean.enterprise.middleware

*blog:      http://manisha-eleperuma.blogspot.com/*

*
*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to