[Mifos-developer] Getting build errors.

[Ajay Kumar]

Hi Guys,
I have been trying to set mifos up and build it from source on my Ubuntu 9.10. I do have the following files under
/application/target
mifos-trunk_r17099-release.zip
mifos-webapp.war

Does this mean, i have a working copy of the webapp irrespective of the error below?

The build process ended with:
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 120 minutes 4 seconds
[INFO] Finished at: Mon Apr 05 03:45:40 IST 2010
[INFO] Final Memory: 60M/254M
[INFO] ------------------------------------------------------------------------

However, there was ONE fatal error that I noticed.
Could this be because of me not running Tomcat during the build process?

[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to start the Tomcat 6.x container. Check the [/home/ajuonline/mifos-gazelle/acceptanceTests/target/logs/tomcat6x.out] file containing the container logs for more details.
Deployable [http://localhost:8083/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.codehaus.cargo.container.ContainerException: Failed to start the Tomcat 6.x container. Check the [/home/ajuonline/mifos-gazelle/acceptanceTests/target/logs/tomcat6x.out] file containing the container logs for more details.
    at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:168)
    at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute(ContainerStartMojo.java:61)
    at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:255)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:8083/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
    at org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)
    at org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:220)
    at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:163)
    ... 21 more
org.codehaus.cargo.container.ContainerException: Deployable [http://localhost:8083/cargocpc/index.html] failed to finish deploying within the timeout period [600000]. The Deployable state is thus unknown.
    at org.codehaus.cargo.container.spi.deployer.DeployerWatchdog.watch(DeployerWatchdog.java:111)
    at org.codehaus.cargo.container.spi.AbstractLocalContainer.waitForCompletion(AbstractLocalContainer.java:220)
    at org.codehaus.cargo.container.spi.AbstractLocalContainer.start(AbstractLocalContainer.java:163)
    at org.codehaus.cargo.maven2.ContainerStartMojo.doExecute(ContainerStartMojo.java:61)
    at org.codehaus.cargo.maven2.AbstractCargoMojo.execute(AbstractCargoMojo.java:255)
    at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
    at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
    at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
    at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
    at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
    at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

--
Best Regards,

Ajay Kumar

http://www.ajuonline.net

[Van Mittal-Henkle]

Hi Ajay,

 

You need to make sure that you do *not* have an instance of tomcat running on the same port as the build while the build is running, otherwise the build will hang.  The safest way is to ensure that tomcat is not running at all (in eclipse WTP or from the command line) when you run a build.

 

Another possible problem is that maven could not download tomcat during the build process.  So if the step above doesn’t help then have a look at http://mifos.org/developers/wiki/MavenSettingsXml and try downloading the tomcat package for the build to use locally.

 

Let us know how it goes.

 

--Van

 

----

Van Mittal-Henkle

Mifos Software Developer

Grameen Foundation

va...@grameenfoundation.org

[Ajay Kumar]

On 6 April 2010 22:02, Van Mittal-Henkle <va...@grameenfoundation.org> wrote:

Another possible problem is that maven could not download tomcat during the build process.  So if the step above doesn’t help then have a look at http://mifos.org/developers/wiki/MavenSettingsXml and try downloading the tomcat package for the build to use locally.

OK. I didnt have Tomcat running so that's not an issue.
I did a "mvn clean install" again (i have done it multiple times)

I tried the custom XML setting after downloading the latest Tomcat's zip file and placing it under /home/user/Downloads/
folder on my Ubuntu. Still I have that error.

Here is the XML file, the FILE PATH URL is correct right?

<settings xmlns="http://maven.apache.org/POM/4.0.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
                    http://maven.apache.org/xsd/settings-1.0.0.xsd">

 <profiles>
   <profile>
     <id>local</id>
     <activation>
       <activeByDefault>true</activeByDefault>
     </activation>
        <properties>
           <tomcat.container.url>file:///home/user/Downloads/apache-tomcat-6.0.26.zip</tomcat.container.url>
        </properties>
   </profile>
 </profiles>
</settings>

[Udai Gupta]

Hi Ajay,

The error is message

"Failed to start the Tomcat 6.x container. Check the
[/home/ajuonline/mifos-gazelle/acceptanceTests/target/logs/tomcat6x.out]
file containing the container logs for more details.
Deployable [http://localhost:8083/cargocpc/index.html] failed to
finish deploying within the timeout period [600000]. The Deployable
state is thus unknown."

Looks like tomcat is not starting correctly.

Steps to troubleshoot this issue.
1. Check /home/ajuonline/mifos-gazelle/acceptanceTests/target/logs/tomcat6x.out,
if there is something unusual then fix it or report it on the same
thread.
2. Try to start tomcat externally at port 8083 for HTTP, see if it works.
3. Make sure that no other process is running at port 8083 when you
build Mifos. You can check if port is occupied or not by using "telnet
localhost 8083". If it connects then the port is occupied and if not
then it's not.

Regards,
Udai

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

[Ajay Kumar]

Hi Udai,

On 7 April 2010 13:39, Udai Gupta <mail...@gmail.com> wrote:

Looks like tomcat is not starting correctly.

Steps to troubleshoot this issue.
1. Check /home/ajuonline/mifos-gazelle/acceptanceTests/target/logs/tomcat6x.out,
if there is something unusual then fix it or report it on the same
thread.

The content of the file reads:
"Error occurred during initialisation of VM
Could not reserve enough space for object heap"

While the last two lines (of 4) in tomcat6x.log file reads:
"[info][talledLocalContainer] Tomcat 6.x starting...
[warn][talledLocalContainer] Java Result : 1
"
I am assuming, this could be possible because of low memory available? I am running Ubuntu 9.10 on a VM which is allocated 1 Gb Memory, though. I will just retry this on my Dual Boot of Ubuntu rather than the VM and see if I get the same error. Or is there anything that comes to your mind as the cause of this problem?
 

2. Try to start tomcat externally at port 8083 for HTTP, see if it works.

3. Make sure that no other process is running at port 8083 when you
build Mifos. You can check if port is occupied or not by using "telnet
localhost 8083". If it connects then the port is occupied and if not
then it's not.

 

Yeah I checked the port is unused and no other process was occupying that port.

[Gangadhar Nittala]

Also check that you have configured the CATALINA_OPTS and M2_OPTS as
described here http://www.mifos.org/knowledge/install-guide/main#set-up-environment-variables.
May be the VM space is causing the tomcat to not startup.

On Apr 7, 9:55 am, Ajay Kumar <ajuonl...@gmail.com> wrote:
> Hi Udai,
>

> ---------------------------------------------------------------------------­---

> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.http://p.sf.net/sfu/intel-sw-dev

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

--
You received this message because you are subscribed to the Google Groups "Mifos Developer" group.
To post to this group, send email to mifosde...@googlegroups.com.
To unsubscribe from this group, send email to mifosdevelope...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mifosdeveloper?hl=en.