This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 58255 - Impossible to deploy webapp
Summary: Impossible to deploy webapp
Status: CLOSED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 4.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: issues@serverplugins
URL:
Keywords:
: 56428 59174 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-04-24 10:40 UTC by _ gtzabari
Modified: 2006-03-24 13:04 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Tomcat component of bad userdir (21.32 KB, application/x-compressed)
2005-04-25 16:18 UTC, _ gtzabari
Details
Entire bad userdir (4.58 MB, application/x-compressed)
2005-04-26 18:32 UTC, _ gtzabari
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ gtzabari 2005-04-24 10:40:46 UTC
dev build 200504211800
JDK 1.5

Whenever I try running a webapp I get:

"Deployment error: TomcatManager.undeploy invalid TargetModuleID passed. See the
server log file for details."

There are no log files that I can see, nor does there seem to be a workaround
for this problem.
Comment 1 zikmund 2005-04-25 09:45:10 UTC
Does it fail only with 4.2? Or with 4.1 too?
Comment 2 Sherold Dev 2005-04-25 10:27:20 UTC
I can't reproduce it. Do you remember what you were doing before seeing this
issue for the first time? (e.g. changing tomcat settings, changing project
context path, "playing" with nb user dir...)

Can you please attach your user directory? Or at least your ".nbattrs" file and
whole "J2EE" folder from nb user directory?

Undeploying your application from the runtime window might work as a
work-around. Please attach your configuration files first, so that we can
analyze them.

Marking as INCOMPLETE until more info is available.

Thank you
Comment 3 _ gtzabari 2005-04-25 16:17:13 UTC
FYI: this is 100% to do with the userdir because when I moved down to dev build
200504171800 I still had the same problem, then I wiped out the userdir and the
problem went away.

So two things: 200504171800 doesn't exibit the problem but 200504211800 does as
far as I can tell and secondly I will attach my "bad userdir" to this issue so
you can take a look at it. In theory if you plug it into your own HD you should
be able to reproduce the error right away.
Comment 4 _ gtzabari 2005-04-25 16:18:39 UTC
Created attachment 21854 [details]
Tomcat component of bad userdir
Comment 5 Sherold Dev 2005-04-26 13:28:14 UTC
Unfortunately, the attached directory is not the NB user directory but the
Tomcat base directory, therefor I can't simulate your environment. Please attach
your NetBeans user directory if you experience this issue again.

Can you explain these two phrases? It looks like a contradiction

"when I moved down to dev build 200504171800 I still had the same problem"

vs.

"200504171800 doesn't exibit the problem"

Thank you
Comment 6 _ gtzabari 2005-04-26 18:32:11 UTC
Created attachment 21879 [details]
Entire bad userdir
Comment 7 _ gtzabari 2005-04-26 18:33:25 UTC
sherold,

What was I saying about 200504171800 is that if you use it with the bad userdir,
it exibits the problem but if you try it with a *fresh* userdir instead it works
fine. I hope that clarifies the situation :)
Comment 8 Sherold Dev 2005-04-28 18:21:37 UTC
Still can't reproduce this issue even if I use your userdir. I didn't find
anything suspicious in it except the weird project location:

"C:\Documents and Settings\Gili\My
Documents\blueeye\trunk\com\be\desktopbeautifier\DesktopBeautifierServer\netbeans4.1"

although I doubt it could cause any problems, especially if it worked with a new
user dir.

I've added some debug messages, which will hopefully help to discover what's
wrong. They should appear in the command line and in the
<NB_USERDIR>/var/log/messages.log. It would be really useful if you could try it
out and provide the log, in case if this issue occurs again.

I'm not sure whether the debug patch will be already in todays daily build but
it should definitely be in tomorrows daily build (of 4.2 release of course).
Comment 9 Sherold Dev 2005-05-02 16:22:00 UTC
It seems that this issue occurs only in the following scenario:

1. have a web application, set its context path to "/x" and deploy it
2. pick a context path which is already used on the server, lets say "/y" for
example and use it for your application
3. run deploy - the exception will pop up

The problem is that there are two web applications which need to be undeployed
"/x" and "/y" but the Tomcat module can currently undeploy only one.

Should be fixed for 4.2 - setting the TM.

Moving down to p3 since this is quite a rare use case and there is an easy
work-around: go to Runtime window/Servers/Tomcat and undeploy the module by hand.
Comment 10 Sherold Dev 2005-05-03 11:20:31 UTC
F.

Commit log:

Checking in tomcat5/src/org/netbeans/modules/tomcat5/TomcatManager.java;
/cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/TomcatManager.java,v 
<--  TomcatManager.java
new revision: 1.74; previous revision: 1.73
done
RCS file:
/cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/progress/MultiProgressObjectWrapper.java,v
done
Checking in
tomcat5/src/org/netbeans/modules/tomcat5/progress/MultiProgressObjectWrapper.java;
/cvs/tomcatint/tomcat5/src/org/netbeans/modules/tomcat5/progress/MultiProgressObjectWrapper.java,v
 <--  MultiProgressObjectWrapper.java
initial revision: 1.1
done
Comment 11 Jiri Kovalsky 2005-05-09 21:02:56 UTC
Verified in development build #200505081800 of NetBeans 4.2. If you encounter
this problem Gili again, don't hesitate to reopen this bug.
Comment 12 Jiri Kovalsky 2005-05-23 14:43:34 UTC
*** Issue 59174 has been marked as a duplicate of this issue. ***
Comment 13 zikmund 2005-06-03 13:16:47 UTC
*** Issue 56428 has been marked as a duplicate of this issue. ***
Comment 14 zikmund 2005-06-03 13:25:03 UTC
More duplicates appear in:
  issue 57353
  http://forum.java.sun.com/thread.jspa?threadID=601132

Increasing priority to P2.