|
BEA-101000(retired)
|
Info: [context] Using classpath: classpath
|
Description
| The Web application servlet context with context path context was initialized by using classpath classpath.
|
|
Cause
| Web application was initialized.
|
|
Action
| This message is for debugging purpose only. Make sure the classpath is correct.
|
|
|
BEA-101001(retired)
|
Info: [context] ServletServlet: Registering: classname as: name
|
Description
| weblogic.servlet.ServletServlet registered Servlet: classname with a servlet stub name in the Web application: context.
|
|
Cause
| ServletServlet registered the servlet class and created a servlet stub for it.
|
|
Action
| Debug message only.
|
|
|
BEA-101002
|
Error: [context] Could not deserialize the context attribute.
|
Description
| The classloader changed for the Web application but failed to deserialized the attributes using the new classloader.
|
|
Cause
| The classloader changed. When this happens, the old attributes will be deserialized using the new classloader.
|
|
Action
| Make sure the attribute class is available to the Web application scope and is serializable.
|
|
|
BEA-101003
|
Alert: [context] method called with a null doc root.
|
Description
| Fatal error: the doc root was not set for Web application: context.
|
|
Cause
| The Web application was not initialized correctly.
|
|
Action
| Check the log file for error messages for this Web application.
|
|
|
BEA-101004(retired)
|
Error: [context] method called with null path.
|
Description
| The VirtualPath passed to the getRealPath was null.
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101005
|
Error: [context] method called with unsafe path: "path".
|
Description
| The method method was called with an unsafe path, which points to a resource outside the Web application scope for context: context.
|
|
Cause
| The virtual path that was passed in points to a resource outside the Web application scope.
|
|
Action
| Check the virtual path being passed to the method and rectify the problem accordingly.
|
|
|
BEA-101006(retired)
|
Info: [context] name looking for resource s.
|
Description
| getResource() method for the Web application: context was invoked for the resource: s.
|
|
Cause
| This is a debug message indicating that getResource is being invoked.
|
|
Action
| Make sure the resource name is correct.
|
|
|
BEA-101007(retired)
|
Info: [context] name looking for stream s.
|
Description
| getResourceAsStream() method for the Web app: context was invoked for the resource: s.
|
|
Cause
| This is a debug message indicating that getResourceAsStream is being invoked.
|
|
Action
| Make sure the resource name is correct.
|
|
|
BEA-101008
|
Error: [context] Cannot get InputStream of resource "s".
|
Description
| getResourceAsStream() method failed to get an InputSteam for the resource: s.
|
|
Cause
| getResourceAsStream() method failed to get an InputSteam for the resource.
|
|
Action
| Make sure the resource exists.
|
|
|
BEA-101009(retired)
|
Debug: [context] Initialized context: "name" with verbose "verbose", reloadCheckSecs: "secs", and CLASSPATH: "classpath"
|
Description
| The Web app with contextPath: context was just initialized.
|
|
Cause
| This is an init debug message for the Web application.
|
|
Action
| This is a debug message only.
|
|
|
BEA-101010(retired)
|
Debug: [context] Registering: "classname" as: "name", with args: "args"
|
Description
| [context] Registering: "classname" as: "name", with args: "args"
|
|
Cause
| Debug message
|
|
Action
| Debug message
|
|
|
BEA-101011(retired)
|
Debug: [context] Registering: "classname" as: "name", with initString: "args"
|
Description
| [context] Registering: "classname" as: "name", with initString: "args"
|
|
Cause
| Debug message
|
|
Action
| Debug message
|
|
|
BEA-101012(retired)
|
Debug: [context] Could not find servlet for path: "url".
|
Description
| The webapp: context did not find the servlet registered with the path: url.
|
|
Cause
| Servlet was not registered.
|
|
Action
| Please register the missing servlet.
|
|
|
BEA-101013(retired)
|
Debug: [context] Found servlet for path: "url"
|
Description
| [context] Found servlet for path: "url"
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101014(retired)
|
Debug: [context] Removing ServletStub: "name"
|
Description
| [context] Unregistering ServletStub: "name"
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101015(retired)
|
Debug: [context] Invoking servlet
|
Description
| [context] Invoking servlet
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101016(retired)
|
Error: [context] MAX post size size exceeded.
|
Description
| The Content-Length for the incoming POST exceeded the configured MaxPostSize for the Web server: size.
|
|
Cause
| This parameter is used to prevent Denial of Service attacks.
|
|
Action
| Please re-adjust the MaxPostSize parameter, if the incoming post request needs to be served.
|
|
|
BEA-101017
|
Error: [context] Root cause of ServletException.
|
Description
| [context] Root cause of ServletException, which the Web application container caught while servicing the request.
|
|
Cause
| The Web application container caught an unexpected exception.
|
|
Action
| Check the exception for the exact error message.
|
|
|
BEA-101018(retired)
|
Error: [context] Servlet failed with ServletException
|
Description
| [context] Servlet failed with ServletException
|
|
Cause
| An unexpected error occurred.
|
|
Action
| Check the exception for exact error message.
|
|
|
BEA-101019
|
Error: [context] Servlet failed with IOException
|
Description
| [context] Servlet failed with IOException
|
|
Cause
| An unexpected IOException was caught while processing request.
|
|
Action
| Check the exception for exact error message.
|
|
|
BEA-101020
|
Error: [context] Servlet failed with Exception
|
Description
| [context] Servlet failed with Exception
|
|
Cause
| An unexpected error occurred.
|
|
Action
| Check the exception for exact error message.
|
|
|
BEA-101021(retired)
|
Alert: Request URI for "context0" context did not start with context path "path1".
|
Description
| Request URI for "context0" context did not start with context path "path1".
|
|
Cause
| Since the webapp context received the request, the URI was expected to start with the context path. However, that is not the case.
|
|
Action
| This should never happen. Check the log file for more error messages.
|
|
|
BEA-101022(retired)
|
Debug: [context] Treating servlet mappings of extensions as lower case
|
Description
| [context] Treating servlet mappings of extensions as lower case
|
|
Cause
| Message not in use
|
|
Action
| Message not in use
|
|
|
BEA-101023(retired)
|
Debug: [context] Lowering extension "ext"
|
Description
| [context] Lowering extension "ext"
|
|
Cause
| Message not in use
|
|
Action
| Message not in use
|
|
|
BEA-101024
|
Critical: [context] Unsupported error status code for error-page in web.xml.
|
Description
| [context] Unsupported error-code for error-page in web.xml.
|
|
Cause
| The format was invalid.
|
|
Action
| Check the web.xml and fix the error-page error-code.
|
|
|
BEA-101025
|
Alert: [context] Document root is null.
|
Description
| Doc root not set for the Web application : context.
|
|
Cause
| This should never happen. The initialization failed.
|
|
Action
| Check the log file for error messages during the Web app initialization phase.
|
|
|
BEA-101026(retired)
|
Debug: [context] Document root: "path" does not exist as an absolute path. Trying it as a path relative to the per-server directory.
|
Description
| [context] Document root: "path" does not exist as an absolute path,. Tying it as a path relative to the per-server directory.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101027
|
Alert: [context] Document root: "path" does not exist.
|
Description
| [context] Document root: "path" does not exist.
|
|
Cause
| Unexpected error message
|
|
Action
| Check if the directory exists.
|
|
|
BEA-101028(retired)
|
Alert: [context] Document root: "path" is not a directory.
|
Description
| [context] Document root: "path" is not a directory.
|
|
Cause
| Message not in use
|
|
Action
| Message not in use
|
|
|
BEA-101029
|
Error: [context] cannot make temp directory "path". Will not be able to compile JSPs.
|
Description
| Failed to create the temp directory with path: path for webapp: context.
|
|
Cause
| Temp directory creation failed.
|
|
Action
| Check the write permissions.
|
|
|
BEA-101030(retired)
|
Error: [context] Document root: "path" does not resolve to a canonical name.
|
Description
| [context] Document root: "path" does not resolve to a canonical name.
|
|
Cause
| Message not in use
|
|
Action
| Message not in use
|
|
|
BEA-101031(retired)
|
Debug: [context] extracting class files to: path.
|
Description
| [context] extracting class files to: path.
|
|
Cause
| Debug Message. The container extacts the class files from WEB-INF/classes in a separate JAR file when the Web application has been deployed as a WAR.
|
|
Action
| Debug Message
|
|
|
BEA-101032(retired)
|
Debug: [context] extracted class files successfully.
|
Description
| [context] extracted class files successfully.
|
|
Cause
| Debug Message.
|
|
Action
| Debug Message.
|
|
|
BEA-101033(retired)
|
Error: [context] failed to extract class files.
|
Description
| [context] failed to extract class files.
|
|
Cause
| The container extracts the class files from WEB-INF/classes into a separate JAR file when the Web application has been deployed as a WAR file.
|
|
Action
| Check the write permissions on disk and also check the exception for the exact error message.
|
|
|
BEA-101034(retired)
|
Error: [context] failure extracting WAR classes.
|
Description
| [context] Failed to extact the class files in a separate JAR for the WAR.
|
|
Cause
| The container extracts the class files from WEB-INF/classes in a separate JAR file when the Web application has been deployed as a WAR.
|
|
Action
| Check the write permissions on the disk. Also check the exception for the exact error message.
|
|
|
BEA-101035(retired)
|
Debug: [context] Check access passed for uri.
|
Description
| [context] Authorization check passed for uri.
|
|
Cause
| Debug message
|
|
Action
| Debug message
|
|
|
BEA-101036(retired)
|
Debug: [context] Received an authenticated user from session: user.
|
Description
| The http session contains the user: user for the Web application: context.
|
|
Cause
| Debug message
|
|
Action
| Debug message
|
|
|
BEA-101037(retired)
|
Debug: [context] No previous user object is found in session. New authentication of user.
|
Description
| [context] No previous user object is found in session. New authentication of user.
|
|
Cause
| It seems the user has not signed in yet or the previous session got invalidated.
|
|
Action
| Debug message
|
|
|
BEA-101038(retired)
|
Debug: [context] Authenticated new user: user
|
Description
| [context] Authenticated new user: user, who just logged on.
|
|
Cause
| A new user has signed on.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101039(retired)
|
Debug: [context] User: user has permission to execute acl.
|
Description
| [context] User: user has permission to execute acl.
|
|
Cause
| Logging debug information for the logged in user.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101040
|
Error: [context] Error occurred while trying to set "httpdreload".
|
Description
| [context] Error occurred while trying to set "httpdreload".
|
|
Cause
| NumberFormatException occurred while parsing the value assigned to the reloadCheckSecs parameter in web.xml.
|
|
Action
| Make sure you have typed in the value correctly.
|
|
|
BEA-101041
|
Debug: [context] Comparing BUILD_VERSION(s):\n JSP: jspVersion\n WLS: wlsVersion
|
Description
| [context] Comparing BUILD_VERSION(s):\n JSP: jspVersion\n WLS: wlsVersion
|
|
Cause
| This is a debug message to log the fact that JSP recompilation is forced after every release.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101042(retired)
|
Info: [context] class looking for source src
|
Description
| [context] class looking for source src
|
|
Cause
| logging getResourceAsSource() for debug purpose.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101043(retired)
|
Alert: [context] getResource is called when document root is not set.
|
Description
| [context] getResource is called when document root is not set.
|
|
Cause
| ResourceFinder was null
|
|
Action
| Contact WebLogic Server support if you are receiving this message. Please provide a copy of the webapp that caused the problem, and the necessary steps to reproduce the issue.
|
|
|
BEA-101044(retired)
|
Info: [context] Cannot find resource: "src" in document root: "root".
|
Description
| [context] Cannot find resource: "src" in document root: "root".
|
|
Cause
| The requested resource in getResourceAsSource() was not found.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101045
|
Error: [context] s
|
Description
| [context] s
|
|
Cause
| This is a general purpose error message.
|
|
Action
| Check the message for the exact cause and take proper action.
|
|
|
BEA-101046
|
Error: [context] s
|
Description
| [context] s
|
|
Cause
| This is a general purpose error message.
|
|
Action
| Check the exception for exact cause and take proper action.
|
|
|
BEA-101047
|
Info: [Context] s
|
Description
| [Context] s
|
|
Cause
| This is a general purpose info message for debug purpose only.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101048(retired)
|
Error: Specify a secure port in the properties. Using default ports 7001/7002.
|
Description
| Specify a secure port in the properties. Using ports 7001/7002. See release notes for more information.
|
|
Cause
| The secure port was not specified.
|
|
Action
| Check the docs on how to specify a secure port using the Admin Console.
|
|
|
BEA-101049(retired)
|
Error: Expected content length: len bytes, but received read bytes
|
Description
| Expected content length: len bytes but received read bytes
|
|
Cause
| Content length mismatch.
|
|
Action
| Make sure the application is setting the content length properly.
|
|
|
BEA-101050(retired)
|
Error: [context] Cannot register servlet name, because default servlet context is not defined.
|
Description
| [context] Cannot register servlet name, because default servlet context is not defined.
|
|
Cause
| There is no default Web application, so this servlet cannot be registered.
|
|
Action
| You can set a given webapp as a default webapp by setting the context-root="" in weblogic.xml or application.xml for an EAR.
|
|
|
BEA-101051
|
Info: [context] started
|
Description
| [context] started and is ready to receive http requests.
|
|
Cause
| This is an information message indicating that the Web server has been started.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101052
|
Info: [context] Initialized
|
Description
| [context] Initialized
|
|
Cause
| This is an information message indicating that the Web server has been initialized.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101053
|
Info: [logContext] Loading web app: name
|
Description
| [logContext] Loading web app: name
|
|
Cause
| The Web application is being deployed.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101054
|
Info: [context] ctxname is the default Web application for name.
|
Description
| [context] ctxname is the default Web application for name.
|
|
Cause
| The given Web application is being registered as a default Web application.
|
|
Action
| Debug message only. No action necessary.
|
|
|
BEA-101055(retired)
|
Error: [context] Could not load Web application name.
|
Description
| [context] Could not load Web application name.
|
|
Cause
| Failed to deploy the Web application.
|
|
Action
| Check the exception for the exact error message.
|
|
|
BEA-101056(retired)
|
Info: [context] name has no parent context.
|
Description
| [context] name has no parent context.
|
|
Cause
| Context not found with the given name.
|
|
Action
| Debug message only. No action required.
|
|
|
BEA-101057(retired)
|
Info: [context] defaul is the parent context for name.
|
Description
| [context] defaul is the parent context for name.
|
|
Cause
| Found the context with the given name successfully.
|
|
Action
| Debug message only. No action required.
|
|
|
BEA-101058(retired)
|
Debug: [context] Loading name from defaults
|
Description
| [context] Loading name from defaults
|
|
Cause
| Loading context using default settings.
|
|
Action
| Debug message only. No action required.
|
|
|
BEA-101059
|
Debug: [context] Loading name from WAR file: war
|
Description
| [context] Loading name from WAR file: war
|
|
Cause
| Deploying the Web application using the WAR file.
|
|
Action
| Debug message only. No action required.
|
|
|
BEA-101060
|
Info: [context] Loading "name" from directory: "dir"
|
Description
| [context] Loading "name" from directory: "dir"
|
|
Cause
| Deploying the Web application using exploded directory structure.
|
|
Action
| Debug message only. No action required.
|
|
|
BEA-101061
|
Error: [context] Could not find Web application "src".
|
Description
| [context] Could not find Web application "src".
|
|
Cause
| Unable to load the descriptor for the Web application with the name given.
|
|
Action
| Check the error message for details and check if the Web application has been configured properly.
|
|
|
BEA-101062
|
Error: [context] Error reading Web application "src".
|
Description
| [context] Error reading Web application "src".
|
|
Cause
| IOException occurred while reading the descriptors for the Web application.
|
|
Action
| Check if the web.xml and weblogic.xml descriptors exist in the right place.
|
|
|
BEA-101063(retired)
|
Error: [ctx] Error parsing descriptor in Web appplication "src".
|
Description
| [ctx] Error parsing descriptor in Web appplication "src".
|
|
Cause
| Unexpected error occurred while reading the descriptors for the Web application.
|
|
Action
| Check if the web.xml and weblogic.xml descriptors exist in the right place.
|
|
|
BEA-101064
|
Error: [ctx] Error parsing descriptor in Web appplication "src"
|
Description
| [ctx] Error parsing descriptor in Web appplication "src"
|
|
Cause
| Unexpected error while reading the descriptors for the webapp
|
|
Action
| Please check if the web.xml/weblogic.xml exist in the right place
|
|
|
BEA-101065(retired)
|
Error: [ctx] Failed to obtain local host name
|
Description
| [ctx] Failed to obtain local host name
|
|
Cause
| Unable to resolve the local host into a valid host name.
|
|
Action
| Check your configuration.
|
|
|
BEA-101066
|
Error: [ctx] Cannot initialize http URL resources. Could not get JNDI context: err.
|
Description
| You will not be able to invoke the configured JNDI resources using HTTP tunneling.
|
|
Cause
| The JNDI context was not found, so the URL Contexts could not be registered.
|
|
Action
| Check if JNDI was properly configured.
|
|
|
BEA-101067
|
Error: [ctx] Disregarding null URL resource value for property jndiName
|
Description
| [ctx] Disregarding null URL resource value for property jndiName
|
|
Cause
| The URL for the JNDI resource specified in URLResource was null.
|
|
Action
| Correct your configuration (WebServerMBean). The URLs cannot be null.
|
|
|
BEA-101068
|
Error: [ctx] Could not parse URL resource value url.
|
Description
| [ctx] Could not parse URL resource value url.
|
|
Cause
| The URL for the JNDI resource specified in URL Resource was malformed.
|
|
Action
| Correct your configuration (WebServerMBean). Specify a valid URL.
|
|
|
BEA-101069
|
Error: [ctx] Could not bind URL url to JNDI name jndi error message: err.
|
Description
| [ctx] Could not bind URL url to JNDI name jndi error message: err.
|
|
Cause
| Failed to bind the URL with the JNDI name.
|
|
Action
| Correct your configuration (WebServerMBean).
|
|
|
BEA-101070
|
Info: [ctx] Bound URL resource "url" to JNDI name "jndi".
|
Description
| [ctx] Bound URL resource "url" to JNDI name "jndi".
|
|
Cause
| This is an information message only.
|
|
Action
| No action required.
|
|
|
BEA-101071(retired)
|
Error: [ctx] HTTP log file does not use version 1.0 of Extended Log File format.
|
Description
| [ctx] HTTP log file does not use version 1.0 of Extended Log File format.
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101072(retired)
|
Error: [ctx] Exception reading headers of HTTP log file
|
Description
| [ctx] Exception reading headers of HTTP log file
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101073(retired)
|
Error: [ctx] HTTP log file is not in Extended Log Format
|
Description
| [ctx] HTTP log file is not in Extended Log Format
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101074(retired)
|
Error: [ctx] Exception closing HTTP log file
|
Description
| [ctx] Exception closing HTTP log file
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101075
|
Info: [ctx] HttpServer is shuttingdown.
|
Description
| [ctx] HttpServer is shuttingdown.
|
|
Cause
| The webserver is shutting down.
|
|
Action
| Debug message. No action required.
|
|
|
BEA-101076(retired)
|
Info: [ctx] Destroying servlets in default servlet context.
|
Description
| [ctx] Destroying servlets in default servlet context.
|
|
Cause
| Destroying servlets in the default Web application upon Web server shutdown.
|
|
Action
| Debug message. No action required.
|
|
|
BEA-101077(retired)
|
Info: [ctx] Created log stream fName.
|
Description
| [ctx] Created log stream fName.
|
|
Cause
| Debug message.
|
|
Action
| No action required.
|
|
|
BEA-101078(retired)
|
Info: [ctx] Created double buffered log stream fName.
|
Description
| [ctx] Created double buffered log stream fName.
|
|
Cause
| Debug message.
|
|
Action
| No Action required.
|
|
|
BEA-101079(retired)
|
Error: [ctx] Exception occurred while opening HTTP log file: logfile.
|
Description
| [ctx] Exception occurred while opening HTTP log file: logfile.
|
|
Cause
| The log file could not be opened.
|
|
Action
| Check the exception for details.
|
|
|
BEA-101080(retired)
|
Error: [ctx] Exception occurred while flushing HTTP log file.
|
Description
| [ctx] Exception occurred while flushing HTTP log file.
|
|
Cause
| The flush failed.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101081(retired)
|
Error: [ctx] Event Parameter Exception:
|
Description
| [ctx] Event Parameter Exception:
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101082(retired)
|
Error: [ctx] Event Generation Exception:
|
Description
| [ctx] Event Generation Exception:
|
|
Cause
| Message not in use.
|
|
Action
| Message not in use.
|
|
|
BEA-101083
|
Error: Connection failure.
|
Description
| The HttpRequest failed to execute.
|
|
Cause
| Failed while writing data into the stream.
|
|
Action
| Check the exception for exact cause.
|
|
|
BEA-101084(retired)
|
Info: First line: line
|
Description
| First line of the HTTP request containing: method + uri + protocol
|
|
Cause
| This is an information message.
|
|
Action
| No action required.
|
|
|
BEA-101085(retired)
|
Info: host: host
|
Description
| host: host
|
|
Cause
| Debug message - host header
|
|
Action
| No action required.
|
|
|
BEA-101086
|
Info: No host in HTTP header. Dispatching to default HTTP server.
|
Description
| No host in HTTP header. dispatching to default HTTP server.
|
|
Cause
| Host header missing.
|
|
Action
| Make sure the requests are accompanied with a host header in order for Virtual Hosting to work. Also, proper HTTP redirects must have a host header.
|
|
|
BEA-101087
|
Info: host is not a virtual host. Dispatching to default HTTP server.
|
Description
| host is not a virtual host. Dispatching to default HTTP server.
|
|
Cause
| The host header is missing from the HTTP request.
|
|
Action
| Make sure the requests are accompanied with a host header in order for Virtual Hosting to work. Also, proper HTTP redirects must have a host header.
|
|
|
BEA-101088
|
Info: Dispatching request to host.
|
Description
| Dispatching request to host.
|
|
Cause
| Dispatching the request to the Web server (Virtual Host) defined by the host header.
|
|
Action
| Check the configuration.
|
|
|
BEA-101089(retired)
|
Warning: Unable to resolve the request "line" on server to any deployed Web application.
|
Description
| Unable to resolve the request "line" on server to any deployed Web application.
|
|
Cause
| The Web application is either not deployed or the request was not formed correctly.
|
|
Action
| Check if the Web application was deployed.
|
|
|
BEA-101090(retired)
|
Debug: Bad first line: line
|
Description
| Bad first line: line
|
|
Cause
| Request was malformed.
|
|
Action
| Check the HTTP request.
|
|
|
BEA-101091(retired)
|
Error: HTTP/1.1 without Host request-header.
|
Description
| HTTP/1.1 without Host request-header. The HOST header is mandatory in HTTP1.1.
|
|
Cause
| Host header is mandatory in HTTP 1.1.
|
|
Action
| Make sure all the clients send the host header with the request.
|
|
|
BEA-101092(retired)
|
Info: POST without Content-Length.
|
Description
| POST without Content-Length. Content length header is mandatory if the post is not chunk transfer encoded.
|
|
Cause
| Post came without a content-length.
|
|
Action
| Make sure either the content length is present or the post is chunk transfer encoded.
|
|
|
BEA-101093
|
Error: Problem occurred while dispatching servlet request.
|
Description
| Problem occurred while dispatching servlet request.
|
|
Cause
| The request could not be dispatched into the execute queue.
|
|
Action
| The request could be malformed. Check the exception for the exact cause.
|
|
|
BEA-101094(retired)
|
Error: Malformed HTTP header, no 1st line - localCount: count localBuf: dump, dump description
|
Description
| This is a malformed request.
|
|
Cause
| The header was found to be in an invalid format.
|
|
Action
| Check the HTTP 1.0/1.1 specs for the correct format.
|
|
|
BEA-101095
|
Error: POST time exceeded the configured MaxPostTimeSecs of time.
|
Description
| POST time exceeded the configured MaxPostTimeSecs of time.
|
|
Cause
| The parameter makes sure that a malicious user does not send slow POSTs to cause a denial of service attack.
|
|
Action
| If you think the time was too short, try increasing the value of MaxPostTimeSecs using the Admin Console.
|
|
|
BEA-101096
|
Error: POST size exceeded the MaxPostSize=size.
|
Description
| POST size exceeded the MaxPostSize=size.
|
|
Cause
| The parameter makes sure that a malicious user does not send huge POSTs to cause a denial of service attack.
|
|
Action
| If you think the post size is unreasonable, try increasing MaxPostSize using the Admin Console.
|
|
|
BEA-101097(retired)
|
Debug: Registering ServletContext: "name"
|
Description
| Registering ServletContext: "name"
|
|
Cause
| Debug message
|
|
Action
| No action required.
|
|
|
BEA-101098(retired)
|
Warning: Cannot resolve request for URI: "uri".
|
Description
| Cannot resolve request for URI: "uri".
|
|
Cause
| The request could not resolve to any Web application deployed in the server.
|
|
Action
| Make sure the Web application was deployed and is activated to server requests.
|
|
|
BEA-101099(retired)
|
Debug: Found context: "name" for URI: "uri"
|
Description
| Found context: "name" for URI: "uri"
|
|
Cause
| Debug message
|
|
Action
| Needs no action
|
|
|
BEA-101100
|
Error: [ctx] Got bad cookie header: header from User-Agent: agent
|
Description
| [ctx] Got bad cookie header: header from User-Agent: agent
|
|
Cause
| Cookie was malformed.
|
|
Action
| Refer to the cookie specs for the correct format: http://www.ietf.org/rfc/rfc2965.txt (Oct 2000; Obsoletes: 2109) http://www.ietf.org/rfc/rfc2109.txt (Feb 1997) http://www.ietf.org/rfc/rfc2616.txt (Jun 1999; Obsoletes: 2068) http://www.ietf.org/rfc/rfc2068.txt (Jan 1997)
|
|
|
BEA-101101
|
Error: [ctx] Unable to create new session.
|
Description
| [ctx] Unable to create new session.
|
|
Cause
| A new session could not be created.
|
|
Action
| Make sure the persistent store has been properly configured.
|
|
|
BEA-101102(retired)
|
Debug: [ctx] ServletRequestImpl: s
|
Description
| [ctx] ServletRequestImpl: s
|
|
Cause
| Debug message.
|
|
Action
| No action required.
|
|
|
BEA-101103(retired)
|
Error: [ctx] ServletRequestImpl: s
|
Description
| [ctx] ServletRequestImpl: s
|
|
Cause
| This is an unexpected error message.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101104
|
Error: Servlet execution in servlet context "ctx0" failed, t1.
|
Description
| Servlet execution in servlet context "ctx0" failed, t1.
|
|
Cause
| Unexpected error occurred while serving the request. This is not a simple client connection reset error.
|
|
Action
| Check the error message for the exact cause.
|
|
|
BEA-101105
|
Error: [ctx] error-page location: "location" for the error-code: "code" does not exist. Serving the default error page.
|
Description
| [ctx] error-page location: "location" for the error-code: "code" does not exist. Serving the default error page.
|
|
Cause
| The error-page you configured in web.xml does not exist. A configuration error has occurred.
|
|
Action
| Correct the web.xml descriptor, or make the resource available.
|
|
|
BEA-101106
|
Error: [ctx] Could not serve custom error page: "loc" for the error code: "code"
|
Description
| [ctx] Could not serve custom error page: "loc" for the error code: "code"
|
|
Cause
| The error-page you configured in web.xml does not exist. A configuration error has occurred.
|
|
Action
| Correct the web.xml descriptor, or make the resource available.
|
|
|
BEA-101107
|
Error: [ctx] Problem occurred while serving the error page.
|
Description
| [ctx] Problem occurred while serving the error page.
|
|
Cause
| The error-page you configured in web.xml could not be served.
|
|
Action
| Check your configuration in web.xml.
|
|
|
BEA-101108
|
Error: [ctx] Unsupported encoding: "encoding" specified.
|
Description
| [ctx] Unsupported encoding: "encoding" specified.
|
|
Cause
| The encoding specified is not supported by the underlying VM.
|
|
Action
| Make sure that the encoding specified is valid, or install the additional encoding classes.
|
|
|
BEA-101109(retired)
|
Error: [ctx] Location: " loc" for the exception: "err" does not exist. Serving the default error page.
|
Description
| [ctx] Location: " loc" for the exception: "err" does not exist. Serving the default error page.
|
|
Cause
| The exception location you specified in web.xml was not found.
|
|
Action
| Correct web.xml or make the resource available.
|
|
|
BEA-101110(retired)
|
Error: [ctx] Problem occurred while serving the exception page.
|
Description
| [ctx] Problem occurred while serving the exception page.
|
|
Cause
| Could not serve the exception page you specified for the exception type.
|
|
Action
| Check your configuration.
|
|
|
BEA-101111(retired)
|
Debug: [ctx] ServletResponseImpl: s
|
Description
| [ctx] ServletResponseImpl: s
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101112(retired)
|
Debug: [ctx] Got expected AddToMapException e . Note this is not an error.
|
Description
| [ctx] Got expected AddToMapException e. Note this is not an error.
|
|
Cause
| This is a debug message only.
|
|
Action
| This exception is used an expected behavior and used in constructive sense by the container. Please ignore.
|
|
|
BEA-101113(retired)
|
Error: [ctx] Error instantiating servlet "name" in the Single Thread Model.
|
Description
| [ctx] Error instantiating servlet "name" in the Single Thread Model.
|
|
Cause
| Failed to get a pooled instance.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101114(retired)
|
Info: [ctx] ServletStubImpl.isAvailable
|
Description
| [ctx] ServletStubImpl.isAvailable
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101115(retired)
|
Info: [ctx] name=name
|
Description
| [ctx] name=name
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101116(retired)
|
Info: Web application: ctx is currently unavailable. Message:s.
|
Description
| Web application: ctx is currently unavailable. Message:s.
|
|
Cause
| The Web application is currently unavailable.
|
|
Action
| Check if the Web application has been deactivated intentionally.
|
|
|
BEA-101117(retired)
|
Debug: [ctx] theServlet=servlet
|
Description
| [ctx] theServlet=servlet
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101118(retired)
|
Debug: [ctx] isSingleThreadModel=single
|
Description
| [ctx] isSingleThreadModel=single
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101119(retired)
|
Info: [ctx] servletPool=pool
|
Description
| [ctx] servletPool=pool
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101120(retired)
|
Info: [ctx] available=avail
|
Description
| [ctx] available=avail
|
|
Cause
| This is a debug message.
|
|
Action
| No action required.
|
|
|
BEA-101121(retired)
|
Info: [ctx] ServletStubImpl.prepareServlet
|
Description
| [ctx] ServletStubImpl.prepareServlet
|
|
Cause
| Creating servlet instances and initializing them.
|
|
Action
| Debug message. No action required.
|
|
|
BEA-101122
|
Info: [ctx] Servlet: "name" is permanently unavailable.
|
Description
| [ctx] Servlet: "name" is permanently unavailable.
|
|
Cause
| The Web application is not available currently.
|
|
Action
| Check to see if the Web application has been deactivated. Check if redeployment is in progress.
|
|
|
BEA-101123
|
Info: [ctx] Servlet: "name" will be unavailable for the next: "time" seconds.
|
Description
| [ctx] Servlet: "name" will be unavailable for the next: "time" seconds.
|
|
Cause
| The servlet has been marked as unavailable.
|
|
Action
| Make the request again after the specified time.
|
|
|
BEA-101124(retired)
|
Error: [ctx] Error loading servlet: "name"
|
Description
| [ctx] Error loading servlet: "name"
|
|
Cause
| Failed to load the servlet.
|
|
Action
| Check if the servlet has been configured properly in web.xml. Also, check the exception for the exact cause.
|
|
|
BEA-101125
|
Error: [ctx] Error occurred while instantiating servlet: "name".
|
Description
| [ctx] Error occurred while instantiating servlet: "name".
|
|
Cause
| Failed to instantiate the servlet.
|
|
Action
| Check if the servlet has been configured properly in web.xml. Also, check the exception for the exact cause.
|
|
|
BEA-101126
|
Error: [ctx] Error casting servlet: "name" to javax.servlet.Servlet
|
Description
| [ctx] Error casting servlet: "name"
|
|
Cause
| The servlet class that has been configured does not implement javax.servlet.Servlet.
|
|
Action
| Fix the definition of the class.
|
|
|
BEA-101127(retired)
|
Warning: HTTP services are disabled.
|
Description
| HTTP services are disabled.
|
|
Cause
| HTTP services have been disabled temporarily.
|
|
Action
| HTTP request will not be served. Contact your system administrator.
|
|
|
BEA-101128
|
Info: Initializing HTTP services.
|
Description
| Initializing HTTP services.
|
|
Cause
| This is an information only message.
|
|
Action
| Make sure the resources are available now.
|
|
|
BEA-101129
|
Info: Initializing the Web application container.
|
Description
| Initializing the Web application container.
|
|
Cause
| This is an informational message.
|
|
Action
| This is an informational message.
|
|
|
BEA-101130(retired)
|
Info: Creating default Web server named: name.
|
Description
| Creating default Web server named: name.
|
|
Cause
| This is an informational message.
|
|
Action
| This is an informational message.
|
|
|
BEA-101131(retired)
|
Error: The Web application container has not been initialized. Cannot register servlet name.
|
Description
| The Web application container has not been initialized. Cannot register servlet name.
|
|
Cause
| The servlet registration was attempted before the Web application container was initialized.
|
|
Action
| Please report this to BEA support.
|
|
|
BEA-101132(retired)
|
Error: J2EEService not initialized. Cannot register servlet name.
|
Description
| J2EEService not initialized. Cannot register servlet name.
|
|
Cause
| The servlet registration was attempted before the J2EE container was initialized.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101133
|
Info: Initializing Web server name.
|
Description
| Initializing Web server name.
|
|
Cause
| The Web server was just initialized.
|
|
Action
| No action required.
|
|
|
BEA-101134(retired)
|
Info: Registering host: name
|
Description
| Registering host: name
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101135
|
Info: name is the default Web server.
|
Description
| name is the default Web server.
|
|
Cause
| Logging the default Web server name.
|
|
Action
| Informational message only for debug purpose. No action required.
|
|
|
BEA-101136
|
Info: Registering virtual host: name.
|
Description
| Registering virtual host: name.
|
|
Cause
| Virtual Host (non-default Web server) has been registered.
|
|
Action
| Informational message only for debug purposes. No action required.
|
|
|
BEA-101137(retired)
|
Info: Registered Servlet:servletName ClassName:className
|
Description
| Registered Servlet:servletName ClassName:className
|
|
Cause
| Servlet has been registered.
|
|
Action
| Informational message only for debug purposes. No action required.
|
|
|
BEA-101138
|
Warning: ctx One of the getParameter family of methods called after reading from the ServletInputStream. Not merging post parameters.
|
Description
| ctx One of the getParameter family of methods called after reading from the ServletInputStream. Not merging post parameters.
|
|
Cause
| If the servlet reads the data from the input stream directly, then the request data will not be available for the getParameter family of methods.
|
|
Action
| If your code relies on post parameters being avaliable through the getParameter method, please fix your code.
|
|
|
BEA-101139(retired)
|
Info: Loading servlet name into ctx context.
|
Description
| Loading servlet name into ctx context.
|
|
Cause
| Loading the servlet on startup, as it was marked as load-on-startup in web.xml.
|
|
Action
| This is an informational message for debug purposes only. No action required.
|
|
|
BEA-101140
|
Error: Error occurred while creating servlet servletName (class: className, initArgs: initArgs) for Web application webapp.
|
Description
| Error occurred while creating servlet servletName (class: className, initArgs: initArgs) for Web application webapp.
|
|
Cause
| Failed to initialize the servlet instance.
|
|
Action
| Please check your configuration and the exception for the exact error message.
|
|
|
BEA-101141(retired)
|
Error: Error creating Web app runtime for webapp: t.
|
Description
| Error creating Web app runtime for webapp: t.
|
|
Cause
| The Web application runtime MBean that is used for monitoring could not be created.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101142
|
Error: Error unregistering servlet runtime runtime.
|
Description
| Error unregistering servlet runtime runtime.
|
|
Cause
| The servlet runtime MBean that is used for monitoring could not be destroyed.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101143
|
Error: Error occurred while unregistering Web application component runtime runtime.
|
Description
| Error occurred while unregistering Web application component runtime runtime.
|
|
Cause
| The Web application runtime MBean that is used for monitoring could not be destroyed.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101144(retired)
|
Warning: You must declare virtual host names for virtHost.
|
Description
| You must declare virtual host names for virtHost - which is a manadatory element.
|
|
Cause
| VirtualHost is a manadatory parameter as the Web server resolution is based on the host name.
|
|
Action
| Correct the configuration using the Admin Console.
|
|
|
BEA-101145(retired)
|
Info: Generating a default Web application named name.
|
Description
| Generating a default Web application named name.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101146(retired)
|
Debug: Registering default ServletContext: "name"
|
Description
| Registering default ServletContext: "name"
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101147
|
Debug: svr Found no context for "url". This request does not match the context path for any installed Web applications, and there is no default Web application configured.
|
Description
| svr Found no context for "url". This request does not match the context path for any installed Web applications, and there is no default Web application configured.
|
|
Cause
| The request did not find a matching Web application deployed in the Web server.
|
|
Action
| Make sure the Web application has been deployed.
|
|
|
BEA-101148(retired)
|
Debug: Resolving URI: Searching for uri in ctx.
|
Description
| Resolving URI: Searching for uri in ctx.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101149(retired)
|
Debug: ctx: Relative URI for uri is relUri.
|
Description
| ctx: Relative URI for uri is relUri.
|
|
Cause
| Relative URI is relative to the current servlet context.
|
|
Action
| Information message only.
|
|
|
BEA-101150(retired)
|
Debug: ctx: URI for uri redirected to relUri.
|
Description
| ctx: URI for uri redirected to relUri.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101151(retired)
|
Debug: ctx: uri resolved to the default servlet (stub).
|
Description
| ctx: uri resolved to the default servlet (stub).
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101152(retired)
|
Debug: ctx: uri resolved to the servlet (stub).
|
Description
| ctx: uri resolved to the servlet (stub).
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101153(retired)
|
Debug: Socket connection was reset by peer.
|
Description
| Socket connection was reset by peer. The client abnormally terminated the connection.
|
|
Cause
| The connection was abnormaly terminated by the client before the server could flush the complete response.
|
|
Action
| Informational message only. The server tries to squelch these socket reset exceptions if possible, because socket exception is a very common occurrence.
|
|
|
BEA-101154(retired)
|
Error: Got an error while resolving entity "id". Check your DTD reference.
|
Description
| Got an error while resolving entity "id". Check your DTD reference.
|
|
Cause
| Descriptor validation failed.
|
|
Action
| Check the DTD and make sure the descriptors comply with that. Check the exception message for more details.
|
|
|
BEA-101155(retired)
|
Error: Could not resolve entity "id". Check your DTD reference.
|
Description
| Could not resolve entity "id". Check your DTD reference.
|
|
Cause
| Descriptor validation failed.
|
|
Action
| Check the DTD and make sure the descriptors comply with that. Check the exception message for more details.
|
|
|
BEA-101156(retired)
|
Warning: A Web server named "defsvr" already exists. The declared Web server "newsvr" will be ignored.
|
Description
| A Web Server named "defsvr" already exists. The declared Web server "newsvr" will be ignored.
|
|
Cause
| The Web server is using a name that is already in use.
|
|
Action
| Choose a different name.
|
|
|
BEA-101157(retired)
|
Error: [ctx] Unable to create a new session, as the server is in a suspended state.
|
Description
| [ctx] Unable to create a new session, as the server is in a suspended state.
|
|
Cause
| New session creation failed.
|
|
Action
| Wait until the server comes back.
|
|
|
BEA-101158(retired)
|
Debug: Exception thrown while loading appName: msg
|
Description
| Exception thrown while loading appName: msg
|
|
Cause
| The Web application could not be deployed.
|
|
Action
| Check the exact error message and fix the configuration problem.
|
|
|
BEA-101159
|
Error: [ctx] Received IllegalAccessException while instantiating servlet: "name". Make sure your servlet implementation is a public class.
|
Description
| [ctx] Received IllegalAccessException while instantiating servlet: "name". Make sure your servlet implementation is a public class.
|
|
Cause
| This occurs if WebLogic attempts to instantiate a servlet class that is not declared public.
|
|
Action
| Make sure that your servlet implementation is a public class.
|
|
|
BEA-101160
|
Warning: Deployment descriptor is malformed, check against the DTD: msg.
|
Description
| Deployment descriptor is malformed, check against the DTD: msg.
|
|
Cause
| The web.xml file is not in strict conformance to the DTD. You may experience problems with your deployment if this is not corrected.
|
|
Action
| Check your web.xml file against the DTD to ensure conformance. Remember that ordering of elements is important.
|
|
|
BEA-101161(retired)
|
Warning: Public ID references the old version of Servlet DTD. Change the public ID in web.xml file to "s".
|
Description
| Public ID references the old version of Servlet DTD. Change the public ID in web.xml file to "s".
|
|
Cause
| The Public ID in WEB-INF/web.xml references the old version of Servlet DTD.
|
|
Action
| Generally, this will not cause any problems with your application unless the DTD has changed in such a way that your web.xml cannot be parsed. To avoid the message, change the public ID in web.xml file to the current version of the Servlet DTD.
|
|
|
BEA-101162
|
Warning: User defined listener s failed: t.
|
Description
| User defined listener s failed: t.
|
|
Cause
| The listener failed while processing the event fired by the container.
|
|
Action
| Please check the exception for exact error message and fix the listener code.
|
|
|
BEA-101163
|
Error: Could not load user defined listener: s
|
Description
| Could not load user defined listener: s.
|
|
Cause
| The listener class could not be loaded or instantiated.
|
|
Action
| Please check the exception for the exact error message and fix the listener code.
|
|
|
BEA-101164
|
Warning: User defined class s is not a Listener, as it does not implement the correct interface(s).
|
Description
| User defined class s is not a listener, as it does not implement the correct interface(s).
|
|
Cause
| Invalid class.
|
|
Action
| Fix the listener code to implement appropriate interfaces.
|
|
|
BEA-101165
|
Error: Could not load user defined filter in web.xml: s.
|
Description
| Could not load user defined filter in web.xml: s.
|
|
Cause
| The filter class could not be loaded.
|
|
Action
| Check the configuration and make sure the class is avaliable to the context classloader.
|
|
|
BEA-101166(retired)
|
Warning: User defined class s is not a filter.
|
Description
| User defined class s is not a filter. The class must implement javax.servlet.Filter.
|
|
Cause
| User defined class does not implement the javax.servlet.Filter interface.
|
|
Action
| Please fix the filter class.
|
|
|
BEA-101167(retired)
|
Warning: The servlet-mapping with pattern s has an invalid servlet reference.
|
Description
| The servlet-mapping with pattern s has an invalid servlet reference.
|
|
Cause
| The servlet was not configured properly.
|
|
Action
| Please check the configuration in web.xml.
|
|
|
BEA-101168
|
Error: The security-role-assignment references an invalid security-role: s.
|
Description
| The security-role-assignment references an invalid security-role: s.
|
|
Cause
| The security-role-assignment specified in weblogic.xml is not valid.
|
|
Action
| Make sure the role-name defined in web.xml, is valid. Also check the DTD and examples for the correct syntax.
|
|
|
BEA-101169
|
Warning: The servlet svlt is referenced but not defined in web.xml.
|
Description
| The servlet svlt is referenced but not defined in web.xml.
|
|
Cause
| The servlet-mapping element in web.xml refers to a servlet name that was not defined.
|
|
Action
| Make sure the servlet-name that is used for the mapping is defined. Please check the DTD for the syntax.
|
|
|
BEA-101170
|
Error: The servlet svlt is referenced in servlet-mapping pattern, but not defined in web.xml.
|
Description
| The servlet svlt is referenced in servlet-mapping pattern, but not defined in web.xml.
|
|
Cause
| The servlet-mapping element in web.xml refers to a servlet name that was not defined.
|
|
Action
| Make sure the servlet-name that is used for the mapping is defined. Check the DTD for the syntax.
|
|
|
BEA-101171
|
Warning: The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.
|
Description
| The web.xml descriptor has no resource-ref entries for the reference-descriptor defined in weblogic.xml.
|
|
Cause
| The resource-ref-name referred by reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.
|
|
Action
| Please make sure the resource-ref-name matches a resource-ref-name defined in web.xml.
|
|
|
BEA-101172
|
Warning: The web.xml descriptor has no ejb-ref entries.
|
Description
| The web.xml descriptor has no ejb-ref entries.
|
|
Cause
| The ejb-ref-name referred by reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.
|
|
Action
| Please make sure ejb-ref-name matches a ejb-ref-name defined in web.xml.
|
|
|
BEA-101173
|
Warning: Did not find resource-ref in web.xml matching name.
|
Description
| Did not find resource-ref in web.xml matching name.
|
|
Cause
| The resource-ref-name referred by reference-descriptor in weblogic.xml should have a corresponding resource-ref-name defined in web.xml.
|
|
Action
| Please make sure the resource-ref-name matches a resource-ref-name defined in web.xml.
|
|
|
BEA-101174
|
Warning: Did not find ejb-ref in web.xml matching name.
|
Description
| Did not find ejb-ref in web.xml matching name.
|
|
Cause
| The ejb-ref-name referred by reference-descriptor in weblogic.xml should have a corresponding ejb-ref-name defined in web.xml.
|
|
Action
| Please make sure ejb-ref-name matches a ejb-ref-name defined in web.xml.
|
|
|
BEA-101175
|
Warning: [ctx] Exception occurred while closing zip file zip.
|
Description
| [ctx] Exception occurred while closing zip file zip.
|
|
Cause
| Failed to close a zip file while undeploying a Web application.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101176
|
Debug: Non-uniform configuration detected. Could not find context for uri in the secondary server.
|
Description
| Non-uniform configuration detected. Could not find context for uri in the secondary server.
|
|
Cause
| No Web application with this context path has been deployed on the secondary server. WebLogic session replication mechanism does not support non-uniform deployments.
|
|
Action
| Please make sure you target the whole cluster.
|
|
|
BEA-101177(retired)
|
Debug: Looking for ctx in ctxList.
|
Description
| Looking for ctx in ctxList.
|
|
Cause
| Resolving the request to one of the deployed servlet contexts.
|
|
Action
| This is an informational message only intended for debugging. No action required.
|
|
|
BEA-101178(retired)
|
Error: Error deploying internal context ctx.
|
Description
| Error deploying internal context ctx.
|
|
Cause
| The internal Web application failed to deploy.
|
|
Action
| Please report this problem to BEA support.
|
|
|
BEA-101179(retired)
|
Error: [ctx] Error occurred while parsing descriptor in Web application "src" [Path="path", URI="uri"
|
Description
| [ctx] Error occurred while parsing descriptor in Web application "src" [Path="path", URI="uri"
|
|
Cause
| The descriptor was not configured correctly. The Web application will not be deployed.
|
|
Action
| Additional messages must have been logged, which will have the exact problem. Correct the configuration problem in the descriptor and refer to the DTD for the exact syntax.
|
|
|
BEA-101180
|
Warning: The auth-constraint references security-role: s, which is not defined in web.xml.
|
Description
| The auth-constraint references security-role: s, which is not defined in web.xml.
|
|
Cause
| The auth-constraint should refer to roles that have been defined in web.xml.
|
|
Action
| Add the definition of this role in the security-role element of web.xml.
|
|
|
BEA-101181(retired)
|
Warning: Could not find web.xml under WEB-INF in the doc root: dir.
|
Description
| Could not find web.xml under WEB-INF in the doc root: dir.
|
|
Cause
| The web.xml descriptor is a mandatory component for a Web application.
|
|
Action
| Add a web.xml file under the WEB-INF directory.
|
|
|
BEA-101182(retired)
|
Warning: Could not find context: ctx with the given name for unregistering.
|
Description
| Could not find context: ctx with the given name for unregistering.
|
|
Cause
| An error occurred while a Web application was being unloaded.
|
|
Action
| Review the stack trace to try to understand the cause of the error.
|
|
|
BEA-101183(retired)
|
Info: [logContext] Unloading Web application: name.
|
Description
| [logContext] Unloading Web application: name.
|
|
Cause
| The Web application is being undeployed.
|
|
Action
| This is an informational message for debug purposes. No action required.
|
|
|
BEA-101184(retired)
|
Info: Updating context table of webserver from oldList to newList.
|
Description
| Updating context table of webserver from oldList to newList.
|
|
Cause
| The list of servlet contexts maintained by the Web server was modified as a result of either deployment or undeployment.
|
|
Action
| This informational message is for debugging purposes only. No action required.
|
|
|
BEA-101185(retired)
|
Info: Changing default context of webserver from oldCtx to newCtx.
|
Description
| Changing default context of webserver from oldCtx to newCtx.
|
|
Cause
| The default Web application has been changed.
|
|
Action
| Informationaly message for debugging only. No action required.
|
|
|
BEA-101186(retired)
|
Error: Application deployment failed. You have attempted to deploy an application that uses J2EE 1.3 features. J2EE 1.3 features are currently disabled in this server. To run WebLogic Server with J2EE 1.3 features enabled, obtain the "WebLogic Server 6.1 (Includes J2EE 1.3 features)" download from http://commerce.bea.com/downloads/products.jsp
|
Description
| Application deployment failed. You have attempted to deploy an application that uses J2EE 1.3 features. J2EE 1.3 features are currently disabled in this server. To run WebLogic Server with J2EE 1.3 features enabled, obtain the "WebLogic Server 6.1 (Includes J2EE 1.3 features)" download from http://commerce.bea.com/downloads/products.jsp
|
|
Cause
| Message no longer in use.
|
|
Action
| Message no longer in use.
|
|
|
BEA-101187(retired)
|
Warning: The filter-mapping with pattern s has an invalid filter reference.
|
Description
| The filter-mapping with pattern s has an invalid filter reference.
|
|
Cause
| The filter-mapping refers to a filter-name that has not been defined.
|
|
Action
| Please add the missing filter definition.
|
|
|
BEA-101188
|
Error: Bad exception-type exists in web.xml: name.
|
Description
| Bad exception-type exists in web.xml: name.
|
|
Cause
| An invalid class can cause this Exception while registering the Web application.
|
|
Action
| Check your classpath.
|
|
|
BEA-101189
|
Error: Could not load the url-match-map class defined in weblogic.xml: name.
|
Description
| Could not load the url-match-map class defined in weblogic.xml: name.
|
|
Cause
| An invalid classname will cause this exception while registering the Web application.
|
|
Action
| Check your classpath.
|
|
|
BEA-101190(retired)
|
Notice: Could not create temp file name.
|
Description
| Could not create temp file name.
|
|
Cause
| NT causes problems in some java.io.File operations when the path is over 256 characters.
|
|
Action
| Move your Web application to a directory closer to the root directory to decrease the path length.
|
|
|
BEA-101191(retired)
|
Debug: AdministrationPort is configured on port "adminPort" and console connection is using port "localPort"
|
Description
| AdministrationPort is configured on port "adminPort" and console connection is using port "localPort"
|
|
Cause
| Debug Message.
|
|
Action
| Debug Message.
|
|
|
BEA-101192(retired)
|
Error: Could not load the pre-processor-class defined in weblogic.xml: name.
|
Description
| Could not load the pre-processor-class defined in weblogic.xml: name.
|
|
Cause
| An invalid classname can cause this exception while registering a Web application.
|
|
Action
| Check your classpath.
|
|
|
BEA-101193(retired)
|
Warning: User-defined class s is not a valid Preprocessor. It must implement the weblogic.servlet.ServletPreprocessor interface.
|
Description
| User-defined class s is not a valid Preprocessor. It must implement the weblogic.servlet.ServletPreprocessor interface.
|
|
Cause
| The user-defined class does not implement weblogic.servlet.ServletPreprocessor.
|
|
Action
| Please fix the definition of the class.
|
|
|
BEA-101194
|
Warning: The preprocessor prep is referenced but not defined in weblogic.xml.
|
Description
| The preprocessor prep is referenced but not defined in weblogic.xml.
|
|
Cause
| The preprocessor element is not defined in weblogic.xml.
|
|
Action
| Check your weblogic.xml descriptor.
|
|
|
BEA-101195(retired)
|
Warning: [context] Could not resolve TLD from the given location "location".
|
Description
| [context] Could not resolve TLD from the given location "location".
|
|
Cause
| TLD location is incorrect.
|
|
Action
| Please make sure the correct TLD location is specified in the web.xml descriptor.
|
|
|
BEA-101196
|
Warning: [ctx]: Error while parsing the Tag Library Descriptor at "location".
|
Description
| [ctx]: Error while parsing the Tag Library Descriptor at "location".
|
|
Cause
| TLD parsing exception occurred.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101198
|
Error: Could not deploy role: role for Web application: webapp application: app.
|
Description
| Could not deploy role: role for Web application: webapp application: app.
|
|
Cause
| The Web application could not deploy the role defined in web.xml.
|
|
Action
| Make sure the security is configured properly in the server. Also check the stack trace for the exact cause.
|
|
|
BEA-101199
|
Error: Could not deploy policy for resource: resource.
|
Description
| Could not deploy policy for resource: resource.
|
|
Cause
| The Web applicatoin failed to deploy the policy for the security-constraint defined in web.xml.
|
|
Action
| Make sure the security is configured properly in the server. Also check the stack trace for the exact cause.
|
|
|
BEA-101200
|
Warning: CacheFilter not caching the response for uri: uri reason: message
|
Description
| CacheFilter not caching the response for uri: uri reason: message
|
|
Cause
| CacheFilter does not cache responses unless the status is 200.
|
|
Action
| Check the message for information on how to fix the problem.
|
|
|
BEA-101201
|
Debug: app:module loading descriptor
|
Description
| app:module loading descriptor
|
|
Cause
| The Web application is attempting to parse the Web application descriptors web.xml and weblogic.xml.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101202
|
Debug: app:module preparing the Web application module for deploymemt.
|
Description
| app:module preparing the Web application module for deploymemt.
|
|
Cause
| Preparing the Web application for deployment.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101203(retired)
|
Debug: app:module Received new classloader for the Web application.
|
Description
| app:module Received new classloader for the Web application. A change in classes or JAR files must have triggered this.
|
|
Cause
| A new classloader has been assigned to the Web application.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101204(retired)
|
Debug: app:module Incorporating new files for the Web application module.
|
Description
| app:module Incorporating new files for the Web application module.
|
|
Cause
| The Web application received an update call with a list of modified files.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101205
|
Debug: app:module Rolling back the Web application module.
|
Description
| app:module Rolling back the Web application module.
|
|
Cause
| The Web application is being undeployed.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101206
|
Debug: app:module Activating the Web application module.
|
Description
| app:module Activating the Web application module. Should be ready to serve requests.
|
|
Cause
| The Web application is being activated to server requests.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101207
|
Debug: app:module Deactivating Web application module.
|
Description
| app:module Deactivating Web application module. It will be unavailable to serve http requests.
|
|
Cause
| The Web application is being deactivated. The new requests will be returned with a service unavailable status message.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101208
|
Debug: app:module is ready to serve http requests. Invoking start().
|
Description
| app:module is ready to serve http requests. Invoking start().
|
|
Cause
| The start() method of the module lifecycle has been invoked.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101209
|
Debug: app:module Ready to serve requests.
|
Description
| app:module Ready to serve requests.
|
|
Cause
| The Web application deployment completed successfully.
|
|
Action
| Information message only for debug purposes. No action required.
|
|
|
BEA-101210(retired)
|
Debug: app:module Registering servlet servlet with initArgs args.
|
Description
| app:module Registering servlet servlet with initArgs args.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101211
|
Debug: app:module Precompiling JSPs at startup with JSP config jspc.
|
Description
| app:module Precompiling JSPs at startup with JSP config jspc. The JspDescriptor in weblogic.xml was set to precompile = true.
|
|
Cause
| JSPs are being pre-compiled on startup.
|
|
Action
| This configuration has been set in weblogic.xml.
|
|
|
BEA-101212
|
Warning: app:module Failure while Precompiling JSPs: t.
|
Description
| app:module Failure while Precompiling JSPs: t.
|
|
Cause
| Failed to precompile JSPs on startup.
|
|
Action
| Please check the exception for the exact cause.
|
|
|
BEA-101213
|
Debug: app:module Binding web.xml resource reference name to JNDI name jndiname.
|
Description
| app:module Binding web.xml resource reference name to JNDI name jndiname.
|
|
Cause
| Debug message
|
|
Action
| Debug Message
|
|
|
BEA-101214
|
Error: Included resource or file "includedURI" not found from requested resource "referringURI".
|
Description
| Included resource or file "includedURI" not found from requested resource "referringURI".
|
|
Cause
| The included file is missing.
|
|
Action
| Add the missing file.
|
|
|
BEA-101215
|
Error: Malformed Request "url". Request parsing failed, Code: code
|
Description
| Malformed Request "url". Request parsing failed, Code: code
|
|
Cause
| The request does not follow the pattern specified by HTTP 1.0/1.1 specification(s).
|
|
Action
| Fix the client that sent the invalid request.
|
|
|
BEA-101216
|
Error: Servlet: "name" failed to preload on startup in Web application: "contextPath".
|
Description
| Servlet: "name" failed to preload on startup in Web application: "contextPath".
|
|
Cause
| The servlet that was marked as load-on-startup failed to preload on startup.
|
|
Action
| Check the exception for exact cause.
|
|
|
BEA-101217
|
Error: Cannot deploy newctx from newroot on webserver, because there is already a Web application named origctx loaded from origroot, using the context path contextPath.
|
Description
| Cannot deploy newctx from newroot on webserver, because there is already a Web application named origctx loaded from origroot, using the context path contextPath.
|
|
Cause
| The Web application that is being deployed has been assigned a context path that is already in use.
|
|
Action
| Choose a different context path.
|
|
|
BEA-101218
|
Error: An error exists in web.xml for servlet "servletName". Neither servlet-class nor jsp-file is defined.
|
Description
| An error exists in web.xml for servlet "servletName". Neither servlet-class nor jsp-file is defined.
|
|
Cause
| The servlet element should contain either servlet-class or jsp-file. Both are missing.
|
|
Action
| Update the web.xml descriptor.
|
|
|
BEA-101219(retired)
|
Error: Error initializing servlet context "ctx".
|
Description
| Error initializing servlet context "ctx".
|
|
Cause
| The Web application failed to initialize. It will not be deployed.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101220
|
Error: Error occurred while setting document root for "ctx" to "path".
|
Description
| Error occurred while setting document root for "ctx" to "path".
|
|
Cause
| Setting the doc root for the Web application failed. The Web application will not be deployed.
|
|
Action
| Check the IOException message for exact cause of the problem.
|
|
|
BEA-101221
|
Error: The url-pattern is empty or null for url-pattern ctx in pattern.
|
Description
| The url-pattern is empty or null for url-pattern ctx in pattern.
|
|
Cause
| Not a valid url-pattern for the servlet.
|
|
Action
| If you intended it to be a default servlet, then specify / or /*.
|
|
|
BEA-101222(retired)
|
Error: ctx: You are not allowed to unregister the default servlet.
|
Description
| ctx: You are not allowed to unregister the default servlet.
|
|
Cause
| You are not allowed to unregister the default servlet since this action is forbidden.
|
|
Action
| Please fix the code which is trying to perform this action.
|
|
|
BEA-101223
|
Error: ctx: The server server is temporarily suspended.
|
Description
| ctx: The server server is temporarily suspended.
|
|
Cause
| The server has been suspended by the administrator.
|
|
Action
| Wait until it comes back up again.
|
|
|
BEA-101224(retired)
|
Error: [context] Cannot load Implicit TLDs
|
Description
| [context] Cannot load Implicit TLDs.
|
|
Cause
| Failed to register implicit TLDs for the Web application.
|
|
Action
| Please check the exception for the exact cause.
|
|
|
BEA-101225(retired)
|
Error: ContextPath: contextPath Preprocessor: name invocation failed.
|
Description
| ContextPath: contextPath Preprocessor: name invocation failed.
|
|
Cause
| The servlet preprocessor that intercepts the request before the authentication and dispatch phase failed to execute.
|
|
Action
| Check the exception for the exact cause of the problem.
|
|
|
BEA-101226
|
Error: AuthFilter: name invocation failed in: phase phase for URI: uri
|
Description
| AuthFilter: name invocation failed in: phase phase for URI: uri
|
|
Cause
| The authentication filter that acts before and after the authentication phase failed to execute.
|
|
Action
| Please check the exception for the exact cause of the problem.
|
|
|
BEA-101227(retired)
|
Info: webapp: descriptor deployment descriptor is malformed. Check against the DTD: msg.
|
Description
| webapp: descriptor deployment descriptor is malformed. Check against the DTD: msg.
|
|
Cause
| The web.xml file is not in strict conformance to the DTD. You may experience problems with your deployment if this is not corrected.
|
|
Action
| Check your descriptor file against the DTD to ensure conformance. Remember that ordering of elements is important.
|
|
|
BEA-101228
|
Error: Failed to undeploy security policy for resource: resource while undeploying Web application.
|
Description
| Failed to undeploy security policy for resource: resource while undeploying Web application.
|
|
Cause
| The security policy defined in web.xml failed to undeploy upon Web application undeployment
|
|
Action
| Check the exception for the exact cause of the problem.
|
|
|
BEA-101229
|
Error: Failed to undepoy security policy for resource: resource while undeploying the Web application.
|
Description
| Failed to undepoy security policy for resource: resource while undeploying the Web application.
|
|
Cause
| The security role defined in web.xml failed to undeploy upon Web application undeployment.
|
|
Action
| Check the exception for the exact cause of the problem.
|
|
|
BEA-101230(retired)
|
Warning: [context] Could not find a TLD file at the given location: "file".
|
Description
| [context] Could not find a TLD file at the given location: "file".
|
|
Cause
| Failed to find the TLD file at the given location.
|
|
Action
| Make sure the TLD file is present at the given location.
|
|
|
BEA-101231
|
Error: HTTP log file does not use version 1.0 of the Extended Log File format.
|
Description
| HTTP log file does not use version 1.0 of the Extended Log File format.
|
|
Cause
| The ELF headers in the existing log file specifies a version other than 1.0.
|
|
Action
| Only version 1.0 is supported. Delete the existing log file and startover again.
|
|
|
BEA-101232
|
Error: Exception occurred while reading headers of HTTP log file.
|
Description
| Exception occurred while reading headers of HTTP log file.
|
|
Cause
| Received IOException while reading the headers.
|
|
Action
| Check the exception for the exact cause of the problem.
|
|
|
BEA-101233(retired)
|
Error: HTTP log file is not in Extended Log File format. Log file fields are missing.
|
Description
| HTTP log file is not in Extended Log File format. Log file fields are missing.
|
|
Cause
| Required Fields header is missing from Extended Log File headers.
|
|
Action
| Add the required Fields header.
|
|
|
BEA-101234
|
Error: Attempting to initialize ExtendedLogFormat application specific header: fieldName. However, failed due to exception.
|
Description
| Attempting to initialize ExtendedLogFormat application specific header: fieldName. However, failed due to exception.
|
|
Cause
| Unexpected error occurred while initializing the log file format.
|
|
Action
| Check the exception for the exact error message.
|
|
|
BEA-101235
|
Error: Attempting to initialize ExtendedLogFormat application specific header: fieldName. However, failed because class: className is not an instance of weblogic.servlet.logging.CustomELFLogger.
|
Description
| Attempting to initialize ExtendedLogFormat application specific header: fieldName. However, failed because class: className is not an instance of weblogic.servlet.logging.CustomELFLogger.
|
|
Cause
| Unexpected error occurred while initializing the ExtendedLogFormat.
|
|
Action
| Check the exception for the exact error message.
|
|
|
BEA-101236
|
Error: Format of log field fieldName is incorrect.
|
Description
| Format of log field fieldName is incorrect.
|
|
Cause
| The log field is in an invalid format.
|
|
Action
| Check the log field and fix the format.
|
|
|
BEA-101237
|
Info: HTTP logging has been disabled for the Web server: httpServer.
|
Description
| HTTP logging has been disabled for the Web server: httpServer.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101238(retired)
|
Info: HTTP log rotation is size based for the Web server: httpServer.
|
Description
| HTTP log rotation is size based for the Web server: httpServer.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101239(retired)
|
Info: HTTP log rotation is date based for the Web server: httpServer.
|
Description
| HTTP log rotation is date based for the Web server: httpServer.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101240(retired)
|
Error: Unknown HTTP log rotation type: type for the Web server: httpServer; using default type - size-based rotation.
|
Description
| Unknown HTTP log rotation type: type for the Web server: httpServer. Using default type - size-based rotation.
|
|
Cause
| HTTP log rotation type is not recognized.
|
|
Action
| Fix the configuration. The valid values are: "none", "byTime", and "bySize".
|
|
|
BEA-101241(retired)
|
Error: Failed to open HTTP log file: filename for the Web server: httpServer.
|
Description
| Failed to open HTTP log file: filename for the Web server: httpServer.
|
|
Cause
| Unexpected error occurred.
|
|
Action
| Check the disk for permissions.
|
|
|
BEA-101242
|
Error: Failed to roll HTTP log file for the Web server: httpServer.
|
Description
| Failed to roll HTTP log file for the Web server: httpServer.
|
|
Cause
| Unexpected error occurred.
|
|
Action
| Check the exception message for the exact cause.
|
|
|
BEA-101243(retired)
|
Info: HTTP log rotation scheduled to begin at: tm. Rotation taking place every: period minutes for the Web server: httpServer.
|
Description
| HTTP log rotation scheduled to begin at: tm. Rotation taking place every: period minutes for the Web server: httpServer.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101244(retired)
|
Debug: HTTP log rotation triggered, bytesWritten: bytes for the Web server: httpServer.
|
Description
| HTTP log rotation triggered, bytesWritten: bytes for the Web server: httpServer.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101245(retired)
|
Debug: Flushing LogStreamTrigger for the Web server: httpServer.
|
Description
| Flushing LogStreamTrigger for the Web server: httpServer.
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101246(retired)
|
Error: Error occurred while flushing HTTP log file for the Web server: httpServer\nt.
|
Description
| Error occurred while flushing HTTP log file for the Web server: httpServer\nt.
|
|
Cause
| Failed to flush the log.
|
|
Action
| Check the exception nessage for details.
|
|
|
BEA-101247
|
Warning: rootDir: Public ID references the old version of the Servlet DTD. You must change the public ID in web.xml file to "s".
|
Description
| rootDir: Public ID references the old version of the Servlet DTD. You must change the public ID in web.xml file to "s".
|
|
Cause
| The Public ID in WEB-INF/web.xml references the old version of servlet DTD.
|
|
Action
| Generally, this will not cause any problems with your application unless the DTD has changed in a way that your web.xml cannot be parsed. To avoid the message, change the public ID in web.xml file to the current version of the servlet DTD.
|
|
|
BEA-101248
|
Warning: [ctx]: Deployment descriptor "location" is malformed. Check against the DTD: msg (line line, column coulmn).
|
Description
| [ctx]: Deployment descriptor "location" is malformed. Check against the DTD: msg (line line, column coulmn).
|
|
Cause
| The descriptor file is not in strict conformance to its DTD. You may experience problems with your deployment if this is not corrected.
|
|
Action
| Check your descriptor file against the DTD to ensure conformance. Remember that ordering of elements is important.
|
|
|
BEA-101249
|
Error: [context]: Servlet class className for servlet svltName could not be loaded because the requested class was not found in the classpath classPath.\nt.
|
Description
| [context]: Servlet class className for servlet svltName could not be loaded because the requested class was not found in the classpath classPath.\nt.
|
|
Cause
| The servlet class was not recognized by the Web application classloader.
|
|
Action
| Make sure the servlet class is available either in WEB-INF/classes or WEB-INF/lib or system classpath.
|
|
|
BEA-101250
|
Error: [context]: Servlet class className for servlet svltName could not be loaded because a class on which it depends was not found in the classpath classPath.\nt.
|
Description
| [context]: Servlet class className for servlet svltName could not be loaded because a class on which it depends was not found in the classpath classPath.\nt.
|
|
Cause
| One of the classes the servlet class uses was not recognized by the Web application classloader.
|
|
Action
| Make sure the class is available either in WEB-INF/classes or WEB-INF/lib or system classpath.
|
|
|
BEA-101251
|
Error: [context]: Could not load servlet class className for servlet svltName because a resource on which it depends was not found in the classpath classPath.\nt.
|
Description
| [context]: Could not load servlet class className for servlet svltName because a resource on which it depends was not found in the classpath classPath.\nt.
|
|
Cause
| This exception is thrown if the Java Virtual Machine cannot find an appropriate native-language definition of a method that is declared native.
|
|
Action
| This could be due to a problem with path/LD_LIBRARY_PATH. Check if the resource it complains about exists.
|
|
|
BEA-101252
|
Error: [context]: Servlet class className for servlet svltName could not be verified.\nt.
|
Description
| [context]: Servlet class className for servlet svltName could not be verified.\nt.
|
|
Cause
| This exception is thrown when the "verifier" detects that a class file, though well formed, contains some sort of internal inconsistency or security problem.
|
|
Action
| Verify the servlet class.
|
|
|
BEA-101253
|
Error: [context]: Servlet class className for servlet svltName could not be defined. The class file could be corrupt.\nt.
|
Description
| [context]: Servlet class className for servlet svltName could not be defined. The class file could be corrupt.\nt.
|
|
Cause
| This exception is thrown when the Java Virtual Machine attempts to read a class file and determines that the file is malformed or otherwise cannot be interpreted as a class file.
|
|
Action
| Check to see if the class file is corrupt.
|
|
|
BEA-101254
|
Error: [context]: Servlet class className for servlet svltName could not be handled by the classloader with classpath classPath. \nt.
|
Description
| [context]: Servlet class className for servlet svltName could not be handled by the classloader with classpath classPath. \nt.
|
|
Cause
| Subclasses of LinkageError indicate that a class has some dependency on another class; however, the latter class has incompatibly changed after the compilation of the former class.
|
|
Action
| Check the class and its dependencies.
|
|
|
BEA-101255(retired)
|
Error: The default Web application assignment for the Web server: webserver has an error, because the original default Web application: original has been assigned the context-root value of "" or "/" in weblogic.xml or application.xml.
|
Description
| The default Web application assignment for the Web server: webserver has an error, because the original default Web application: original has been assigned the context-root value of "" or "/" in weblogic.xml or application.xml.
|
|
Cause
| The original default Web application was assigned a context-root of "/". You cannot change the context-root.
|
|
Action
| Setting the default Web application using console is not a recommended practice. Use weblogic.xml or application.xml to defined the context-roots.
|
|
|
BEA-101256
|
Error: The run-as user: user for the servlet: servlet for Web application: webapp could not be resolved to a valid user in the system. Verify the user exists.
|
Description
| The run-as user: user for the servlet: servlet for Web application: webapp could not be resolved to a valid user in the system. Verify the user exists.
|
|
Cause
| The run-as element in weblogic.xml refers to an invalid user.
|
|
Action
| Check to see if the user exists.
|
|
|
BEA-101257
|
Error: Failed to parse the client certificate in header: header. Ignoring this certificate.
|
Description
| Failed to parse the client certificate in header: header. Ignoring this certificate.
|
|
Cause
| The format of the client certificate was invalid.
|
|
Action
| Please check the exception for more details.
|
|
|
BEA-101258
|
Error: Invalid JSP parameter in weblogic.xml with name: name.
|
Description
| Invalid JSP parameter in weblogic.xml with name: name.
|
|
Cause
| The JSP parameter is not recognized.
|
|
Action
| Please check the weblogic.xml descriptor, and refer to the DTD for the correct syntax and element information.
|
|
|
BEA-101259(retired)
|
Warning: JSP parameter with name "name" in weblogic.xml is deprecated.
|
Description
| JSP parameter with name "name" in weblogic.xml is deprecated.
|
|
Cause
| This parameter has been deprecated.
|
|
Action
| This parameter could be removed from the future releases. Refer to the WebLogic Server documentation for alternate functionality.
|
|
|
BEA-101260
|
Error: The JSP parameter name in weblogic.xml is empty.
|
Description
| The JSP parameter name in weblogic.xml is empty.
|
|
Cause
| One of the mandatory elements in weblogic.xml was found to be empty.
|
|
Action
| Check the weblogic.xml descriptor.
|
|
|
BEA-101261
|
Error: Invalid session parameter name in weblogic.xml: name.
|
Description
| Invalid session parameter name in weblogic.xml: name.
|
|
Cause
| One of the session parameters configured in weblogic.xml was invalid.
|
|
Action
| Check the weblogic.xml; correct the session parameter.
|
|
|
BEA-101262
|
Warning: The session parameter name "name" in weblogic.xml is deprecated.
|
Description
| The session parameter name "name" in weblogic.xml is deprecated.
|
|
Cause
| This parameter has been deprecated.
|
|
Action
| See the WebLogic Server documentation for alternative. This parameter might be removed from future releases.
|
|
|
BEA-101263
|
Error: The session parameter name in weblogic.xml is empty.
|
Description
| The session parameter name in weblogic.xml is empty.
|
|
Cause
| The param-name element is a mandatory element.
|
|
Action
| Check the weblogic.xml descriptor.
|
|
|
BEA-101264
|
Error: uri: CLIENT-CERT-based authentication failed.
|
Description
| uri: CLIENT-CERT-based authentication failed.
|
|
Cause
| Authentication failed.
|
|
Action
| Either the cert was missing or the user the cert resolves to is not a valid user in the system.
|
|
|
BEA-101265(retired)
|
Error: uri: CLIENT-CERT-based authentication failed. Invalid or missing client certificate.
|
Description
| uri: CLIENT-CERT-based authentication failed. Invalid or missing client certificate.
|
|
Cause
| The Client-Cert auth type relies on receiving a valid certificate.
|
|
Action
| The cert was either missing or had an invalid format.
|
|
|
BEA-101266(retired)
|
Error: Failed to recognize HTTP log filename format: filename for Web server: httpServer.
|
Description
| Failed to recognize HTTP log filename format: filename for Web server: httpServer.
|
|
Cause
| File name has invalid format.
|
|
Action
| Check the exception for more details
|
|
|
BEA-101267
|
Error: Failed while destroying filter: s.
|
Description
| Failed while destroying filter: s.
|
|
Cause
| Failed while destroying the filter on the Web application undeploy.
|
|
Action
| There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
|
|
|
BEA-101268
|
Error: ctx: Failed while destroying servlet: s.
|
Description
| ctx: Failed while destroying servlet: s.
|
|
Cause
| Failed while destroying servlet on Web application undeploy.
|
|
Action
| There might be a problem in the implementation of the destroy method. Check the exception for the exact cause.
|
|
|
BEA-101269(retired)
|
Error: The init-as user: user for the servlet: servlet for the Web application: webapp could not be resolved to a valid user in the system. Verify the user exists.
|
Description
| The init-as user: user for the servlet: servlet for Web application: webapp could not be resolved to a valid user in the system. Check to see if the user exists.
|
|
Cause
| The init-as element in weblogic.xml refers to an invalid user.
|
|
Action
| Check to see if the user exists.
|
|
|
BEA-101270(retired)
|
Error: The destroy-as user: user for the servlet: servlet for the Web application: webapp could not be resolved to a valid user in the system. Check to see if the user exists.
|
Description
| The destroy-as user: user for the servlet: servlet for the Web application: webapp could not be resolved to a valid user in the system. Check to see if the user exists.
|
|
Cause
| The destroy-as element in weblogic.xml refers to an invalid user.
|
|
Action
| Check to see if the user exists.
|
|
|
BEA-101271
|
Error: The url-pattern element is not specified for the web-resource-collection/web-resource-name: resourceName in the web.xml descriptor.
|
Description
| The url-pattern element is not specified for the web-resource-collection/web-resource-name: resourceName in the web.xml descriptor.
|
|
Cause
| The url-pattern element is a mandatory element.
|
|
Action
| If you want the security constraint to apply for all requests, specify url-pattern=/*.
|
|
|
BEA-101272(retired)
|
Error: webapp: Dynamic Descriptor update failed, because the temporary property file: fileName was not found.
|
Description
| webapp: Dynamic Descriptor update failed, because the temporary property file: fileName was not found.
|
|
Cause
| WebLogic Server uses a temporary properties file to propogate changes to the managed servers and places them inside the WEB-INF directory.
|
|
Action
| Make sure the WEB-INF directory has write permissions.
|
|
|
BEA-101273(retired)
|
Error: webapp: Dynamic Descriptor update failed, because the temporary property file fileName was not readable.
|
Description
| webapp: Dynamic Descriptor update failed, because the temp property file fileName was not readable.
|
|
Cause
| WebLogic Server uses a temporary properties file to propogate changes to the managed servers and places them inside the WEB-INF directory.
|
|
Action
| Make sure the WEB-INF directory has write permissions
|
|
|
BEA-101274(retired)
|
Error: webapp: Property: prop was assigned a value: value, which is invalid. The correct type should be: type.
|
Description
| webapp: Property: prop was assigned a value: value, which is invalid. The correct type should be: type.
|
|
Cause
| The value assigned to the property has an invalid format.
|
|
Action
| Check the type in weblogic.management.configuration.WebAppComponentMBean.
|
|
|
BEA-101275
|
Notice: Server has detected non-replicated sessions while SUSPENDING. Server will wait for non-replicated sessions to either become invalidated or timed out or will wait until a secondary is chosen using the lazy process (meaning if a session does not have a secondary, the server waits until the next request to create the secondary). The current timeout value is timeout seconds. To terminate non-replicated sessions immediately, use the FORCESHUTDOWN option.
|
Description
| Server has detected non-replicated sessions while SUSPENDING. Server will wait for non-replicated sessions to either become invalidated or timed out or will wait until a secondary is chosen using the lazy process (meaning if a session does not have a secondary, the server waits until the next request to create the secondary). The current timeout value is timeout seconds. To terminate non-replicated sessions immediately, use the FORCESHUTDOWN option.
|
|
Cause
| During graceful shutdown, the server waits for in-flight work to complete. This includes non-replicated sessions.
|
|
Action
| No action is needed. Use FORCESHUTDOWN to ignore in-flight work and force shutdown of the server.
|
|
|
BEA-101276
|
Notice: Web application(s) webAppList still have non-replicated sessions after interval minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.
|
Description
| Web application(s) webAppList still have non-replicated sessions after interval minutes of initiating SUSPEND. Waiting for non-replicated sessions to finish.
|
|
Cause
| The server is waiting for sessions to finish before gracefully shutting down.
|
|
Action
| No action required. Use FORCESHUTDOWN to ignore in-flight work and shutdown the server.
|
|
|
BEA-101277
|
Notice: Web application(s) webAppList has countList non-replicated session(s) respectively.
|
Description
| Web application(s) webAppList has countList non-replicated session(s) respectively.
|
|
Cause
| The server has detected non-replicated sessions while gracefully shutting down.
|
|
Action
| No action is needed. Use FORCESHUTDOWN to ignore in-flight work and shutdown the server.
|
|
|
BEA-101278
|
Notice: There are no active sessions. The Web service is ready to suspend.
|
Description
| There are no active sessions. The Web service is ready to suspend.
|
|
Cause
| All active sessions have completed. The Web service is ready to gracefully shutdown.
|
|
Action
| No action is needed.
|
|
|
BEA-101279
|
Debug: app:module Removing Web application module.
|
Description
| app:module Removing Web application module. The Web application will be undeployed.
|
|
Cause
| The Web application is being undeployed.
|
|
Action
| No action required.
|
|
|
BEA-101280
|
Error: Failed to create WebServerRuntimeMBean for the Web server: name.
|
Description
| Failed to create WebServerRuntimeMBean for the Web server: name.
|
|
Cause
| The Web server creates a runtime MBean during the initialization phase for monitoring.
|
|
Action
| Check the exception for exact cause.
|
|
|
BEA-101281(retired)
|
Warning: ctx: Partial update of jarFile could not be done. The specified resource was not found in the doc root docroot.
|
Description
| ctx: Partial update of jarFile could not be done. The specified resource was not found in the doc root docroot.
|
|
Cause
| Unable to find the resource specified in the doc root.
|
|
Action
| The specified resource was not found in the doc root. Make sure that the resource is present in the application before performing the partial update.
|
|
|
BEA-101282
|
Error: ctx: jspServlet "className" defined in weblogic.xml could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.
|
Description
| ctx: jspServlet "className" could not be registered. It should be a subclass of javax.servlet.http.HttpServlet.
|
|
Cause
| The user-defined class should be a subclass of javax.servlet.http.HttpServlet.
|
|
Action
| The jspServlet class must be a subclass of javax.servlet.http.HttpServlet.
|
|
|
BEA-101283
|
Error: ctx: jspServlet "className" defined in weblogic.xml could not be loaded.
|
Description
| ctx: jspServlet "className" defined in weblogic.xml could not be loaded.
|
|
Cause
| Unable to load the user-defined class.
|
|
Action
| Make sure that the class appears in the webapp-classpath.
|
|
|
BEA-101284(retired)
|
Error: ctx: jspPrecompiler "className" defined in weblogic.xml is invalid. It must implement weblogic.servlet.internal.JSPPrecompiler.
|
Description
| ctx: jspPrecompiler "className" defined in weblogic.xml is invalid. It must implement weblogic.servlet.internal.JSPPrecompiler.
|
|
Cause
| The given class does not exist or it does not implement the weblogic.servlet.jsp.JSPPrecompiler interface.
|
|
Action
| Please make sure that the class exists and implements the weblogic.servlet.jsp.JSPPrecompiler interface.
|
|
|
BEA-101285(retired)
|
Error: Unable to bind ROIDLookupImpl into the JNDI initial context for Web server: webserver.
|
Description
| Unable to bind ROIDLookupImpl into the JNDI initial context for Web server: webserver.
|
|
Cause
| This is an unexpected error.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101286(retired)
|
Error: Unable to lookup JNDI name name for ROIDLookupImpl for the Web server: webserver.
|
Description
| Unable to lookup JNDI name name for ROIDLookupImpl for the Web server: webserver.
|
|
Cause
| This is an unexpected error.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101287
|
Error: context. The servlet: servlet received exception during servlet destroy. Make sure you call super.init(config) in the init() method.
|
Description
| context. The servlet: servlet received exception during servlet destroy. Make sure you call super.init(config) in the init() method.
|
|
Cause
| This is due to a bug in javax.servlet.GenericServlet.
|
|
Action
| Make sure you call super.init(config) in the init() method for the servlet.
|
|
|
BEA-101288
|
Error: Application:app WebAppModule: module failed to set contextPath: cp.
|
Description
| Application:app WebAppModule: module failed to set contextPath: cp.
|
|
Cause
| The set context path call failed for the MBean.
|
|
Action
| Check if the context path assigned to this Web application module is valid.
|
|
|
BEA-101289(retired)
|
Error: context: Failed to set runtime for the Web application.
|
Description
| context: Failed to set runtime for the Web application.
|
|
Cause
| Failed while trying to register the runtime MBean for the Web application.
|
|
Action
| Check the exception for more information.
|
|
|
BEA-101290(retired)
|
Error: Found invalid encoding for: file while persisting at dir: location.
|
Description
| Found invalid encoding for: file while persisting at dir: location.
|
|
Cause
| The encoding specified for the descriptor is invalid.
|
|
Action
| Correct the encoding.
|
|
|
BEA-101291
|
Error: The webAppModule: module in application: app is unable to reload classes because it shares a classloader with other modules.
|
Description
| In WebLogic Server, servlet reloading is achieved by the manipulation of classloaders. Java classloaders do not generally allow for removing or changing classes that they have loaded. Therefore, in order to reload classes, a container must reload the entire classloader into which the class was loaded. Normally, each Web application within an EAR has its own classloader. When servlets or other classes from the WAR are reloaded, this classloader is replaced with a new one. When a classloader-structure definition is given in weblogic-application.xml, it is possible that a Web application will share its classloader with other modules. In this case, automatic class reloading is disabled for the Web application.
|
|
Cause
| An attempt to reload a class was made when the classloader was shared by other modules.
|
|
Action
| Ensure that the module has its own classloader or reload all modules that share the classloader at once.
|
|
|
BEA-101292
|
Error: Validation failed for the descriptor: descriptor param: param.
|
Description
| Validation failed for the descriptor: descriptor param: param.
|
|
Cause
| The container found an illegal value assigned to this parameter.
|
|
Action
| Check the error message for the exact cause.
|
|
|
BEA-101293(retired)
|
Error: ClassCastException authenticating user for Web application: logContext.
|
Description
| ClassCastException authenticating user for Web application: logContext.
|
|
Cause
| An unexpected error occurred while authenticating the user credentials.
|
|
Action
| Check the error message for the exact cause.
|
|
|
BEA-101294(retired)
|
Error: Failed to set AuthFilter for Web application: logContext AuthFilterName: filterName
|
Description
| Failed to set AuthFilter for Web application: logContext AuthFilterName: filterName
|
|
Cause
| An unexpected error occurred while setting the AuthFilter for the Web application.
|
|
Action
| Check the error message for the exact cause.
|
|
|
BEA-101295
|
Info: Recompiling JSP [context], resource [resource], because it is stale. It was previously compiled using a different version of WebLogic Server.\n JSP build version: jspVersion\n WLS build version: wlsVersion.
|
Description
| JSPs that have been previously compiled using a different version of WebLogic Server or JSPC may be incompatible with WebLogic Server at runtime.
|
|
Cause
| JSP was compiled using a different version of WebLogic Server or JSPC.
|
|
Action
| To precompile JSPs, make sure that you precompile them using the same version, service pack, rolling patches, and temporary-patches in your classpath for WebLogic or JSPC. This will ensure the same version string and compatibility at runtime.
|
|
|
BEA-101296
|
Warning: Unable to load the default compiler class "className". Using the default javac compiler to compile JSPs.
|
Description
| The compiler class "className" could not be found.
|
|
Cause
| The compiler class was not found and hence could not be loaded.
|
|
Action
| Make sure that the class exists in the classpath.
|
|
|
BEA-101297
|
Error: The value assigned to the container-descriptor param: index-directory-sort-by in weblogic.xml is invalid: value. The valid values are "NAME", "LAST_MODIFIED", or "SIZE".
|
Description
| The value assigned to the container-descriptor param: index-directory-sort-by in weblogic.xml is invalid: value. The valid values are "NAME", "LAST_MODIFIED", or "SIZE". If none specified, it defaults to sort by "NAME"
|
|
Cause
| An invalid value is specified in weblogic.xml for the container-descriptor param: index-directory-sort-by.
|
|
Action
| Fix the values in the weblogic.xml descriptor. Valid values are "NAME", "LAST_MODIFIED", or "SIZE".
|
|
|
BEA-101298(retired)
|
Error: An exception was caught in the WebServiceImpl servlet.
|
Description
| An exception was caught in the WebServiceImpl servlet.
|
|
Cause
| An error condition was reported.
|
|
Action
| No user action required.
|
|
|
BEA-101299
|
Warning: The servlet-mapping for servlet-name "name" will override the default mapping for *.jsp. This can lead to a show code vulnerability.
|
Description
| The servlet-mapping for servlet-name "name" will override the default mapping for *.jsp. This can lead to a show code vulnerability.
|
|
Cause
| The url-pattern *.jsp is being overriden in the web.xml by a user-defined servlet.
|
|
Action
| Since the default JSP servlet will be overriden, care must be taken to ensure that JSP source code does not appear directly on the browser.
|
|
|
BEA-101300(retired)
|
Error: The local-path: localPath specified for the virtual-directory-mapping pattern in weblogic.xml for the Web application: logContext (docroot=docRoot), is not valid.
|
Description
| The local-path: localPath specified for the virtual-directory-mapping pattern in weblogic.xml for the Web application: logContext (docroot=docRoot), is not valid.
|
|
Cause
| A relative path was possibly assigned to the local-path. If so, the container makes the path relative to the doc root.
|
|
Action
| Make sure that the relative path exists with respect to the doc root.
|
|
|
BEA-101302
|
Warning: Webapp: webapp, the method role: rolename defined in the descriptor: file has not been mapped to a principal name in weblogic.xml. Will use the first principal-name: principal specified in security-role-assignment as the run-as-identity. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
|
Description
| Webapp: webapp, the method role: rolename defined in the descriptor: file has not been mapped to a principal name in weblogic.xml. Will use the first principal-name: principal specified in security-role-assignment as the run-as-identity. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
|
|
Cause
| Did not find a mapping for the run-as role in weblogic.xml.
|
|
Action
| Since the server has decided to use the implicit map, make sure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
|
|
|
BEA-101303
|
Warning: Webapp: webapp, the method role: rolename defined in the descriptor: file has not been mapped to a principal name in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for method for the servlet. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
|
Description
| Webapp: webapp, the method role: rolename defined in the descriptor: file has not been mapped to a principal name in weblogic.xml. Also there is no security-role-assignment defined for this role. Will use the rolename itself as a principal-name for method for the servlet. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
|
|
Cause
| Did not find a mapping for the run-as role in weblogic.xml.
|
|
Action
| Since the server has decided to use the implicit map, make sure that this is the principal-name you intended to use. The run-as role can be mapped to a principal name in weblogic.xml using either run-as-role-assignment element or the servlet-descriptor/run-as-principal-name.
|
|
|
BEA-101304
|
Warning: Webapp: webapp, the str1: roles defined in web.xml str2 not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.
|
Description
| Webapp: webapp, the str1: roles defined in web.xml str2 not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.
|
|
Cause
| Did not find a mapping for the roles which was supposed to be mapped to a principals in security-role-assignment in weblogic.xml.
|
|
Action
| Since the server has decided to use the implicit map, make sure that this is the principal-name you intended to use.
|
|
|
BEA-101305
|
Error: [ctx] Error-page location: "location" for the error-code: "code" causes an infinite loop condition as it throws the same code for which it has been mapped.
|
Description
| [ctx] Error-page location: "location" for the error-code: "code" causes an infinite loop condition as it throws the same code for which it has been mapped.
|
|
Cause
| The servlet for the error page, which maps to the given error code, throws the same error code. This causes an infinite loop condition.
|
|
Action
| Fix the error page
|
|
|
BEA-101306
|
Error: Could not resolve entity "id" for the webapp at: "docRoot". Check your DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
|
Description
| Could not resolve entity "id" for the webapp at: "docRoot". Check your DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
|
|
Cause
| Descriptor validation failed.
|
|
Action
| Check the DTD and make sure the descriptors comply with that. Check the exception message for more details. Also make sure there are no typos in the DOCTYPE header.
|
|
|
BEA-101307
|
Error: Got an error while resolving entity "id" for the webapp at: "docRoot". Check your DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
|
Description
| Got an error while resolving entity "id" for the webapp at: "docRoot". Check your DTD reference in the corresponding descriptor (web.xml/weblogic.xml).
|
|
Cause
| Descriptor validation failed.
|
|
Action
| Check the DTD and make sure the descriptors comply with that. Check the exception message for more details. Also make sure there are no typos in the DOCTYPE header.
|
|
|
BEA-101308
|
Debug: msg
|
Description
| Uncataloged debug message.
|
|
Cause
| This is an informational/debug message
|
|
Action
| No action is required
|
|
|
BEA-101309(retired)
|
Error: [context] could not deserialize the context attribute "name"
|
Description
| The classloader changed for the Web application but failed to deserialized the attributes using the new classloader.
|
|
Cause
| Classloader changed, when this happens, the old attributes will be deserialized using the new classloader.
|
|
Action
| Make sure the attribute class is available to the Web application scope and is serializable.
|
|
|
BEA-101310
|
Error: Web server: webserver, failed to perform batched update for replicated sessions against jndiname: name on the secondary server: host http-port: port https-port: sslport
|
Description
| Web server: webserver, failed to perform batched update for replicated sessions against jndiname: name on the secondary server: host http-port: port https-port: sslport
|
|
Cause
| The rmi call from the trigger, which was intended to periodically update the read-only replicated sessions on the secondary server, failed.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101311(retired)
|
Info: Compiling generated java class: file for jsp produced the following Java compiler output:\noutput
|
Description
| When the JSP compiler is run for a given jsp, it generates a java file. After it generates this java file, it invokes the Java compiler to compile it. The output from the Java compiler follows this log message. Most likely these will be syntax errors in the jsp file or the dependent classes are not in the webapp classloaders classpath.
|
|
Cause
| While compiling JSP generated classes, the Java compiler produced output.
|
|
Action
| Need to fix the syntax errors if any. Make sure all the required classes are in either in the WEB-INF/classes directoy, in a jar file under WEB-INF/lib or in the system classpath.
|
|
|
BEA-101312(retired)
|
Error: The VirtualHostNames for the VirtualHost: virtualHostName has been assigned a null value.
|
Description
| The VirtualHostNames for the VirtualHost: virtualHostName has been assigned a null value.
|
|
Cause
| VirtualHostNames was assigned a null value which is illegal.
|
|
Action
| The value should be a valid dnsname or a comma separated list of dnsnames. Use the administrative console to fix this problem.
|
|
|
BEA-101313(retired)
|
Warning: The webapp descriptor WEB-INF/web.xml is missing from the webapp: docroot path: path
|
Description
| The webapp descriptor WEB-INF/web.xml is missing from the webapp: docroot path: path
|
|
Cause
| Didnt find the webapp descriptor file web.xml which was supposed to be under the WEB-INF directory. Will create an empty descriptor.
|
|
Action
| It is possible that wrong source path was given for deployment as a result of which the webapp container could not locate the web.xml. Please specify correct source path if thats the case.
|
|
|
BEA-101314(retired)
|
Error: The alternative descriptor file: altdd is missing for the webapp: docroot path: path
|
Description
| The alternative descriptor file: altdd is missing for the webapp: docroot path: path
|
|
Cause
| Didnt find the alternative webapp descriptor file for the webapp. Will create an empty descriptor.
|
|
Action
| Please make sure the source path was specified correctly.
|
|
|
BEA-101315(retired)
|
Warning: The webapp descriptor WEB-INF/web.xml is missing from the webapp: warpath
|
Description
| The webapp descriptor WEB-INF/web.xml is missing from the webapp: warpath
|
|
Cause
| Didnt find the webapp descriptor file web.xml which was supposed to be under the WEB-INF directory. Will create an empty descriptor.
|
|
Action
| It is possible that wrong source path was given for deployment as a result of which the webapp container could not locate the web.xml. Please specify correct source path if thats the case.
|
|
|
BEA-101316(retired)
|
Error: The alternative descriptor file: altdd is missing for the webapp: warpath
|
Description
| The alternative descriptor file: altdd is missing for the webapp: warpath
|
|
Cause
| Didnt find the alternative webapp descriptor file for the webapp. Will create an empty descriptor.
|
|
Action
| Please make sure the source path was specified correctly.
|
|
|
BEA-101317
|
Warning: The webapp: webapp has specified "DIGEST" as the auth-method in web.xml, which is not implemented. Will default to BASIC.
|
Description
| The webapp: webapp has specified "DIGEST" as the auth-method in web.xml, which is not implemented. Will default to BASIC.
|
|
Cause
| DIGEST authentication is not implemented yet. The webapp will fallback to BASIC authentication.
|
|
Action
| Choose either BASIC, FORM or CLIENT-CERT.
|
|
|
BEA-101318
|
Error: The webapp: webapp has specified: authMethod as the auth-method in web.xml, which is not valid. Valid values are BASIC (default), FORM and CLIENT-CERT.
|
Description
| The webapp: webapp has specified: authMethod as the auth-method in web.xml, which is not valid. Valid values are BASIC (default), FORM and CLIENT-CERT.
|
|
Cause
| Invalid authentication method specified in web.xml.
|
|
Action
| The valid values are BASIC, FORM and CLIENT-CERT. Please fix the web.xml file for the webapp.
|
|
|
BEA-101319
|
Error: The webapp: webapp has "FORM" based authentication specified but the mandatory element: formLoginConfig is left blank.
|
Description
| The webapp: webapp has "FORM" based authentication specified but the mandatory element: formLoginConfig is left blank.
|
|
Cause
| form-login-page and form-error-page are mandatory elements when auth-method is "FORM"
|
|
Action
| Please fix the web.xml for the specified webapp.
|
|
|
BEA-101320
|
Debug: Administration access is configured on channel "adminName" on adminAddress:adminPort, but the request for application with contextPath: contextPath is using channel "localName" on localAddress:localPort - access will be denied. The application is either console/management application, or with specified to "true" in weblogic.xml.
|
Description
| Administration access is configured on channel "adminName" on adminAddress:adminPort, but the request for application with contextPath: contextPath is using channel "localName" on localAddress:localPort - access will be denied. The application is either console/management application, or with specified to "true" in weblogic.xml.
|
Cause
| Console/Management request or request with specified to "true"came on a non-admin channel when an admin channel was enabled.
|
Action
| Use an admin channel for management/console requests or requests with specified to "true".
| | |
|
BEA-101321(retired)
|
Error: Invalid date format for HTTP log rotation begin time: "value", expected format: "format". Server will start rotating the logs after mins minutes (specified log rotation period).
|
Description
| Invalid date format for HTTP log rotation begin time: "value", expected format: "format". Server will start rotating the logs after mins minutes (specified log rotation period).
|
|
Cause
| The specified date for HTTP log rotation begin time was not in the correct format. Expected format is: "format". The server will start the log rotation after mins minutes (LogRotationPeriodMins) instead.
|
|
Action
| Please correct the date format using the administrative console.
|
|
|
BEA-101322(retired)
|
Error: [ctx] Unsupported encoding for weblogic.http.URIDecodeEncoding: "encoding" specified. Using UTF-8
|
Description
| [ctx] Unsupported encoding for weblogic.http.URIDecodeEncoding: "encoding" specified. Using UTF-8
|
|
Cause
| The encoding specified is not supported by the underlying VM.
|
|
Action
| Please check the system property weblogic.http.URIDecodeEncoding
|
|
|
BEA-101323
|
Debug: HTTP socket connection was reset by peer.
|
Description
| HTTP socket connection was reset by peer. The client abnormally terminated the connection.
|
|
Cause
| The connection was abnormaly terminated by the client before the server could flush the complete response.
|
|
Action
| Informational message only. The server tries to squelch these socket reset exceptions if possible, because socket exception is a very common occurrence.
|
|
|
BEA-101324(retired)
|
Error: Failed to invoke the request lifecycle listener for webapp: logCtx
|
Description
| Failed to invoke the request lifecycle listener for webapp: logCtx
|
|
Cause
| Unexpected error in the user code
|
|
Action
| Please check the exception message for details.
|
|
|
BEA-101325
|
Error: The local-path: localPath specified for the virtual-directory-mapping specified in weblogic.xml for the Web application: logContext (docroot=docRoot), is not valid.
|
Description
| The local-path: localPath specified for the virtual-directory-mapping specified in weblogic.xml for the Web application: logContext (docroot=docRoot), is not valid.
|
|
Cause
| A relative path was possibly assigned to the local-path. If so, the container makes the path relative to the doc root.
|
|
Action
| Make sure that the relative path exists with respect to the doc root.
|
|
|
BEA-101326
|
Error: The element: element contains an undefined security-role: role
|
Description
| The element: element contains an undefined security-role: role
|
|
Cause
| The security-role definition is mandatory.
|
|
Action
| Make sure the security role-name is defined in web.xml. Also check the DTD and examples for the correct syntax.
|
|
|
BEA-101327
|
Error: The element: element is not allowed to appear more than once in the descriptor: descriptor
|
Description
| The element: element is not allowed to appear more than once in the descriptor: descriptor
|
|
Cause
| The parser found more than one occurrences for the element
|
|
Action
| Please make sure than the element appears only once - please check the schema
|
|
|
BEA-101328
|
Error: context: invalid dispatcher: dispatcher for filter-mapping: filter
|
Description
| context: invalid dispatcher: dispatcher for filter-mapping: filter
|
|
Cause
| Invalid value found for the dispatcher for filter mapping.
|
|
Action
| Valid values are: "REQUEST", "FORWARD", "INCLUDE" or "ERROR"
|
|
|
BEA-101329(retired)
|
Debug: Destroying default ServletContext: "name"
|
Description
| Destroying default ServletContext: "name"
|
|
Cause
| Debug Message
|
|
Action
| Debug Message
|
|
|
BEA-101330(retired)
|
Debug: Destroying ServletContext: "name"
|
Description
| Destroying ServletContext: "name"
|
|
Cause
| Debug message
|
|
Action
| No action required.
|
|
|
BEA-101331
|
Error: Cannot deploy newctx from newroot on webserver, because there is already a non-versioned Web application named origctx loaded from origroot, using the context path contextPath.
|
Description
| Cannot deploy newctx from newroot on webserver, because there is already a non-versioned Web application named origctx loaded from origroot, using the context path contextPath.
|
|
Cause
| The Web application version that is being deployed has been assigned a context path that is already in use by a non-versioned Web application.
|
|
Action
| Choose a different context path, or undeploy the conflicting Web application.
|
|
|
BEA-101332
|
Error: Failed to register JACC policy context handlers for the webapp container
|
Description
| Failed to register JACC policy context handlers for the webapp container
|
|
Cause
| Unexpected error
|
|
Action
| Please see the error message for more explanation
|
|
|
BEA-101333(retired)
|
Error: Failed to commit the JACC policy config for the webapp: logCtx
|
Description
| Failed to commit the JACC policy config for the webapp: logCtx
|
|
Cause
| Unexpected error
|
|
Action
| Please see the error message for more explanation and also check if the jacc repository is set correctly
|
|
|
BEA-101334(retired)
|
Error: Failed to refresh the JACC policy for the webapp: logCtx
|
Description
| Failed to refresh the JACC policy for the webapp: logCtx
|
|
Cause
| Unexpected error
|
|
Action
| Please see the error message for more explanation and also check if the jacc repository is set correctly
|
|
|
BEA-101335(retired)
|
Error: WebApp: logCtx, failed to link the JACC PolicyConfiguration of the module: modName
|
Description
| WebApp: logCtx, failed to link the JACC PolicyConfiguration of the module: modName
|
|
Cause
| Unexpected error while the webapp was trying to link to the PolicyConfigurations of other modules in the same application as required by the JACC (JSR-115) spec.
|
|
Action
| Please see the error message for more explanation
|
|
|
BEA-101336(retired)
|
Error: Failed to link the JACC PolicyConfiguration for the webapp: logCtx
|
Description
| Failed to link the JACC PolicyConfiguration for the webapp: logCtx
|
|
Cause
| Unexpected error while the webapp was trying to link to the PolicyConfigurations of other modules in the same application as required by the JACC (JSR-115) spec.
|
|
Action
| Please see the error message for more explanation
|
|
|
BEA-101337
|
Error: Received a SecurityException during: operation, for : uri, webapp: logCtx
|
Description
| Received a SecurityException during: operation, for : uri, webapp: logCtx
|
|
Cause
| It seems the user doesnt have enought privileges
|
|
Action
| Please see the error message for more explanation
|
|
|
BEA-101338
|
Warning: The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead use the servletMapping = "/" to define the default servlet.
|
Description
| The context parameter "weblogic.httpd.defaultServlet" has been deprecated. Instead use the servletMapping = "/" to define the default servlet.
|
|
Cause
| You are using a deprecated context param.
|
|
Action
| By default the servlet weblogic.servlet.FileServlet is the default servlet. If you want to override the default, define a new servlet-mapping in web.xml with url-pattern = "/".
|
|
|
BEA-101339
|
Warning: The context parameter: oldName has been deprecated. Instead use the element: newName in weblogic.xml.
|
Description
| The context parameter: oldName has been deprecated. Instead use the element: newName in weblogic.xml.
|
|
Cause
| You are using a deprecated context param.
|
|
Action
| Please replace it with the suggested alternative in weblogic.xml.
|
|
|
BEA-101340
|
Warning: The context parameter "weblogic.httpd.servlet.classpath" has been deprecated. Instead use manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual-directories in weblogic.xml
|
Description
| The context parameter "weblogic.httpd.servlet.classpath" has been deprecated. Please use manifest classpath or WEB-INF/lib or WEB-INF/classes or virtual-directories in weblogic.xml
|
|
Cause
| You are using a deprecated context param.
|
|
Action
| There are better way to extend the classpath exposed to the webapp classloader: eg. virtual-directories and manifest classpath.
|
|
|
BEA-101341
|
Info: app: Class file up-to-date for jsp : uri
|
Description
| app: Class file up-to-date for jsp : uri
|
|
Cause
| This message indicates that the class file associated with the jsp is up-to-date.
|
|
Action
| No action necessary.
|
|
|
BEA-101342
|
Warning: app: Error(s) encountered while pre-compiling jsp uri\n errors
|
Description
| app: Error(s) encountered while pre-compiling jsp uri\n errors.
|
|
Cause
| The jsp file shown by the error message had errors and could not be pre-compiled.
|
|
Action
| Correct the errors shown by the message so that it gets pre-compiled without errors.
|
|
|
BEA-101343
|
Info: app: Attempting to precompile uri, since the class file associated with it was found to out-of-date.
|
Description
| app: Attempting to precompile uri, since class file associated with it was found to be out-of-date.
|
|
Cause
| This message indicates that the class file associated with the given jsp was out of date and needs recompilation.
|
|
Action
| No action necessary.
|
|
|
BEA-101344
|
Info: app: Attempting to precompile uri, since the class file associated with it was not found in the webapp classpath.
|
Description
| app: Attempting to precompile uri, since the class associated with it was not found in the webapp classpath.
|
|
Cause
| This message indicates that the class file associated with the given jsp was not found in the webapp application classpath and thus needs to be compiled.
|
|
Action
| No action necessary.
|
|
|
BEA-101345
|
Warning: A change in value was detected for the "Fields" directive in access.log for webserver: webserver. Rotating the access.log. The value defined for the WebServerMBean will take precedence. Default being "time cs-method cs-uri sc-status". Old value: "old" and new value: "new".
|
Description
| A change in value was detected for the "Fields" directive in access.log for webserver: webserver. Rotating the access.log. The value defined for the WebServerMBean will take precedence. Default being "time cs-method cs-uri sc-status". Old value: "old" and new value: "new".
|
|
Cause
| This message indicates that value from WebServerMBean.getELFFields() was different that the value in the "Fields" directive on the top of access.log.
|
|
Action
| If you intended to change the ELF fields by hand editing access.log, that way is no more supported. Please change the access.log "Fields" using the Admin Console.
|
|
|
BEA-101346
|
Error: The virtual host name: name being used by the VirtualHost: webserver is already in use by: existing
|
Description
| The virtual host name: name being used by the VirtualHost: webserver is already in use by: existing
|
|
Cause
| Duplicate name usage for VirtualHostNames.
|
|
Action
| Please fix the VirtualHostNames fields for the VirtualHost and choose a unique name.
|
|
|
BEA-101347
|
Error: The server channel name (NetworkAccessPoint): name being used by the VirtualHost: webserver is already in use by: existing
|
Description
| The server channel name (NetworkAccessPoint): name being used by the VirtualHost: webserver is already in use by: existing
|
|
Cause
| Duplicate name usage for ServerChannelName for VirtualHosts.
|
|
Action
| Please fix the ServerChannelName field for the VirtualHost and choose a unique name.
|
|
|
BEA-101348
|
Error: The server channel name (NetworkAccessPoint): name being used by the VirtualHost: webserver is not defined. This virtual host will not be deployed.
|
Description
| The server channel name (NetworkAccessPoint): name being used by the VirtualHost: webserver is not defined. This virtual host will not be deployed.
|
|
Cause
| NetworkAccessPoint is not yet defined.
|
|
Action
| Please choose a different NetworkAccessPoint name or define a new one using console.
|
|
|
BEA-101349
|
Error: Failed to save the WorkContexts into the session/cache for the request: request
|
Description
| Failed to save the WorkContexts into the session/cache for the request: request
|
|
Cause
| Unexpected exception
|
|
Action
| At the end of the request the webapp container saves the WorkContexts into the session and the local cache in order to propagate them between successive http requests. Please contact support and report this problem.
|
|
|
BEA-101350
|
Notice: Web application(s) webAppList of module webAppModuleName of application appName has countList pending session(s) respectively.
|
Description
| Web application(s) webAppList of module webAppModuleName of application appName has countList pending session(s) respectively.
|
|
Cause
| The server has detected pending sessions for the webapp module while the application is gracefully transitioning from running to admin mode.
|
|
Action
| No action is needed. Use -force option to ignore in-flight work and bring the application to admin mode.
|
|
|
BEA-101351
|
Notice: Server has detected pending sessions while gracefully transitioning webapp module webAppModuleName of application appName from running to admin mode. Server will wait for pending sessions to either become invalidated or timed out. The current timeout value is timeout seconds. To terminate sessions immediately, use the -force option.
|
Description
| Server has detected pending sessions while gracefully transitioning webapp module webAppModuleName of application appName from running to admin mode. Server will wait for pending sessions to either become invalidated or timed out. The current timeout value is timeout seconds. To terminate sessions immediately, use the -force option.
|
|
Cause
| During graceful transition of the application from running to admin mode, the server waits for in-flight work to complete. This includes pending sessions.
|
|
Action
| No action is needed. Use -force to ignore in-flight work and force transition of the application from running to admin mode.
|
|
|
BEA-101352
|
Notice: There are no active sessions. The webapp module webAppModuleName of application appName is ready to go into admin mode.
|
Description
| There are no active sessions. The webapp module webAppModuleName of application appName is ready to go into admin mode.
|
|
Cause
| All active sessions have completed. The Web service is ready to gracefully transition to admin mode.
|
|
Action
| No action is needed.
|
|
|
BEA-101353(retired)
|
Error: The graceful transition of module webAppModuleName of application appName from running to admin mode failed.
|
Description
| The graceful transition of module webAppModuleName of application appName from running to admin mode failed.
|
|
Cause
| An unexpected error occurred.
|
|
Action
| Check the exception for exact error message.
|
|
|
BEA-101354
|
Notice: Web application(s) webAppList of module webAppModuleName of application appName still have pending sessions after interval minutes of initiating transition from running to admin mode. Waiting for pending sessions to finish.
|
Description
| Web application(s) webAppList of module webAppModuleName of application appName still have pending sessions after interval minutes of initiating transition from running to admin mode. Waiting for pending sessions to finish.
|
|
Cause
| The server is waiting for sessions to finish for the application before gracefully shutting down.
|
|
Action
| No action required. Use -force option to ignore in-flight work and force transition of the application into admin mode.
|
|
|
BEA-101355
|
Error: [ctx] Version version is specified for WebServices webService, but versioning of WebServices is not supported.
|
Description
| [ctx] Version version is specified for WebServices webService, but versioning of WebServices is not supported.
|
|
Cause
| Attempted to deploy WebServices with versioning.
|
|
Action
| Please deploy the WebServices (or the application containing the WebServices) without versioning.
|
|
|
BEA-101356
|
Error: WebApp: ctx failed to load the shared library (fastfile) for using nativeIO in the FileServlet, falling back to the standard IO.
|
Description
| WebApp: ctx failed to load the shared library (fastfile) for using nativeIO in the weblogic.servlet.FileServlet, falling back to the standard IO (Java).
|
|
Cause
| Unexpected error while attempting to load the native library (fastfile) for using native IO in the FileServlet.
|
|
Action
| Make sure that the shared library (fastfile) exists in a directory that is in the LD_LIBRARY_PATH or PATH. Also note that NativeIO is supported on Windows, Linux and Solaris. If problem persists, contact BEA Customer Support.
|
|
|
BEA-101357
|
Notice: A force graceful production to admin mode transition is initiated. The webapp module webAppModuleName of application appName is ready to go into admin mode.
|
Description
| A force graceful production to admin mode transition is initiated. The webapp module webAppModuleName of application appName is ready to go into admin mode.
|
|
Cause
| A force graceful production to admin mode transition is initiated. The Web service is ready to transition to admin mode.
|
|
Action
| No action is needed.
|
|
|
BEA-101358
|
Error: The message-destination 'destName' declared in the web.xml deployment descriptor of the WebApp module 'jarName', does not have a corresponding message-destination-descriptor element in the weblogic.xml descriptor.
|
Description
| Each logical message-destination declared in the web.xml deployment descriptor must have a corresponding message-destination-descriptor element in the weblogic.xml descriptor. The message-destination-descriptor maps the logical message-destination-name to the actual message destination.
|
|
Cause
| A declared message-destination is not mapped correctly.
|
|
Action
| Map the declared message-destination to the actual message destination using the message-destination-descriptor element in weblogic.xml.
|
|
|
BEA-101359
|
Error: The servlet servletClassName init method failed while it was run in the background. The exception was: th.
|
Description
| A servlet init method was marked to run in the background. This init method threw an exception.
|
|
Cause
| The servlet init method threw an exception.
|
|
Action
| The cause of the exception must be corrected, and then the application should be redeployed.
|
|
|
BEA-101360
|
Info: Recompiling JSP [context], resource [resource], because it is stale.
|
Description
| JSP is out of date, so needs to be recompiled.
|
|
Cause
| JSP was changed from the last time it was compiled.
|
|
Action
| The JSP will be always recompiled if found different from the last compiled version.
|
|
|
BEA-101361
|
Error: [context] A library reference in weblogic.xml has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1
|
Description
| [context] A library reference in weblogic.xml has an illegal Specification-Version: specVersion. The Specification-Version must be a valid version string: int(.int)*, int >=0. For example: 2.1.1
|
|
Cause
| Cannot parse the Specification-Version of a library reference in weblogic.xml
|
|
Action
| Fix the librarys Specification-Version in weblogic.xml to conform to the required version string syntax.
|
|
|
BEA-101362
|
Error: [context] could not deserialize the scope scoped attribute with name: "name"
|
Description
| The classloader changed for the Web application but failed to deserialized the attributes using the new classloader.
|
|
Cause
| Classloader changed. When this happens, the old attributes will be deserialized using the new classloader. The classloader can change either as a result of dynamic reload of classes (controlled by weblogic.xml parameter "reload-check-secs" or upon across webapp dispatch (include/forward).
|
|
Action
| Make sure the attribute class is available to the Web application scope and the attribute class and all the references it holds are serializable.
|
|
|
BEA-101363
|
Info: Application: app, WebApp: webapp has context-root specified in application.xml: "appCP". The context-root specified in weblogic.xml: "cp" will be ignored.
|
Description
| Application: app, WebApp: webapp has context-root specified in application.xml: "appCP". The context-root specified in weblogic.xml: "cp" will be ignored.
|
|
Cause
| The context-root specified in application.xml takes higher precedence than the one in weblogic.xml.
|
|
Action
| This is just an info message. Please make sure this is what you intended to do.
|
|
|
BEA-101364
|
Warning: app:module Failure while Precompiling JSP: jspFile.
|
Description
| app:module Failure while Precompiling JSP: jspFile.
|
|
Cause
| Failed to precompile JSP on partial update.
|
|
Action
| Please check the exception for the exact cause.
|
|
|
BEA-101365(retired)
|
Info: CompleteMessageTimeout has been set for HTTP Messages.
|
Description
| CompleteMessageTimeout has been set for HTTP Messages.
|
|
Cause
| Information Message.
|
|
Action
| No Action Required.
|
|
|
BEA-101366
|
Info: The server could not send the HTTP message during the configured timeout value. The socket has been closed.
|
Description
| The server could not send the HTTP message during the configured timeout value. The socket has been closed.
|
|
Cause
| Information Message.
|
|
Action
| Please bump up the value of CompleteMessageTimeout. The default is 60 sec. If you have slow clients that cannot complete the messsage transfer and are getting timed out raise the value.
|
|
|
BEA-101367
|
Error: Error occurred while extracting archived file for "context", located at "path".
|
Description
| Error occurred while extracting archived file for "context", located at "path".
|
|
Cause
| An error occurred while extracting the archived war file, due to path length limitations on some OSs
|
|
Action
| Some OSs only allow a certain number of characters in the file name. This limitation can be noticed when extracting an archive in a deeply nested directory. Since the default temporary directory for extracting all archives is relative to the server root directory, it is recommended that one use the System property weblogic.j2ee.application.tmpDir and set it to a shorter file path. OR one could ensure that the server is started in a directory with a shorted file path.
|
|
|
BEA-101368(retired)
|
Warning: The URL pattern : pattern has a pre-existing stub : existingStub . Hence the new stub : newStub will be destroyed.
|
Description
| The URL pattern : pattern has a pre-existing stub : existingStub . Hence the new stub : newStub will be destroyed.
|
|
Cause
| JSPServlet tried to generate the stub for same JSP more than once.
|
|
Action
| The application logic need to be verified. Please contact support and report this problem.
|
|
|
BEA-101369
|
Warning: context: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
|
Description
| context: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
|
|
Cause
| context: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
|
|
Action
| context: The encoding jsp-descriptor param has been deprecated. Consider declaring the encoding in the jsp-config element (web.xml) or as a page directive (pageEncoding) instead.
|
|
|
BEA-101370
|
Error: There was a failure when merging library descriptors into the application descriptors for application context. Please make sure that the descriptors are valid. The error is message
|
Description
| There was a failure when merging library descriptors into the application descriptors for application context. Please make sure that the descriptors are valid. The error is message
|
|
Cause
| The library or the application descriptors are invalid.
|
|
Action
| Fix the descriptors in application or the library.
|
|
|
BEA-101371
|
Error: There was a failure when processing annotations for application context. Please make sure that the annotations are valid. The error is message
|
Description
| There was a failure when processing annotations for application context. Please make sure that the annotations are valid. The error is message
|
|
Cause
| The descriptor has an invalid servlet-class, filter-class or listener-class
|
|
Action
| Fix the descriptors in application or the library.
|
|
|
BEA-101372
|
Warning: There was a failure in application context when attempting to inject dependencies into class. Dependencies will not be injected into this class.
|
Description
| There was a failure in application context when attempting to inject dependencies into class. Dependencies will not be injected into this class.
|
|
Cause
| The annotations defined in the class may be invalid or the descriptor may be having conflicting entries.
|
|
Action
| Please check the annotations defined in this class. Also verify if the descriptor has valid entries.
|
|
|
BEA-101373
|
Warning: Reloading classes in application context failed due to change of annotations on a refreshed class. Modified or new annotations will not be processed during Servlet reload as they involve a non-dynamic change. Please redeploy the application for these annotations to be processed.
|
Description
| Reloading classes in application context failed due to change of annotations on the refreshed class. Modified or new annotations will not be processed during reload.
|
|
Cause
| New or modified annotations will not be processed in application context due to Servlet refresh.
|
|
Action
| Redeploy the application for reloading classes when annotations are modified.
|
|
|
BEA-101374
|
Warning: The web container failed to lookup transaction associated with the current thread for webapp: $context.
|
Description
| The web container failed to lookup transaction associated with the current thread for webapp: $context.
|
|
Cause
| After the response is sent, the container needs to check if there is any active transaction associated with the thread so that it can abort the transaction. See exception message for more details.
|
|
Action
| See exception message for more details.
|
|
|
BEA-101375
|
Warning: [ctx]: Error while parsing the JSF Faces Config Descriptor at "location".
|
Description
| [ctx]: Error while parsing the JSF Faces Config Descriptor at "location".
|
|
Cause
| JSF Faces Config Descriptor parsing exception occurred.
|
|
Action
| Check the exception for the exact cause.
|
|
|
BEA-101376
|
Warning: Unable to purge cache of Bean classes from BeanELResolver, error occurs at "t".
|
Description
| Unable to purge cache of Bean classes from BeanELResolver, error occurs at "t".
|
|
Cause
| Unable to get cache property of BeanELResolver.
|
|
Action
| Please contact support and report this problem.
|
| |
