My Oracle Support Banner

Web Server 6.1 Startup Exception Failure ContextConfig /web-app-uri WEB3524 Parse Error in Application web.xml, org.xml.sax.SAXParseException The Content of Element Type "web-app" Must Match (Doc ID 1287686.1)

Last updated on JANUARY 31, 2022

Applies to:

Oracle iPlanet Web Server - Version 6.1 to 7.0 [Release 6.1 to 7.0]
Information in this document applies to any platform.


After adding a <listener> element to amserver web application. Web server reports the following exceptions in the errors log on startup.

info ((PID)): CORE3282: stdout: org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".

 failure ((PID)): ContextConfig[/amserver] WEB3524: Parse error in application web.xml
org.xml.sax.SAXParseException: The content of element type "web-app" must match "(icon?,display-name?,description?,distributable?,context-param*,filter*,filter-mapping*,listener*,servlet*,servlet-mapping*,session-config?,mime-mapping*,welcome-file-list?,error-page*,taglib*,resource-env-ref*,resource-ref*,security-constraint*,login-config?,security-role*,env-entry*,ejb-ref*,ejb-local-ref*)".

failure ((PID)): ContextConfig[/amserver]: WEB3525: Occurred at line 753 column 11

failure ((PID)): ContextConfig[/amserver]: WEB3541: Marking this application unavailable due to previous error(s)

failure ((PID)): WebModule[/amserver]: WEB2705: Context startup failed due to previous errors

failure ((PID)): WebModule[/amserver]: WEB2720: Error initializing naming context for context /amserver
javax.naming.NamingException: WEB3880: Unknown context name : StandardEngine[null].StandardHost[].StandardContext[/amserver]


This error is caused because the web.xml deployment descriptor file elements are out of order with the 2.3 servlet specification.

The <listener> element was placed in the applications web.xml file before "display-name, description, distributable,context-param*, filter*, filter-mapping*" elements.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.