Use a separate lock file for each CVS module

We have some error when we want to update the path of the log for cvs module. For uknown reason it has been working for an update or two and stop to work after it raised this error.
Now we are not able to update anything for cvs concern unless we stop the server and erase the cvslog.write.lock.

2005-06-14 17:40:34,140 ERROR [atlassian.jira.vcs.DefaultRepositoryManager] Error occurred while updating repository 'BNPPA_Tarification_Tool_A2A': Could not obtain lock 'D:\JIRA-INT\bnppa-atlassian-jira\bin\logs\cvslog.write.lock' in 10000 msecs.
com.atlassian.jira.util.LockException: Could not obtain lock 'D:\JIRA-INT\bnppa-atlassian-jira\bin\logs\cvslog.write.lock' in 10000 msecs.
at com.atlassian.jira.vcs.cvsimpl.CvsRepositoryUtilImpl.updateCvs(CvsRepositoryUtilImpl.java:245)
at com.atlassian.jira.vcs.cvsimpl.CvsRepository.updateCvs(CvsRepository.java:204)
at com.atlassian.jira.vcs.cvsimpl.CvsRepository.updateRepository(CvsRepository.java:295)
at com.atlassian.jira.vcs.DefaultRepositoryManager.updateRepository(DefaultRepositoryManager.java:489)
at com.atlassian.jira.vcs.DefaultRepositoryManager.updateRepositories(DefaultRepositoryManager.java:445)
at com.atlassian.jira.service.services.vcs.VcsService.run(VcsService.java:54)
at com.atlassian.jira.service.JiraServiceContainer.run(JiraServiceContainer.java:59)
at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:50)
at org.quartz.core.JobRunShell.run(JobRunShell.java:191)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:516)