[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5918) Seam ear project is sometimes undeployed incorrectly

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-5918:
------------------------------------

I'm really not able to replicate this and I've tried for a while now. 

I suppose there's always a *chance* that JMX is failing on the call to restart scanning, though I find that *extremely* unlikely. The reason I find it extremely unlikely is if the call to STOP scanning goes through, odds are very strong that the call to re-start scanning will also go through. 

A glance through the code shows that even if a publish exception is thrown, the jmx call to restart scanning still gets called. So I'm not sure why this would be. 

In My recent tests though I noticed no failures at all. 

> Seam ear project is sometimes undeployed incorrectly
> ----------------------------------------------------
>
>                 Key: JBIDE-5918
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5918
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>         Environment: JBDS 3.0.0. #173, RHEL 5 Client, OpenJDK 1.6
>            Reporter: Jiri Peterka
>            Assignee: Rob Stryker
>             Fix For: 3.1.1
>
>
> There is strange undeployment, here is wha I did.
> 1. Install new JBDS eclipse with EAP
> 2. Start server
> 3. Create seam ear project testseam1 (everything default)
> - project is deployed and information is in the console view
> 4. Click on testseam1 project and run on the server on context menu
> - chek it in the internal browser
> 5. Click on the server in server view
> 6. "Add and remove" and undeploy all
> - deployed files are removed from the jboss-deploy folder, but no information about undeployment is present neither in console nor in log files 
> and what is strange, seam project is still accessible through eclipse web browser
> When deploy/undeploy without JBDS it works fine. I was able to duplicate this only on RHEL and not everytime. Usually for the first time with clean installation.
> It's not critical because after some time or eclipse restart it works normal. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira