[
https://issues.jboss.org/browse/JBIDE-17668?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-17668:
---------------------------------------
Unfortunately I can't reproduce this. Here's what I tried:
1. Create a JBoss AS 4.2.3 server
2. Create a dynamic web project with an index.html
3. Start the server and deploy the project (or in reverse order - tried both)
4. Change the html file and save
5. Now the deployment republishes and the change is visible after reloading the browser
I did not have the extra message in the server log that you reported. And the server
didn't stop or restart. Just the deployment was republished.
Next, I tried the same with an ear project. Again, no problem.
I can try this on windows later to see if that makes any difference.
Could you perhaps try with a clean workspace and a new installation of JBoss AS 4.2.3?
That would help isolate the issue.
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)