[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=12979214#comment-12979214 ] 

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

Yea sure it was a fresh workspace, fresh Eclipse 4.4 RC3 Luna, JBoss Tools 4.2.0 Beta2  (tried nightly too), and fresh JBoss 4.2.3GA

When using the eclipse metadata it works, but i need the deployments on the JBoss folder. But the error happens without deployments too, only setting that radio button is enough for the exceptions to come

Did you try too and for you the error did not come? strange.. 

> 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
>
> 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)