[#BAM-1080] Lock obtain timed out error

Bamboo

Lock obtain timed out error

Created: 29/Mar/07 06:50 PM Updated: 25/Sep/07 09:10 PM

Component/s:

Build Process

Affects Version/s:

1.0.2

Fix Version/s:

1.1

Time Tracking:

Not Specified

File Attachments:

logfile.tgz (1.15 MB)

Internal Priority:	2. High
Participants:	Ajay Sridhar [Atlassian], Edwin Wong [Atlassian], Herry Wiputra, Mark Chaimungkalanont [Atlassian], Philip Nathan Provoost and Sam Berlin
Since last comment:	48 weeks, 1 day ago
Internal Work Bucket:	Info Gathering
Number of comments:	7
Labels:

Description

« Hide

We keep getting the following error over and over again.
At one stage we have a build that is running for 2000+ minutes where it normally would only take 50 minutes to run.

Build Babylon - Trunk: Could not save the build results (Occurrences 1)
(java.io.IOException: Lock obtain timed out: Lock@/tmp/lucene-ed82f3d1b9a2ff1733816749ce5d18d1-write.lock)
Strack Trace

java.io.IOException: Lock obtain timed out: Lock@/tmp/lucene-ed82f3d1b9a2ff1733816749ce5d18d1-write.lock
at org.apache.lucene.store.Lock.obtain(Lock.java:58)
at org.apache.lucene.index.IndexWriter.(IndexWriter.java:255)
at org.apache.lucene.index.IndexWriter.(IndexWriter.java:225)
at com.atlassian.bamboo.index.IndexConnectionManager.getWriter(IndexConnectionManager.java:104)
at com.atlassian.bamboo.index.IndexConnectionManager.index(IndexConnectionManager.java:75)
at com.atlassian.bamboo.index.DefaultBuildResultsIndexer.indexBuildResultKeepConnection(DefaultBuildResultsIndexer.java:146)
at com.atlassian.bamboo.index.DefaultBuildResultsIndexer.indexBuildResult(DefaultBuildResultsIndexer.java:90)
at com.atlassian.bamboo.build.pipeline.tasks.SaveBuildTask.call(SaveBuildTask.java:74)
at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
at edu.emory.mathcs.backport.java.util.concurrent.helpers.ThreadHelpers$1.run(ThreadHelpers.java:34)
at java.lang.Thread.run(Thread.java:595)

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Edwin Wong [Atlassian] added a comment - 01/Apr/07 09:44 PM

Hi Herry,

I was just wondering whether this is a recurring problem, or only occurred after a certain event (e.g. an upgrade?)

Also, would you like to attach your full atlassian-bamboo.log files to this issue?

As a work around, would you like to perform a full re-index on your Bamboo instance and see if that removes the lock problem? To do this, you can go to Administration -> Indexing. (Please beware that indexing may take a while.)

Cheers,
Edwin

[ Permlink | « Hide ]

Ajay Sridhar [Atlassian] added a comment - 30/Apr/07 01:40 AM

Hi Henry,

We haven't heard back from you in a while. Were you able to resolve this issue?

Cheers,
AJay

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 01/May/07 08:26 AM

Herry,

I'll time this issue out for now. If the issue resurfaces, please let us know and provide us with the atlassian-bamboo.log file.

Cheers,

Mark C

[ Permlink | « Hide ]

Philip Nathan Provoost added a comment - 11/May/07 06:47 AM

Hello Guys,

I am also having this strange error on my bamboo installation. I am using the bamboo 1.1 release. This error occurs only when I am activating the clover xml output.

Cheers,

Philip

[ Permlink | « Hide ]

Philip Nathan Provoost added a comment - 11/May/07 06:50 AM

This is the complete logfile which shows this error. The permgensize is 256M in our bamboo environment.

[ Permlink | « Hide ]

Ajay Sridhar [Atlassian] added a comment - 14/May/07 01:02 AM

Hi Philip,

Sorry for the inconvenience.

I have raised a Support request https://support.atlassian.com/browse/BSP-86 on your behalf, the login details has been mailed to your registered JIRA e-mail address.

Please reply to this issue, if you have any problems logging in.

Cheers,
Ajay

[ Permlink | « Hide ]

Sam Berlin added a comment - 25/Sep/07 09:10 PM

We are also having this error in our Bamboo 1.2.3. Was there any fix we can try? Thanks.