For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 5 replies, 3 voices, and was last updated 19 years, 10 months ago by
.
-
Posts
-
I can start and stop Websphere 5.1 server using MyEclipse. When I launch the Websphere 5.1 server in debug mode using MyEclipse, if I change any Java files , it says “Hot code replacement is not suppported” and I am forced to restart the server whenever I make a small change in the Java files in Debug mode. Is there any fix for this? Thanks in advance.
“Hot code replacement is not suppported”
That sounds like the JVM error message that you get when you’ve changed the “shape” of the file. Are the changes small ones, internal to one method, or more than that? Or, it could be that the IBM JDK for 5.1 doesn’t support hot code replacement at all. If that’s the case, since you *must* run WebSphere with a 5.1 JDK then I don’t think there’s anything that can be done about it.
I deployed my .ear file using Websphere 5.1 admin console. I am pointing my MyEclipse workspace directly to the Websphere deployed path. So that when I modify any JSPs or Java files using MyEclipse, it will directly reflect on the Websphere workspace. When I modify JSPs everything is fine. If I modify any Java files, it will be recompiled and replaced into WEB-INF/classes folder of Websphere workpace, but the server complains “Hot code replacement not supported: and I have to restart the server to reflect the changes made in the Java file. This only happens when I start the server in the debug mode. I know in Websphere Studio(WSAD) it does not happen and I can change Java files even in debug mode and there is no need to restart Websphere test environment. But using MyEclipse it does not behave that way. Any suggestions or ideas? Thanks.
I am using the JDK that comes with Websphere 5.1 install to run the appserver. Now I got it upto the point by using a VM argument -Xj9 to make the server allow for the Hot Code Replacement in the debug mode. So now it dynamically reloads the classes, but it restarts the enterprise application automatically everytime I make a change to a Java class that is already being loaded(executed by the server). I feel there is no need to restart the enterprise application(.ear) for a small change that I make in a Java class function. It should have a feature to support “Hot Method replacement”. Let me know your opinion. Thanks.
It should have a feature to support “Hot Method replacement”. Let me know your opinion. Thanks.
sekarramasubban, this is exactly what happens implicitly when you are running Eclipse with a 1.4+ VM as well as your app server, however some app servers require that you run them with the JDK they ship, and sometimes those VMs are either not new enough, or their interaction with the VM you are running Eclipse with does not allow the hot syncing to take place. Hot syncing is a very touchy function and is implemented by the VMs, if hotsync is failing it’s really a problem either with the VM you are running Eclipse with (the Eclipse debugger performs the sync) or the VM you are running your app server with.
