For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 24 replies, 4 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
This seems to be a known bug with JDK 1.4.1, try upgrading to 1.4.2_05:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=71044i mentioned in my previous messages that
JDK ——j2sdk1.4.2_05Yes, but I wasn’t paying attention… that’s the key here.
I’m pretty stumped here to be honest… the “atomic bomb” test I can think of is:
1) Redownload Tomcat 4.1.x (zip) and unzip it to a new location
2) Redownload Eclipse 3.0.1 and MyEclipse 3.8.2
3) Do an entirely fresh install of Eclipse and MyEclipse
4) Setup the connector and hit Start, did it work? If THAT didn’t even work then there is something sinister going on.. make sure you don’t have stray libs lying around in your <jdk dir>\jre\lib\ext directory and make sure you have the connector to launch Tomcat and Eclipse are all setup to be 1.4.2 (maybe uninstall any old Java versions you have installed).Riyad,
I got a pop up window saying “Hot code is not in sync …”
and gives me three options like”continue,terminate,restart”…Why this happens and what action do i need to take?
I got this message previously and after few days tomcat server was not starting from ME..
Thank you
Why this happens and what action do i need to take?
This message is actually sent from the application server, intercepted by the Eclipse debugger and shown to you. Essentially when using an exploded deployment, MyEclipse will hot-deploy your changes immediately upon saving the file. Most of the time the applciation server will happily reload the changes after a certain amount of time (e.g. 15 seconds). However if your class’s structure changes too much (methods, member variables, etc.) then the application server is unable to cleanly reload the class without restarting the web application (using the Tomcat manager) or restarting the entire application server… when this happens it sends back a warning to Eclipse to let it know that the user should likely restart it… this is the dialog you are seeing.
What I like to do is keep an extra browser window open with Tomcat manager open in it, and when I get this message I hit “continue” and alt-tab over to my browser and hit “reload” for that particular web application, that does the trick nicely.
