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 118010 - Tomcat is installed with too strict access restrictions
Summary: Tomcat is installed with too strict access restrictions
Status: RESOLVED DUPLICATE of bug 115367
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-06 19:24 UTC by jlaiho
Modified: 2007-10-09 10:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
WebApplication1 output when trying to run (410 bytes, text/plain)
2007-10-06 19:27 UTC, jlaiho
Details
Tomcat output when trying to start (1.13 KB, text/plain)
2007-10-06 19:28 UTC, jlaiho
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jlaiho 2007-10-06 19:24:20 UTC
When installing as root (with umask 0022, so shouldn't be an issue here), apache-tomcat-6.0.13 gets installed with too
strict access restrictions: files within apache-tomcat-6.0.13/conf are not readable by regular users.

As a result, when a regular user attempts to execute a web application project within Tomcat, the Tomcat startup will
fail with error message:

/home/jlaiho/NetBeansProjects/WebApplication1/nbproject/build-impl.xml:548: Deployment error:
Starting of Tomcat failed, Tomcat base dir doesn't exist.
See the server log for details.

... however, the directory structure does exist - but the configuration files do not - which is revealed by looking at
the server log. The relevant log snippets are attached.
Comment 1 jlaiho 2007-10-06 19:27:57 UTC
Created attachment 50309 [details]
WebApplication1 output when trying to run
Comment 2 jlaiho 2007-10-06 19:28:47 UTC
Created attachment 50310 [details]
Tomcat output when trying to start
Comment 3 jlaiho 2007-10-06 19:33:46 UTC
... and as a clarification, the problem went away when I removed the .netbeans directory from my non-root user, and
provided global read access to the files in the NetBeans-installed apache-tomcat-6.0.13/conf directory. After
that, when running a web application project, the personal tomcat directory was created just fine with all the
configuration files in place.

I assume just removing and recreating the server would have been sufficient, but in this case I didn't have anything
valuable in the .netbeans directory, so I decided to do it this way.
Comment 4 Petr Hejl 2007-10-09 10:08:38 UTC

*** This issue has been marked as a duplicate of 115367 ***