[jboss-jira] [JBoss JIRA] (WFLY-2391) Wildfly caches content in exploded mode, breaking developer productivity

[Chris R. (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12825455#comment-12825455 ] 

Chris R. edited comment on WFLY-2391 at 10/29/13 10:34 AM:
-----------------------------------------------------------

EDIT: 

I removed caching from servlet container, deploying is now possible

I removed:
                <buffer-cache name="default" buffer-size="1024" buffers-per-region="1024" max-regions="10"/>

I'm unable to deploy my projects now:

11:27:20,808 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "foo_frontend.war")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"foo_frontend.war\".INSTALL"],
    "Services that may be the cause:" => [
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
        "jboss.undertow.bufferCache.default"
    ]
}}


                
      was (Author: goot):
    I removed 
                <buffer-cache name="default" buffer-size="1024" buffers-per-region="1024" max-regions="10"/>

I'm unable to deploy my projects now:

11:27:20,808 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "foo_frontend.war")]) - failure description: {"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
    "Services that were unable to start:" => ["jboss.deployment.unit.\"foo_frontend.war\".INSTALL"],
    "Services that may be the cause:" => [
        "jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
        "jboss.undertow.bufferCache.default"
    ]
}}


                  
> Wildfly caches content in exploded mode, breaking developer productivity
> ------------------------------------------------------------------------
>
>                 Key: WFLY-2391
>                 URL: https://issues.jboss.org/browse/WFLY-2391
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Undertow)
>    Affects Versions: 8.0.0.Beta1
>         Environment: MacOSX with JBossTools 4.1.1.Beta1
>            Reporter: Xavier Coulon
>            Assignee: Stuart Douglas
>         Attachments: jboss-as-kitchensink-html5-mobile.war.zip
>
>
> While I was building a sample application with JBoss Tools 4.1.1.beta1 on WildFly 8.0.Beta1, I noticed that after a few minutes (or a few browser requests), the content of my index.html file seemed to be cached by the server, although I used the "exploded content" deployment mode (since I published the content using the WildFly Server Adapter in JBoss Tools).
>  
> I checked the actual content of the index.html in the deployments folder and it contained the latest changes, which means that the JBoss Tools Server Adapter is doing its job well ;-)
> I also tried to edit the index.html file directly in the deployments folder, and once again, I got no update in both Chrome and Firefox browsers.
>  
> I checked in the "Network" tab of the browsers and could see that the server response for the index.html page had a "200 OK" status, which means that there's no browser caching involved.
> I tried to get the index.html page with cUrl and got the same old version, which definitely excludes a browser caching issue.
> At the end of the dat, this means that after a few changes, my browsers keep getting an old version of the deployed resources, which in turns means that I have to stop and restart the server to get the new content, and this is pretty bad in term of dev productivity.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira