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

[Nero M (JIRA)]

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

Nero M commented on JBIDE-17668:
--------------------------------

Just FYI : Ive also tryed to use the context menu "incremental deploy" method to redeploy, but this also results in JBoss 4.2.3 trying to redeploy the ear - which of course a.) Is very slow and b.) sometimes simply doesnt work especially if there are EAR-dependency

The desired behaviour should be that only the changed file is being redeployed without touching the EAR/WAR folders or doing any communication to JBoss. 

Ive found a workaround for now which is to set the following in jboss-service.xml

<attribute name="ScanEnabled">false</attribute>

 However this is not very desired, because each time i change a small file , the workers redeploy very slowly, the change sometimes is visibly only 2minutes later. (Note: The EARs we have are very big) 

> 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
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 4.2.0.Beta3
>
>         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)