[jbosstools-issues] [JBoss JIRA] (JBIDE-17668) JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x)

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-17668:
---------------------------------------

Nero, I can reproduce this on Windows. I think we will be able to take it from here.
Steps are easy (just like Nero reported):
1. Start JBoss Tools/JBDS
2. Add JBoss AS 4.2.3 server
3. Open server editor, go to Deployment tab, change deployment settings to Use the JBoss deploy folder, save
4. Create a an empty EAR project
5. Start the JBoss server
6. Wait a few seconds, you will get errors - see Nero's screenshot above.

It seems the tooling tries to deploy everything in the deploy folder again (which in case of JBoss AS 4.2.3 means many of the services).
I think this is the culprit:

Workaround: Use workspace metadata for the deployment (this is the default) or a custom directory.

I suspect that this may affect JBoss AS 5/6 and EAP 5.x as well.

> JBoss 4.2.3 Hot Deployment does not work (worked with 4.1.x)
> ------------------------------------------------------------
>
>                 Key: JBIDE-17668
>                 URL: https://issues.jboss.org/browse/JBIDE-17668
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 4.2.0.Beta2
>         Environment: Win7 x64, Eclipse Luna 4.4 RC3, JBoss 4.2.3GA
>            Reporter: Nero M
>            Priority: Blocker
>         Attachments: duplicate-scanner.png
>
>
> When i start JBoss 4.2.3GA i get this:
> org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.remoting:type=Connector,name=DefaultEjb3Connector,handler=ejb3
> 	at org.jboss.system.ServiceCreator.install(ServiceCreator.java:103)
> Then when i change any file (just an xhtml for instance) The Server shuts down. Instead it should just hot-deploy that file like it did with Kepler + AS Tools 4.1. But here it seems a full deployment is being done (Not just the file) resulting in a Server reboot 
> 12:09:29,452 INFO  [EARDeployer] Undeploying J2EE application, destroy step: file:/C:/server/jboss/............ear
> 12:09:29,452 INFO  [EARDeployer] Undeployed J2EE application: file:/C:/server/jboss/..........................ear
> Thanks for any help :( If this is not fixed, we cannot move to Luna. unfortunately i cant move to a different application server



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)