Skip to main content

unlock the static files while jetty is running on windows.

When running a java maven web application  in jetty on windows. All static files are locked and not able edit and save those files while jetty is running.

This will eat developers time beacuse each and every change in javascript & css files, jetty have to re-started. Depends on application's dependencies that build will take more than 5minutes.

Why jetty is locking the static files?

Jetty buffers static content for webapps such as html files, css files, images etc and uses memory mapped files to do this if the NIO connectors are being used. The problem is that on Windows, memory mapping a file causes the file to be locked, so that the file cannot be updated or replaced. This means that effectively you have to stop Jetty in order to update a file



Jetty provides a configuration switch in the webdefault.xml file for the DefaultServlet which enables or disables the use of memory mapped files. If you are running on Windows and are having file locking problems, you should set this switch to disable memory mapped file buffers.

webdefault.xml:
The webdefault.xml file saves web applications from having to define a lot of house-keeping and container-specific elements in their own web.xml files.

Here is the solution to solve that problem:

1. Find the jetty jar in maven repository normally in windows path will be C:\Documents and Settings\<user>\.m2\repository\org\mortbay\jetty\jetty\6.1.25\jetty.jar.
Extract the jar  and find the webdefault.xml org/mortbay/jetty/webapp/webdefault.xml



2. Change the value for "useFileMappedBuffer" from "true" to "false" in webdefault.xml

<init-param>   <param-name>useFileMappedBuffer</param-name>   <param-value>true</param-value> <!-- change to false --> </init-param>

3. copy the webdefault.xml to your applicaiton dierectory "src/main/resources"

4. Edit your POM to specify the custom webdefault.xml in jetty plugin
    Add the below in jetty plugin configuration under the tag <WebAppConfig>
    <defaultsDescriptor>webdefault.xml</defaultsDescriptor>


<plugin>
               ..........
                <configuration>
                    <webAppConfig>
                        <contextPath>/</contextPath>
                         .................
                        <defaultsDescriptor>webdefault.xml</defaultsDescriptor>
                    </webAppConfig>

                </configuration>
              ...............

</plugin>


that's all... now we can edit & save the static files while jetty server is running.


Happy coding...

Comments

  1. ParameswaranAugust 5, 2011 at 3:56 PM

    nice one. It really saves my time when i work on the css and .js files.

    ReplyDelete
  2. Stephen BoeschMay 29, 2014 at 10:01 PM

    I am using jetty 9 on windows7 32 bit. Unfortunately this solution does not work on that combination.

    ReplyDelete

Post a Comment

Popular posts from this blog

Running and debugging jetty maven plugin in Netbeans

Coding with Netbeans will make developer life simple. We don't need search for plugins and install different plugins from different places. Maven projects can opened as directly in Netbeans without any settings. Here is the way to run & debug using maven jetty plugin. We can't add Jetty server as servers in Netbeans. Run project: Right click on project and open the properties. click on "Actions" on left side. On right side there will be list of available actions.  To run jetty can be created a new action or override default "Run Project" Here I am overriding default one, Because I can run the project just by hitting "F6" key click on "Run Project" Enter the value "Execute Goals" as "jetty:run", If you want run as offline add "jetty:run -o" "Active Profiles" can be empty In "set Properties" field we can set like skip test. Here I am skipping test. Done, After setting y
2 comments
Read more

remove(unset) property in a property file using ANT PropertyFile task

Using PropertyFile task we can edit the property file during ANT build. Edit property value are very easy and can find here details. http://ant.apache.org/manual/Tasks/propertyfile.html but delete a property or comment a property is the tricky one. If we are using latest ant version (1.8.1 or later), we can delete a property like below. <propertyfile file="my.properties" comment="My properties">   < entry  key="propertykey" operation="del"/> < /propertyfile> but the older version that is before 1.8.1 don't have operation called " del ", if we run the command in lower version ant, we will get a error says undefined operation "del".      there is workaround instead deleting a property we can comment that property using ant's replace command. < replace file="sample.properties">                      < replacefilter token="propertykey" value="#propert
Post a Comment
Read more

Disable hibernate Optimistic Lock for specific scenario

Optimistic Lock gives more control on concurrent modification on data. That can be achieved very easily in hibernate using @Version column. But in some cases we may have to avoid concurrency check, example background process. To disable Optimistic lock set OptimisticLockMode as NONE for entity class while hibernate is initiating. We can't remove version column that needs Database changes and ORM changes. In this way we can disable Optimistic Lock by code. implement "org.hibernate.event.Initializable" interface override the below method.     @Override     public void initialize(Configuration cfg) {         Iterator<?> persistentClassIterator = cfg.getClassMappings();         while (persistentClassIterator.hasNext()) {             PersistentClass persistentClass = PersistentClass.class.cast(persistentClassIterator.next());                     Iterator propertyIterator = persistentClass.getDeclaredPropertyIterator();                    while (proper
Post a Comment
Read more