Oracle® Fusion Middleware Messages for Oracle Service Bus
11g Release 1 (11.1.1.7)

E15034-09

Back to Index Page


WliSbTransports Subsystem Messages

The WliSbTransports catalog contains messages in the range BEA381400 - BEA381449. 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-381401

Error: Exception in method: e

Description

An unexpected general purpose exception has occurred in OSB WS transport. There should be an error message that points to the cause of the problem.

Action

Contact technical support.

BEA-381403

Warning: No Error destination is configured for WS business service: refName

Description

No error queue destination is configured for this business service. If the failed messages to be put into the desired queue, please configure the error queue destination in the business service.

BEA-381404

Error: One or more endpoint URLs in this WS transport business service are plain HTTP URLs but policy requires the HTTPS protocol

Description

This endpoint's policy requires HTTPS access. All URLs in this endpoint must use the HTTPS protocol

Action

Edit the endpoint URLs to make sure all URLs use the HTTPS protocol

BEA-381405

Error: URI uri for this proxy service is already used by OSB Kernel application

Description

An error had occured while registering a new WS proxy service: The URI configured for this proxy service "/" is already used by internal OSB Kernel application.

Action

Check the transport configuration for WS proxy service and make sure that a different unique value is used for the URI of this proxy.

BEA-381406

Error: Cannot create an inbound WS endpoint with absolute URI uri

Description

An error had occured while registering a new WS proxy service: The URI configured for this proxy service is an absolute URI. Only relative URIs are supported for WS proxy services.

Action

Check the transport configuration for WS proxy service and make sure that only a relative URI (e.g. "/foo") is used.

BEA-381407

Error: URI uri for this proxy service is already used by another proxy service: other

Description

An error had occured while registering a new WS proxy service: The URI configured for this proxy service is already used by another WS proxy service or HTTP proxy service. Each WS proxy service has to have a unique URI.

Action

Check the transport configuration for WS proxy service and make sure that unique value for the URI is used.

BEA-381408

Error: WS business service should always have absolute URI. Given URI is not absolute: uri

Description

WS business service should have absolute URIs.

Action

Change the WS business service configuration and make sure that all the URIs should be absolute.

BEA-381409

Error: WS outbound services can only have http and https schemes. Given URI has invalid scheme:uri

Description

An error occurred while registering new WS business service: WS business services can only have http and https schemes.

Action

Change the scheme of the WS business service to http or https.

BEA-381410

Error: The ws-policy of the WS business service requirest HTTPS BASIC authentication but no service account has been configured

Description

An HTTPS BASIC authentication policy requires the endpoint to send a username/password when connecting to the back-end service. A service account specifies how to get the username/password and allows the endpoint to get the username/password. This endpoint is configured for outbound HTTPS BASIC authentication but the service account reference is null.

Action

Configure a service account reference in the endpoint configuration page.

BEA-381411

Error: An entry with key:mappingId is timed out in WsCorrelationTable.

Description

While invoking a WS business service, a response to a WS request did not arrive in before the specified response timeout occurred.

Action

Check that WS business service or the target webservice is functioning properly and increase the response timeout value if necessary.

BEA-381412

Error: An error occured while sending the message reliably to the target reliable webservice.

Description

Reliable delivery failure has occurred while sending the message to the target reliable webservice. This failure might be because of Sequence timeout, inactivity timeout, authentication/authorization failures or bad certificate errors etc.

Action

Check that WS business service or the target webservice is functioning properly.

BEA-381413

Error: URI:uri of WS proxy service has / at the end.

Description

WS proxy services should not have an ending / in URI.

Action

Remove the ending / in the URI of the WS proxy service.

BEA-381414

Error: Attempting an indirect send to a WS transport proxy which requires BASIC authentication (proxy). Proxy-to-proxy routing and test console access are not allowed with this pattern

Description

WS transport proxy services which require username/password (i.e. BASIC) authentication cannot be invoked from another proxy or from the test console.

Action

Check the message flow configuration and make sure there are no proxy-to-proxy routes where the target proxy service is a WS transport endpoint with BASIC authentication. Also, whenever using the test console to test such a WS transport proxy, make sure you set the "direct call" check-box to true.

BEA-381415

Error: X.509 token identity assertion is not enabled in the security realm. An identity asserter with X.509 token support enabled is required because ws proxy service "inboundEndpoint" has a ws-policy which requires CLIENT-CERT authentication

Description

An identity asserter with X.509 token support enabled is required whenever the ws-policy requires 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-381416

Error: The X.509 username-mapper sub-plugin of the default identity asserter in not configured. The username-mapper is required because ws proxy service "inboundEndpoint" has a ws-policy which requires CLIENT-CERT authentication

Description

An identity asserter with X.509 token support enabled and username-mapper plugin enabled is required whenever the ws-policy requires CLIENT-CERT authentication (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-381417

Error: WS transport proxy "proxy" is configured with client-certificate-required policy and is deployed in a cluster. There is typically a load-balancer between the client and the cluster. The load balancer forwards client-certificates to the server, but the server will only honor this certificate if it is configured with "Client Cert Proxy Enabled", otherwise the certificate will be ignored and the request will fail.

Description

Typically, when a WS transport proxy is configured with client-certificate-required policy and is deployed in a cluster, the managed servers must be configured with "Client Cert Proxy Enabled". This is so that the managed servers will honor the certificate in the "WL-Proxy-Client-Cert" HTTP header. Make sure to read the section on SSL configuration in WebLogic Server documentation when using this feature.

Action

Set "Client Cert Proxy Enabled" to true in the WLS console. This can be done at the cluster level or individually for each managed server in the cluster. Make sure to read the section on SSL configuration in WebLogic Server documentation when using this feature. Use a weblogic.security.net.ConnectionFilter to ensure that this WebLogic Server instance accepts connections only from the machine on which the proxy-server plugin is running, otherwise you will create a security vulnerability because the WL-Proxy-Client-Cert header can be spoofed.

BEA-381418

Error: Unexpected failure while processing an incoming message for endpoint name

Description

There was an unexpected error while processing an inbound message by specified WS proxy service.

Action

Contact technical support.

BEA-381419

Error: WS business service URLs must start with either http:// or https:// and have a hostname

Description

An error had occured while registering a new WS 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 WS business service and make sure that a valid URL is being entered.

BEA-381420

Info: "Synchronous" property in WS transport configuration is upgraded to "Same Transaction For Response" in service configuration.

Description

"Synchronous" property in WS transport configuration is upgraded to "Same Transaction For Response" in service configuration.

BEA-381421

Info: Error Queue Configuration is upgraded.

Description

Error Queue Configuration is upgraded.

BEA-381422

Error: Sending the failed request message to error queue is failed for service: refGlobalName with error : th

Description

Sending the failed request message to error queue is failed for service.

Cause

Error queue configured for the service may not be available or it may not be accepting the messages from OSB as the security credentials do not match.

Action

Make sure configured error queue is available and provide right credentials to the service.

 

Back to Index Page

Copyright © 2008, 2013, Oracle. All rights reserved.