[jbosstools-issues] [JBoss JIRA] (JBIDE-10903) Deploy folder sometimes not added to JBoss deployment path list

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-10903:
-------------------------------------

The event is being triggered as follows:

 1) You click 'start' or 'run' on the server
 2) The server launches, and a "poll thread" is launched in the background
 3) this poll thread uses a specified mechanism to check if the server is up or down every few seconds
    a) This mechanism can be chosen in the server editor, double-click your server, and on the right side, you'll see a polling section. Choices are things like jmx, as7 management, web port, etc. 
 4) Once the poll thread decides the server is up, it sets the server state to 'started'. You should notice this in the server view
 5) Once the server has been marked as started, one of the server state change listeners gets alerted the state has been set to 'started' in the servers view, and then begins to add the server folder. 

I've added some more tracing to both JMXServerLifecycleListener and LocalJBoss7DeploymentScannerAdditions, but there's not really much more tracing that can be done. I'm not sure what level fo debugging is appropriate here. As of now all I'm tracing is when I actually add a url over the wire. If there were any exceptions they'd already be logged. I'm not sure how useful these will be to replicating the issue, but, more logging is better than no logging
                
> Deploy folder sometimes not added to JBoss deployment path list
> ---------------------------------------------------------------
>
>                 Key: JBIDE-10903
>                 URL: https://issues.jboss.org/browse/JBIDE-10903
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS/Servers
>    Affects Versions: 3.3.0.M5
>         Environment: Windows 7 / Eclipse Indigo SR1 / JBoss 4.2.3 
>            Reporter: Daniel Atallah
>            Assignee: Rob Stryker
>             Fix For: 3.3.0.Beta3
>
>
> A number of people in my team have run into intermittent issues where when the Server is started, the deploy folder that is specified in the Server "Deployment" tab doesn't seem to ever get added to the list of locations that JBoss looks for stuff to deploy.
> We're using a custom deploy folder (it's an ordinary directory on a local drive).
> The normal course of operations is that JBoss starts up successfully and outputs the following line:
> {noformat}19:41:06,117 INFO  [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 15s:550ms{noformat}
> Then, if things work successfully, a few seconds later the following output appears and my EAR is deployed (my custom deploy folder is "C:/export/spare/Devl-JBoss/development/dev/deploy"):
> {noformat}19:41:14,948 INFO  [EARDeployer] Init J2EE application: file:/C:/export/spare/Devl-JBoss/development/dev/deploy/Foo.ear/{noformat}
> If things don't work successfully, the second line never appears and the server just sits there without any of the deployed resources being available.
> Not being familiar with how the JBoss Tools integration works, it looks to me that JBoss Tools is somehow waiting for the Server to start up fully before adding the deploy folder and in the cases where it doesn't work, it never notices that the Server has started up so it never adds the deploy folder.
> I've tried setting the server logging to TRACE level and when it isn't working, the custom deploy folder doesn't appear anywhere in the log output.
> This issue is intermittent, I haven't been able to identify any specific scenarios under which it is triggered.
> When it does happen, sometimes restarting the server will resolve it, but other times we need to do a "Clean" publish to the server, and sometimes even that will not fix the issue (more than once deleted my workspace .metadata and started clean to get it working).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira