WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, IBM i, Linux, Solaris, Windows, z/OS


CWSOA

CWSOA0001I: The Service Component Architecture (SCA) composite is starting in the {0} application.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0002I: The Service Component Architecture (SCA) composite in the {0} application has started successfully.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0003E: The Service Component Architecture (SCA) composite in the {0} application failed to start. Check the server log files for more details.
Explanation The SCA composite failed to start correctly for the specified Web application.
Action Check your SCA composite for errors and review the server log files.
CWSOA0004E: The embedded Service Component Architecture (SCA) Run time failed to start. Check the server log files for more details.
Explanation The embedded SCA Runtime failed to start correctly.
Action Check the server log files for errors.
CWSOA0005I: The embedded Service Component Architecture (SCA) run time is starting.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0006I: The embedded Service Component Architecture (SCA) run time startup process is complete.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0007I: The embedded Service Component Architecture (SCA) run time is stopping.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0008I: The embedded Service Component Architecture (SCA) run time shutdown process is complete.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0009I: The embedded Service Component Architecture (SCA) run time is initializing.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0010I: The embedded Service Component Architecture (SCA) run time has been initialized.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0011I: The Service Component Architecture (SCA) composite in the {0} application is stopping.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0012I: The Service Component Architecture (SCA) composite in the {0} application has stopped successfully.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA0013E: The Service Component Architecture (SCA) composite in the {0} application did not stop properly. Check the server log files for more details.
Explanation The SCA composite failed to stop properly for the specified Web application.
Action Please check your SCA composite for errors and review the server logs.
CWSOA1001E: The Service Component Architecture (SCA) Runtime cannot resolve the {0} imports for the {1} Service Component Architecture (SCA) composite.
Explanation Matching dependent assets cannot be located for the unresolved imports.
Action Check your SCA asset and make sure the dependent assets are imported.
CWSOA1002E: Web applications cannot contain references with callbacks using the Web services binding.
Explanation Web Applications may not contain references with callbacks using the Web Services Binding.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1003E: The Service Component Architecture (SCA) Runtime cannot determine the Java implementation class for the wsdlElement.
Explanation The Service Component Architecture (SCA) Runtime cannot determine the Java Implementation Class for wsdlElement.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1004E: The Service Component Architecture (SCA) Runtime cannot create the Service Component Architecture (SCA) Codegen directory. Check server log files for more details.
Explanation The SCA Codegen directory failed to be created. Check server logs for more details.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1005W: The ConstrainingType is not supported on {0}.
Explanation The ConstrainingType is an unsupported specification scenario.
Action Do not set the ConstrainingType on either composites or components.
CWSOA1006E: The conversation is not supported on {0}.
Explanation Conversations on service interfaces and callback interfaces is not supported.
Action Do not set the conversation on service interfaces and callback interfaces.
CWSOA1007E: The {0} implementation type is not supported.
Explanation The implementation type is not supported.
Action Use one of the supported implementation types.
CWSOA1008E: The {0} binding type is not supported.
Explanation The binding type is not supported.
Action Use one of the supported binding types.
CWSOA1014E: The service is unavailable for the referenced target.
Explanation The service is unavailable for reference target.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1015E: The service is not installed for the referenced target.
Explanation The service is not installed for reference target.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1016E: The Service Component Architecture (SCA) Runtime cannot determine the destination endpoint from the service registry for the referenced target.
Explanation Unable to determine the destination endpoint from Service Registry for reference target.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1017E: The Service Component Architecture (SCA) Runtime cannot handle mixed payloads between OMElements <type?> and other types.
Explanation Cannot handle mixed payloads betweem OMElements and other types.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1018E: The Service Component Architecture (SCA) Runtime cannot determine the endpoint URI for the reference.
Explanation Unable to determine Endpoint URI for reference.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1019E: The Service Component Architecture (SCA) Runtime cannot determine the wsPolicy <noun?> for the reference.
Explanation Unable to determine wsPolicy for reference.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1020E: This service is available on secure channels only.
Explanation This service is available on secure channels only.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1021E: The Service Component Architecture (SCA) Runtime cannot register the service with the service registry.
Explanation Unable to register service with the Service Registry.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1022W: The Service Component Architecture (SCA) Runtime cannot stop the service with the service registry.
Explanation Unable to stop service with the Service Registry.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1023E: Absolute URI cannot be specified as the location to host this service:
Explanation Absolute URI cannot be specified as the location to host this service:
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1024I: WebSphere Application Server Feature Pack for Service Component Architecture configured AxisService for service.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA1025E: The Service Component Architecture (SCA) Runtime cannot obtain the CompUnitInfoLoader value.
Explanation Unable to obtain CompUnitInfoLoader.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1026E: The Service Component Architecture (SCA) Runtime cannot obtain the CompUnitInfoLoader URL prefix for the service.
Explanation The Service Component Architecture (SCA) Runtime cannot obtain the CompUnitInfoLoader URL prefix for a service.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1027E: The Service Component Architecture (SCA) Runtime cannot determine the wsPolicy for the service.
Explanation The Service Component Architecture (SCA) Runtime cannot determine the wsPolicy for the service.
Action If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/.
CWSOA1500E: The {0} composite and {1} component are duplicate.
Explanation The component names must be unique across all of the applications.
Action Ensure that the component names are unique across all of the applications.
CWSOA1501W: The service side default binding uri {0} is not supported.
Explanation we do not support user defined uri on binding.sca. The URI should be calculated by runtime in the form of component's uri/service name.
Action Make sure not defining default binding URI.
CWSOA1502E: The service side default binding uri {0} is not supported.
Explanation we do not support user defined uri on binding.sca. The URI should be calculated by runtime in the form of component's uri/service name.
Action Make sure not defining default binding URI.
CWSOA1503E: Duplicate components exist: {0}
Explanation The component names must be unique across all of the applications.
Action Ensure that the component names are unique across all of the applications.
CWSOA1504E: A policy set is attached to component {0} which uses JEE implementation type.
Explanation Authorization & runAs identity policy for impl.jee is handled by the implementation. Policy sets cannot be used to perform authorization checks and set runAs identity.
Action Detach the policy set and specify the roles and security constraints in the EAR file.
CWSOA1601W: Validation warning: {0}
Explanation check the message for the reason
Action check the message for the reason
CWSOA1602E: Validation error: {0}
Explanation check the message for the reason
Action check the message for the reason
CWSOA1603E: The destination resource with JNDI name {0} already exists.
Explanation The create attribute is set to 'always', but the resource can not be created because the resource already exists.
Action Delete the existing resource, or change the create attribute to 'ifnotexist'
CWSOA1604E: The activation specification with JNDI name {0} already exists.
Explanation The create attribute is set to 'always', but the resource can not be created because the resource already exists.
Action Delete the existing resource, or change the create attribute to 'ifnotexist'
CWSOA1605E: The connection factory with JNDI name {0} already exists.
Explanation The create attribute is set to 'always', but the resource can not be created because the resource already exists.
Action Delete the existing resource, or change the create attribute to 'ifnotexist'
CWSOA1606E: A destination JNDI name is required for the JMS binding used by reference {0} in component {1}.
Explanation A destination resource was not specified, but is required for the binding
Action Specify a destination resource JNDI name
CWSOA1607E: An activation specification cannot be created for service {0} in component {1} using the default JNDI name {2} and bus name {3}.
Explanation The service's JMS binding uses an existing resource that is associated with the bus named in the message. The JMS binding does not provide an existing activation specification. An activation specification with the default JNDI name cannot be created for this bus name.
Action Specify an activation specification JNDI name. An activation specification can be created in this situation if it is given a different JNDI name.
CWSOA1608E: A connection factory cannot be created for service {0} in component {1} using the default JNDI name {2} and bus name {3}.
Explanation The service's JMS binding uses an existing resource that is associated with the bus named in the message. The JMS binding does not provide an existing connection factory. A connection factory with the default JNDI name cannot be created for this bus name.
Action Specify a connection factory JNDI name. A connection factory can be created in this situation if it is given a different JNDI name.
CWSOA1609E: A connection factory cannot be created for reference {0} in component {1} using the default JNDI name {2} and bus name {3}.
Explanation The reference's JMS binding uses an existing resource that is associated with the bus named in the message. The JMS binding does not provide an existing connection factory. A connection factory with the default JNDI name cannot be created for this bus name.
Action Specify a connection factory JNDI name. A connection factory can be created in this situation if it is given a different JNDI name.
CWSOA1610W: The connection factory with JNDI name {0} was not found.
Explanation The create attribute is set to 'never', but the resource does not exists.
Action Make sure to create the resource.
CWSOA1611W: The destination resource with JNDI name {0} was not found.
Explanation The create attribute is set to 'never', but the resource does not exists.
Action Make sure to create the resource.
CWSOA1612W: The activation specification with JNDI name {0} was not found.
Explanation The create attribute is set to 'never', but the resource does not exists.
Action Make sure to create the resource.
CWSOA1613E: An unsupported intent, propagatesTransaction, was found on the binding.atom element in service/reference {0}.
Explanation The propagatesTransaction intent is not supported on binding.atom.
Action Remove the propagatesTransaction intent from the binding.atom element.
CWSOA1614E: An unsupported intent, propagatesTransaction, was found on the binding.jsonrpc element in service/reference {0}.
Explanation The propagatesTransaction intent is not supported on binding.jsonrpc.
Action Remove the propagatesTransaction intent from the binding.jsonrpc element.
CWSOA1700I: A bus named {0} has been created for the JMS binding in component {1}.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA1701I: A bus destination named {0} has been created on bus {1} for the JMS binding in component {2}.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA1702I: A destination resource has been created with JNDI name {0} and arguments "{1}" for the JMS binding in component {2}.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA1703I: An activation specification has been created with JNDI name {0} and arguments "{1}" for the JMS binding in component {2}.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA1704I: A connection factory has been created with JNDI name {0} and arguments "{1}" for the JMS binding in component {2}.
Explanation This message is for informational purposes only.
Action No action is required.
CWSOA1800E: An activation specification {0} cannot be created for the JMS binding used by service {1} in component {2}. The binding uses JMS resources that are not for the default messaging provider.
Explanation JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider.
Action Update the JMS binding to refer to an existing activation specification for the appropriate JMS provider.
CWSOA1801E: A response connection factory {0} cannot be created for the JMS binding used by service {1} in component {2}. The binding uses JMS resources that are not for the default messaging provider.
Explanation JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider.
Action Update the JMS binding to refer to an existing connection factory for the appropriate JMS provider.
CWSOA1802E: A connection factory {0} cannot be created for the JMS binding used by reference {1} in component {2}. The binding uses JMS resources that are not for the default messaging provider.
Explanation JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider.
Action Update the JMS binding to refer to an existing connection factory for the appropriate JMS provider.
CWSOA1803E: A destination {0} cannot be created for the JMS binding used by service {1} in component {2}. The binding uses JMS resources that are not for the default messaging provider.
Explanation JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider.
Action Update the JMS binding to refer to an existing destination for the appropriate JMS provider.
CWSOA1804E: A destination {0} cannot be created for the JMS binding used by reference {1} in component {2}. The binding uses JMS resources that are not for the default messaging provider.
Explanation JMS resources can be created automatically for a JMS binding only if the binding uses the default messaging provider.
Action Update the JMS binding to refer to an existing destination for the appropriate JMS provider.
CWSOA1901E: Duplicate JavaEE applications exist: {0}
Explanation The Java EE applications associated with SCA component implementation must be unique across all of the applications.
Action Ensure that the Java EE application names are unique across all of the applications.
CWSOA1902E: The composition unit targets used in implementation.jee are not matching. {0}
Explanation The CU referred via implementation.jee must be targeted to all servers in which the CU using implementation.jee is targeted.
Action Change targets of composition units to match when using implementation.jee.
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 7:56:37 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.soa.sca.runtime.messages.SCAMessages.html

© Copyright IBM Corporation 2006, 2010. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)