geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: Geronimo2.1.0 build failure with Java5 (method getContentType() not found)
Date Sun, 21 Jun 2009 16:04:52 GMT

On Jun 21, 2009, at 2:29 AM, Mohanraj Loganathan wrote:

> Hello
>
> After a long time, i could able to build the geronimo using Harmony  
> JDK. But Building was not so smooth. I need to build the modules one  
> by one. I struck at running the testsuites module .
>
> It is failed to verify the Geronimo server start.  But i am sure  
> server is started. Server logs shows that server is up and running.  
> But build script while running the command-testsuite failed to  
> detect the server start. Any help would be much appreciated. Please  
> note, Harmony doesnt implement JPA.

umm, neither does any other vm, not sure what you mean here.  Maybe it  
doesn't implement java agents or not the same way?

I wonder if harmony implements jmx remoting?  checking whether the  
server started relies on this.

thanks
david jencks

> hence i removed the option from batch script while starting.
>
> I am getting the following error:
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Unable to  
> verify if the server was started in the given time (300 seconds)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
> 584)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor 
> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:50
> 0)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 
> 479)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor 
> .executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
> a:331)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor 
> .executeTaskSegments(DefaultLifecycleExecutor.java:292)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 
> 336)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 
> 129)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
>         at  
> java.lang.reflect.VMReflection.invokeMethod(VMReflection.java)
>         at java.lang.reflect.Method.invoke(Method.java:317)
>         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.apache.maven.plugin.MojoExecutionException: Unable to  
> verify if the server was started in the given time
> (300 seconds)
>         at  
> org 
> .apache 
> .geronimo 
> .mavenplugins 
> .geronimo 
> .reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:10
> 6)
>         at  
> org 
> .apache 
> .maven 
> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 
> 453)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 
> 559)
>         at  
> org 
> .apache 
> .maven 
> .lifecycle 
> .DefaultLifecycleExecutor 
> .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:50
> 0)
>         ... 13 more
> Caused by: org.apache.maven.plugin.MojoExecutionException: Unable to  
> verify if the server was started in the given time
> (300 seconds)
>         at  
> org 
> .apache 
> .geronimo 
> .mavenplugins 
> .geronimo.server.StartServerMojo.doExecute(StartServerMojo.java:350)
>         at  
> org 
> .apache 
> .geronimo 
> .mavenplugins 
> .geronimo 
> .reporting.ReportingMojoSupport.execute(ReportingMojoSupport.java:99
> )
>         at  
> org 
> .apache 
> .maven 
> .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 
> 453)
>         ... 15 more
>
> On Wed, May 13, 2009 at 8:03 AM, Jack Cai <greensight@gmail.com>  
> wrote:
> Mohan, the problem might be with the Harmony code - could be a  
> compability issue or a defect. So you'll want to spend some time  
> debugging it.
>
> I agree with Kevan that it will be cool that Geronimo can be built  
> and run with Harmony. Someday we might be officially "support"  
> Harmony as a runtime, and even do a JEE cert with Harmony?
>
> -Jack
>
> 2009/5/12 Kevan Miller <kevan.miller@gmail.com>
>
>
> On May 12, 2009, at 8:54 AM, Luciano Salotto wrote:
>
>> I would recommend trying this with Sun or IMB JDK, I believe those  
>> are the only two recommended JDK's
>>
>> http://cwiki.apache.org/GMOxDEV/building-apache-geronimo.html
>
> Agreed. However, if somebody's interested on working on it, I think  
> it would be cool to see Harmony issues identified and resolved.
>
> --kevan
>
>
>
>
>
> -- 
> Mohan


Mime
View raw message