• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 752
  • Last Modified:

Error: 404 SC_NOT_FOUND

Hi All,
> We have recently upgraded our IPlanet Application Server 6.0 from SP2 to SP3 and
> having problem when we tried to run the JSPs. It was working fine with IAS
> 6.0 SP2 and getting errors with SP3. Has anyone see these errors before ? Any help on this
> would be greatly appreciated!

> -- error starts here
> Error: 404 SC_NOT_FOUND
> Extension of file not found, while displaying static content
> -- error ends---

> Here is the kjs log information

> Extension of file not found, while displaying static content

> 14/Sep/2001 20:05:17:7] info: --------------------------------------
> [14/Sep/2001 20:05:17:7] info: jsp.APPS.useme.viewTaxonomy: init
> [14/Sep/2001 20:05:17:7] info: --------------------------------------
> [14/Sep/2001 20:05:17:7] info: --------------------------------------
> [14/Sep/2001 20:05:17:7] info: StaticServlet: init
> [14/Sep/2001 20:05:17:7] info: --------------------------------------
> [14/Sep/2001 20:05:17:7] error: SERVLET-fileext_not_set: Extension of file
> not found, while displaying static content

Please Help out of this problem as soon as possible.

Thanks
Anil
0
anilkumar246
Asked:
anilkumar246
  • 2
1 Solution
 
gongjunCommented:
There is no support in the plugin /servlet engine for serving static pages from the web server's doc root, if the request includes the prefix NASApp. The plugin forwards all such requests to the StaticServlet on the application server. If the access is for /NASApp/Foo/Bar.html, and bar.html has a relative link to Boo.js, then both Bar.html and Boo.js need to be on the application server's doc root. Static content can only be served off the web server's doc root, is if the URL does not include /NASApp. Docs on the web server's doc root, can only be supported by changing all relative links to absolute links without NASApp. Users are encouraged to use WebServer doc root for static serving, and to code the JSPs accordingly. Currently,the iPlanet Application Server deployment tool only deploys the application on the Application server. To have static content served by the Web server, the static file must be manually moved to the web server doc root, and the links replaced so that the don't have the prefix NASApp. On a UNIX system, write access is required to both the ias/registry/reg.dat file and the ias/APPS directory to run iPlanet Application Server deployment tool. Arrange this by always running the deployment tool as a user having privileges equal to the user who installed iPlanet Application Server, or by changing the protections after installation.

0
 
gongjunCommented:
Install a separate iPlanet Application Server with a single kjs process to run Catalog Manager. This iAS installation can be used exclusively for Catalog Manager.

Or

Configure the iAS that will run with multiple kjs processes:
1. Run the iAS administrative utility (ksvradmin or startconsole).
2. Select the application menu option.
3. In the left (navigation) frame, click ias/Default/System.
4. In the right frame, check the Sticky option for StaticServlet and JSPRunner.
5. To commit your settings, click Apply Changes.
0
 
VenabiliCommented:
No comment has been added lately, so it's time to clean up this TA.
I will leave a recommendation in the Cleanup topic area that this question is:

- Points for gongjun

Please leave any comments here within the next seven days.
 
PLEASE DO NOT ACCEPT THIS COMMENT AS AN ANSWER!
 
Venabili
EE Cleanup Volunteer
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now