50 J2EE JSP-00002 to J2EE JSP-00302

J2EE JSP-00002: an internal JSP error occurred. Additional information follows: {0}.

Cause: JSP encountered an unexpected situation. This may be a bug in the JSP servlet.

Action: Contact Oracle Support Services. Oracle Support Services may recommend increasing the log level to FINER to help understand the situation.

Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00003: unable to fully process the TLD cache for the following reason: {0}.

Cause: An error occured while the Tag Library Descriptor cache was created or accessed.

Action: Check the TLD for validity and fix the TLD, or remove it if it is not used in the application. If the logging level is set to FINER more information should be available in the exception contained in the error message.

Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00005: unable to send the following error in the response. Response code: {0} Error message: {1}.

Cause: An exception occurred that prevented the error status from being sent in the response.

Action: See the exception cited in the error message. It may be necessary to increase the logging level to FINER to see the exception.

Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00006: unable to prepare or access an auxiliary object: {0} {1}.

Cause: The auxiliary object required for tracking JSP page dependencies was not read in or created.

Action: Recompile the page after checking factors that impact file reading such as disk corruption, permissions, and file handles.

Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00007: cannot find the message resource file, {0}, in the server to report error messages.

Cause: Due to a missing error message resource bundle, the underlying error message was not presented.

Action: Contact Oracle Support Services.

Level: 1

Type: NOTIFICATION

Impact: Installation

J2EE JSP-00008: unable to dispatch JSP page: {0}.

Cause: An error prevented the dispatching of the JSP page.

Action: Correct the error described in this logged message.

Level: 1

Type: NOTIFICATION

Impact: Requests/Responses

J2EE JSP-00009: unable to return the following error in the response: {0}.

Cause: An input-output error occurred while trying to write an error message to the servlet response stream.

Action: The logged message contains the error message that could not be returned in the response, and the associated exception. It may be necessary to increase the logging level to FINER to see the exception. Scan the log files for additional error messages that may reveal the root cause of this problem.

Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00010: building the cache named {0}.

Cause: Started building the Tag Library Descriptor persistent cache.

Action: none

Level: 1

Type: NOTIFICATION

Impact: Deployment

J2EE JSP-00011: Invalid JSP tag library location. {0} does not exist or is not a directory.

Cause: An invalid or nonexistent directory name was supplied as a tag library location.

Action: Correct the directory name and insure that it is available.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00012: obtaining application resources.

Cause: Finished obtaining current Tag Library Descriptors for this application.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00013: the initialization of TLD cache is complete.

Cause: Initialization of the Tag Library Descriptor persistent cache is completed.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00014: the number of listeners in TLDs visible to this application is {0}

Cause: The number of listener elements found in the Tag Library Descriptors visible to the applications was reported.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00015: starting to read the persistent TLD cache named {0}.

Cause: The Tag Library Descriptor persistent cache was read.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00016: completing cache update

Cause: Updating the Tag Library Descriptor persistent cache was completed.

Action: See error message.

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00017: inserting TLD at: {0}

Cause: The TLD at the given URL was inserted into the TLD persistent cache.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00018: applying update to TLD at: {0}

Cause: The TLD at the given URL was updated in the TLD persistent cache.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00019: completing processing of TLD persistent cache

Cause: The processing of this TLD persistent cache is finished.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00020: writing TLD persistent cache to file system

Cause: Finished writing out the Tag Library Descriptor Persistent Cache.

Action: See error message.

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00021: URL for entry is {0}.

Cause: Processed a TLD at the following given URL.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00022: loading external TLD with uri element, {0}, from JAR {1}.

Cause: Loaded TLD from the location external to the application given in the message text.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00023: loading application TLD with uri element, {0}, from location {1}.

Cause: Loaded TLD from the application location given in the message text.

Action: See error message.

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00024: loading TLD accessible via the name, {0}, from {1}

Cause: Loaded tag library descriptor at the following location for access via file or jar name.

Action: See error message.

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00025: finding listener, {0}, in TLD

Cause: The name of a listener element found in a Tag Library Descriptor visible to the application is supplied.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00026: missing required uri element in external TLD: {0}

Cause: Encountered a Tag Library Descriptor with an invalid or missing uri-element where one is required. For example, global tag libraries and those extrenal to the application must have URI elements.

Action: Supply the URI element in the TLD file or move the tag library to the application level.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00027: unable to parse TLD file: {0}

Cause: The TLD at the given location could not be parsed.

Action: Check for invalid XML syntax, especially unbalanced angle brackets or start and end tags.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00028: duplicate URI element, {0}, in TLD, {1}, and TLD, {2}

Cause: More than one tag library descriptor encountered using the same URI element. URI elements visible to the application must be unique.

Action: Change one of the uri element values or exclude one of the tag libraries from the this application.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00029: unable to obtain cache key: {0}

Cause: A corrupted cache key was encountered in the TLD cache.

Action: Stop the server, delete the TLD cache files from the application's persistence directory and from the global directory, tldcache and restart the application server. Contact Oracle Support Services if this problem persists.

Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00030: unable to obtain the JSP parameters

Cause: A unknown problem was encountered when attempting to initialize JSP configuration parameters.

Action: Verify the XML syntax in orion-web.xml, especially in the attributes of ojsp-init element if used. Verify the syntax of any init-parameters supplied to the JspServlet in web.xml or global-web-applications.xml. Then redeploy the application. If that fails, or if errors were found in the global-web-applciation.xml, restart the server. If the problem persists contact Oracle Support Services

Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00031: refreshing the cache named {0}.

Cause: Started refreshing the Tag Library Descriptor cache.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00032: looking for global resource at {0}.

Cause: The global Tag Library Descriptors were sought in the location or locations cited in the error message.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00033: unable to process an invalid or unsupported TLD version: {0}

Cause: An invalid or unsupported value of the taglib element's attribute, version, element was supplied.

Action: The taglib element is the root element for all TLD's. The element's attribute, version, must be either 2.0 or 2.1.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00034: loading cachedConfigTable from persistent cache

Cause: The internal configuration data structure was loaded from the persistent Tag Libary Descriptor cache.

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00035: unable to load changeAwareClassLoader class. Shared libraries from web-app and enclosing app will not be scanned for TLDs

Cause: Loading of ChangeAwareClassLoader failed

Action: none

Level: 1

Type: TRACE

Impact: Deployment

J2EE JSP-00036: unbable to obtain Tag Library listeners: {0}

Cause: An error was encountered while obtaining Tag Library listeners during the parsing of Tag Library Descriptors.

Action: Verify that classes given in the listener-classes element are available in the application's class path. Check for general XML syntax (i.e., unmatched quotes or start/end tags) in the application's TLD's.

Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00037: cannot load tag library {0} specified in web.xml

Cause: A tag library defined in the application's web.xml file was not loaded.

Action: Verify that the taglib-uri and taglib-location are correctly formatted and point to valid values, and that the tag library implementations classes are available to the application.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00038: error preparing dependency file for tag file:

Cause: An error was encountered while writing or preparing the dependency file for a tag file.

Action: Recompile the page that accesses the tag file after checking factors that impact file writing such as disk space, permissions, and file handles.

Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00039: invalid tag file: {0}. File must end with .tag or .tagx and start with /WEB-INF/tags or /META-INF/tags.

Cause: Encountered a tag file path that is an invalid or non-existent location.

Action: Correct the tagfile-path element value by ensuring that it ends with either .tag or .tagx, and starts with either /WEB-INF/tags or /META-INF/tags.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00040: duplicate tag name : {0}. TLD is invalid

Cause: A tag name that was used in more than one Tag Library Descriptor was visible to the application and caused an error.

Action: Tag names must be unique. Change the duplicate name in that tag or tag file element.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00041: The value {0} is invalid for main mode.

Cause: An invalid value for the main mode was detected.

Action: Valid values for the main mode are recompile, reload and justrun.

Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00042: The value {0} is invalid for debug.

Cause: An invalid JSR45 debug parameter was specified.

Action: Valid values for debug are none, file and class.

Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00043: The value {0} is invalid for tags reuse.

Cause: An invalid tags reuse parameter was specified.

Action: Valid values for tag resuse are compiletime, compiletime-with-release and none.

Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00044: error invoking the following JSP tag life-cycle method: {0}

Cause: An internal error occured. The JSP runtime failed to execute a method provided by the Oracle JSF Injection Provider. The JSP page in which the error occured will not be serviced.

Action: Contact Oracle Support Services.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00045: unable to scan annotation for tag {0}: {1}

Cause: The tag implementation class given in the error text could not be scanned for annotations.

Action: See the error cited in the error message to determine what action is required.

Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00046: Unable to load class {0} while scanning for annotated JSP tags.

Cause: The tag class for annotations cited in the error message was not scanned. The class appeared to be missing, or was unloadable.

Action: Make sure that the missing class is available in the application class path. Verify that the class file was generated with a jdk version that supports annotations.

Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00047: unable to scan annotation {0}. It is not a JSP tag.

Cause: The class to be scanned does not implement the JspTag interface or cannot be loaded.

Action: Make sure the class is available in the application classpath and that it implements the javax.servlet.jsp.tagext.JspTag interface.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00048: annotation scanning is incomplete: {0}

Cause: Scanning for annotations in the Tag Library Descriptors, visible to the application, was not completed.

Action: Verify that the class is availble in the applications classpath. If so, check application server log files for problems such as out of memory, file permissions, network access.

Level: 1

Type: WARNING

Impact: Files

J2EE JSP-00050: Parameter {0} is no longer supported as of Oracle Containers for J2EE 11g. The parameter is ignored.

Cause: An application attempted to use the parameter cited in the error message that was desupported as of release 11G.

Action: You can avoid this message by removing the given parameter.

Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00051: unable to write an auxiliary object during the page compilation: {0} {1}.

Cause: The auxiliary object required for tracking the JSP page dependencies could not be written to a file.

Action: Recompile the page after investigating the factors that impact file writing such as disk space, permissions, and file handles.

Level: 1

Type: NOTIFICATION

Impact: Files

J2EE JSP-00052: Using the ProviderURI {0} that is returned from custom provider for processing requests.

Cause: An application-specific provider was registered and used.

Action: none

Level: 1

Type: TRACE

Impact: Configuration

J2EE JSP-00053: The value {0} is an invalid value for generic servlet mode.

Cause: An invalid parameter for the generic servlet mode was specified.

Action: Use a valid parameter value. They include shared, single, none, and single_and_persist.

Level: 1

Type: WARNING

Impact: Configuration

J2EE JSP-00054: Unable to retrieve HttpApp object through ThreadState.

Cause: An application that did not use the default OC4J HttpApplication object failed to supply its own application context object.

Action: Supply the application context or allow the use of the default one.

Level: 1

Type: WARNING

Impact: Programmatic

J2EE JSP-00055: Setting JSP:Config parameter {0} = {1}

Cause: The JSP:Config parameter cited in the message was set.

Action: none

Level: 32

Type: TRACE

Impact: Configuration

J2EE JSP-00056: The web.xml at {0} is version 2.3 but has a <jsp-config> element. Ignoring <jsp-config> element.

Cause: Web.xml version 2.3 does not include support for <jsp-config>

Action: Either remove the <jsp-config> element or upgrade the web.xml to version 2.4 or higher

Level: 1

Type: WARNING

Impact: Other

J2EE JSP-00057: unable to determined the last-modified date of the file at path, {0}.

Cause: This is usually caused by an IO error. However this error may related to something that happened before this instanceof OC4J started. This has been known to happen if at some point two processes attempted to write to the same file at the same time. This error can also occur if the file was last modified within one second of EPOCH (at 0 hour on January 1, 1970), in this case it should be ignored.

Action: Verify that the file is not corrupted. If it is not, this error can be ignored. You may use the touch command, in unix, to update the last modified date of the file to prevent subsequent logging of this error. If the file is corrupted attempt to determine the cause of the corruption and fix it, or Contact Oracle Support Services.

Level: 1

Type: ERROR

Impact: Other

J2EE JSP-00058: error attemping to parse web.xml at {0}.

Cause: Error parsing the web.xml file located at the path location listed in the log message.

Action: Attempt to fix the error in the web.xml file base on the information contained in the log message.

Level: 1

Type: WARNING

Impact: Deployment

J2EE JSP-00059: unable to inject a resource.

Cause: The exception cited in the error message occurred when the JSP page was processed.

Action: Read the exception cited in the error message to understand the cause. If no exception is shown, increase the log level to FINER.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00060: unable to parse the tld with the following url: {0}. Error details follow: {1}.

Cause: Failed to parse the tag specified in the error message.

Action: Read the error details cited in the error message and attempt to fix the offending tag, or remove it is it is not needed.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00061: there is a JSP error in file {0} at line {1}. The error is: {2}, in {3}.

Cause: A JspParse Exception was encountered.

Action: Examine the content of the error message which indicates the nature and location of the error. Then fix the error.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00062: unable to get the TLD document associated to file {0} at line {1}. The error is: {3}.

Cause: Internal error. Inconsistent gathering of performance statistics

Action: Examine the content of the error message which indicates the nature and location of the error. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00063: unable to read the jar file named {0}.

Cause: An input-ouput exception occured while attempting to read the jar file specified in the message.

Action: Examine the content of the error message which indicates the nature and location of the error. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00064: unable to obtain URI because of an XML parsing exception in file, {0} at element, {1}.

Cause: An exception occured in the XML parser while parsing for a URI.

Action: Examine the content of the error message which contains at least the name of the relevant file and most likely the name of the relevant XML element. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00065: unable to process the file at {0} due to an input-ouput exception.

Cause: An input-output exception prevented the processing of the file named in the log message.

Action: Examine the content of the error message which indicates the nature of the error as well as the location of the file involved. Attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00066: unable to find class named {0} in resource {1}.

Cause: The JSP runtime could not find the class specified in the message in the resource also specified in the message.

Action: Verify the resource in question and attempt to fix the error. If that does not work, contact Oracle Support Services and give them the full error message.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00067: unable to read optional data.

Cause: The JSP runtime encountered a java.io.OptionalDataException.

Action: Read the full error message and consult the Javadoc on OptionalDataException to understand the problem and attempt to fix it. If that does not work, contact Oracle Support Services and give them the full error message.

Level: 16

Type: TRACE

Impact: Requests/Responses

J2EE JSP-00068: invalid taglib uri: {0}, unless non taglib namespace was intended in a JSP document.

Cause: An invalid taglib uri was specified.

Action: Fix the taglib attributes in your jsp.

Level: 1

Type: NOTIFICATION

Impact: Configuration

J2EE JSP-00069: Name space, {0}, also known as {1} will override name space {2}

Cause: The namespace definition in the last tld defining the namespace overrided any previous definition of that namespace.

Action: See error message.

Level: 1

Type: WARNING

Impact: Other

J2EE JSP-00070: an unlikely, but generally harmless, situation has been detected. Additional information follows: {0}.

Cause: JSP encountered an rare situation. This should not cause any adverse effect on yor application.

Action: If this occurs in the absence of other errors, this is most likely a benign situation, if accompanied by other error messages, this may held diagnose the root cause of the problem reported by the other error messages. You may Contact Oracle Support Services to help us improve the product in future releases. Oracle Support Services may recommend increasing the log level to FINER to help understand the situation.

Level: 1

Type: WARNING

Impact: Requests/Responses

J2EE JSP-00101: Inconsistent use of the DMS (statistics aggregation) framework. The problem occured in application, {0}, for this uri: {1}. {2}

Cause: Internal error. Inconsistent gathering of performance statistics

Action: Examine the error message to determine which statistics are inconsistent; those statistics should not be trusted. Contact Oracle Support Services and give them the full error message.

Level: 1

Type: ERROR

Impact: Performance

J2EE JSP-00111: the Oracle DMS framework is unavailable.

Cause: The JSP servlet could not find the Oracle DMS classes.

Action: If using a third-party application server, the DMS functionality will simply not be available. If using an Oracle Application Server, this message indicates that there is something wrong with the installation. In that case, contact Oracle Support Services and give them the full error message.

Level: 1

Type: WARNING

Impact: Installation

J2EE JSP-00300: unable to access osgi.syspath, {0}, even though it exists.

Cause: There is a problem with the path corresponding to System property osgi.sypath.

Action: Check that the path is valid, unlocked, and that WebSphere has read/write permissions for it.

Level: 1

Type: ERROR

Impact: Files

J2EE JSP-00301: unable to extract the local classpath field.

Cause: There is a problem extracting the local class path from the WebSphere class loader.

Action: Contact Oracle Support Services and ask for a patch if this prevents ojsp.next from functioning normally.

Level: 1

Type: ERROR

Impact: Programmatic

J2EE JSP-00302: unable to determine the osgi pluggin classpath.

Cause: There is a problem assembling the osgi plugin class path.

Action: Contact Oracle Support Services and ask for a patch if this prevents ojsp.next from functioning normally.

Level: 1

Type: ERROR

Impact: Programmatic