Petr Blaha asked me to attach file :
Userdir/tomcat55.properties

I would also highlight :
- I hadn't imported any settings, it was running with new build for the first
time on the new userdir, with default settings
- the only actions/steps I'd done are mentioned in the report, no changes in
properties, no additional installed servers.... 

Created attachment 33012 [details]
tomcat55.properties file created in my userdir

We also found out, that in Properties dialog over the Bundled Tomcat node (in
Runtime tab under Servers node), there is the property :
"Catalina Base "
the value is :
"{MYUSEDIR}/apache-tomcat-5.5.17_base"

BUT there is no such directory created. So probably this is the root of all
these problems.

This is not a P1 -> P3 see the bug priority guidelines

http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html

I cannot reproduce it, so it seem more like some local problem, not a real
issue. Marking as INCOMPLETE until more info is be provided

Please make sure that no other Tomcat instance is runnning on the bundled Tomcat
port (8084 is the default port for the bundled Tomcat).

If this is not the problem, please attach your IDE message log and
$nb_userdir/apache-tomcat-5.5.17_base/conf/tomcat-users.xml file

Hey Stepane, Marian says that directory $nb_userdir/apache-tomcat-5.5.17_base
does not exist, so he can not attach tomcat-users.xml. Did you try to reproduce
it using the same build of JDK 6?

> This is not a P1 -> P3 see the bug priority guidelines
This is P1 : Product feature does not work, no workaround exists 

> I cannot reproduce it, so it seem more like some local problem, not a real
> issue. Marking as INCOMPLETE until more info is be provided

After almost an hour I found (with friendly help from Petr), that the problem is
in running another instance of Tomcat on the same machine, as you said above on
the same port 8084. 

I am just curious , How regular user (if she is running another tomcat on the
same port , I agree it's not very common usecase, but nobody could say it's
impossible) can find  why it actually doesn't work ? So why do you not provide
the original tomcat instance under the Servers node in runtime tab, or why you
don't inform user about already running tomcat server, when she run the project,
or why you are not asking to register to already running tomcat server ? I think
there is a lot of options how it could be solved, but one is general: please do
something, because in the current state it simply doesn't work.

P1 -> P3

> This is P1 : Product feature does not work, no workaround exists 

It does exist, just stop the other Tomcat instance and then start the one in
your IDE.

Closing as INVALID.

As you noticed the problem was that there was another Tomcat instance running,
this is also why the catalina base directory was not created.

There is unfortunately no way how we could find out which Tomcat instance is
running on a given port and thus we cannot provide any useful hint to the user.

As I've already said, you are asking for the name/server of "some" running
tomcat and you don't know where is this tomcat from? 

> INVALID: The problem described is not an issue
- thi is an issue, if I can't run my application from NetBeans - I think it's an
issue, isn't it ?

I understand that it was a flustrating experiance for you but please be
reasonable. I gave you a workaround and your raised the priority back to P1 w/o
any explanation. Changing priority and resolution back and forth is
good-for-nothing, so I am giving up.

I doubt that a normal user will ever use two NB instances simultaneously, so
this is really a corner case. More over, if you start one Tomcat from one IDE
and have troubles loggin in 'another' Tomcat instance running on the same port,
you could suspect that there might be some conflict and then find out what is wrong.

Anyway, since there is no way this could be fixed I have to close this issue as
WONTFIX. Please do not open it, unless you provide a patch or at least detailed
explanation how we can fix it. If you provide the explanation, please make sure
that it really works. Thanks

> I understand that it was a flustrating experiance for you but please be
Yes it was.

> reasonable. I gave you a workaround and your raised the priority back to P1 
ok, step by step  :
Is this P1 as defined by priority guideline :
YES
Is this INVALID ?
No.
SO shy not to reopen ?
...

> w/o any explanation. Changing priority and resolution back and forth is
> good-for-nothing, so I am giving up.

So please be "reasonalbe" and find out fix or workarround.



> I doubt that a normal user will ever use two NB instances simultaneously, so
> this is really a corner case. More over, if you start one Tomcat from one IDE

Ok, does it mean tomcat can't be run more than once on the same computer ? There
is nothing like this in the documentation, is it ?

> and have troubles loggin in 'another' Tomcat instance running on the same 
> port,you could suspect that there might be some conflict and then find out 
> what is wrong.
... you suspect .... how ? why ? all properties in IDE are pointing you to the
current build/run of NB+tomcat, so if the user trust the IDE, and I hope they
do, there no reason to look somewhere else ....

> Anyway, since there is no way this could be fixed I have to close this issue 
> as WONTFIX. Please do not open it, unless you provide a patch or at least 
There is no way? Does it mean you don't know about running tomcat in the port
you tried to run another one ? There has to be some log or fail ... isn't there ?

> detailed explanation how we can fix it. If you provide the explanation, please
> make sure that it really works. Thanks
;) This is really very very nice, something like do it yourself doesn't look
like serious help or at least try to help, thanks.

So please provide patch ... try the fix, but don't close this issue as WONTFIX
untill you try atleast to do something, but closing.

After discussing this issue in person we agreed on closing it

-> WONTFIX