[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7814) User is not notified when deployment fails

Rob Stryker (JIRA) jira-events at lists.jboss.org
Tue Dec 14 11:51:53 EST 2010


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

Rob Stryker commented on JBIDE-7814:
------------------------------------

In the past we only showed the error message and jmx box when JMX poller was used, never for publishing. Publishing never got a front-and-center error message and was alwyas silently logged. Always. So this is not a regression at all. 

> User is not notified when deployment fails
> ------------------------------------------
>
>                 Key: JBIDE-7814
>                 URL: https://issues.jboss.org/browse/JBIDE-7814
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.2.0.Beta2
>            Reporter: Libor Zoubek
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.2.0.CR1
>
>         Attachments: JBIDE-7814.jpg, serverlog.jpg
>
>
> AFAIK when deploying we are calling server via JMX. What happens when JMX call is not successful? Nothing good. Studio shows project as deployed, but app server in worse case does not know about deployment (when target dir is set to workspace), in better case notices it after a few seconds.
> User than can only guess what and why is his project not deployed.
> This confusing behavior can be simply reproduced on any soa-p server, since you have to uncomment 'admin=admin' line in file /server/default/conf/soa-users.properties to make JMX working. If you do not do that, you'll reproduce.
> AS Adapter should warn user on JMX call errors.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list