svn - ERROR CarbonDeploymentSchedulerTask Error while running deployment scheduler -
hello have problem wso2 cluster svn sync,the error follow when wso2 esb managernode start :
2013-09-04 15:32:34,781 [-] [pool-10-thread-1] error carbondeploymentschedulertask error while running deployment scheduler.. java.lang.outofmemoryerror: java heap space @ java.util.arrays.copyof(arrays.java:2367) @ java.lang.abstractstringbuilder.expandcapacity(abstractstringbuilder.java:130) @ java.lang.abstractstringbuilder.ensurecapacityinternal(abstractstringbuilder.java:114) @ java.lang.abstractstringbuilder.append(abstractstringbuilder.java:415) @ java.lang.stringbuffer.append(stringbuffer.java:237) @ org.tmatesoft.svn.core.svnerrormessage.getfullmessage(svnerrormessage.java:257) @ org.tmatesoft.svn.core.internal.wc.svnerrormanager.error(svnerrormanager.java:58) @ org.tmatesoft.svn.core.internal.wc.admin.svnadminareafactory.open(svnadminareafactory.java:163) @ org.tmatesoft.svn.core.internal.wc.admin.svnwcaccess.doopen(svnwcaccess.java:364) @ org.tmatesoft.svn.core.internal.wc.admin.svnwcaccess.open(svnwcaccess.java:272) @ org.tmatesoft.svn.core.internal.wc.admin.svnwcaccess.open(svnwcaccess.java:265) @ org.tmatesoft.svn.core.internal.wc.admin.svnwcaccess.open(svnwcaccess.java:261) @ org.tmatesoft.svn.core.wc.svnstatusclient.dostatus(svnstatusclient.java:316) @ org.tmatesoft.svn.core.javahl.svnclientimpl.status(svnclientimpl.java:296) @ org.tmatesoft.svn.core.javahl.svnclientimpl.status(svnclientimpl.java:278) @ org.tigris.subversion.svnclientadapter.javahl.abstractjhlclientadapter.getstatus(abstractjhlclientadapter.java:542) @ org.tigris.subversion.svnclientadapter.svnkit.svnkitclientadapter.getstatus(svnkitclientadapter.java:144) @ org.tigris.subversion.svnclientadapter.javahl.abstractjhlclientadapter.getstatus(abstractjhlclientadapter.java:528) @ org.tigris.subversion.svnclientadapter.javahl.abstractjhlclientadapter.getstatus(abstractjhlclientadapter.java:521) @ org.wso2.carbon.deployment.synchronizer.subversion.svnbasedartifactrepository.cleanupdeletedfiles(svnbasedartifactrepository.java:486) @ org.wso2.carbon.deployment.synchronizer.subversion.svnbasedartifactrepository.checkout(svnbasedartifactrepository.java:352) @ org.wso2.carbon.deployment.synchronizer.internal.deploymentsynchronizer.checkout(deploymentsynchronizer.java:181) @ org.wso2.carbon.deployment.synchronizer.internal.deploymentsynchronizerserviceimpl.update(deploymentsynchronizerserviceimpl.java:87) @ org.wso2.carbon.core.deployment.carbondeploymentschedulertask.deploymentsyncupdate(carbondeploymentschedulertask.java:146) @ org.wso2.carbon.core.deployment.carbondeploymentschedulertask.run(carbondeploymentschedulertask.java:111) @ java.util.concurrent.executors$runnableadapter.call(executors.java:471) @ java.util.concurrent.futuretask$sync.innerrunandreset(futuretask.java:351) @ java.util.concurrent.futuretask.runandreset(futuretask.java:178) @ java.util.concurrent.scheduledthreadpoolexecutor$scheduledfuturetask.access$301(scheduledthreadpoolexecutor.java:178) @ java.util.concurrent.scheduledthreadpoolexecutor$scheduledfuturetask.run(scheduledthreadpoolexecutor.java:293) @ java.util.concurrent.threadpoolexecutor.runworker(threadpoolexecutor.java:1110) @ java.util.concurrent.threadpoolexecutor$worker.run(threadpoolexecutor.java:603)
check whether have provided minimum hardware requirements provided in wso2 product documentation. if try allowing more memory used jvm using -xmx vm argument. instance, java -xmx1024m
Comments
Post a Comment