The WliSbTransports catalog contains messages in the range
BEA381300 - BEA381399. Messages in this catalog are part of the
com.bea.wli.sb.transports Internationalization package and the
com.bea.wli.sb.transports Localization package.
|
BEA-381303
|
Warning: No response meta data was set. Will assume OK response code
|
Description
| While preparing the response to HTTP proxy, no response metadata was given to the proxy by OSB pipeline. As a result, the HTTP proxy will assume successful completion of the request and send HTTP OK (200) status code back to the client |
|
Action
| No action is necessary |
|
|
BEA-381304
|
Error: Exception in method: e
|
Description
| An unexpected exception has occurred in OSB HTTP transport. There should be an error message that points to cause of the problem |
|
Action
| Contact technical support |
|
|
BEA-381307
|
Warning: Ignoring destroy errors cause
|
Description
| A non-fatal internal error has occured while registering or unregisterering artifacts for HTTP proxy service. There should be an error message that points to the cause of the problem. The error will be ignored |
|
Action
| No action is necessary |
|
|
BEA-381308
|
Warning: Ignoring unprepare errors cause
|
Description
| A non-fatal internal error has occured while registering or unregisterering artifacts for HTTP proxy service. There should be an error message that points to the cause of the problem. The error will be ignored |
|
Action
| No action is necessary |
|
|
BEA-381309
|
Warning: Ignoring deactivate errors cause
|
Description
| A non-fatal internal error has occured while registering or unregisterering artifacts for HTTP proxy service. There should be an error message that points to the cause of the problem. The error will be ignored |
|
Action
| No action is necessary |
|
|
BEA-381310
|
Warning: Ignoring force production to admin errors cause
|
Description
| A non-fatal internal error has occured while registering or unregisterering artifacts for HTTP proxy service. There should be an error message that points to the cause of the problem. The error will be ignored |
|
Action
| No action is necessary |
|
|
BEA-381311
|
Warning: Ignoring remove errors cause
|
Description
| A non-fatal internal error has occured while registering or unregisterering artifacts for HTTP proxy service. There should be an error message that points to the cause of the problem. The error will be ignored |
|
Action
| No action is necessary |
|
|
BEA-381316
|
Error: X.509 token identity assertion is not enabled in the security realm
|
Description
| An identity asserter with X.509 token support enabled is required because HTTPS inbound endpoint inboundEndpoint specifies CLIENT-CERT authentication |
|
Action
| Enable X.509 identity assertion in your Identity Assertion provider in the security realm pages of the WebLogic Server console |
|
|
BEA-381317
|
Error: The X.509 username-mapper sub-plugin of the default identity asserter in not configured
|
Description
| HTTPS inbound endpoint inboundEndpoint specifies CLIENT-CERT authentication, therefore the username mapper properties of the default identity asserter must be configured (this is required to support 2-way SSL) |
|
Action
| Configure the username-mapper fields of the Default Identity Assertion provider in the security realm pages of the WebLogic Server console |
|
|
BEA-381318
|
Error: URI uri for this proxy service is already used by another proxy service: other
|
Description
| An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service is already used by another HTTP proxy service or WS proxy service. Each HTTP proxy service has to have a unique URI. |
|
Action
| Check the transport configuration for HTTP proxy service and make sure that unique value for the URI is used. |
|
|
BEA-381319
|
Error: HTTP business service URLs must start with either http:// or https:// and have a hostname
|
Description
| An error had occured while registering a new HTTP business service: One of the URLs configured for the business service is invalid. According to RFC 2616, HTTP urls must start with http:// and have a hostname |
|
Action
| Check the transport configuration for HTTP business service and make sure that a valid URL is being entered |
|
|
BEA-381320
|
Error: Cannot create an inbound HTTP endpoint with absolute URI uri
|
Description
| An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service is an absolute URI. Only relative URIs are supported for HTTP proxy services. |
|
Action
| Check the transport configuration for HTTP proxy service and make sure that only a relative URI (e.g. "/someName") is used. |
|
|
BEA-381321
|
Error: URI uri for this proxy service is already used by OSB Kernel application
|
Description
| An error had occured while registering a new HTTP proxy service: The URI configured for this proxy service "/" is already used internal OSB Kernel application. |
|
Action
| Check the transport configuration for HTTP proxy service and make sure that a different unique value is used for the URI of this proxy |
|
|
BEA-381322
|
Error: Failed to add a header named headerName: HTTP headers need to be string, instead className was found
|
Description
| There was a problem while setting specified header name/value pair in outbound HTTP request or inbound response. HTTP transport only allows String header values while another data type was given. One way it could happen is when using transport header action to pass all transport headers through from one transport that supports non-String headers, such as JMS, to HTTP transport |
|
Action
| Check the pipeline configuration to make sure only Strings are used to set transport header values of HTTP outbound request or inbound response |
|
|
BEA-381323
|
Error: SSL client authentication is not allowed over plain-text HTTP
|
Description
| The proxy service is configured for client-certificate authentication but it is not an https endpoint. Client-certificate authentication is only allowed over https endpoints |
|
Action
| Set the https-required flag to true in the transport configuration page |
|
|
BEA-381324
|
Error: Invalid http transport-level authentication configuration: custom token authentication is not supported on business services
|
Description
| The HTTP transport configuration of this outbound endpoint specifies custom-token authentication. This is not supported in this Oracle Service Bus release |
|
Action
| Change the authentication method in the endpoint configuration page |
|
|
BEA-381325
|
Warning: Invalid http transport-level custom token authentication configuration: invalid token type
|
Description
| This endpoint is configured with transport-level custom token authentication for tokens of type "tokenType". There is no Identity Assertion Provider for this token type or the token type has not been activated |
|
Action
| Go to the security realm pages in the WebLogic Server console to make sure your security realm has an Identity Assertion Provider which supports tokens of type "tokenType"; also make sure the token type is in the providers list of enabled tokens |
|
|
BEA-381326
|
Error: Invalid http transport-level custom token authentication configuration: header name has not been specified
|
Description
| Transport-level custom token authentication requires you to specify the name of the HTTP header that will carry the token |
|
Action
| Edit the http endpoint configuration details and specify the name of the custom token http header |
|
|
BEA-381327
|
Error: Transport-level custom token identity assertion failed
|
|
BEA-381328
|
Error: Inbound http BASIC authentication failed
|
|
BEA-381329
|
Error: Inbound SSL client certificate authentication failed
|
|
BEA-381330
|
Error: Outbound HTTP request resulted in failure due to code : msg. Request will be retried
|
|
BEA-381331
|
Error: A token-type must be configured when using custom token authentication
|
Description
| The endpoint is configured for custom token authentication. A token-type must be specified |
|
Cause
| The token-type is null or empty |
|
Action
| In the HTTP transport-specific configuration page, choose a token-type from the drop-down list or select a different authentication method |
|
|
BEA-381332
|
Error: The name of the HTTP header which carries the custom token must be specified
|
Description
| The endpoint is configured for custom token authentication. The name of the HTTP header which carries the custom token must be specified |
|
Cause
| The header-name is null or empty |
|
Action
| In the HTTP transport-specific configuration page, enter the name of the HTTP header or select a different authentication method |
|
|
BEA-381333
|
Error: HTTP method "GET" is only allowed for Service Type any xml or messaging type with none as the request type.
|
Action
| Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered. |
|
|
BEA-381334
|
Error: HTTP methods "PUT" and "DELETE" are only allowed for Service Type any xml or messaging type.
|
Action
| Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered. |
|
|
BEA-381335
|
Error: HTTP method "HEAD" is only allowed for Service Type any xml or messaging type with none as the response type.
|
Action
| Check the transport configuration for HTTP business service and make sure that a valid HTTP method name is being entered. |
|
|
BEA-381336
|
Error: HTTP business service has no URIs configured.
|
Action
| Check the transport configuration for HTTP business service and make sure that URI set should not be empty. |
|
|
BEA-381337
|
Error: HTTP business service cannot have both ''chunked streaming mode'' and ''follow HTTP redirects'' options enabled.
|
Action
| Check the transport configuration for HTTP business service and make sure that both ''chunked streaming mode'' and ''follow HTTP redirects'' options are not enabled. |
|