Issue copied in detail from
JBossTools has the following workflow when the workspace recognizes a change:
1) User changes files.
2) Server adapter tells server to stop scanning for changes in the directory we are copying to via deployment scanner (via jmx).
3) Server adapter copies files.
4) Server adapter tells server to start scanning for changes in the directory we are copying to (via jmx deployment scanner)
5) Server eventually sees the changes and redeploys/picksup the changes (depends on the kind of content, but thats unrelated to this I believe)
At some point, after using eclipse for a period of time (1 hour? etc) and executing hot deployments and publishes regularly, the server stops responding to further incremental changes and hot deployments. The theory was that step 4) was failing, which is re-enabling the deployment scanner. However, manually re-enabling it does not fix the problem. (There is no mbean to check the state of the deployment scanner. The relevent mbean only has setters for this setting).
So, as mentioned, when the server stops responding to hot deployments, manually re-enabling the deployment scanner does not fix the issue. Further incremental deployments are still not recognized, and only a restart of the application server fixes the issue. However, it is recurring.
Again, this issue is hard to track down, but all attempts to isolate the issue in tools indicate that jbosstools is properly updating class files, xml files, html files, and all other content in teh deployment folder. it is only the server which is no longer recognizing changes.