- This topic has 4 replies, 2 voices, and was last updated 20 years ago by
.
-
Posts
-
I have recently updated to 3.8.4 from 3.8.3. I am using Tomcat 5.0.28.
When I add a new servlet I’m getting a Hot Swap error. I don’t believe this happened in versions before 3.8.4. I used to only get this if I changed the signature of a class.
Is it supposed to be this way? Did I screw something up?
Thanks
WallyWally,
Can you give us a little more detail what the error is? Are you referring the popup dialog that Eclipse throws up talking about hotswap failing? That message is actually FROM the app server to the Eclipse debugger, so if you are seeing this message, then it means Tomcat is telling Eclipse that, independent of MyEclipse.Yes I am referring to the popup about HotSwap failing.
I’m pretty sure this didn’t happen with 3.8.3. Did anything change that I’m seeing the error now and maybe should have in the past?
If you did a reinstall or a -clean, it is *possible* that the setting to SHOW those warnings was turned back on (Window > Prefs > Java > Debug > “Show error when hotcode replace fails”)
Regardless, this is an Eclipse debugger setting, MyEclipse doesn’t effect it, so I’m guessing it just got turned on. I checked mine and it is turned off and I usually run with default settings.
Also note that in my experience, even though you get that message, the app will likely keep working just fine as Tomcat will usually reload the file without problems. However if the app server eventually dies with a VM termination, just restart it. Usually it gets overwhelmed with too many complex hotcode replacements. I like to just turn that warning off and keep working and just wait to see the console messages from Tomcat when it reloads my file before trying the page again that uses the code.
