|Re: Application is loaded by 2 classloaders [message #523432 is a reply to message #523422]
||Fri, 26 March 2010 13:38
| Larry Isaacs
Registered: July 2009
> You are right. It appears that tomcat is running 2 classloaders and
> Eclipse has nothing to do with that. However, I cannot get it working as
> it should. I will ask a question in tomcat's forum.. If someone here has
> experienced similar behavior and has some idea I will be grateful for
> any info. Thank you and sorry for the post.
I believe there has been, or still is, a quirk in server "publishing".
If you remove a project from a server and restart Eclipse without
publishing the server, the server handling may fail to remember that
though the project has been removed, the published copy of the project
still needs to be deleted from the server. This published copy can get
left behind. Normally for Tomcat, this copy gets left behind under
"wtpwebapps" and has no impact when the Tomcat server is run (i.e. there
is no <Context> to serve it). However, if you used the "webapps" folder
instead of "wtpwebapps", a published project left behind under "webapps"
would continue to be served. While it's more likely the cause of the
problem is in your web application, this scenario could be a
possibility. If you think the scenario is possible, just create a new
Tomcat server, add your project, then see if the same symptom appears.
If it does, you have confirmation it's not a "left behind" published
Note: The only "pluto" I'm aware of is Apache Pluto, which is a portlet
container and not a servlet container. I don't know enough about
portlet containers to say if this could explain the behavior you are
seeing, but I know there are differences.
Powered by FUDForum
. Page generated in 0.02031 seconds