Oracle GlassFish Server 3.0.1 Error Message Reference

WEB


WEB0121 Enabled session ID reuse for web module [{0}] deployed on virtual server [{1}]

Cause:

Use caution before enabling this feature, because it puts the burden of creating unpredictable session ids on the client, which may not be trusted

Solution:

Check your sun-web.xml for a property with name reuseSessionID, and set it to false if you do not want to enable this feature


WEB0126 Failed to parse sun-web.xml singleThreadedServletPoolSize property value ({0}) of web module deployed at {1}, using default ({2})

Cause:

The value of the singleThreadedServletPoolSize property in the sun-web.xml deployment descriptor cannot be parsed as an Integer

Solution:

Make sure to specify an Integer as the value of the singleThreadedServletPoolSize property


WEB0137 Invalid redirect property value [{0}] for virtual server [{1}]: More than one [{2}] component

Cause:

The value of the redirect property of the virtual server specifies more than one component of the same name

Solution:

Check the redirect property of the virtual server and make sure it does not specify more than one component of the same name


WEB0138 Invalid redirect property value [{0}] for virtual server [{1}]: Missing from component

Cause:

The redirect property value of the virtual server is missing a from component

Solution:

Make sure to specify a from component for the redirect property of the virtual server


WEB0139 Invalid redirect property value [{0}] for virtual server [{1}]: Missing url or url-prefix component

Cause:

The redirect property value of the virtual server is missing an url or url-prefix component

Solution:

Make sure that the value of the redirect property of the virtual server specifies an url or url-prefix component, but not both


WEB0140 Invalid redirect property value [{0}] for virtual server [{1}]: Both url and url-prefix specified

Cause:

The value of the redirect property of the virtual server specifies both an url and an url-prefix component

Solution:

Make sure that the value of the redirect property of the virtual server specifies an url or url-prefix component, but not both


WEB0141 Invalid redirect property value [{0}] for virtual server [{1}]: escape must be equal to yes or no

Cause:

The value of the escape component is invalid

Solution:

Make sure to specify either yes or no (case-insensitive) as the value of the escape component for the redirect property of the virtual server


WEB0142 Invalid send-error property value [{0}] for virtual server [{1}]: More than one [{2}] component

Cause:

The value of the send-error property of the virtual server specifies more than component of the same name

Solution:

Check the send-error property of the virtual server and make sure it does not specify more than one component of the same name


WEB0143 Invalid send-error property value [{0}] for virtual server [{1}]: Missing path component

Cause:

The value of the send-error property of the virtual server is missing a path component

Solution:

Make sure to specify a path component for the send-error property of the virtual server


WEB0145 Unable to deploy web module [{0}] at root context of virtual server [{1}], because this virtual server declares a default-web-module

Cause:

There can be at most one web module occupying a virtual server's root context at any time

Solution:

You must first undeclare a virtual server's default-web-module in order to be able to deploy to the virtual server's root context


WEB0147 Unable to add listener of type [{0}] to virtual server [{1}]

Cause:

Declared listener is neither of type org.apache.catalina.ContainerListener nor org.apache.catalina.LifecycleListener

Solution:

Make sure the declared listener implements org.apache.catalina.ContainerListener or org.apache.catalina.LifecycleListener


WEB0152 Unable to load web module [{0}] at context root [{1}], because it is not correctly encoded

Cause:

The specified context root contains one or more '%' characters and therefore is assumed to have been encoded using some multibyte encoding scheme, but it fails to be decoded using UTF-8 which is assumed as the default multibyte encoding

Solution:

When deploying to a multibyte context root, make sure it is encoded according to UTF-8


WEB0203 Error looking up the configuration information of the default-web-module [{0}] for virtual server [{1}]

Cause:

The web module that has been designated as the default-web-module may not exist

Solution:

Make sure that the web module that has been designated as the default-web-module for the virtual server has been deployed


WEB0207 Invalid sso-cookie-secure configuration [{0}] for virtual server [{1}]

Cause:

The sso-cookie-secure attribute of the virtual server has an unsupported value

Solution:

Make sure the value of the sso-cookie-secure attribute of the virtual server is set to 'true', 'false', or 'dynamic'


WEB0305 Unable to parse proxy port component ({0}) of server-name attribute of network-listener {1}

Cause:

HTTP listener's proxy port is not a numeric string

Solution:

Check to see if the value of the HTTP listener's server-name attribute contains a colon, and if so, make sure the name component following the colon is a numeric string


WEB0315 The host name {0} is shared by virtual servers {1} and {2}, which are both associated with the same HTTP listener ({3})

Cause:

Two or more virtual servers associated with the same HTTP listener share the same host name

Solution:

Make sure that the sets of host names of all virtual servers associated with the same HTTP listener are disjunct


WEB0324 Missing end delimiter in access log pattern: {0}

Cause:

The given access log pattern is missing a trailing '%'

Solution:

Make sure that any access log pattern element is bounded by a leading and trailing '%'


WEB0354 Unable to parse max-history-files access log configuration [{0}]

Cause:

max-history-files not specified as an integer

Solution:

Make sure the value of the com.sun.enterprise.server.logging.max_history_files system property or max-history-files attribute of access-log is given as an integer


WEB0356 Web module [{0}] not loaded to any virtual servers

Cause:

No virtual servers specified on which to load the web module


WEB0358 Invalid attribute [{0}] in thread-pool configuration

Cause:

The specified attribute value cannot be parsed as an Integer

Solution:

Make sure to specify an Integer as the attribute value


WEB0400 Unable to set request encoding [{0}] determined from sun-web.xml deployment descriptor of web application [{1}]

Cause:

The sun-web.xml deployment descriptor specifies an invalid request encoding

Solution:

Check the form-hint-field, default-charset, and locale-charset-map configuration in the sun-web.xml deployment descriptor and make sure it specifies a valid request encoding


WEB0500 default-locale attribute of locale-charset-info element is being ignored

Cause:

This attribute has been deprecated

Solution:

Use default-charset attribute of parameter-encoding element instead


WEB0509 Unable to add valve to web module [{0}]

Cause:

Valve declaration is missing a name attribute

Solution:

You must specify a name attribute with your valve declaration


WEB0510 Unable to add valve with name [{0}] to web module [{1}]

Cause:

Valve declaration is missing a class-name attribute

Solution:

You must specify a class-name attribute with your valve declaration


WEB0512 Object of type {0} is not a valve

Cause:

Declared custom valve does not implement any of the required valve interfaces

Solution:

Make sure the declared custom valve implements org.apache.catalina.Valve or org.glassfish.web.valve.GlassFishValve


WEB0513 Unable to add listener of type [{0}] to web module [{1}]

Cause:

Declared listener does not implement any of the required interfaces

Solution:

Make sure the declared listener implements org.apache.catalina.ContainerListener, org.apache.catalina.LifecycleListener, or org.apache.catalina.InstanceListener


WEB0516 Unable to save sessions for web module [{0}] during redeployment

Cause:

An HTTP session that was supposed to survive the redeployment of the web module failed to be serialized. This kind of error can occur only if the keepSessions property of the redeploy command has been set to true

Solution:

Make sure that all HTTP sessions of the web module are serializable, or disable the feature that preserves HTTP sessions across redeployments


WEB0517 Unable to restore sessions for web module [{0}] from previous deployment

Cause:

An HTTP session that was supposed to survive the redeployment of the web module failed to be restored (deserialized). This can happen if an application class that was used as a session attribute has changed incompatibly

Solution:

Make sure that any application classes that are being used as session attributes change only in a compatible way during redeployments


WEB9002 Illegal value ([{0}]) for scope attribute of cache tag

Cause:

Only 'request', 'session', and 'application' scopes are supported for caching purposes

Solution:

If the scope attribute of the cache tag is specified, make sure its value is set to 'request', 'session', or 'application'


WEB9031 WebappClassLoader unable to load resource [{0}], because it has not yet been started, or was already stopped

Cause:

This problem usually indicates that the classloader of a web application was cached, and an attempt is being made to have it load resources even though the web application with which the classloader used to be associated has already been undeployed

Solution:

Make sure that the classloader associated with your web application is not cached and used beyond the lifetime of your web application


WEB9032 Class {0} has unsupported major or minor version numbers, which are greater than those found in the Java Runtime Environment version {1}

Cause:

This error indicates that a web application contains class files that were compiled with a version of the Java programming language compiler that is greater than the version of the Java Runtime Environment with which the GlassFish application server process was launched

Solution:

Make sure that the classes of your web application have been compiled with a version of the Java programming language compiler that is less than or equal to the version of the Java Runtime Environment with which the GlassFish application server process was launched