[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] jetty taking long time to startupp
|
tubin,
The webapp won't redeploy if you change a static file that is part
of the webapp project itself. If however your webapp uses another
webapp in overlay that contains static files, if that webapp is
rebuilt, then your webapp will also redeploy.
regards
Jan
tubin gen wrote:
got jetty 7.1.0.v20100505 works fine ,
but reloading I am not clear.
I added <scanIntervalSeconds>10</scanIntervalSeconds> and
<reload>automatic</reload> to my jetty configration,
any time I make change to html or css whole application is restarted
which takes time ,is there a better way to reload static files like
css or html ?
On Mon, May 24, 2010 at 2:52 PM, Jesse McConnell
<jesse.mcconnell@xxxxxxxxx <mailto:jesse.mcconnell@xxxxxxxxx>> wrote:
http://repo2.maven.org/maven2/org/eclipse/jetty/
if you picked up pre0 them your looking in the wrong place..
7.1.2 was recently released
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx <mailto:jesse.mcconnell@xxxxxxxxx>
On Mon, May 24, 2010 at 13:43, tubin gen <fachhoch@xxxxxxxxx
<mailto:fachhoch@xxxxxxxxx>> wrote:
> Ok I moved to jetty 7.0.0pre0
>
> I end up with this error.Please help me.
>
>
>
>
> + Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Building audit.war Maven Webapp
> [INFO] task-segment: [jetty:run]
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Preparing jetty:run
> [INFO] [groovy:generateStubs {execution: default}]
> [INFO] No sources found for Java stub generation
> [INFO] [resources:resources]
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] Copying 218 resources
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [groovy:compile {execution: default}]
> [INFO] No sources found to compile
> [INFO] [groovy:generateTestStubs {execution: default}]
> [INFO] No sources found for Java stub generation
> [INFO] [resources:testResources]
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory
> E:\workspace\Audit.gov\audit.war\src\test\resources
> [INFO] [compiler:testCompile]
> [INFO] Not compiling test sources
> [INFO] [groovy:testCompile {execution: default}]
> [INFO] Test compiliation is skipped
> [INFO]
>
------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Failed to configure plugin parameters for:
> org.mortbay.jetty:jetty-maven-plugin:7.0.0pre0
>
>
> Cause: Cannot find setter nor field in
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext for 'jettyEnvXml'
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error
configuring:
> org.mortbay.jetty:jetty-maven-plugin. Reason: Unable to parse the
created
> DOM for plugin configuration
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:707)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
> 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.apache.maven.plugin.PluginConfigurationException:
Error
> configuring: org.mortbay.jetty:jetty-maven-plugin. Reason: Unable
to parse
> the created DOM for plugin configuration
> at
>
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1356)
> at
>
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:717)
> at
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:461)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
> ... 16 more
> Caused by:
>
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Cannot find setter nor field in
> org.mortbay.jetty.plugin.Jetty6PluginWebAppContext for 'jettyEnvXml'
> at
>
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.<init>(ComponentValueSetter.java:68)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:134)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.fromConfiguration(ObjectWithFieldsConverter.java:90)
> at
>
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:247)
> at
>
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:137)
> at
>
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:56)
> at
>
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:1350)
> ... 19 more
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Total time: 4 seconds
> [INFO] Finished at: Mon May 24 14:41:12 EDT 2010
> [INFO] Final Memory: 30M/53M
> [INFO]
>
------------------------------------------------------------------------
>
>
> On Mon, May 24, 2010 at 2:24 PM, Joakim Erdfelt
<joakim@xxxxxxxxxxx <mailto:joakim@xxxxxxxxxxx>> wrote:
>>
>> Unless you are doing work against bleeding edge Servlet 3.0
spec, do not
>> use Jetty 8.x, stick with Jetty 7.x.
>> The configuration process for Servlet 3.0 spec is very heavy on
>> WEB-INF/lib analysis and discovery of configuration pieces.
analysing all
>> tlds, xml files, and even the classes themselves for annotations.
>> If you have a very large webapp, or a large set of jar files in
>> WEB-INF/lib, the startup will take a while with Servlet 3.0 spec.
>> - Joakim
>> On Mon, May 24, 2010 at 9:21 AM, tubin gen <fachhoch@xxxxxxxxx
<mailto:fachhoch@xxxxxxxxx>> wrote:
>>>
>>> I am using maven jetty plugin version 8
>>> here is my pom configration for jetty
>>>
>>> <plugin>
>>> <groupId>org.mortbay.jetty</groupId>
>>> <artifactId>jetty-maven-plugin</artifactId>
>>> <version>8.0.0.M0</version>
>>> <configuration>
>>> <scanIntervalSeconds>10</scanIntervalSeconds>
>>> <webAppConfig>
>>> <contextPath>/artms</contextPath>
>>> <jettyEnvXml>${basedir}/jetty-env.xml</jettyEnvXml>
>>> </webAppConfig>
>>> <reload>automatic</reload>
>>> </configuration>
>>> <dependencies>
>>> <dependency>
>>> <groupId>commons-dbcp</groupId>
>>> <artifactId>commons-dbcp</artifactId>
>>> <version>1.2.2</version>
>>> </dependency>
>>> <dependency>
>>> <groupId>com.oracle</groupId>
>>> <artifactId>ojdbc</artifactId>
>>> <version>14</version>
>>> </dependency>
>>> </dependencies>
>>> </plugin>
>>> yes the log4j error is through my app.
>>>
>>> On Mon, May 24, 2010 at 11:17 AM, Jan Bartel <janb@xxxxxxxxxxx
<mailto:janb@xxxxxxxxxxx>> wrote:
>>>>
>>>> tubin,
>>>>
>>>> What version of jetty are you discussing?
>>>>
>>>> Also, there is an error logged in the log4j logger - is that an
>>>> error from your app?
>>>>
>>>> thanks
>>>> Jan
>>>>
>>>> tubin gen wrote:
>>>>>
>>>>> jetty takes 4 minutes after it logs this
>>>>> *2010-05-21 15:26:47.975*:INFO::No annotation on initializer
class
>>>>> org.apache.jasper.runtime.TldScanner log4j:ERROR Parsing
error on line 10
>>>>> and column 14 log4j:ERROR The content of element type
"layout" must match
>>>>> "(param)*". *2010-05-21
15:30:01.488*:INFO:/artms:Initializing Spring root
>>>>> WebApplicationContext
>>>>>
>>>>> please tell me why is it taking so long
>>>>> see the time difference for both the below lines
>>>>>
>>>>> **2010-05-21 15:26:47.975*:INFO::No annotation on initializer
class
>>>>> org.apache.jasper.runtime.TldScanner *
>>>>>
>>>>> *2010-05-21 15:30:01.488*:INFO:/artms:Initializing Spring root
>>>>> WebApplicationContext
>>>>>
>>>>>
>>>>>
------------------------------------------------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> jetty-users mailing list
>>>>> jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
>>>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>>>
>>>> --
>>>> Jan Bartel, Webtide LLC | janb@xxxxxxxxxxx
<mailto:janb@xxxxxxxxxxx> | http://www.webtide.com
>>>> _______________________________________________
>>>> jetty-users mailing list
>>>> jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
>>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>>
>>>
>>> _______________________________________________
>>> jetty-users mailing list
>>> jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
>>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>>
>>
>>
>> _______________________________________________
>> jetty-users mailing list
>> jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>
>
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>
>
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx <mailto:jetty-users@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/jetty-users
------------------------------------------------------------------------
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jetty-users
--
Jan Bartel, Webtide LLC | janb@xxxxxxxxxxx | http://www.webtide.com
