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 40432 - [36cat] Web Application deployer freezes.
Summary: [36cat] Web Application deployer freezes.
Status: VERIFIED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-24 17:50 UTC by llturro
Modified: 2004-08-04 16:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Deployer is in an endless loop (78.33 KB, application/zip)
2004-02-24 17:52 UTC, llturro
Details
Deployer finishes (17.90 KB, application/zip)
2004-02-24 17:53 UTC, llturro
Details
Tomcat log file (8.35 KB, text/plain)
2004-02-25 14:29 UTC, llturro
Details
NetBeans ide.log (94.70 KB, text/plain)
2004-02-25 14:31 UTC, llturro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description llturro 2004-02-24 17:50:25 UTC
[ JDK VERSION : J2SE 1.4.2_02 ]

I already posted an issue with this problem, but I couldn't find it anymore so I create a new one.

When importing a web application the deployer freezes. This are the steps I did in order to get the application running normally:

1) I imported the project (portal). When executed the deployer window froze.

2) I removed the project (portal) and renamed the source folder (/home/llturro/portal -> portal_x). 

3) Then I create a new folder (/home/llturro/portal) and a new project (portal).

--- At this point, if I deleted this new folder and renamed the portal_x to portal the problem will remain.

4) Using wizards I add a new Web Module.

5) Now, this is important, the way to get the project working was copying portal_x contents to portal. It may seem that simply adding this folder (portal_x) instead of portal will suffice... no!! don't!!

I'll post the two folders in /system/projects for you to see what is on.
Comment 1 llturro 2004-02-24 17:52:59 UTC
Created attachment 13617 [details]
Deployer is in an endless loop
Comment 2 llturro 2004-02-24 17:53:42 UTC
Created attachment 13618 [details]
Deployer finishes
Comment 3 Petr Jiricka 2004-02-24 19:06:58 UTC
Lluis, which IDE build are you using? What do you mean by that the
deployer "freezes"? Does the IDE become unresponsive, or something else?
Comment 4 llturro 2004-02-24 19:21:23 UTC
Build 200402221900.

This problem arises from Beta version, importing from 3.5.1, whereas
now developer version imported from beta. The deployer window shows no
messages after "Waiting for Tomcat...", I mean, this message is the
last one you're able to see. Then, with the progress bar at an 80%,
stops. You can close that window and run the application, with the
browser, without problems. But each time you want to execute, the
deployer window will show that 80% finished... for ever!!

I already know another person from NetCAT who said he also had the
same problem. He even executed the application from an external
instance of Tomcat.

I first thought it was related to some errors in my tag library's
descriptors (String attribute was to be changed to java.lang.String),
but this second time it's not.
Comment 5 Marek Fukala 2004-02-25 11:36:26 UTC
I have seen the problem when importing from 3.5.1 to netbeans 3.6
beta, but I cannot reproduce it for current trunk build. Lluis, have
you tried a last trunk build?
Comment 6 llturro 2004-02-25 12:12:53 UTC
Yes, I used the last build and imported from beta. Build 200402221900.

The project was running perfectly on beta, once I used the same trick
to unfreeze the deployer dialog. I'm able to reproduce it as many
times as I want. Do you need the project folder along with
.netbeans/3.6Beta/system/Projects/portal?

Comment 7 Petr Jiricka 2004-02-25 13:18:25 UTC
We don't really support importing settings from 3.6 beta, only from
3.5.1. If you can reproduce after import from 3.5.1, then this is
serious. Otherwise, I wouldn't consider it serious. BTW, could you
please also attach the IDE log file and the Tomcat log file? Thanks.
Comment 8 llturro 2004-02-25 14:29:57 UTC
Created attachment 13644 [details]
Tomcat log file
Comment 9 llturro 2004-02-25 14:31:05 UTC
Created attachment 13645 [details]
NetBeans ide.log
Comment 10 llturro 2004-02-25 14:35:31 UTC
I don't really thing it matters whether it was imported from 3.5.1 or
beta. The question is that the deployer process stops end no message
is given to the user. It first happened when importing from 3.5.1 to
beta, and now from beta to dev. And if there was a problem while
importing, then it would also be good to get a message.
Comment 11 Marek Fukala 2004-02-25 15:11:25 UTC
There is a significant difference between -importing- from 3.6 beta
and 3.5.1 so the only import from 3.5.1 to beta or a recent trunk
build should work. If it is possible I would really appreciate if you
try to import your old project from 3.5.1 to current trunk build and
let us know if the deployer freezed again.
Comment 12 llturro 2004-02-25 15:47:05 UTC
Marek, I do not doubt there might exist a difference importing from
one version or the other. I would not dare to tell you that since I'm
completely ignorant of what is imported and how. I meant that the
point is the dialog stops and gives no messages. 

About importing from 3.5.1, I'm sorry but I have not anymore 3.5.1
projects on my Linux.
Comment 13 Marek Fukala 2004-02-25 15:58:43 UTC
Now I understand your problem better ;-). The deployer status window
already provides a reasonable mechanism of displaying error messages,
unfortunately we need a reasonable case enabling us to reproduce the
problem. The primary problem is that the deployment is not possible
after the import. The missing message is only its consequence. I hope
that an error message always shows up when a -valid error- (like
tomcat start problem etc.) occures, but the case you described
(importing 3.6beta to 3.6) is not one of them. 
I have just sent an email to the netCat mailing list asking users to
help with this problem. Thanks you your help!
Comment 14 llturro 2004-02-25 16:53:39 UTC
Ok, I did the import from 3.5 version on my Windows XP. It worked!!

Now I have another issue. I had to manually add the slash on
ContextPath in the META-INF/context.xml (xmlportal -> /xmlportal)

And somethink more, tag libraries still need java.lang.String instead
of String. Will this be changed in future Tomcat releases?
Comment 15 Martin Grebac 2004-02-27 17:02:04 UTC
Well, lots of comments here - I'm lost. Could you please specify again
what's the remaining problem?

As for java.lang.String, it's better to ask on Tomcat users/dev lists.

Comment 16 llturro 2004-02-27 17:13:15 UTC
Hi Martin, I'm lost too!! ;-)). Anyway, the last try --with the last
build-- happened to work and I'd take care to reproduce the "manually
added slash".
Comment 17 Martin Grebac 2004-04-21 09:43:35 UTC
Well, seems like this has been fixed already. If not, please reopen.
Comment 18 Petr Blaha 2004-08-04 16:07:04 UTC
Verified