The ALSB Kernel catalog contains messages in the range
BEA398000 - BEA398999. Messages in this catalog are part of the
com.bea.wli.sb.messages Internationalization package and the
com.bea.wli.sb.messages Localization package.
|
BEA-398000
|
Error: Exception in method, e
|
Description
| An unexpected error has occured in ALSB runtime while processing a message. There should be a specific error message that points to the cause of the error |
|
Action
| Contact technical support |
|
|
BEA-398014
|
Error: Invalid Proxy URI: e
|
Description
| There was an error while processing the configuration for given proxy service: The URI specified was not valid. There should be an error message that points out a specific problem |
|
Action
| Check the URI for the proxy service to make sure it is valid |
|
|
BEA-398015
|
Error: The service definition does not contain a reference to a wsdl
|
Description
| The WSDL-based service being registered is misconfigured: there was a problem retrieving its corresponding WSDL information |
|
Action
| Contact technical suppport |
|
|
BEA-398016
|
Error: Error loading the WSDL from the repository: e
|
Description
| The WSDL-based service being registered is misconfigured: there was a problem retrieving its corresponding WSDL information. There should be an error message that points to the cause of the problem |
|
Action
| Contact technical suppport |
|
|
BEA-398017
|
Error: The service definition contains a reference to a port not present in the wsdl: port
|
Description
| There was a problem while registering a WSDL-based service: specified WSDL port is not present in associated WSDL resource |
|
Action
| Contact technical support |
|
|
BEA-398018
|
Error: The service definition contains a reference to a binding not present in the wsdl: binding
|
Description
| There was a problem while registering a WSDL-based service: specified WSDL binding is not present in associated WSDL resource |
|
Action
| Contact technical support |
|
|
BEA-398019
|
Error: Mismatch between the WSDL binding and the service definition type: binding
|
Description
| There was an unexpected problem while registering a WSDL-based service: the type of WSDL binding in WSDL resource is SOAP whereas the service is not of SOAP type |
|
Action
| Contact technical support |
|
|
BEA-398020
|
Error: The wsdl binding has more than one operation you must specify how to select the operations
|
Description
| There was an problem while registering a WSDL-based service: The WSDL binding has more than one operation, so you must specify how to select the operation in service registration wizard |
|
Action
| Check the service configuration and make sure that the operation selection algorithm is properly configured |
|
|
BEA-398021
|
Error: The operation referenced in the service definition cannot be found in the WSDL: operation
|
Description
| There was an problem while registering a WSDL-based service: The operation referenced in the service definition cannot be found in the WSDL: operation |
|
Action
| Check the service configuration and make sure that the operation selection algorithm is properly configured |
|
|
BEA-398023
|
Error: You can only setup inbound web service security on proxy services
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398024
|
Error: This WSDL does not support web service security, you must attach a policy first
|
Description
| A service defined by the WSDL requires web service security policy but the WSDL does not have any |
|
Action
| Attach ws-policy to the WSDL or configure custom ws-policy for the service |
|
|
BEA-398025
|
Error: You can only setup a service account on business services
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398026
|
Error: You can only use web service security with a SOAP binding
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398027
|
Error: You can only use a HTTP binding with verb="POST"
|
Description
| There was an problem while registering a WSDL-based service: corresponding WSDL binding was HTTP with non-POST verb, which is not allowed |
|
Action
| Correct the WSDL resource or choose another WSDL binding for the service |
|
|
BEA-398028
|
Error: You cannot select operations for business services
|
Description
| There registered business service is not properly configured: it is not allowed to have operation selection algorithm for business services |
|
Action
| Contact technical support |
|
|
BEA-398029
|
Error: The schema defined for mixed type, cannot be found in the repository
|
Description
| There was a problem registering Messaging Type service: the corresponding XML schema resource was not found |
|
Action
| Contact technical support |
|
|
BEA-398030
|
Error: The schema defined for mixed type, cannot be parsed
|
Description
| There was a problem registering Messaging Type service: the corresponding XML schema resource could not be parsed |
|
Action
| Contact technical support |
|
|
BEA-398031
|
Error: The element defined for mixed type, cannot be found in the schema
|
Description
| There was a problem registering Messaging Type service: the specified element was not found in the XML schema resource |
|
Action
| Contact technical support |
|
|
BEA-398032
|
Error: The type defined for mixed type, cannot be found in the schema
|
Description
| There was a problem registering Messaging Type service: the specified type was not found in the XML schema resource |
|
Action
| Contact technical support |
|
|
BEA-398033
|
Error: The operation operation is a notification or a solicit-response, invert the message order or select another binding
|
Description
| There was a problem registering a WSDL-based service: the operation operation is a notification or a solicit-response |
|
Action
| Invert the message order or select another WSDL binding |
|
|
BEA-398034
|
Error: Two operations expect the same incoming message, you must use a selector different than message body
|
Description
| There was a problem registering a WSDL-based service: the specified operation selection algorithm was SOAP Body while the associated WSDL binding was such that it is impossible to distinguish different operations based on data in the body of the incoming SOAP message. |
|
Action
| Choose a different operation selection algorithm for the service or use a different WSDL binding |
|
|
BEA-398038
|
Error: Proxy service "proxy" does not have a credential for web service security encryption (no service key provider has been specified). The ws-policy of operation "operation" requires an encryption credential.
|
Description
| The ws-policy of the proxy service contains a confidentiality assertion, the proxy must have a reference to a service key provider |
|
Action
| In the security tab, assign a service key provider to the proxy service (the service key provider must have an encryption credential) |
|
|
BEA-398040
|
Error: Proxy service "proxy" does not have a credential for web service security digital signatures (no service key provider has been specified). The ws-policy of operation "operation" requires a digital signature credential.
|
Description
| The ws-policy of the proxy service contains an integrity assertion, the proxy must have a reference to a service key provider |
|
Action
| In the security tab, assign a service key provider to the proxy service (the service key provider must have a digital signature credential) |
|
|
BEA-398042
|
Error: Proxy service "proxy" does not have a credential for outbound two-way SSL authentication (no service key provider has been specified)
|
Description
| At least one route out of the proxy service requires 2-way SSL, the proxy must have a reference to a service key provider |
|
Action
| In the security tab, assign a service key provider to the proxy service (the service key provider must have an SSL client authentication credential) |
|
|
BEA-398043
|
Error: The ws-policy of operation "operation" for proxy service "proxy" contains a confidentiality assertion but service key provider "psp" does not have an encryption credential
|
Description
| The ws-policy of the proxy service requires encryption, the service key provider linked to the proxy service must have an encryption credential |
|
Action
| Edit the service key provider and assign it an encryption credential, or edit the proxy service and choose a different service key provider (in the security tab) |
|
|
BEA-398044
|
Error: The ws-policy of operation "operation" for proxy service "proxy" contains an integrity assertion but service key provider "psp" does not have a digital signature credential
|
Description
| The ws-policy of the proxy service requires digital signatures, the service key provider linked to the proxy service must have a digital signature credential |
|
Action
| Edit the service key provider and assign it a digital signature credential, or edit the proxy service and choose a different service key provider (in the security tab) |
|
|
BEA-398046
|
Error: Proxy service "proxy" has one or more routes to a service which requires 2-way SSL authentication, but the proxy service does not have a credential for outbound SSL (service key provider "psp" does not have an SSL credential).
|
Description
| At least one route out of the proxy service requires 2-way SSL, the proxy must have a reference to a service key provider |
|
Action
| In the security tab, assign a service key provider to the proxy service (the service key provider must have an SSL client authentication credential) |
|
|
BEA-398052
|
Error: Could not retrieve an X.509 certificate from PKI Credential provider [service key provider: "proxyServiceProvider", key alias: "keyAlias"]
|
Description
| An error occurred while calling the PKI Credential Mapper Provider lookup method |
|
Cause
| Please contact technical support |
|
|
BEA-398053
|
Error: Either there are duplicate values for the soapAction attribute for different operations in the selected WSDL binding or soapAction is not defined for at least one operation in the WSDL. Therefore SOAPAction header operation selection algorithm cannot be used
|
Description
| There was a problem registering a WSDL-based service: Either there are duplicate values for the soapAction attribute for different operations in the selected WSDL binding or soapAction is not defined for at least one operation in the WSDL. Therefore SOAPAction header operation selection algorithm cannot be used |
|
Action
| Choose a different operation selection algorithm for the service or use a different WSDL binding |
|
|
BEA-398055
|
Error: Business service "busSvcName" cannot be associated with a router
|
Description
| There was an unexpected error validating the configuration of business service busSvcName: business services cannot be associated with a message flow |
|
Action
| Checking service configuration and/or contact technical support |
|
|
BEA-398056
|
Error: No router is defined for proxy service "proxyName"
|
Description
| There was an unexpected error validating the configuration of business service proxyName: proxy services have to be associated with a message flow |
|
Action
| Checking service configuration and/or contact technical support |
|
|
BEA-398059
|
Error: Proxy service "proxyName" has web service security configuration but either: 1) its WSDL does not have web service security policies, or 2) the tag is missing from the WSDL. You must edit/save the proxy (that will remove the web service security configuration), or add web service security policies to the WSDL.
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398060
|
Error: The ws-policy of operation "operation" in proxy service "proxyName" contains a concrete confidentiality assertion. Confidentiality assertions assigned to proxy services must be abstract, the encryption certificate must not be embedded in the policy.
|
Description
| The proxy service is a WS-Security (web services security) active intermediary. Its ws-policy includes a "confidentiality" assertion (this is a BEA-proprietary policy assertion which specifies that the client must encrypt the request message). This confidentiality assertion is concrete. That means the policy includes a base-64 encoded certificate (in the /wssp:Confidentiality/wssp:KeyInfo/wssp:SecurityTokenReference/wssp:Embedded/wsse:BinarySecurityToken element). Proxy services should not have concrete confidentiality assertions on its policy because the proxys encryption certificate is assigned through a service key provider. |
|
Action
| Make the policy abstract. To do this edit the policy and delete the SecurityToken and SecurityTokenReference child elements inside the /wssp:Confidentiality/wssp:KeyInfo element. |
|
|
BEA-398061
|
Error: The ws-policy of operation "operation" in business service "bizSvcName" contains an abstract confidentiality assertion. Confidentiality assertions assigned to business services must not be abstract, the encryption certificate must be embedded in the policy
|
Description
| The ws-policy of the business service includes a "confidentiality" assertion (this is a BEA-proprietary policy assertion which specifies that request messages to this service must be encrypted). This confidentiality assertion is abstract. That means the policy does not include an embedded base-64 encoded server certificate. The confidentiality assertion must be concrete. |
|
Action
| Make the policy concrete. To do this edit the policy and make sure there are SecurityToken and SecurityTokenReference child elements inside the /wssp:Confidentiality/wssp:KeyInfo element. The value of the SecurityTokenReference element is an embedded base-64 encoded server certificate (it must be the servers encryption certificate). Consult AquaLogic Service Bus security documentation to find examples of what this policy should look like. |
|
|
BEA-398062
|
Error: An error occurred during web service security validation: msg
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398063
|
Error: There is an outbound call to operation "operation" on service "targetService", this operation requires encrypted response messages; the proxy must be assigned to a service key provider
|
Description
| One or more nodes in the pipeline route messages to a service whose ws-policy specify that response messages to the proxy must be encrypted with the proxys encryption key. The proxy service should have a reference to a service key provider from which ALSB will get the proxys encryption credential (ALSB will send this certificate on the request message), but no service key provider reference has been assigned to the proxy. |
|
Action
| Edit the proxy service. In the security tab choose a service key provider (the service key provider must have an encryption credential). |
|
|
BEA-398064
|
Error: There is an outbound call to operation "operation" on service "targetService", this operation requires signed request messages; the proxy must be assigned to a service key provider
|
Description
| One or more nodes in the pipeline route messages to a service whose ws-policy require ALSB to sign the request messages. The proxy service should have a reference to a service key provider from which ALSB will get the proxys digital signature credential, but no service key provider reference has been assigned to the proxy. |
|
Action
| Edit the proxy service. In the security tab choose a service key provider (the service key provider must have a digital signature credential). |
|
|
BEA-398065
|
Error: There is an outbound call to operation "operation" on service "targetService", this operation requires encrypted response messages but the service key provider does not have an encryption credential
|
Description
| One or more nodes in the pipeline route messages to a service whose ws-policy specify that response messages to the proxy must be encrypted with the proxys encryption key. The service key provider assigned to this proxy does not have an encryption credential. |
|
Action
| Edit the service key provider and choose an encryption credential; or alternatively, edit the proxy service and -in the security tab- choose a different service key provider (one which has an encryption credential). |
|
|
BEA-398066
|
Error: There is an outbound call to operation "operation" on service "targetService", this operation requires signed request messages but the service key provider does not have a digital signature credential
|
Description
| One or more nodes in the pipeline route messages to a service whose ws-policy require ALSB to sign the request messages. The service key provider assigned to this proxy does not have an encryption credential. |
|
Action
| Edit the service key provider and choose a digital signature credential; or alternatively, edit the proxy service and -in the security tab- choose a different service key provider (one which has a digital signature credential). |
|
|
BEA-398068
|
Info: \n [ALSB Tracing] Invoking service name with \n $outbound = outbound
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever a service is invoked for outbound request |
|
Action
| No action is required |
|
|
BEA-398072
|
Info: \n [ALSB Tracing] Routing to serviceName with message context: \nmessageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever a service is invoked for outbound request in asynchronous (non-blocking) fashion |
|
Action
| No action is required |
|
|
BEA-398073
|
Info: \n [ALSB Tracing] Entering dispatch, Pipeline Context = pipelineContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever a service is invoked for outbound request in synchronous (blocking) fashion |
|
Action
| No action is required |
|
|
BEA-398074
|
Info: \n [ALSB Tracing] The following variables are added: \n variables
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever new variables are added to the message context during runtime processing |
|
Action
| No action is required |
|
|
BEA-398075
|
Info: \n [ALSB Tracing] The following variables are deleted: \n variables
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever existing variables are deleted from the message context during runtime processing |
|
Action
| No action is required |
|
|
BEA-398076
|
Info: \n [ALSB Tracing] The following variables are changed: \n variables
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever values of existing variables are updated in the message context during runtime processing |
|
Action
| No action is required |
|
|
BEA-398077
|
Info: \n [ALSB Tracing] Entering proxy name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message comes to the route node for processing |
|
Action
| No action is required |
|
|
BEA-398078
|
Info: \n [ALSB Tracing] Entering route node name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message enters an ALSB pipeline route node for processing |
|
Action
| No action is required |
|
|
BEA-398079
|
Info: \n [ALSB Tracing] Entering pipeline pair name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message enters an ALSB pipeline pair node for processing |
|
Action
| No action is required |
|
|
BEA-398080
|
Info: \n [ALSB Tracing] Entering stage name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message enters an ALSB pipeline stage for processing |
|
Action
| No action is required |
|
|
BEA-398081
|
Info: \n [ALSB Tracing] Echoing request
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever ALSB is about to echo the contents of incoming message request |
|
Action
| No action is required |
|
|
BEA-398082
|
Info: \n [ALSB Tracing] Entering conditional branch node name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message enters an ALSB conditional branch node for processing |
|
Action
| No action is required |
|
|
BEA-398083
|
Info: \n [ALSB Tracing] Entering operation branch node name with message context" \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message enters an ALSB operation branch node for processing |
|
Action
| No action is required |
|
|
BEA-398084
|
Info: \n [ALSB Tracing] Exit dispatch, Pipeline Context = pipelineContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the invokation of the service for outbound request is completed |
|
Action
| No action is required |
|
|
BEA-398085
|
Info: \n [ALSB Tracing] Exiting error handler... \n Pipeline Context = pipelineContext \n Message Context = messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the invokation of the error handler is completed |
|
Action
| No action is required |
|
|
BEA-398086
|
Info: \n [ALSB Tracing] The process is resumed
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of the incoming message has been resumed |
|
Action
| No action is required |
|
|
BEA-398089
|
Info: \n [ALSB Tracing] Entering pipeline name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever an incoming message first comes comes into ALSB pipeline for processing |
|
Action
| No action is required |
|
|
BEA-398090
|
Info: \n [ALSB Tracing] Exiting stage
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever processing of the message exits a stage |
|
Action
| No action is required |
|
|
BEA-398091
|
Info: \n [ALSB Tracing] Exiting stage with fault: \nfault
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever processing of the message exits a stage with a fault condition |
|
Action
| No action is required |
|
|
BEA-398092
|
Info: \n [ALSB Tracing] Invoking service name in request path \n $outbound = outbound
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever a service is invoked for outbound request while processing in request path |
|
Action
| No action is required |
|
|
BEA-398093
|
Info: \n [ALSB Tracing] Invoking service name in response path \n $outbound = outbound
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever a service is invoked for outbound request while processing in response path |
|
Action
| No action is required |
|
|
BEA-398094
|
Info: \n [ALSB Tracing] Request message context: \ndata
|
Description
| This is an informational message from ALSB tracing subsystem that is logged to show the contents of the message context on an outbound request |
|
Action
| No action is required |
|
|
BEA-398095
|
Info: \n [ALSB Tracing] Response message context: \ndata
|
Description
| This is an informational message from ALSB tracing subsystem that is logged to show the contents of the message context after the response to outbound request is received |
|
Action
| No action is required |
|
|
BEA-398096
|
Info: \n [ALSB Tracing] Exiting serviceName
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message exits the route node |
|
Action
| No action is required |
|
|
BEA-398097
|
Info: \n [ALSB Tracing] Entering error handler of proxy name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message exits the error handler associated with the route node |
|
Action
| No action is required |
|
|
BEA-398098
|
Info: \n [ALSB Tracing] Entering error handler of route node name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message enters the error handler associated with the route node |
|
Action
| No action is required |
|
|
BEA-398099
|
Info: \n [ALSB Tracing] Entering error handler of pipeline name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message enters the error handler associated with the pipeline node |
|
Action
| No action is required |
|
|
BEA-398100
|
Info: \n [ALSB Tracing] Entering error handler of stage name with message context: \n messageContext
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message enters the error handler associated with a stage |
|
Action
| No action is required |
|
|
BEA-398101
|
Info: \n [ALSB Tracing] Exiting route node
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message in the route node is complete |
|
Action
| No action is required |
|
|
BEA-398102
|
Info: \n [ALSB Tracing] Exiting route node with fault: \nfault
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message in the route node is complete with a fault condition |
|
Action
| No action is required |
|
|
BEA-398103
|
Info: \n [ALSB Tracing] Exiting branch node
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing of a message in the conditional branch node is complete |
|
Action
| No action is required |
|
|
BEA-398104
|
Info: \n [ALSB Tracing] Exiting pipeline pair
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing in the pipeline pair node is complete |
|
Action
| No action is required |
|
|
BEA-398105
|
Info: \n [ALSB Tracing] Exiting Pipeline
|
Description
| This is an informational message from ALSB tracing subsystem that is logged whenever the processing in the pipeline is complete |
|
Action
| No action is required |
|
|
BEA-398106
|
Error: The ws-policy of operation "operation" in service "serviceName" contains an identity assertion. The business service should have a web service security service account, but none has been configured.
|
Description
| The ws-policy of operation "operation" in service "serviceName" contains an identity assertion. Only web service security username tokens are supported for identity purposes. This business service must have a web service security service account. |
|
Action
| Edit the business service. In the security tab, choose a web service security service account. |
|
|
BEA-398107
|
Error: The ws-policy for service "serviceName" and operation "operation" contains a policy assertion with qname "assertionQName". This assertion is not recognized. Make sure the namespace declaration and local-name are correct.
|
Description
| The ws-policy contains a policy assertion which is not recognized. |
|
Action
| Edit the ws-policy and make sure all policy assertions are supported by AquaLogic Service Bus. |
|
|
BEA-398108
|
Error: Business service "serviceName" has web service security configuration but either: 1) its WSDL does not have web service security policies, or 2) the tag is missing from the WSDL. You must edit/save the service (that will remove the web service security configuration), or add web service security policies to the WSDL.
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398109
|
Warning: The proxy service has message-level custom token authentication for tokens of type "tokenType". This token-type is not recognized.
|
Description
| The token-type specified in the services message-level custom token authentication is not recognized. Either there is no Identity Assertion Provider for this token type or the token type has not been "activated". |
|
Action
| Check your domains security realm configuration. Make sure there is an Identity Assertion Provider for your token type. Also make sure the token type has been enabled for that particular Identity Assertion Provider. Consult WebLogic Server security documentation for more information on the identity assertion process and Identity Assertion Providers. |
|
|
BEA-398110
|
Error: Business service "serviceFullName" has configuration for message-level custom token authentication. Message-level custom token authentication only applies to proxy services.
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398111
|
Error: Proxy service "serviceFullName" has configuration for message-level custom authentication. Message-level custom authentication is not valid on services with binary or text binding.
|
Description
| An unexpected error occurred. The service definition is invalid. |
|
Action
| Contact technical support |
|
|
BEA-398112
|
Error: Operation "operationName" in proxy service "serviceFullName" is configured for WS-Security authentication, but the proxy service is also configured for message-level custom token authentication. WS-Security authentication and message-level custom authentication are mutually exclusive.
|
Description
| WS-Security authentication and message-level custom authentication are mutually exclusive. |
|
Action
| Make sure your proxy service is not configured for both types of authentication. You may have to edit the proxy service or the ws-policy to make sure that at most one of these two techniques is used. |
|
|
BEA-398113
|
Error: Invalid custom authentication token selector: msg
|
Description
| The XPath expression in the custom-token selector is invalid |
|
Action
| Enter a valid XPath expression in the custom-token selector field |
|
|
BEA-398114
|
Error: Invalid username selector: msg
|
Description
| The XPath expression in the username selector is invalid |
|
Action
| Enter a valid XPath expression in the username selector field |
|
|
BEA-398115
|
Error: Invalid password selector: msg
|
Description
| The XPath expression in the password selector is invalid |
|
Action
| Enter a valid XPath expression in the password selector field |
|
|
BEA-398116
|
Error: Invalid user-defined authentication context property selector: msg
|
Description
| The XPath expression in the user-defined property selector is invalid |
|
Action
| Enter a valid XPath expression in the user-defined property selector field |
|
|
BEA-398117
|
Error: Invalid variable name in selector: "variable"
|
Description
| The variable name in a custom-token must be either "header" or "body" |
|
Action
| Edit the proxy service. In the security tab, choose a valid message part for your custom-token. |
|
|
BEA-398118
|
Error: The ws-policy of operation "operation" in proxy service "proxyService" contains an Identity assertion for UsernameToken without password. Such UsernameTokens can only be used when the token is signed, however, this ws-policy does not have an Integrity assertion. Either add an Integrity assertion policy or change your Identity policy so that the UsernameToken includes a password.
|
Description
| A web service security username token without a password can only be trusted if the token itself is signed by the message producer. |
|
Action
| Edit the ws-policy and make sure it either forbids username tokens without password, or otherwise have the policy require a digital signature which covers the username token. |
|
|
BEA-398119
|
Warning: The ws-policy of operation "operation" in proxy service "proxyService" contains an Identity assertion for UsernameToken without password. Such UsernameTokens can only be used when the token is signed. ALSB cannot determine if your policy requires the token to be signed or not. Make sure your policy requires the token to be signed, otherwise requests might result in a runtime error.
|
Description
| A web service security username token without a password can only be trusted if the token itself is signed by the message producer. |
|
Action
| Edit the ws-policy and make sure it either forbids username tokens without password, or otherwise have the policy require a digital signature which covers the username token. |
|
|
BEA-398120
|
Error: The WSDL for the typed transport endpoint could not be accessed.
|
Description
| There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration |
|
Action
| Contact technical support |
|
|
BEA-398121
|
Error: Error loading the WSDL for the typed transport endpoint: e
|
Description
| There was a problem retrieving the WSDL from the typed transport service endpoint at the time of service registration. There should be an error message that points to the specific cause of the error |
|
Action
| Contact technical support |
|
|
BEA-398122
|
Error: Missing logging element in the service entry element.
|
Description
| There was an unexpected error while validating service configuration: a required element "logging" was missing from the configuration |
|
Action
| Contact technical support |
|
|
BEA-398123
|
Error: Missing sla-alerting element in the service entry element.
|
Description
| There was an unexpected error while validating service configuration: a required element "sla-alerting" was missing from the configuration |
|
Action
| Contact technical support |
|
|
BEA-398124
|
Error: Missing pipeline-alerting element in the service entry element.
|
Description
| There was an unexpected error while validating service configuration: a required element "pipeline-alerting" was missing from the configuration |
|
Action
| Contact technical support |
|
|
BEA-398125
|
Error: Logging element should not exist in the service entry element.
|
Description
| There was an unexpected error while validating service configuration: business service configuration cannot have "logging" element |
|
Action
| Contact technical support |
|
|
BEA-398126
|
Error: sla-alerting element should not exist in the service entry element.
|
Description
| There was an unexpected error while validating service configuration: business service configuration cannot have "sla-alerting" element |
|
Action
| Contact technical support |
|
|
BEA-398127
|
Error: pipeline-alerting element should not exist in the service entry element.
|
Description
| There was an unexpected error while validating service configuration: business service configuration cannot have "pipeline-alerting" element |
|
Action
| Contact technical support |
|
|
BEA-398128
|
Error: Web service policy is not allowed on service serviceName because the service binding is not based on WSDL
|
Description
| The service definition is invalid; it should not contain any ws-policy configuration. |
|
Action
| Contact technical support. |
|
|
BEA-398129
|
Error: An error occurred while computing the web service policy for service service: error
|
|
BEA-398130
|
Error: Service "serviceName" must have RM (reliable messaging) policy assertions in its web service policy
|
Description
| WS transport services must have RM (reliable messaging) policy. |
|
Action
| Configure the services ws-policy. Make sure it has RM policy assertions. |
|
|
BEA-398131
|
Error: This service should not have WebLogic Server 9.X-style security policy assertions
|
Description
| WS transport services cannot have WebLogic Server 9.X-style security policy assertions |
|
Action
| Configure the service's ws-policy. Make sure it does not have any WebLogic Server 9.X-style security policy assertions. |
|
|
BEA-398132
|
Error: RM (reliable messaging) policy assertions are not allowed on this service.
|
Description
| RM (reliable messaging) policy assertions are only allowed on ws-transport services. |
|
Action
| Either remove the RM policy assertions from the service's ws-policy or switch the service to the ws transport. |
|
|
BEA-398133
|
Error: WSSP 1.2 policy assertions (Web Services Security Policy 1.2) are not allowed on this service.
|
Description
| WSSP 1.2 assertions are not allowed in this version of AquaLogic Service Bus (except in some cases in ws transport endpoints) |
|
Action
| Edit the service's ws-policy. Either remove the WSSP 1.2 policy assertions or replace it with WebLogic Server 9.X-style security policy assertions. |
|
|
BEA-398134
|
Error: Proxy service proxyName is marked as a web service security intermediary but does not have web service security policies
|
Description
| A web service security intermediary proxy service must have security policy (in it ws-policy). |
|
Action
| If you want this proxy service to be a web service security intermediary, edit the services ws-policy and make sure it includes security policy. If on the other hand you do not want this proxy service to be a web service security intermediary, go to the security tab and click "update" (without making any other changes). |
|
|
BEA-398135
|
Error: Business service bizSvcName has a service account reference for web service security authentication but does not have web service security policies
|
Description
| A web service security service account is only meaningful if the business service has web service security policy (in its ws-policy). This business service has a reference to a web service security service account (although you may not be able to see it in the console). |
|
Action
| Either add security policy to this services ws-policy or go to the security tab and click "update"(without making any other changes). |
|
|
BEA-398136
|
Error: Proxy service proxyName is enabled for content streaming and cannot be marked as a web service security intermediary
|
Description
| Content streaming feature is not allowed if your service is configured as a web service security active intermediary. |
|
Action
| Edit the service and turn off content streaming feature |
|
|
BEA-398137
|
Error: Proxy service proxyName is enabled for content streaming and perform custom authentication
|
Description
| Content streaming feature is not allowed if your service is configured for custom authentication. |
|
Action
| Edit the service and turn off content streaming feature |
|
|
BEA-398138
|
Error: WSI-Compiance cannot be checked in proxies enabled for content streaming
|
|
BEA-398139
|
Error: The binding type of service service is based on wsdl, the service should have ws-policy configuration
|
|
BEA-398140
|
Error: Proxy service "service" is a passive wss intermediary. The ws-policy of operation "operation" contains an abstract confidentiality assertion but the proxy service does not have a service key provider reference or the referenced service key provider does not have an encryption credential. You will be able to invoke this proxy service but its effective WSDL will not have an encryption certificate. Clients must get this certificate out-of-band.
|
Description
| A passive wss intermediary is a proxy service which has ws-security policy in its public WSDL (the "effective" WSDL) but which does not perform any ws-security processing (it simply relays the security header to a back-end service). Whenever a passive wss intermediary has an "abstract confidentiality" policy, the proxy should have a service key provider which in turn must have an encryption credential. This encryption credential will be then inlined in the effective WSDL. |
|
Action
| Edit the proxy service. In the security tab, choose a service key provider (the service key provider must have an encryption credential). |
|
|
BEA-398141
|
Error: One or more ws-policies have been bound to operation "operation" but there is no such operation
|
Description
| The service has custom ws-policy. One of the custom ws-policies is assigned to an operation which does not exist in the WSDL. This may be the result of a change in the WSDL. |
|
Action
| Either edit the WSDL and add the missing operation, or if no such operation exists, edit the service, go to the policy tab and click "update" (without making any other changes). |
|
|
BEA-398142
|
Error: One or more ws-policies have been bound to the response of operation "operation" but the operation is one-way
|
Description
| The service has custom ws-policy. One of the custom ws-policies is assigned to the response message of an operation which is declared in the WSDL to be a one-way operation. Such operations do not have response messages. This may be the result of a change in the WSDL. |
|
Action
| Edit the service, go to the policy tab and click "update" (without making any other changes). |
|
|
BEA-398143
|
Error: A reliable messaging policy is bound to operation "operation"; reliable messaging policies can only be bound to the service as a whole
|
Description
| RM (reliable messaging) policies cannot be bound to specific operations, they can only be bound to the entire service. |
|
Action
| Edit the services ws-policy. Make sure RM policies are bound to the service as a whole. |
|
