WSCL

WSCL0001I: Command line, property file, and system property arguments resolved to: File to launch = {0} CC Property File = {1} Client Jar File = {2} Alternate DD = {3} BootstrapHost = {4} BootstrapPort = {5} Trace enabled = {6} Tracefile = {7} Init only = {8} Classpath Parameter = {9}
WSCL0002I: Setting DataSource Property {0} to value {1} on DataSource {2}.
WSCL0003I: Establish a setter method on the DataSource {0} for the Property {1}.
WSCL0004I: Setting resource Property {0} to value {1}.
WSCL0005I: JMS resource using supplied JNDI binding mechanism: {0}.
WSCL0006I: JMS resource using an indirectly supplied JNDI binding mechansim: {0}.
WSCL0007I: Loading the default resource binders.
WSCL0008I: Adding binder {0} from the properties file.
WSCL0009I: No binders were found in the properties file.
WSCL0010I: Resource binders loaded successfully.
WSCL0011I: Stack Trace: {0}
WSCL0012I: Processing command line arguments.
WSCL0013I: Initializing the Java EE Application Client Environment.
WSCL0014I: Invoking the Application Client {0}
WSCL0015I: Processing the Application Client archive file: {0}.
WSCL0016I: Using temporary directory {0}.
WSCL0017I: Loading the Main class {0} for the Application Client jar file {1}.
WSCL0018I: Processing Resource Provider factory: {0}.
WSCL0019I: Found Resource Provider factory of type: {0}.
WSCL0020I: Processed Resource Provider of type: {0}.
WSCL0021I: Opening archive file: {0}.
WSCL0022I: Searching for the resource respository.
WSCL0023I: The resource respository was not found. Creating a new repository: {0}
WSCL0024I: Adding {0} {1} to the JNDI table.
WSCL0025I: Binding EJB reference object: JNDI name: {0} Description: {1}
WSCL0026I: Adding EJB references defined in the properties file.
WSCL0027I: No EJB references defined in the properties file.
WSCL0028I: Binding environment entry: JNDI name: {0} Type: {1} Value: {2} Description: {3}
WSCL0029I: Binding resource reference object: JNDI name: {0} Type: {1} Description: {2}
WSCL0030I: No resource provider references configured for this provider.
WSCL0031I: The object was bound successfully.
WSCL0032I: Loading the following URLs with the class loader: {0}
WSCL0033I: The main class was loaded with: {0}
WSCL0034I: Binding Enterprise Extension resource {0}
WSCL0035I: Initialization of the Java EE Application Client Environment has completed.
WSCL0036I: Parsing classpath: {0}
WSCL0100E: Exception received: {0}
WSCL0101E: An invalid or missing parameter on launchClient. See help message on launchClient.
WSCL0102E: Missing property value for -CC parameter: {0}.
WSCL0103E: An invalid -CC property value was specified: {0}.
WSCL0104E: The required parameter specifying the EAR file for the client application was null.
WSCL0105E: Cannot launch more than one Java EE application per Java Virtual Machine.
WSCL0106W: The parameter {0} has been deprecated and will not be used.
WSCL0120E: The JDBC property {0} is required.
WSCL0121E: The Class for DataSource {0} was not found: {1}
WSCL0122E: Received an IllegalAccessException while attempting to access or create DataSource {0}: {1}
WSCL0123E: Received an IllegalAccessException while attempting to access Property {0} on DataSource {1}: {2}
WSCL0124E: Received an InstantiationException while attempting to create DataSource {0}: {1}
WSCL0125E: Received an IllegalArgumentException while attempting to set the value for DataSource Property {0} on DataSource {1}. Unknown parameters are required. : {2}
WSCL0126E: Received an InvocationTargetException while attempting to set the value for DataSource Property {0} on DataSource {1}: {2}
WSCL0127W: Encountered an unsupported DataSource Property {0}: {1}
WSCL0128E: Unable to establish a setter method for Property {0} on DataSource {1}.
WSCL0129E: The DataSource classname {0} is not of the required type javax.sql.DataSource.
WSCL0130E: The specified object reference for creating of the DataSource is not of the required type javax.naming.Reference.
WSCL0131E: Received an IntrospectionException while attempting to introspect DataSource {1}: {2}
WSCL0150W: Unknown JMS resource type: {0}
WSCL0151W: The property value for Property {0} for the {1} Resource was set to an invalid value of {2}.
WSCL0152W: The Class for the JNDI binding mechanism {0} was not found.
WSCL0153W: The required constructor for the JNDI binding mechanism {0}(java.util.Properties) was not found: {1}
WSCL0154W: Unable to construct an instance of JNDI binding mechanism {0}(java.util.Properties)
WSCL0155W: The URL specification {0} is not valid.
WSCL0156W: Unable to create a URL resource because:
WSCL0157W: Unable to decode the password for resource {0} when attempting to set property {1}.
WSCL0158W: Unable to create a mail resource with properties: {0} because:
WSCL0159W: Unable to create a data source resource with properties: {0} because:
WSCL0160W: An unexpected classloader {0} was used to load class {1} for resource {2}.
WSCL0161E: The resource configuration information is not compatible with the resource type {0}. The object was not bound into the namespace.
WSCL0162W: The following classpath entries do not exist on the local system: {0}
WSCL0200E: The Enterprise Archive file {0} does not contain an Application Client jar file.
WSCL0201E: No manifest entry found in Application Client jar file {0}.
WSCL0202E: The manifest file for the Application Client jar file {0} located in the Enterprise Archive file {1} does not contain a Main-Class entry for the client application main class.
WSCL0203E: Unable to locate the Application Client jar file {0} in the Enterprise Archive file {1}.
WSCL0204W: Failed to start the process to remove the temporary directory {0}.
WSCL0205W: The incorrect class loader was used to load {0}
WSCL0206E: File {0} is not a valid Enterprise Archive file.
WSCL0207E: Jar file {0} in Enterprise Archive file {1} is not an Application Client jar file.
WSCL0208E: System property {0} cannot be set to a file.
WSCL0209E: Failed to create archive directory {0}.
WSCL0210E: The Enterprise archive file {0} could not be found.
WSCL0211E: The specified client jar file {0} is configured with multiple deployment descriptors. Use the -CCaltDD parameter to specify which one should be used.
WSCL0212E: The specified client jar file {0} with the specified alternate deployment descriptor {1} cannot be found in the Enterprise archive file.
WSCL0213E: The specified client jar file {0} with the specified alternate deployment descriptor {1} is not an application client archive module.
WSCL0220E: An unsuccessful attempt was made to find the resource configuration information for {0}.
WSCL0280W: An EJB object could not be created because the name is null.
WSCL0300W: An environment object could not be created for {0} because the value of {1} is not valid for type {2}.
WSCL0301W: An environment object could not be created for {0} because the type {1} is not supported.
WSCL0330W: Unable to update the classpath for resource {0} because the classpath {1} specified in the client resource configuration file is not in the correct format.
WSCL0331E: An unexpected error occurred while trying to create URL stream handler class {0} for protocol {1}.
WSCL0332E: The resource configuration file is at the incorrect version. Use the Application Client Resource Configuration Tool (clientConfig command) to migrate the resources.
WSCL0350W: Unable to create a resource for {0} because the following error occurred:
WSCL0351W: Unable to create a resource for {0} because the resource type {1} specified in the Application Client deployment descriptor is not supported. Verify the type specified on the <res-type> entry is one of the following: {2}
WSCL0370W: An unexpected error occurred while trying to bind an Enterprise Extension resource.
WSCL0400I: Binding resource environment reference object: JNDI name: {0} Type: {1} Description: {2}
WSCL0401I: Binding message destination reference object: JNDI name: {0} Type: {1} Description: {2}
WSCL0500I: Creating security callback handler class: {0}
WSCL0501I: Security callback handler created successfully.
WSCL0502E: Security callback handler class could not be created because:
WSCL0503E: The configured callback handler class {0} cannot be used because it does not implement the {1} interface.
WSCL0600I: Binding HandleDelegate object.
WSCL0601E: The HandleDelegate could not be bound because:
WSCL0700E: The JMS classname {0} is not of the required type.
WSCL0701E: The specified object reference for creating the JMS object is not of the required type javax.naming.Reference.
WSCL0702E: Unable to establish a setter method for Property {0} on object {1}.
WSCL0703E: Received an IllegalAccessException while attempting to access Property {0} on object {1}: {2}
WSCL0704E: Received an IllegalArgumentException while attempting to set the value for Property {0} on object {1} : {2}
WSCL0705E: Received an InvocationTargetException while attempting to set the value for Property {0} on JMS object {1} : {2}
WSCL0800I: Creating security manager: {0}
WSCL0801I: Security manager created and enabled successfully.
WSCL0802W: A security manager is already enabled for this process. The specified security manager {0} will not be used.
WSCL0803E: Unable to continue because the specified security manager could not be created for the following reason:
WSCL0900I: Initializing and starting components.
WSCL0901I: Component initialization completed successfully.
WSCL0902I: Component initialization completed, however some components failed to initialize.
WSCL0903E: Component initialization failed for the following reason:
WSCL0910I: Initializing component: {0}
WSCL0911I: Component initialized successfully.
WSCL0912E: Component failed to initialize.
WSCL1001E: The Java EE Connector Architecture specification version must be, at a minimum, 1.5 for the resource adapter. The resource adapter is not installed
WSCL1002E: The resource adapter does not contain any outbound resource adapter definitions. The resource adapter is not installed.
WSCL1003E: Error extracting archive: directory {0} does not exist or is not a directory.
WSCL1101I: The specified installed connectors directory {0} does not exist.
WSCL1102W: The specified installed connectors directory {0} is not a directory.
WSCL1201E: The following injection exception occurred for the handling PostConstruct method: {0}
WSCL1202E: The following injection exception occurred for the handling PreDestroy method: {0}
WSCL1203W: More than one PostConstruct or PreDestroy method exists in the {1} class. The {0} PostConstruct or PreDestroy method will not be invoked by the container.
WSCL1204E: The container cannot create an EntityManagerFactory object in the {0} persistence unit for dependency injection. The persistence unit is in the {2} client module of the {1} application.
WSCL1205W: A duplicate binding entry found for {0} name {1}.
WSCL1206E: The NamingException occurred while trying to resolve a resource reference for: {0}


Terms and conditions for information centers | Feedback

Last updated: November 13, 2013 05:41 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=com.ibm.ws.client.applicationclient.ResourceBundle.dita
File name: com.ibm.ws.client.applicationclient.ResourceBundle.html