|Problems with publishing to Tomcat [message #758251]
||Tue, 22 November 2011 07:42
| Mauro Molinari
Registered: July 2009
this message is particularly for Larry Isaacs, that I know is the
WebTools developer that cares this part of WTP.
It happened many times to me (and quite often to my co-workers) that
problems are encountered while publishing to Tomcats. Which kind of
problems? The deployed folder is in some way corrupted: completely empty
(although WTP says the webapp is published) or partially empty. In these
cases, usually a "clean" on the server is needed to make things work
again (trying to perform "Publish" is useless, because WTP thinks the
server is already published), but recently, with Indigo, it seems like
the Clean operation is not so effective, so that removing the web module
from the server, publishing, re-adding the web module to the server and
publishing again is needed to get it working again.
This is obviously time consuming especially if working on large
projects. Moreover, it gives the user a feeling that all these tools are
not working at all.
I wrote some times here on the newsgroups and I saw other people
experiencing this kind of problems, but nobody could provide easy steps
to reproduce to help Larry to investigate and fix this problem. I still
don't have the steps to reproduce, however I know for sure that these
kind of things happen whenever WTP has some problems writing on the
deploy folder or (more easily) deleting contents from the deploy folder.
This may happen particularly in Windows when JARs are locked (either by
the running server itself or for other reasons). But my co.workers using
Linux recently see this problem almost always.
The problem is that we are working with a huge proprietary project and
we are using a lot of Eclipse plugins and maybe it isn't even WTP's
fault. So it's not easy to isolate a test case to reproduce and submit a
However, the main problem is that when publishing errors occur:
- no error reporting is performed at all (maybe something is written in
the error log?) -OR-
- an error is printed, but WTP thinks the publishing has been performed
all the same, so the server gets to the "Published" state even if
contents are not really published
In any case, a corrupted state is reached and cleaning or
removing/readding the webapp from the server is needed to fix that.
So, my request is: could at least WTP be made more resilient to
publishing errors? Could errors be reported cleanly and make the
publishing fail, so that the user may retry later, without having the
server reach a corrupted state?
I may help Larry to diagnose the problem and try some patches if needed
(although it would be necessary for these patches to be against WTP
3.3.x/Indigo). I would appreciate very much any feedback on this.
Thanks in advance,