You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Emmanuel Venisse <em...@gmail.com> on 2009/11/19 14:03:11 UTC
Re: YOHO, anybody out there? RE: A lock could not be obtained within
the time requested
Can you try to delete build results first, maybe only some of them if you
have lot.
Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <ge...@edb.com>wrote:
> This must have happened for others as well, I guess, any ideas anybody?
>
>
> Geir
>
> -----Original Message-----
> From: Engebakken Geir
> Sent: 17. november 2009 11:27
> To: Engebakken Geir; users@continuum.apache.org
> Subject: RE: A lock could not be obtained within the time requested
>
> Forgot to say that this is continuum 1.2.2.
>
>
> Geir
>
> -----Original Message-----
> From: Engebakken Geir
> Sent: 17. november 2009 11:26
> To: 'users@continuum.apache.org'
> Subject: A lock could not be obtained within the time requested
>
> We try to remove a project in our continuum setup, and continuum just hangs
> and the log shows a java stacktrace in an sql select statement ending with
> :
>
> A lock could not be obtained within the time requested
>
>
> Any ideas what this might be.
>
> Geir
>
>
>
>
Re: Problem with multi module maven project
Posted by Dima K <dm...@gmail.com>.
One idea- not really good solution but temporally hack - try to use
symbolic link on server for access to right directories
With best regards,
Dmitro Kopylov
2009/12/9 Engebakken Geir <ge...@edb.com>:
> We have a multi module maven project that we have added to continuum, by the parent pom. Continuum then put all subprojects into continuum. But the problem is that all subprojects are placed in the same directory "level", that is for us this is :
>
> /usr/local/continuum/data/working-directory
>
> All projects are placed in a flat structure there with a numeric id as top level directory.
>
> This is a problem for the submodules, as they refer to some files in the parent project like this :
>
> <axis2.wsdlFile>${basedir}/../../wsdl/documentws/document/Document.wsdl</axis2.wsdlFile>
>
> The ../.. notation from ($basedir) then fails. Any idea how we can fix this ?
>
> Geir
>
>
>
Problem with multi module maven project
Posted by Engebakken Geir <ge...@edb.com>.
We have a multi module maven project that we have added to continuum, by the parent pom. Continuum then put all subprojects into continuum. But the problem is that all subprojects are placed in the same directory "level", that is for us this is :
/usr/local/continuum/data/working-directory
All projects are placed in a flat structure there with a numeric id as top level directory.
This is a problem for the submodules, as they refer to some files in the parent project like this :
<axis2.wsdlFile>${basedir}/../../wsdl/documentws/document/Document.wsdl</axis2.wsdlFile>
The ../.. notation from ($basedir) then fails. Any idea how we can fix this ?
Geir
RE: YOHO, anybody out there? RE: A lock could not be obtained
within the time requested
Posted by Engebakken Geir <ge...@edb.com>.
OK, thanks a lot I will try this!
My remark regarding lack of docs was just a hint that it could be better :)
Geir
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: 20. november 2009 00:42
To: users@continuum.apache.org
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
On Thu, Nov 19, 2009 at 10:23 AM, Wendy Smoak <ws...@gmail.com> wrote:
> I vaguely remember a utility to automate deleting old build results,
> you might find it in the list archives.
Here it is (but I've only used it against 1.3.x, I don't know if it'll
work with 1.2.x):
http://svn.apache.org/repos/asf/continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-client/src/main/java/org/apache/maven/continuum/xmlrpc/client/BuildResultsPurge.java
--
Wendy
Re: YOHO, anybody out there? RE: A lock could not be obtained within
the time requested
Posted by Wendy Smoak <ws...@gmail.com>.
On Thu, Nov 19, 2009 at 10:23 AM, Wendy Smoak <ws...@gmail.com> wrote:
> I vaguely remember a utility to automate deleting old build results,
> you might find it in the list archives.
Here it is (but I've only used it against 1.3.x, I don't know if it'll
work with 1.2.x):
http://svn.apache.org/repos/asf/continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-client/src/main/java/org/apache/maven/continuum/xmlrpc/client/BuildResultsPurge.java
--
Wendy
Re: YOHO, anybody out there? RE: A lock could not be obtained within
the time requested
Posted by Wendy Smoak <ws...@gmail.com>.
On Thu, Nov 19, 2009 at 8:35 AM, Engebakken Geir
<ge...@edb.com> wrote:
> There are some 500 build results in the list, I guess this is what halts the delete so there is a timeout, but I have to mark each one of them for deletion?
>
> I deleted 32 of them, and it took 5 minutes!
>
> There must be a way to set this up so that they are deleted manually each night, now where is the manual, oops doesn't exist ...
I think you said 1.2.2, so the docs are here...
http://continuum.apache.org/docs/1.2.2/
In 1.3.x there is a build output purge feature but it only deletes the
output directories, not the database records. The idea was that you
need to keep them around for statistics. I think there's a JIRA issue
open to change this, you can watch/vote for it.
I vaguely remember a utility to automate deleting old build results,
you might find it in the list archives.
Maybe you can use Selenium to automate deleting them through the web interface?
--
Wendy
RE: YOHO, anybody out there? RE: A lock could not be obtained
within the time requested
Posted by Engebakken Geir <ge...@edb.com>.
There are some 500 build results in the list, I guess this is what halts the delete so there is a timeout, but I have to mark each one of them for deletion?
I deleted 32 of them, and it took 5 minutes!
There must be a way to set this up so that they are deleted manually each night, now where is the manual, oops doesn't exist ...
Geir
-----Original Message-----
From: Engebakken Geir [mailto:geir.engebakken@edb.com]
Sent: 19. november 2009 16:20
To: users@continuum.apache.org; Emmanuel Venisse
Subject: RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
On a second thought, I guess you mean the build results in the DB of course, so I look into that now, but there is a lot!
I guess there must be a way to set up purging older builds or something.....
Geir
-----Original Message-----
From: Engebakken Geir [mailto:geir.engebakken@edb.com]
Sent: 19. november 2009 16:14
To: Emmanuel Venisse; users@continuum.apache.org
Subject: RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
I removed the build results (that is the output directory for the builds, which in this case was /usr/local/continuum/data/build-output-directory/67, this is what you meant?)
But had the same error when deleting the project. After that I can show the project group list in the web interface, but if I click any project group, continuum hangs and I must restart continuum.
Geir
From: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
Sent: 19. november 2009 14:03
To: users@continuum.apache.org
Cc: Engebakken Geir
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
Can you try to delete build results first, maybe only some of them if you have lot.
Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <ge...@edb.com>> wrote:
This must have happened for others as well, I guess, any ideas anybody?
Geir
-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@continuum.apache.org<ma...@continuum.apache.org>
Subject: RE: A lock could not be obtained within the time requested
Forgot to say that this is continuum 1.2.2.
Geir
-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@continuum.apache.org<ma...@continuum.apache.org>'
Subject: A lock could not be obtained within the time requested
We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :
A lock could not be obtained within the time requested
Any ideas what this might be.
Geir
RE: YOHO, anybody out there? RE: A lock could not be obtained
within the time requested
Posted by Engebakken Geir <ge...@edb.com>.
On a second thought, I guess you mean the build results in the DB of course, so I look into that now, but there is a lot!
I guess there must be a way to set up purging older builds or something.....
Geir
-----Original Message-----
From: Engebakken Geir [mailto:geir.engebakken@edb.com]
Sent: 19. november 2009 16:14
To: Emmanuel Venisse; users@continuum.apache.org
Subject: RE: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
I removed the build results (that is the output directory for the builds, which in this case was /usr/local/continuum/data/build-output-directory/67, this is what you meant?)
But had the same error when deleting the project. After that I can show the project group list in the web interface, but if I click any project group, continuum hangs and I must restart continuum.
Geir
From: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
Sent: 19. november 2009 14:03
To: users@continuum.apache.org
Cc: Engebakken Geir
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
Can you try to delete build results first, maybe only some of them if you have lot.
Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <ge...@edb.com>> wrote:
This must have happened for others as well, I guess, any ideas anybody?
Geir
-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@continuum.apache.org<ma...@continuum.apache.org>
Subject: RE: A lock could not be obtained within the time requested
Forgot to say that this is continuum 1.2.2.
Geir
-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@continuum.apache.org<ma...@continuum.apache.org>'
Subject: A lock could not be obtained within the time requested
We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :
A lock could not be obtained within the time requested
Any ideas what this might be.
Geir
RE: YOHO, anybody out there? RE: A lock could not be obtained
within the time requested
Posted by Engebakken Geir <ge...@edb.com>.
I removed the build results (that is the output directory for the builds, which in this case was /usr/local/continuum/data/build-output-directory/67, this is what you meant?)
But had the same error when deleting the project. After that I can show the project group list in the web interface, but if I click any project group, continuum hangs and I must restart continuum.
Geir
From: Emmanuel Venisse [mailto:emmanuel.venisse@gmail.com]
Sent: 19. november 2009 14:03
To: users@continuum.apache.org
Cc: Engebakken Geir
Subject: Re: YOHO, anybody out there? RE: A lock could not be obtained within the time requested
Can you try to delete build results first, maybe only some of them if you have lot.
Emmanuel
On Thu, Nov 19, 2009 at 1:03 PM, Engebakken Geir <ge...@edb.com>> wrote:
This must have happened for others as well, I guess, any ideas anybody?
Geir
-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:27
To: Engebakken Geir; users@continuum.apache.org<ma...@continuum.apache.org>
Subject: RE: A lock could not be obtained within the time requested
Forgot to say that this is continuum 1.2.2.
Geir
-----Original Message-----
From: Engebakken Geir
Sent: 17. november 2009 11:26
To: 'users@continuum.apache.org<ma...@continuum.apache.org>'
Subject: A lock could not be obtained within the time requested
We try to remove a project in our continuum setup, and continuum just hangs and the log shows a java stacktrace in an sql select statement ending with :
A lock could not be obtained within the time requested
Any ideas what this might be.
Geir