Problem with continuum
Hi, Anybody there are solution to this problem. I´ve never saw this. Provider message: The svn command failed. Command output: --- svn: Your .svn/tmp directory may be missing or corrupt; run 'svn cleanup' and try again svn: Can't open file 'Sigmai-Evolution\SigmaiWeb\JavaSource\br\com\hst\j2ee\sigmai\web\struts\form\report\.svn\tmp\text-base\ReportBdRemainingBySegmentAtCommissionerSupervisorForm.java.svn-base': The system cannot find the path specified. --- -- Glauber Stéfano Rezende
RE: Problem with continuum
You need file access to your continuum application. (Through ssh or on the machine itself for example) Continuum uses a work directory where the checkouts are made. Here lies the problem. (For every build the working copy is updated, not recreated.) As a side note for the dev'ers. Would it be possible to get some functionality to recreate your workingcopy? At the moment I have the same problem and no direct connection to the machine, only the web interface. Hth, Nick Stolwijk How I do this? -- Glauber Stéfano Rezende HST Sistemas Tecnologia CM - Configuration Manager Fone: +55 19 3294-0331 http://www.hst.com.br
Problem within Continuum 1.1 Beta 2 or Beta 3 generate-sources
Hello, i'd like to know why mvn ignores my generate-sources when running in continuum ? If i do on cmd-line: mvn generate-source all is fine ? thanks for answer, Jens
Re: Problem starting Continuum webapp interface
the default http port used by continuum is 8080. Do you have an other server on this port? You can change it in apps/continuum/conf/application.xml Actually, you can't deploy continuum in a servlet container. Normally, it will be possible in 1.1 Emmanuel Punyashloka Biswal a écrit : Hi, I'm trying to set up Continuum release 1.0.3 on a ppc mac. When I try to use plexus.sh to start the program, it starts listening for XMLRPC connections on port 8000, but doesn't bring up the web interface on port 8080 like the documentation says it should. Do I need to change some configuration settings? Also, are there instructions for deploying continuum using my own servlet container? Thanks! Punya
Problem starting Continuum
Hi all, I am new to Continuum, so still learning how to use it. I am using Continuum 1.0.3. Previously, I was able to start the Continuum server, but this morning, when I tried to start it, I got the following errors (from my wrapper.log): INFO | jvm 1| 2006/05/31 09:36:24 | Error while deploying application 'continuum-plexus-application-1.0.3.jar'. INFO | jvm 1| 2006/05/31 09:36:24 | org.codehaus.plexus.application.ApplicationServerException: Could not deploy the JAR INFO | jvm 1| 2006/05/31 09:36:24 | Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.continuum.Continuum', it could not be started INFO | jvm 1| 2006/05/31 09:36:24 | Caused by: org.apache.maven.continuum.store.ContinuumStoreException: Database is corrupted. There are more than one systemConfiguration object. Can someone explain what this means and how I may fix the problem? Will I have to re-install Continuum again since the database is corrupted? If so, is there a way to save the information I currently have in Continuum? Thanks for any help you can give me!
Re: Problem starting Continuum
I think you'll need to reinstall your continuum. Before to do it, you can connect to the derby database with a jdbc client and try to remove the duplicated object (or remove this table, it will be recreated at startup normally) but you perhaps have some other error in your db. Emmanuel Mike Lee a écrit : Hi all, I am new to Continuum, so still learning how to use it. I am using Continuum 1.0.3. Previously, I was able to start the Continuum server, but this morning, when I tried to start it, I got the following errors (from my wrapper.log): INFO | jvm 1| 2006/05/31 09:36:24 | Error while deploying application 'continuum-plexus-application-1.0.3.jar'. INFO | jvm 1| 2006/05/31 09:36:24 | org.codehaus.plexus.application.ApplicationServerException: Could not deploy the JAR INFO | jvm 1| 2006/05/31 09:36:24 | Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.continuum.Continuum', it could not be started INFO | jvm 1| 2006/05/31 09:36:24 | Caused by: org.apache.maven.continuum.store.ContinuumStoreException: Database is corrupted. There are more than one systemConfiguration object. Can someone explain what this means and how I may fix the problem? Will I have to re-install Continuum again since the database is corrupted? If so, is there a way to save the information I currently have in Continuum? Thanks for any help you can give me!
Re: Problem with continuum-1.0.3
Here is the final explanation of a long exchange with Emmanuel for my
problem...
Finally I did find why Continuum blocked during CVS project checkout.
It was because of compress option -z3 used by default for all cvs commands
in new version (1.0-beta-3) of SCM CVS API.
example : cvs -f -d :pserver:[EMAIL PROTECTED]:/logiciels/COUPLAGECVS -q
checkout -d 40 CouplageProject
Maven Website (http://maven.apache.org/scm/cvs.html) explains how to disable
the compress option but there is two mistakes on this page and it doesn't
work that easily...
For more info, look at the 2 JIRA SCM-190 and SCM-191 I created.
If you want - like me - to disable the compress option (-z3) in continuum
1.0.3, you have to :
- add the line
wrapper.java.additional.6=-Dmaven.scm.cvs.use_compression=false in
continuum-1.0.3/bin/solaris/wrapper.conf
- add cvs-settings.xml with compressionLevel0/compressionLevel in *${
user.dir}/.scm/* (*continuum-1.0.3/bin/solaris/.scm/*) and not in *${
user.home}/.scm/*
Tibo
2006/4/26, Emmanuel Venisse [EMAIL PROTECTED]:
Thibaut Cazenave a écrit :
I did it many times yesterday.
Like I said, each time, checkout stops on the same file.
I can send you the log of what I did yesterday. But it is too big for
the
continuum-users mailing list. If you need it I can send it to you
directly.
What I did :
1. Add my custom M2 plugins project which contains 3 plugins -- this
works
2. Restart Continuum
3. Add my main project (Couplage Project) -- this failed
I'll do what you ask this morning and send you the new log.
Send it me directly.
How do you remove the database ?
By deleting the folder continuum in apps ?
Or you can only delete database folder in apps/continuum ?
You can remove continuum folder but the database directory will be enougth
Emmanuel
Continuum runs on Solaris 8
Tibo
2006/4/26, Emmanuel Venisse [EMAIL PROTECTED]:
Can you do some tests?
1- Remove your database
2- start continuum and configure it
3- add all your projects
4- wait the checkout of files (without browsing continuum web interface,
so logs will be clean)
5- Send me logs
What is the OS that host Continuum?
Emmanuel
Thibaut Cazenave a écrit :
Yes sorry,
I've got to come back to work to check these points.
This file on which continuum blocked is not that big : 23533 o on my
CVS
repository
There are bigger files on my project.
When checkouted on Windows, this file sizes 20 ko.
I've got 1596 files and 2876 folders in my project.
And more than 6 lines of code.
If you need more info, just ask.
Thx
Tibo
2006/4/26, Emmanuel Venisse [EMAIL PROTECTED]:
Thibaut,
Can you answer to my questions?
Emmanuel
Thibaut Cazenave a écrit :
Emmanuel Venisse :
Is it a big file?
How many files do you have in your project?
The best place for continuum question is the continuum mailing list,
thanks.
Emmanuel
Thibaut CAZENAVE a écrit :
Hi,
I just install Continuum 1.0.3. I've got a serious problem when I
add
my
Maven2 Project.
My Maven project is composed of 7 modules.
When I add the parent Project, Continuum checkouts the all 7 modules
in
/build-directory/6/ -- this works well
Then Continuum checkouts the first childin
/build-directory/7/
--
this works well
Then Continuum checkouts the second child in /build-directory/8/ --
this
failed
Continuum stays blocked when checkouting one file.
Then nothing happens. It is impossible to build one of the modules
because
the checkout of second child is pending...
What is strange is that it is always on the same file.
I start from scratch a few time and it always do the same thing on
the
same file : PlayerCommonHelper.java
I look on CVS and I don't find anythinf special on this file (same
owner,
same rights, etc)
When I look on build-directory/8/ for this module which checkout
seems
to
fail, I notice that the module is well checkouted and that every
file
is
here (even PlayerCommonHelper.java)
If during the checkout, I try to do navigate in continuum website, I
got
many exceptions.
Here is the log :
If someone is interested for the complete log, please ask.
Thanks for your help.
374969 [Thread-22] DEBUG org.apache.maven.scm.manager.ScmManager -
U
8/src/main/java/com/edfgdf/a16/application/impl/disws/common/scort/PlayerCommonHelper.java
637645 [SocketListener0-4] ERROR
org.codehaus.plexus.summit.renderer.Renderer:velocity - Error
rendering
template:
EOFException(java.net.SocketException: Broken pipe)
at
org.mortbay.http.BufferedOutputStream.flush(
BufferedOutputStream.java
:195)
at
org.mortbay.http.ChunkingOutputStream.flush(
ChunkingOutputStream.java
:67)
at
org.mortbay.util.ByteBufferOutputStream.ensureSpareCapacity(
ByteBufferOutputStream.java:342)
at
Re: Problem with continuum-1.0.3
Thibaut, Can you answer to my questions? Emmanuel Thibaut Cazenave a écrit : Emmanuel Venisse : Is it a big file? How many files do you have in your project? The best place for continuum question is the continuum mailing list, thanks. Emmanuel Thibaut CAZENAVE a écrit : Hi, I just install Continuum 1.0.3. I've got a serious problem when I add my Maven2 Project. My Maven project is composed of 7 modules. When I add the parent Project, Continuum checkouts the all 7 modules in /build-directory/6/ -- this works well Then Continuum checkouts the first childin /build-directory/7/ -- this works well Then Continuum checkouts the second child in /build-directory/8/ -- this failed Continuum stays blocked when checkouting one file. Then nothing happens. It is impossible to build one of the modules because the checkout of second child is pending... What is strange is that it is always on the same file. I start from scratch a few time and it always do the same thing on the same file : PlayerCommonHelper.java I look on CVS and I don't find anythinf special on this file (same owner, same rights, etc) When I look on build-directory/8/ for this module which checkout seems to fail, I notice that the module is well checkouted and that every file is here (even PlayerCommonHelper.java) If during the checkout, I try to do navigate in continuum website, I got many exceptions. Here is the log : If someone is interested for the complete log, please ask. Thanks for your help. 374969 [Thread-22] DEBUG org.apache.maven.scm.manager.ScmManager - U 8/src/main/java/com/edfgdf/a16/application/impl/disws/common/scort/PlayerCommonHelper.java 637645 [SocketListener0-4] ERROR org.codehaus.plexus.summit.renderer.Renderer:velocity - Error rendering template: EOFException(java.net.SocketException: Broken pipe) at org.mortbay.http.BufferedOutputStream.flush(BufferedOutputStream.java:195) at org.mortbay.http.ChunkingOutputStream.flush(ChunkingOutputStream.java:67) at org.mortbay.util.ByteBufferOutputStream.ensureSpareCapacity(ByteBufferOutputStream.java:342) at org.mortbay.util.ByteBufferOutputStream.write(ByteBufferOutputStream.java:182) at org.mortbay.http.BufferedOutputStream.write(BufferedOutputStream.java:141) at org.mortbay.http.HttpOutputStream.write(HttpOutputStream.java:442) at org.mortbay.jetty.servlet.ServletOut.write(ServletOut.java:42) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204) at java.io.Writer.write(Writer.java:126) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:291) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.codehaus.plexus.summit.renderer.VelocityRenderer.render(VelocityRenderer.java:70) at org.codehaus.plexus.summit.display.ClassicBufferedDisplay.render(ClassicBufferedDisplay.java:98) at org.codehaus.plexus.summit.pipeline.valve.DisplayValve.invoke(DisplayValve.java:48) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) 641202 [SocketListener0-3] INFO org.codehaus.plexus.action.Action:login - Trying to log in 'THC'. 689957 [SocketListener0-3] WARN JPOX.RDBMS.SQL - Object with id 0 not found ! 689960 [SocketListener0-3] ERROR org.apache.maven.continuum.web.tool.FormicaTool - Error while evaluation
Re: Problem with continuum-1.0.3
Yes sorry, I've got to come back to work to check these points. This file on which continuum blocked is not that big : 23533 o on my CVS repository There are bigger files on my project. When checkouted on Windows, this file sizes 20 ko. I've got 1596 files and 2876 folders in my project. And more than 6 lines of code. If you need more info, just ask. Thx Tibo 2006/4/26, Emmanuel Venisse [EMAIL PROTECTED]: Thibaut, Can you answer to my questions? Emmanuel Thibaut Cazenave a écrit : Emmanuel Venisse : Is it a big file? How many files do you have in your project? The best place for continuum question is the continuum mailing list, thanks. Emmanuel Thibaut CAZENAVE a écrit : Hi, I just install Continuum 1.0.3. I've got a serious problem when I add my Maven2 Project. My Maven project is composed of 7 modules. When I add the parent Project, Continuum checkouts the all 7 modules in /build-directory/6/ -- this works well Then Continuum checkouts the first childin /build-directory/7/ -- this works well Then Continuum checkouts the second child in /build-directory/8/ -- this failed Continuum stays blocked when checkouting one file. Then nothing happens. It is impossible to build one of the modules because the checkout of second child is pending... What is strange is that it is always on the same file. I start from scratch a few time and it always do the same thing on the same file : PlayerCommonHelper.java I look on CVS and I don't find anythinf special on this file (same owner, same rights, etc) When I look on build-directory/8/ for this module which checkout seems to fail, I notice that the module is well checkouted and that every file is here (even PlayerCommonHelper.java) If during the checkout, I try to do navigate in continuum website, I got many exceptions. Here is the log : If someone is interested for the complete log, please ask. Thanks for your help. 374969 [Thread-22] DEBUG org.apache.maven.scm.manager.ScmManager - U 8/src/main/java/com/edfgdf/a16/application/impl/disws/common/scort/PlayerCommonHelper.java 637645 [SocketListener0-4] ERROR org.codehaus.plexus.summit.renderer.Renderer:velocity - Error rendering template: EOFException(java.net.SocketException: Broken pipe) at org.mortbay.http.BufferedOutputStream.flush(BufferedOutputStream.java :195) at org.mortbay.http.ChunkingOutputStream.flush(ChunkingOutputStream.java :67) at org.mortbay.util.ByteBufferOutputStream.ensureSpareCapacity( ByteBufferOutputStream.java:342) at org.mortbay.util.ByteBufferOutputStream.write( ByteBufferOutputStream.java:182) at org.mortbay.http.BufferedOutputStream.write(BufferedOutputStream.java :141) at org.mortbay.http.HttpOutputStream.write(HttpOutputStream.java:442) at org.mortbay.jetty.servlet.ServletOut.write(ServletOut.java :42) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204) at java.io.Writer.write(Writer.java:126) at org.apache.velocity.runtime.parser.node.ASTReference.render( ASTReference.java:291) at org.apache.velocity.runtime.parser.node.SimpleNode.render( SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.codehaus.plexus.summit.renderer.VelocityRenderer.render( VelocityRenderer.java:70) at org.codehaus.plexus.summit.display.ClassicBufferedDisplay.render( ClassicBufferedDisplay.java:98) at org.codehaus.plexus.summit.pipeline.valve.DisplayValve.invoke( DisplayValve.java:48) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke( AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch( WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle( WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at
Re: Problem with continuum-1.0.3
Can you do some tests? 1- Remove your database 2- start continuum and configure it 3- add all your projects 4- wait the checkout of files (without browsing continuum web interface, so logs will be clean) 5- Send me logs What is the OS that host Continuum? Emmanuel Thibaut Cazenave a écrit : Yes sorry, I've got to come back to work to check these points. This file on which continuum blocked is not that big : 23533 o on my CVS repository There are bigger files on my project. When checkouted on Windows, this file sizes 20 ko. I've got 1596 files and 2876 folders in my project. And more than 6 lines of code. If you need more info, just ask. Thx Tibo 2006/4/26, Emmanuel Venisse [EMAIL PROTECTED]: Thibaut, Can you answer to my questions? Emmanuel Thibaut Cazenave a écrit : Emmanuel Venisse : Is it a big file? How many files do you have in your project? The best place for continuum question is the continuum mailing list, thanks. Emmanuel Thibaut CAZENAVE a écrit : Hi, I just install Continuum 1.0.3. I've got a serious problem when I add my Maven2 Project. My Maven project is composed of 7 modules. When I add the parent Project, Continuum checkouts the all 7 modules in /build-directory/6/ -- this works well Then Continuum checkouts the first childin /build-directory/7/ -- this works well Then Continuum checkouts the second child in /build-directory/8/ -- this failed Continuum stays blocked when checkouting one file. Then nothing happens. It is impossible to build one of the modules because the checkout of second child is pending... What is strange is that it is always on the same file. I start from scratch a few time and it always do the same thing on the same file : PlayerCommonHelper.java I look on CVS and I don't find anythinf special on this file (same owner, same rights, etc) When I look on build-directory/8/ for this module which checkout seems to fail, I notice that the module is well checkouted and that every file is here (even PlayerCommonHelper.java) If during the checkout, I try to do navigate in continuum website, I got many exceptions. Here is the log : If someone is interested for the complete log, please ask. Thanks for your help. 374969 [Thread-22] DEBUG org.apache.maven.scm.manager.ScmManager - U 8/src/main/java/com/edfgdf/a16/application/impl/disws/common/scort/PlayerCommonHelper.java 637645 [SocketListener0-4] ERROR org.codehaus.plexus.summit.renderer.Renderer:velocity - Error rendering template: EOFException(java.net.SocketException: Broken pipe) at org.mortbay.http.BufferedOutputStream.flush(BufferedOutputStream.java :195) at org.mortbay.http.ChunkingOutputStream.flush(ChunkingOutputStream.java :67) at org.mortbay.util.ByteBufferOutputStream.ensureSpareCapacity( ByteBufferOutputStream.java:342) at org.mortbay.util.ByteBufferOutputStream.write( ByteBufferOutputStream.java:182) at org.mortbay.http.BufferedOutputStream.write(BufferedOutputStream.java :141) at org.mortbay.http.HttpOutputStream.write(HttpOutputStream.java:442) at org.mortbay.jetty.servlet.ServletOut.write(ServletOut.java :42) at sun.nio.cs.StreamEncoder$CharsetSE.writeBytes(StreamEncoder.java:336) at sun.nio.cs.StreamEncoder$CharsetSE.implWrite(StreamEncoder.java:395) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:136) at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:146) at java.io.OutputStreamWriter.write(OutputStreamWriter.java:204) at java.io.Writer.write(Writer.java:126) at org.apache.velocity.runtime.parser.node.ASTReference.render( ASTReference.java:291) at org.apache.velocity.runtime.parser.node.SimpleNode.render( SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.codehaus.plexus.summit.renderer.VelocityRenderer.render( VelocityRenderer.java:70) at org.codehaus.plexus.summit.display.ClassicBufferedDisplay.render( ClassicBufferedDisplay.java:98) at org.codehaus.plexus.summit.pipeline.valve.DisplayValve.invoke( DisplayValve.java:48) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke( AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch( WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle( WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at
Re: Problem with continuum on solaris zone
On Fri, 2006-01-13 at 09:14 -0500, Sean Schofield wrote: We're trying to setup continuum for the MyFaces project. We have a solaris zone set up and we're having trouble starting the server. $ bin/solaris/run.sh start Starting continuum... bin/solaris/run.sh: ./wrapper: cannot execute We've tried running as root as well but the same result. I know the maven team has a solaris zone with continuum so I was hoping we could get some pointers on how to tweak our zone so we can run continuum. I just realized that the Apache zone is running on Intel hardware and the wrapper distributed with Continuum is Solaris on SPARC. Emmanuel: Is there an issue in Continuum or Plexus about generating the run-time with platforms specific names under bin/ ? I'm sure we've been here before, just couldn't find an issue. -- Trygve
