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

Nero M (JIRA) issues at jboss.org
Wed Jun 25 08:39:24 EDT 2014


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

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

In contrary to one of my previous posts i found out that the error only occurrs when there is an EAR Project in the workspace. 
I retried to start Jboss 4.2.3 on a new and empty workspace, set the "use the JBoss deploy folder" option. Started Server... worked.. waited for more than 20seconds..

So far so good...  Created an empty EAR ( default settings ) nothing fancy. Error comes back.. Now i can just "close" the EAR project. restart the server ->> WORKS. Reopen project -> FAIL

My guess it has something to do with the deployable projects detection or build detection, since it happens only when there is something which can be deployed on server.

IDE Screenshot with error:   http://abload.de/img/scrn191sug.png
IDE Screenshot without error:  http://abload.de/img/scrn2cisqd.png

Thanks

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


More information about the jbosstools-issues mailing list