The WebService1.0 catalog contains messages in the range
BEA220000 - BEA229999. Messages in this catalog are part of the
weblogic.webservice
Internationalization package and the weblogic.i18n
Localization package.
BEA-220000
|
Info: WebService Startup.
Description
| The WebService subsystem has sucessfully started. |
Cause
| This is a normal operation. |
Action
| No action required. |
|
BEA-220001
|
Emergency: The server at url did not provide a valid HTTP response: msg
Description
| An IOException is thrown indicating an invalid HTTP response was provided. |
Cause
| The server may not be properly configured. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220002
|
Emergency: The server at url did not provide a valid HTTP response: msg
Description
| An IOException was thrown indicating an invalid HTTP response was provided. |
Cause
| The HTTP header status length does not agree. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220003
|
Emergency: The server at url did not provide a valid HTTP response: msg
Description
| An IOException was thrown indicating an invalid HTTP response was provided. |
Cause
| The server is not providing HTTP V1.0 or V1.1 protocol. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220004
|
Emergency: The server at url did not provide a valid HTTP response: msg
Description
| An IOException is thrown indicating an invalid HTTP response was provided. |
Cause
| The server status code returned was not recognized. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220005
|
Emergency: The server at url did not provide a valid HTTP response: msg.
Description
| An IOException was thrown indicating an invalid HTTP response was provided. |
Cause
| The server status code was given. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220006
|
Emergency: Content-Length was speified but no value was provided.
Description
| An IOException was thrown indicating an invalid HTTP response was provided. |
Cause
| The content length field must provide a value. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220007
|
Emergency: The specified Content-Length length is invalid.
Description
| An IOException was thrown indicating an invalid HTTP response was provided. |
Cause
| The content length field provided is invalid. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220008
|
Emergency: HTTP Keep-alive was specified, but the Content-Length was not set.
Description
| An IOException was thrown indicating an invalid HTTP response was provided. |
Cause
| The content length field provided is invalid. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220009
|
Emergency: Received EOF before reading the entire message from server.
Description
| An IOException is thrown indicating an invalid HTTP response was provided. |
Cause
| The server sent an EOF before the entire message was received. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220010
|
Emergency: A MIME encoded SOAP response must include a Content-Type MimeHeader specifying the MIME start and boundary.
Description
| A SOAPexception was thrown indicating an invalid HTTP header was provided. |
Cause
| The content length was zero or the content-type was null. However, an attachment was provided. |
Action
| Verify the server configuration and retry the request. |
|
BEA-220011
|
Warning: A bad value was provided for property : value. The default value will be used: defaultValue.
Description
| The system property property was not a valid number. |
Cause
| The value was not correctly provided. |
Action
| Correct the system configuration and retry the request. |
|
BEA-220012
|
Emergency: The ID may not be null.
Description
| Adding a reference, the ID was found to be null. This value must be provided. |
Cause
| The XML stream may be corrupted. |
Action
| Check the content of the XML stream and retry the message. |
|
BEA-220013
|
Emergency: The ID referenced by idref is unknown.
Description
| The XML stream has a reference to an unknown ID. |
Cause
| The XML stream is invalid or corrupted. |
Action
| Correct unknown ID must be resolved and activity retried. |
|
BEA-220014
|
Emergency: Incorrect XML stream open. Use open(XMLNode node) to open this stream.
Description
| This XML stream was improperly opened. |
Cause
| The module was incorrectly called. |
Action
| The program must be corrected to use XMLNode and then activity retried. |
|
BEA-220015
|
Emergency: Incorrect XML stream open. Use open(XMLNode node) to open this stream.
Description
| This XML stream was improperly opened. |
Cause
| The module was incorrectly called. |
Action
| The program must be corrected to use XMLNode and then activity retried. |
|
BEA-220016
|
Emergency: The start element was not found.
Description
| The XML stream parser could not find the start element. |
Cause
| The XML stream is corrupted. |
Action
| Correct the XML stream and retry the task. |
|
BEA-220017
|
Emergency: Element element is not a start element.
Description
| The start element was not found. |
Cause
| The XML stream is corrupted. |
Action
| Correct the XML stream and retry the task. |
|
BEA-220018
|
Info: The handler class:hClass threw an exception from its destroy method. This exception is ignored. The exception was: msg.
Description
| The handler class threw an exception from its destroy method. |
Cause
| A handler class threw an exception from its destroy method. |
Action
| Correct the handler Handler.destroy implementation. |
|
BEA-220019
|
Info: The Web Services server responded with an empty HTTP response. The Content-Length of the response was 0.
Description
| The HTTP response had a Content-Length of 0. |
Cause
| The HTTP response had a Content-Length of 0. |
|
BEA-220020
|
Info: The Web Services call to protocol://h:port received an unexpected end of file (EOF) after reading nr bytes.
Description
| The HTTP response had an unexpected EOF. |
Cause
| The HTTP response had an unexpected EOF. |
|
BEA-220021
|
Info: The Web Services call to url received an unexpected HTTP version major.minor in the response:msg.
Description
| The HTTP response had an unexpected version. |
Cause
| The HTTP response had an unexpected version. |
|
BEA-220022
|
Info: Error reading the response from: url. Please ensure that this is a valid SOAP response. The message was: \n\nmsg
Description
| The HTTP response had an unexpected version. |
Cause
| The HTTP response had an unexpected version. |
|
BEA-220023
|
Info: Ignoring an exception in destroy() from Handler: className. The exception was:\nth.
Description
| Exception in handler destroy() method. |
Cause
| Exception in handler destroy() method. |
|
BEA-220024
|
Info: Handler className threw an exception from its handleRequest method. The exception was:\nth.
Description
| Exception in handler handleRequest() method. |
Cause
| Exception in handler handleRequest() method. |
|
BEA-220025
|
Info: Handler className threw an exception from its handleResponse method. The exception was:\nth.
Description
| Exception in handler handleResponse() method. |
Cause
| Exception in handler handleResponse() method. |
|
BEA-220026
|
Info: Handler className threw an exception from its handleFault method. The exception was:\nth.
Description
| Exception in handler handleFault() method. |
Cause
| Exception in handler handleFault() method. |
|
BEA-220027
|
Info: Web Service reliable agents are started on the server.
Description
| Web Service reliable agents are started on the server. |
Cause
| Web Service reliable agents are started on the server. |
Action
| No action required. |
|
BEA-220028
|
Info: Web Service reliable agents are suspended.
Description
| Web Service reliable agents are suspended. |
Cause
| Web Service reliable agents are suspended. |
Action
| No action required. |
|
BEA-220029
|
Info: Web Service reliable agents are shut down.
Description
| Web Service reliable agents are shut down. |
Cause
| Web Service reliable agents are shut down. |
Action
| No action required. |
|
BEA-220030
|
Error: Failed to create Web Service reliable agents. e.
Description
| Failed to create Web Service reliable agents. |
Cause
| Configuration error or admin server failure. |
Action
| Check configuration. |
|
BEA-220031
|
Info: The server does not support reliable SOAP messaging.
Description
| The server does not support reliable SOAP messaging. |
Cause
| The server does not support reliable SOAP messaging. |
Action
| Check configuration. |
|
BEA-220032
|
Error: Failed to create MessageContext after a SOAP message is recovered from the storage. e.
Description
| Failed to create MessageContext after a SOAP message is recovered from the storage. This Web Service request may not be delivered. |
Cause
| Invalid format from the store or error accessing the store. |
Action
| Contact BEA customer support. |
|
BEA-220033
|
Error: Failed to access the store for reliable delivery. e.
Description
| Failed to access the store for reliable delivery. The reliable delivery agent cannot start working. |
Cause
| Failure accessing JMS. |
Action
| Contact BEA customer support. |
|
BEA-220034
|
Info: A stack trace associated with message id follows: \n
Description
| A stack trace for a previously logged message. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220035
|
Info: A naming exception was thrown while obtaining the intial context.
Description
| A naming exception was thrown while obtaining the intial context. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220036
|
Info: A exception was thrown while obtaining the JMS connection factory.
Description
| A exception was thrown while obtaining the JMS connection factory. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220037
|
Info: A exception was thrown while obtaining the JMS initial context.
Description
| A exception was thrown while obtaining the JMS initial context. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220038
|
Info: A exception was thrown from the onMessage JMS.
Description
| A exception was thrown from the onMessage JMS. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220039
|
Info: A naming exception was thrown from the JMS send message.
Description
| A naming exception was thrown from the JMS send message. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220040
|
Info: A exception was thrown from JMS obtaining the initial factory.
Description
| A exception was thrown from JMS obtaining the initial factory. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220041
|
Info: A exception was thrown from JMS sending to the destination.
Description
| A exception was thrown from JMS sending to the destination. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220042
|
Info: A naming exception was thrown from JMS for this queue.
Description
| A naming exception was thrown from JMS for this queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220043
|
Info: An exception was thrown from JMS obtaining the factory.
Description
| An exception was thrown from JMS obtaining the factory. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220044
|
Info: A exception was thrown from JMS locating this queue.
Description
| A exception was thrown from JMS locating this queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220045
|
Info: A exception was thrown getting the conversational state.
Description
| A exception was thrown getting the conversational state. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220046
|
Info: A remote exception was thrown getting the conversational state.
Description
| A remote exception was thrown getting the conversational state. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220047
|
Info: A exception was thrown from callReceive in the Client Dispatcher.
Description
| A exception was thrown from callReceive in the Client Dispatcher. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220048
|
Info: A exception was thrown from the client handler sending a JAXM message.
Description
| A exception was thrown from the client handler sending a JAXM message. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220049
|
Info: A SOAP exception was thrown from the client conversation handler.
Description
| A SOAP exception was thrown from the client conversation handler. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220050
|
Info: A SOAP exception was thrown from the server conversation handler.
Description
| A SOAP exception was thrown from the server conversation handler. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220051
|
Info: A SOAP exception was thrown from the Invoke handler.
Description
| A SOAP exception was thrown from the Invoke handler. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220052
|
Info: The target endpoint is a malformed URL.
Description
| The target endpoint is a malformed URL. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220053
|
Info: An unexpected exception was caught in the SOAP Envelope InputStream.
Description
| An unexpected exception was caught in the SOAP Envelope InputStream. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220054
|
Info: An unexpected exception was caught in the SOAP Envelope Reader.
Description
| An unexpected exception was caught in the SOAP Envelope Reader. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220055
|
Info: A parse exception was caught in the SOAP Message content.
Description
| A parse exception was caught in the SOAP Message content. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220056
|
Info: A parse exception was caught in the get SOAP Message content.
Description
| A parse exception was caught in the get SOAP Message content. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220057
|
Info: A messaging exception was caught processing MIME SOAP Message content.
Description
| A messaging exception was caught processing MIME SOAP Message content. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220058
|
Info: A messaging exception was caught writing MIME SOAP Message content.
Description
| A messaging exception was caught writing MIME SOAP Message content. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220059
|
Info: A SOAP header exception was caught in setMustUnderstand.
Description
| A SOAP header exception was caught in setMustUnderstand. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220060
|
Info: A SOAP header exception was caught in setActor.
Description
| A SOAP header exception was caught in setActor. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220061
|
Info: A Naming Exception was caught in the deployment descriptor verify.
Description
| A Naming Exception was caught in the deployment descriptor verify. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220062
|
Info: A Message Exception was caught in the Image Encoding Codec.
Description
| A Message Exception was caught in the Image Encoding Codec. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220063
|
Info: A IO Exception was caught in the Image Encoding Codec.
Description
| A IO Exception was caught in the Image Encoding Codec. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220064
|
Info: A Message Exception was caught in the XML Source Encoding Codec.
Description
| A Message Exception was caught in the XML Source Encoding Codec. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220065
|
Info: A IO Exception was caught in the XML Source Encoding Codec.
Description
| A IO Exception was caught in the XML Source Encoding Codec. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220066
|
Info: An InvalidAttributeValue Exception was caught trying to create the JMS Queue.
Description
| An InvalidAttributeValue Exception was caught trying to create the JMS Queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220067
|
Info: A JMS Exception was caught when the listener was being closed.
Description
| A JMS Exception was caught when the listener was being closed. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220068
|
Info: A Exception was caught when introspecting the component.
Description
| A Exception was caught when introspecting the component. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220069
|
Info: A Naming Exception was caught trying to locate the JMS transport.
Description
| A Naming Exception was caught trying to locate the JMS transport. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220070
|
Info: A JMS Exception was caught trying to create the JMS queue.
Description
| A JMS Exception was caught trying to create the JMS queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220071
|
Info: A SOAPException was caught in the onMessage listening to the JMS queue.
Description
| A SOAPException was caught in the onMessage listening to the JMS queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220072
|
Info: An IOException was caught in the onMessage listening to the JMS queue.
Description
| An IOException was caught in the onMessage listening to the JMS queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220073
|
Info: A SOAPException was caught in the servlet base unable to invoke the service.
Description
| A SOAPException was caught in the servlet base unable to invoke the service. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220074
|
Info: A SOAPException was caught in the servlet base unable to send to the client.
Description
| A SOAPException was caught in the servlet base unable to send to the client. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220075
|
Info: A SOAPException was caught in the servlet base unauthorized to send to the client.
Description
| A SOAPException was caught in the servlet base unauthorized to send to the client. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220076
|
Info: An Exception was caught in the Web Service servlet initialization.
Description
| An Exception was caught in the Web Service servlet initialization. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220077
|
Info: An Exception was caught in processing the Web Service deployment descriptor.
Description
| An Exception was caught in processing the Web Service deployment descriptor. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220078
|
Info: An Exception was caught in configuration of the Web Service servlet.
Description
| An Exception was caught in configuration of the Web Service servlet. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220079
|
Info: An Interrupt Exception was caught waiting to send Mail from the queue.
Description
| An Interrupt Exception was caught waiting to send Mail from the queue. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220080
|
Info: An error was reported from the SMTP Gateway.
Description
| An error was reported from the SMTP Gateway. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220081
|
Info: An IOException was reported from the SMTP quit command.
Description
| An IOException was reported from the SMTP quit command. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220082
|
Info: An IOException was reported from the SMTP process read command.
Description
| An IOException was reported from the SMTP process read command. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220083
|
Info: An IOException was reported from the SMTP process close command.
Description
| An IOException was reported from the SMTP process close command. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220084
|
Info: A Binding Exception was thrown while trying to generate the implementation class.
Description
| A Binding Exception was thrown while trying to generate the implementation class. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220085
|
Info: A JAXRPC Exception was thrown while trying to generate the implementation class.
Description
| A JAXRPC Exception was thrown while trying to generate the implementation class. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220086
|
Info: A IOException was thrown while trying to generate the implementation class.
Description
| A IOException was thrown while trying to generate the implementation class. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220087
|
Info: A Binding Exception was thrown while trying to generate the EJB implementation.
Description
| A Binding Exception was thrown while trying to generate the EJB implementation. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220088
|
Info: A JAXRPC Exception was thrown while trying to generate the EJB implementation.
Description
| A JAXRPC Exception was thrown while trying to generate the EJB implementation. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220089
|
Info: A IOException was thrown while trying to generate the EJB implementation.
Description
| A IOException was thrown while trying to generate the EJB implementation. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220090
|
Info: A Binding Exception was thrown while trying to generate the client implementation.
Description
| A Binding Exception was thrown while trying to generate the client implementation. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220091
|
Info: A JAXRPC Exception was thrown while trying to generate the client implementation.
Description
| A JAXRPC Exception was thrown while trying to generate the client implementation. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220092
|
Info: A IOException was thrown while trying to generate the client implementation.
Description
| A IOException was thrown while trying to generate the client implementation. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220093
|
Info: A naming exception was thrown while trying to check compliance of the given EJB.
Description
| A naming exception was thrown while trying to check compliance of the given EJB. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220094
|
Info: An IOException was thrown trying to access the WSDL at the given URL.
Description
| An IOException was thrown trying to access the WSDL at the given URL. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220095
|
Info: An IOException was thrown converting the file to a string.
Description
| An IOException was thrown converting the file to a string. |
Cause
| An error condition was reported. |
Action
| No user action required. |
|
BEA-220096
|
Info: A naming exception was thrown from JMS for this queue.
Description
| A naming exception was thrown from JMS for this queue. |
Cause
| An error condition was reported. |
Action
| Make sure that the queue can be accessed from this server. |
|
BEA-220097
|
Info: An exception was thrown from JMS obtaining the factory.
Description
| An exception was thrown from JMS obtaining the factory. |
Cause
| An error condition was reported. |
Action
| Make sure that the queue can be accessed from this server. |
|
BEA-220098
|
Info: An exception was thrown from JMS locating this queue.
Description
| An exception was thrown from JMS locating this queue. |
Cause
| An error condition was reported. |
Action
| Make sure that the queue can be accessed from this server. |
|
BEA-220099
|
Info: Webservice for webapp named war contextPath uri with webservices ws has been initialized.
Description
| Webservice for webapp named war contextPath uri with webservices ws has been initialized. |
Cause
| A successful webservice deployment |
Action
| No action required. |
|
BEA-220100
|
Warning: An error occurred while registering this webservice for monitoring. Though this does not affect the Webservice itself, monitoring information about it may be unavailable.
Description
| An error occurred while registering this webservice for monitoring. Though this does not affect the Webservice itself, monitoring information about it may be unavailable. |
Cause
| An error condition was reported. |
Action
| No action required. |
|
BEA-220101
|
Error: An Error occurred while loading class className from handler-chain handler in global handler configuration. Error is: e
Description
| An Error occurred while loading class className from handler handler in global handler configuration. Error is: e |
Cause
| The configured class is not present in the classpath. |
Action
| Please check the classpath and try again. |
|
BEA-220102
|
Error: An Error occurred while loading global handler chain. Error is: e
Description
| An Error occurred while loading global handler chain. Error is: e |
Cause
| There might be an error occurred while parsing the server-handler-chain.xml file. |
Action
| Please check the server-handler-chain.xml file and make sure the syntax is correct. |
|