WebSphere ClientWSCL0001I: 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}
Explanation
The parameter values listed were retrieved from three places: 1. the command line (for example,-CCverbose=true) 2. a properties file (for example,-CCpropfile=myapp.properties) 3. system properties (for example,java -Dcom.ibm.CORBA.BootstrapHost=myserver.a.b.com...) The parameters are resolved in the order listed above, with command line values having the highest priority and system properties the lowest.
User Response:
No action is required. The -CCverbose flag was specified on the launchClient command, and this message is a result of setting that flag. It is for information only.
WSCL0002I: Setting DataSource Property {0} to value {1} on DataSource {2}.
Explanation
The application client runtime set the stated property to the stated value on the JDBC Datasource. DataSource properties are configured using the Application Client Resource Configuration Tool
User Response:
No action is required. This is for information only.
WSCL0003I: Establish a setter method on the DataSource {0} for the Property {1}.
Explanation
The application client runtime has established that a method for setting the stated JDBC DataSource property exists.
User Response:
No action is required. This is for information only.
WSCL0004I: Setting resource Property {0} to value {1}.
Explanation
The application client runtime set the stated property to the stated value for the resource.
User Response:
No action is required. This is for information only.
WSCL0005I: JMS resource using supplied JNDI binding mechansim: {0}.
Explanation
The application client runtime is using the stated JNDI binding mechanism for the JMS resource. The binding mechanism specifies a JMS class that provides JMS services to the client and resides on the locally configured client system. The JNDI binding mechanism class can be configured using the Application Client Resource Configuration Tool.
User Response:
No action is required. This is for information only.
WSCL0006I: JMS resource using an indirectly supplied JNDI binding mechansim: {0}.
Explanation
The application client runtime is using the stated JNDI binding mechanism for the JMS resource. This binding mechanism was configured as a link to a JNDI reference located in a remote JNDI namespace and allows the client application to use JMS services. The JNDI binding mechanism can be configured using the Application Client Resource Configuration Tool.
User Response:
No action is required. This is for information only.
WSCL0007I: Loading the default resource binders.
Explanation
The application client runtime is loading the default resource binders. The resource binders allow the application client runtime to load and configure resources used by the client application.
User Response:
No action is required. This is for information only.
WSCL0008I: Adding binder {0} from the properties file.
Explanation
The application client runtime has added the resource binders defined in the properties file. Resource binders defined in the properties file are optional and are used to extend or override the default behavior of the application client runtime.
User Response:
No action is required. This is for information only.
WSCL0009I: No binders were found in the properties file.
Explanation
The properties file contains no resource binders. Resource binders defined in the properties file are optional and are used to extend or override the default behavior of the application client runtime.
User Response:
No action is required. This is for information only.
WSCL0010I: Resource binders loaded successfully.
Explanation
The application client runtime has successfully loaded the resource binders.
User Response:
No action is required. This is for information only.
Explanation
An exception was received by the application client runtime. The stack trace was made available to assist in the problem determination.
User Response:
Analyze the exception and stack trace and correct the problem. For additional help, enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0012I: Processing command line arguments.
Explanation
This is a status message.
User Response:
No action is required. This is for information only.
WSCL0013I: Initializing the J2EE Application Client Environment.
Explanation
This is a status message.
User Response:
No action is required. This is for information only.
WSCL0014I: Invoking the Application Client {0}
Explanation
This is a status message that indicates which class is being started by the launchClient command.
User Response:
No action is required. This is for information only.
WSCL0015I: Processing the Application Client archive file: {0}.
Explanation
The application client runtime is reading and loading the stated application client archive file.
User Response:
No action is required. This is for information only.
WSCL0016I: Using temporary directory {0}.
Explanation
The application client runtime has created the stated temporary directory for use in storing temporary files.
User Response:
No action is required. This is for information only.
WSCL0017I: Loading the Main class {0} for the Application Client jar file {1}.
Explanation
The application client runtime is using a class loader to load the stated main class from the stated application client archive file.
User Response:
No action is required. This is for information only.
WSCL0018I: Processing Resource Provider factory: {0}.
Explanation
The Application Client Resource Configuration Tool is filtering the stated resource provider factories to obtain the pertinent resource providers.
User Response:
No action is required. This is for information only.
WSCL0019I: Found Resource Provider factory of type: {0}.
Explanation
The Application Client Resource Configuration Tool has encountered a resource provider factory of the stated type.
User Response:
No action is required. This is for information only.
WSCL0020I: Processed Resource Provider of type: {0}.
Explanation
The Application Client Resource Configuration Tool has processed a resource provider factory of the stated type.
User Response:
No action is required. This is for information only.
WSCL0021I: Opening archive file: {0}.
Explanation
The Application Client Resource Configuration Tool is opening the stated archive file to obtain the client resource configuration file.
User Response:
No action is required. This is for information only.
WSCL0022I: Searching for the resource respository.
Explanation
The Application Client Resource Configuration Tool is searching for an existing resource repository.
User Response:
No action is required. This is for information only.
WSCL0023I: The resource respository was not found. Creating a new repository: {0}
Explanation
The Application Client Resource Configuration Tool was unable to locate an existing resource repository. A new resource repository is being created with the stated name.
User Response:
No action is required. This is for information only.
WSCL0024I: Adding {0} {1} to the JNDI table.
Explanation
The Application Client Resource Configuration Tool has added the stated entry to the JNDI resource table.
User Response:
No action is required. This is for information only.
WSCL0025I: Binding EJB reference object: JNDI name: {0} Description: {1}
Explanation
The application client runtime is binding the EJB to the local namespace using the stated JNDI name. EJB references are configured using the Application Assembly Tool.
User Response:
No action is required. The -CCverbose flag was specified on the launchClient command, and this message is a result of setting that flag. This is for information only.
WSCL0026I: Adding EJB references defined in the properties file.
Explanation
The application client runtime has added the EJB references defined in the properties file. EJB references specified in a properties file are optional.
User Response:
No action is required. This is for information only.
WSCL0027I: No EJB references defined in the properties file.
Explanation
The properties file contains no EJB references.
User Response:
No action is required. This is for information only.
WSCL0028I: Binding environment entry: JNDI name: {0} Type: {1} Value: {2} Description: {3}
Explanation
The application client runtime is binding the object for the environment entry to the local namespace using the stated JNDI name. Environment entries are configured using the Application Assembly Tool.
User Response:
No action is required. The -CCverbose flag was specified on the launchClient command, and this message is a result of setting that flag. This is for information only.
WSCL0029I: Binding resource reference object: JNDI name: {0} Type: {1} Description: {2}
Explanation
The application client runtime is binding the object for the resource reference entry to the local namespace using the stated JNDI name. Resource references are configured using the Application Assembly Tool.
User Response:
No action is required. The -CCverbose flag was specified on the launchClient command, and this message is a result of setting that flag. This is for information only.
WSCL0030I: No resource provider references configured for this provider.
Explanation
No resource provider references were configured for this provider.
User Response:
No action is required. This is for information only.
WSCL0031I: The object was bound successfully.
Explanation
The object was bound into the local namespace successfully.
User Response:
No action is required. The -CCverbose flag was specified on the launchClient command, and this message is a result of setting that flag. This is for information only.
WSCL0032I: Loading the following URLs with the class loader: {0}
Explanation
The application client runtime is loading the stated URLs. This list is a superset of the resource references that have been configured for this client application with the Application Client Resource Configuration Tool . This helps to determine why a resource reference is not being found.
User Response:
No action is required. This is for information only.
WSCL0033I: The main class was loaded with: {0}
Explanation
The stated class loader was used to load the main class. This is intended to help determine why a different class may fail to load later.
User Response:
No action is required. This is for information only.
WSCL0034I: Binding Enterprise Extension resource {0}
Explanation
The application client runtime is binding the stated enterprise extension resource into the local namespace.
User Response:
No action is required. The -CCverbose flag was specified on the launchClient command, and this message is a result of setting that flag. This is for information only.
WSCL0035I: Initialization of the J2EE Application Client Environment has completed.
Explanation
This is a status message.
User Response:
No action is required. This is for information only.
WSCL0036I: Parsing classpath: {0}
Explanation
The Application Client runtime is parsing the stated classpath string into separate classpath entries.
User Response:
No action is required. This is for information only.
WSCL0100E: Exception received: {0}
Explanation
An exception was received by the application client runtime.
User Response:
Analyze the exception and correct the problem. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0101E: An invalid or missing parameter on launchClient. See help message on launchClient.
Explanation
An invalid or missing parameter was specified on the launchClient command.
User Response:
Determine which parameters were incorrect or missing and correct the error. Specify the -help or -? flag on the launchClient command for additional help.
WSCL0102E: Missing property value for -CC parameter: {0}.
Explanation
The stated -CC parameter was specified without a value on the launchClient command. For example, you may have specified -CCverbose. All -CC parameters require a value to be specified. For example, -CCverbose=true.
User Response:
Specify the property value on the -CC parameter and try again. Specify the -help or -? flag on the launchClient command for additional help.
WSCL0103E: An invalid -CC property value was specified: {0}.
Explanation
A -CC property was specified with an invalid value on the launchClient command.
User Response:
Specify a valid property value for the -CC parameter and try again. Specify the -help or -? flag on the launchClient command for additional help.
WSCL0104E: The required parameter specifying the EAR file for the client application was null.
Explanation
A null or empty string was passed for the Enterprise Archive File (EAR) parameter to the launchClient API. This parameter is required and must point to a valid EAR file.
User Response:
Ensure that you specify the name of a valid EAR file that contains the client application you are attempting to run. You may have to fully qualify the file name. Refer to the launchClient Javadoc for more information.
WSCL0105E: Cannot launch more than one J2EE application per Java Virtual Machine.
Explanation
You tried to launch two different J2EE applications within the same Java Virtual Machine (JVM). The Application Client runtime only allows one application, represented by an Enterprise Archive File (EAR), to be launched within the same JVM. That EAR file can be launched multiple times with different parameters, but it must be the same EAR file. This is because you can only have one JNDI name space active at a time. If you were to launch two applications, they would both use the last JNDI name space to be in initialized. Since this would cause confusion in the programming model, the Application Client runtime only allows one application to be launched per JVM.
User Response:
This is a programming error. The application you are running must be changed to only launch one J2EE application.
WSCL0106W: The parameter {0} has been deprecated and will not be used.
Explanation
The specified parameter is no longer valid and will not be used by the application client Runtime.
User Response:
Remove the specified parameter from your invocation of the application client runtime.
WSCL0120E: The JDBC property {0} is required.
Explanation
A required JDBC property was not specified.
User Response:
Analyze the message data to identify the missing JDBC required property. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0121E: The Class for DataSource {0} was not found: {1}
Explanation
The JDBC DataSource class was not found.
User Response:
Ensure that the DataSource class exists and place it in the classpath so that it may be located by the application client runtime. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0122E: Received an IllegalAccessException while attempting to access or create DataSource {0}: {1}
Explanation
The application client runtime received an IllegalAccessException when attempting to access the JDBC DataSource. The JDBC DataSource class is protected and cannot be accessed by the application client runtime.
User Response:
Change the JDBC DataSource to be publicly available. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0123E: Received an IllegalAccessException while attempting to access Property {0} on DataSource {1}: {2}
Explanation
The application client runtime received an IllegalAccessException when attempting to access the JDBC DataSource access or method to obtain the DataSource property.
User Response:
Change the JDBC DataSource access or method to be publicly available. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0124E: Received an InstantiationException while attempting to create DataSource {0}: {1}
Explanation
The application client runtime received an InstantiationException when attempting to instantiate the JDBC DataSource. The JDBC Datasource is defined as either abstract or an interface.
User Response:
Change the JDBC Datasource to be a concrete class.
WSCL0125E: Received an IllegalArgumentException while attempting to set the value for DataSource Property {0} on DataSource {1}. Unknown parameters are required. : {2}
Explanation
The application client runtime received an IllegalArgumentException when attempting to set a property on the JDBC Datasource. Each JDBC Datasource property requires a method to enable setting the property with the only parameter being the property value.
User Response:
Ensure that the JDBC Datasource property set method exists and only expects one parameter containing the property value.
WSCL0126E: Received an InvocationTargetException while attempting to set the value for DataSource Property {0} on DataSource {1}: {2}
Explanation
The application client runtime received an InvocationTargetException when attempting to set a property on the JDBC Datasource. Each JDBC Datasource property requires a method to enable setting the property with the only parameter being the property value.
User Response:
Ensure that the JDBC Datasource property set method exists and only expects one parameter containing the property value. Analyze the message data for the InvocationTargetException to determine the cause of the problem. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0127W: Encountered an unsupported DataSource Property {0}: {1}
Explanation
The defined JDBC Datasource property is not supported. The application client runtime has ignored this property and continued processing.
User Response:
No action is required. Warning message only. To prevent this warning message in the future, remove the defined property from the JDBC Datasource. Use the Application Client Resource Configuration Toolt o make the necessary modifications to the JDBC Datasource.
WSCL0128E: Unable to establish a setter method for Property {0} on DataSource {1}.
Explanation
The application client runtime was unable to establish a method for setting a property on the JDBC DataSource. Each JDBC DataSource property requires a method to enable setting the property with the only parameter being the property value.
User Response:
Ensure that the JDBC DataSource property set method exists and only expects one parameter containing the property value. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0129E: The DataSource classname {0} is not of the required type javax.sql.DataSource.
Explanation
The JDBC Datasource is required to be of type javax.sql.DataSource.
User Response:
Change the JDBC Datasource to be of type javax.sql.DataSource.
WSCL0130E: The specified object reference for creating of the DataSource is not of the required type javax.naming.Reference.
Explanation
The object reference for the JDBC Datasource is required to be of type javax.naming.Reference.
User Response:
Change the object reference for the JDBC Datasource to be of type javax.naming.Reference.
WSCL0131E: Received an IntrospectionException while attempting to introspect DataSource {1}: {2}
Explanation
The application client runtime received an IntrospectionException when attempting to process the JDBC Datasource.
User Response:
Analyze the exception message data and correct the problem. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0150W: Unknown JMS resource type: {0}
Explanation
The stated JMS Resource is of an unknown type. The JMS Resource is required to be of type Destination or Connection.
User Response:
Ensure that the JMS Resource is of type Destination or Connection. Use the Application Client Resource Configuration Tool to make the necessary modifications to the JMS Resource. For additional help enable debug by specifying the -CCtrace flag on the launchClient command.
WSCL0151W: The property value for Property {0} for the {1} Resource was set to an invalid value of {2}.
Explanation
The stated property for the stated resource was either not a valid type or was not set. The property must be of type java.lang.String, java.lang.Boolean or java.lang.Integer. Properties for resources are configured using the Application Client Resource Configuration Tool . This property was ignored.
User Response:
Ensure the property value is set to a valid type.
WSCL0152W: The Class for the JNDI binding mechanism {0} was not found.
Explanation
The application client runtime was unable to find the class for instantiating the stated JMS binding mechanism. The JNDI binding mechanism is configured using the Application Client Resource Configuration Tool.
User Response:
Ensure that the JMS binding mechanism class exists and is available in the classpath.
WSCL0153W: The required constructor for the JNDI binding mechanism {0}(java.util.Properties) was not found: {1}
Explanation
The application client runtime was unable to instantiate an instance of the stated JMS binding mechanism. The JMS binding mechanism is required to have a class constructor that has one parameter of type java.util.Properties. This binding mechanism class is a user written class and is not supplied by WebSphere.
User Response:
Ensure that the JMS binding mechanism has a constructor with one parameter of type java.util.Properties.
WSCL0154W: Unable to construct an instance of JNDI binding mechanism {0}(java.util.Properties)
Explanation
The application client runtime failed to execute the stated class constructor due to an unexpected error.
User Response:
A programming error exists in the constructor. Analyze the exception received and correct the problem.
WSCL0155W: The URL specification {0} is not valid.
Explanation
The application client runtime was unable to create a URL for the stated URL specification. The URL specified in the client resource configuration file is not properly formed.
User Response:
Correct the URL specification by using the Application Client Resource Configuration Tool.
WSCL0156W: Unable to create a URL resource because:
Explanation
The application client runtime received an unexpected exception while creating the URL resource.
User Response:
Analyze the stated exception received and correct the problem.
WSCL0157W: Unable to decode the password for resource {0} when attempting to set property {1}.
Explanation
The application client runtime was unable to decode the password for the stated resource. The encoding scheme used when the password was encoded is not valid.
User Response:
Correct the password in the client resource configuration file by using the Application Client Resource Configuration Tool.
WSCL0158W: Unable to create a mail resource with properties: {0} because:
Explanation
The application client runtime received an unexpected exception while creating the stated mail resource.
User Response:
Analyze the stated exception received and correct the problem.
WSCL0159W: Unable to create a data source resource with properties: {0} because:
Explanation
The application client runtime received an unexpected exception while creating the stated Datasource resource.
User Response:
Analyze the stated exception received and correct the problem.
WSCL0160W: An unexpected classloader {0} was used to load class {1} for resource {2}.
Explanation
A classpath was specified in the resource configuration file for the stated resource, however the Application Client runtime loaded the stated class using a different classloader than the one created by the Application Client runtime. In most cases, this indicates the stated class was found in the system classpath. This may later cause exceptions such asjava.lang.ClassNotFoundExceptionandjava.lang.NoClassDefFoundErrorwhen the stated class attempts to load other classes. This is a warning only and the stated class was successfully loaded, but the classpath specified in the resource configuration file will not be used.
User Response:
Search through the classpath's specified with the -CCclasspath option and locate the .class file or the jar file that contains the stated class. If you are not using the launchClient command file, you will have to search the system classpath as well. Once you locate the class, remove it and rerun launchClient. Use the Application Client Resource Configuration Tool to configure classpath information for this resource.
WSCL0161E: The resource configuration information is not compatible with the resource type {0}. The object was not bound into the namespace.
Explanation
This resource was configured as the stated type when assembling the Application Client using the Application Assembly Tool. The Application Client runtime found a resource with the same name in the client resource configuration file, however, the client resource configuration information is not compatible with the stated resource type.
User Response:
If the stated type is correct, then use the Application Client Resource Configuration Tool to find the resource with the matching name and delete it, then configure the resource for the appropriate type. If the stated type is incorrect, then use the Application Assembly Tool to configure the correct type.
WSCL0200E: The Enterprise Archive file {0} does not contain an Application Client jar file.
Explanation
The application client runtime was unable to locate the client application jar file in the stated client application Enterprise Archive File (EAR). This may happen for several reasons: - The specified file is not an EAR file. - The specified file is a valid EAR file but does not contain an application client. - The specified EAR file does not match the J2EE version of the application client runtime. - The specified EAR file was not built by the WebSphere Application Assembly Tool.
User Response:
Use the Application Assembly Tool to reassemble the EAR file and be sure to include the application client.
WSCL0201E: No manifest entry found in Application Client jar file {0}.
Explanation
The application client runtime was unable to locate a manifest file in the stated application client jar file. The manifest contains meta data for the J2EE application client and is required.
User Response:
Use the Application Assembly Tool to reassemble the application client jar file. This will add the manifest to the proper path in the application client jar file. Then use the Application Assembly Tool to reassemble the Enterprise Archive file.
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.
Explanation
The application client runtime was unable to locate a manifest entry identifying the main class for the stated application client in the stated Enterprise Archive file.
User Response:
Use the Application Assembly Tool to modify the application client jar file. In the main class field specify the fully-qualified name of the class that you wish to start with the launchClient command. For example, 'com.myCompany.myApp.myClass'.
WSCL0203E: Unable to locate the Application Client jar file {0} in the Enterprise Archive file {1}.
Explanation
The application client runtime was unable to locate the stated application client jar file in the stated Enterprise Archive file. This error occurs when the -CCjar filename parameter is used, and the specified jar file does not exist in the Enterprise Archive file.
User Response:
Change the value for the -CCjar filename parameter to a jar file that exists in the Enterprise Archive file. If the jar file you need is not in the Enterprise Archive file, use the Application Assembly Tool to add the application client jar file to the Enterprise Archive file.
WSCL0204W: Failed to start the process to remove the temporary directory {0}.
Explanation
The application client runtime was unable to start the process used to remove the stated temporary directory that the runtime created.
User Response:
Locate the stated temporary directory and manually remove the directory and files. They are no longer needed and are wasting space on the hard drive. This error generally occurs when java.exe is not in your system path. To prevent this error in the future, locate java.exe and add its path to your system path.
WSCL0205W: The incorrect class loader was used to load {0}
Explanation
The Application Client runtime attempted to load the stated main class from the Enterprise Archive (EAR) file, but another version of the main class was found in one of the application classpath's first. This resulted in the main class being loaded from the hard drive instead of the EAR file. In most cases, this is a severe error that will cause the user program to fail later with exceptions such as java.lang.ClassNotFoundException and java.lang.NoClassDefFoundError when attempting to load EJB's or other classes from the EAR file.
User Response:
Search through the classpath's specified with the -CCclasspath option and the classpath's configured with the Application Client Resource Configuration Tool to locate the .class file or the jar file that contains the main class. If you are not using the launchClient command file, you will have to search the system classpath as well. Once you locate the class, remove it and rerun launchClient.
WSCL0206E: File {0} is not a valid Enterprise Archive file.
Explanation
The stated file was passed to the Application Client runtime, but it does not conform to the Enterprise Archive (EAR) file format.
User Response:
This may happen for one of the following reasons: - The file does not exist. Specify a different file on the launchClient command - The file you specified is not an Enterprise Archive (EAR) file. Your application must be packaged within an Application Client jar file, and this jar file must be packaged within an EAR file. Use the Application Assembly Tool to add your application to an Application Client jar file. Then add your Application Client jar file to an EAR file and rerun launchClient with the EAR file - Your EAR file may be corrupted or built incorrectly. Use the Application Assembly Tool to resave the EAR file. This may correct the error.
WSCL0207E: Jar file {0} in Enterprise Archive file {1} is not an Application Client jar file.
Explanation
The stated jar file name was passed to launchClient with the -CCjar parameter. The jar file exists in the stated Enterprise Archive (EAR) file, but it is not an Application Client jar file.
User Response:
If you remove the -CCjar parameter from the launchClient invocation, the Application Client runtime will automatically locate the Application Client jar file in your EAR file. If you have more than one Application Client jar file in your EAR file, however, you will need to use the -CCjar parameter. If you would like the stated jar file to be an Application Client jar file, perform the following steps in the Application Assembly Tool: 1. Create an Application Client module and add your jar file's contents 2. Delete the existing jar file from your EAR and add the new Application Client module.
WSCL0208E: System property {0} cannot be set to a file.
Explanation
The stated system property was set to a filename, but it should be set to a directory.
User Response:
Change the value of the stated system property to a directory. If your ear file has already been extracted to the hard drive, you can change the value of the system property to the root directory where it was extracted. If you would like the launchClient command to extract the ear file, specify the desired target directory.
WSCL0209E: Failed to create archive directory {0}.
Explanation
The Application Client system property com.ibm.websphere.client.applicationclient.archivedir was set to the stated directory value, and the Application Client runtime failed to create the directory.
User Response:
This is usually caused by specifying a directory value that has multiple subdirectories that don't exist. The Application Client runtime will only create the last subdirectory specified. For example, if you specify "/A/B/C" and subdirectories A or B do not exist, you will receive this failure. With this example, the Application Client runtime will only create the subdirectory C. The other possible failure is you don't have authority to write to the specified directory. If this is the case, you need to specify a different directory or change the directory permissions.
WSCL0210E: The Enterprise archive file {0} could not be found.
Explanation
The specified Enterprise archive file could not be found because either the file name or path are incorrect.
User Response:
Correct the path or the file name and try your request again. If the file name contains spaces, then enclose the file name within quotes, for example, launchClient "my client app.ear".
WSCL0211E: The specified client jar file {0} is configured with multiple deployment descriptors. Use the -CCaltDD parameter to specify which one should be used.
Explanation
The specified application client jar file is configured to use alternate deployment descriptors.
User Response:
Use the -CCaltDD parameter to specify the path to the alternate deployment descriptor. To use the standard deployment descriptor specify the value null on the -CCaltDD parameter.
WSCL0212E: The specified client jar file {0} with the specified alternate deployment descriptor {1} can not be found in the Enterprise archive file.
Explanation
The jar file specified by the -CCjar parameter with deployment descriptor specified by the -CCaltDD parameter cannot be found within the Enterprise archive file.
User Response:
Modify either the -CCjar parameter or the -CCaltDD parameter to specify an application client module within the Enterprise archive file and try your request again.
WSCL0213E: The specified client jar file {0} with the specified alternate deployment descriptor {1} is not an application client archive module.
Explanation
The jar file specified by the -CCjar parameter with deployment descriptor specified by the -CCaltDD parameter is not a application client jar file within the Enterprise archive file.
User Response:
Modify the -CCjar parameter and the -CCaltDD parameter to specify an application client module within the Enterprise archive file and try your request again.
WSCL0220E: An unsuccessful attempt was made to find the resource configuration information for {0}.
Explanation
The application client runtime was unable to locate the resource configuration information for the stated resource because the name of the resource does not match the JNDI name used when the resource was configured using the Application Client Resource Configuration Tool.
User Response:
Use the Application Client Resource Configuration Tool to change the JNDI name to equal the resource name value that was stated in the message. The resource name value was configured using the Application Assembly Tool.
WSCL0280W: An EJB object could not be created because the name is null.
Explanation
The application client runtime was unable to create a reference to an EJB because the value specified on the
entry in the application client deployment descriptor contains an invalid name. This can happen if the deployment descriptor was created without using the Application Assembly tool.
User Response:
Verify the value specified on the
entry in the application client deployment descriptor contains a valid name or use the Application Assembly tool to configure this EJB resource. WSCL0300W: An environment object could not be created for {0} because the value of {1} is not valid for type {2}.
Explanation
The application client runtime was unable to create an environment object because the value specified on the
entry in the application client deployment descriptor does not contain a valid value for the type specified on the entry. This can occur if the deployment descriptor was created without using the Application Assembly Tool.
User Response:
Change the value specified on the
entry in the application client deployment descriptor to a valid value for the type specified on the entry. Or use the Application Assembly Tool to configure a value that is valid for the type specified. WSCL0301W: An environment object could not be created for {0} because the type {1} is not supported.
Explanation
The application client runtime was unable to create an object defined by the
in the application client deployment descriptor because the type specified for the is not valid. This can occur if the deployment descriptor was created without using the Application Assembly Tool.
User Response:
Change the type specified on the
in the application client deployment descriptor to a valid type or use the Application Assembly Tool to modify the type. The valid types are: java.lang.Boolean, java.lang.String, java.lang.Integer, java.lang.Double, java.lang.Byte, java.lang.Short, java.lang.Long, and java.lang.Float. 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.
Explanation
The application client runtime was unable to update the classpath for the stated resource because the classpath is not in the correct format.
User Response:
Use the Application Client Resource Configuration Tool to change the stated classpath.
WSCL0331E: An unexpected error occurred while trying to create URL stream handler class {0} for protocol {1}.
Explanation
The Application Client runtime was unable to create the stated URL stream handler class for the stated protocol. This is most likely because the stream handler class was specified incorrectly when the URL provider was configured or the stated stream handler class could not be found in the classpath.
User Response:
Use the Application Client Resource Configuration Tool to find the URL provider for the stated protocol and verify that the stream handler class field value and the classpath field value are correct.
WSCL0332E: The resource configuration file is at the incorrect version. Please use the Application Client Resource Configuration Tool (clientConfig command) to migrate the resources.
Explanation
The resource configuration information contained in the application client module was created with a previous version of WebSphere.
User Response:
Run the clientConfig command to have your resources migrated to a format that can be used by this version of WebSphere.
WSCL0350W: Unable to create a resource for {0} because the following error occurred:
Explanation
The application client runtime encountered an unexpected exception while creating the stated resource.
User Response:
Analyze the stated exception received and correct the problem.
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
entry is one of the following: {2}
Explanation
The application client runtime was unable to create the stated resource because the resource type specified by the
element in the application client deployment descriptor was not supported. This can occur if the deployment descriptor was created without using the Application Assembly Tool.
User Response:
Change the type specified on the
entry to one of the stated supported types or use the Application Assembly Tool to configure the resource. WSCL0370W: An unexpected error occurred while trying to bind an Enterprise Extension resource.
Explanation
The application client runtime encountered an unexpected exception while binding an Enterprise Extension resource. The message that follows provides detailed information about the exception.
User Response:
Analyze the exception and correct the problem.
WSCL0400I: Binding resource environment reference object: JNDI name: {0} Type: {1} Description: {2}
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0500I: Creating security callback handler class: {0}
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0501I: Security callback handler created successfully.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0502E: Security callback handler class could not be created because:
Explanation
A error occurred when creating the security callback handler class. The most likely cause of this error is the security callback handler class specified could not be found either because the name is incorrect or it could not be loaded by the WebSphere classloaders.
User Response:
Verify the classname is a fully qualified classname using java class notation, for example, com.mypackage.mysecclass. Also verify the actual class code is is accessible by the WebSphere classloaders. You may have to specify -CCclasspath parameter to have the WebSphere application client runtime find your class.
WSCL0503E: The configured callback handler class {0} cannot be used because it does not implement the {1} interface.
Explanation
The security callback handler class must implement the specified interface. This is a programming error in the security callback handler class.
User Response:
Either have the developer of the specified security callback handler class modify the class so that it implements the specified interface or remove the callback configuration from the application client's deployment descriptor.
WSCL0600I: Binding HandleDelegate object.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0601E: The HandleDelegate could not be bound because:
Explanation
The HandleDelegate object could not be bound into the JNDI name space.
User Response:
Correct the listed errors and try your request again.
WSCL0700E: The JMS classname {0} is not of the required type.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSCL0701E: The specified object reference for creating the JMS object is not of the required type javax.naming.Reference.
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
WSCL0702E: Unable to establish a setter method for Property {0} on JMS object {1}.
Explanation
The application client runtime attempted to set a property, however that property could not be set because it does not exist on the specified JMS object. This is usually caused when a custom property is incorrectly specified for the JMS resource. Custom properties for a resource are configured by the Application Client Resource Configuration Tool.
User Response:
Run the clientConfig command to correct the custom property for the specified JMS resource.
WSCL0703E: Received an IllegalAccessException while attempting to access Property {0} on JMS object {1}: {2}
Explanation
The application client runtime attempted to set the specified property, however the application client runtime does not have access to the definition of the specified class, because the class is not public and in another package. This is usually caused when a custom property is incorrectly specified for the JMS resource. Custom properties for a resource are configured by the Application Client Resource Configuration Tool.
User Response:
Run the clientConfig command to correct or remove the custom property for the specified JMS resource.
WSCL0704E: Received an IllegalArgumentException while attempting to set the value for Property {0} on JMS object {1} : {2}
Explanation
The application client runtime attempted to set the specified custom property, however the value specified is not of the right type or cannot be converted from a string to the correct type. Custom properties for a resource are configured by the Application Client Resource Configuration Tool.
User Response:
Run the clientConfig command to correct the value for the specified custom property for the specified JMS resource.
WSCL0705E: Received an InvocationTargetException while attempting to set the value for Property {0} on JMS object {1} : {2}
Explanation
The application client runtime attempted to set the specified custom property, however the method on the JMS resource object used to set the property threw an exception. Custom properties for a resource are configured by the Application Client Resource Configuration Tool.
User Response:
Run the clientConfig command and verify the value for the custom property is valid for the specified property on the JMS resource object. Refer to the JMS provider's documentation for a list of valid properties and their values.
WSCL0800I: Creating security manager: {0}
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0801I: Security manager created and enabled successfully.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0802W: A security manager is already enabled for this process. The specified security manager {0} will not be used.
Explanation
The application client runtime attempted to set the specified security manager for the Java process, however a security manager is already enabled for this process. The application client runtime will continue to use the security manager that is already set and will not use the specified security manager.
User Response:
Either run the application client runtime without a security manager or set the -CCsecurityManager to disable.
WSCL0803E: Unable to continue because the specified security manager could not be created for the following reason:
Explanation
The -CCsecurityManager parameter was set to enable and a security manager class was specifed using -CCsecurityManagerClass parameter, however the application client runtime could not create the security manager class. The most likely cause of this error is the security manager class specifed could not be found either because the name is incorrect or it could not be loaded by the WebSphere classloaders.
User Response:
Verify the classname is a fully qualified classname using java class notation, for example, com.mypackage.mysecclass. Also verify the actual class code is is accessible by the WebSphere classloaders. You may have to specify -CCclasspath parameter to have the WebSphere application client runtime load your class.
WSCL0900I: Initializing and starting components.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0901I: Component initialization completed successfully.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0902I: Component initialization completed, however some components failed to initialize.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0903E: Component initialization failed for the following reason:
Explanation
A error occurred initializing a component.
User Response:
Correct the listed errors and try your request again.
WSCL0910I: Initializing component: {0}
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0911I: Component initialized successfully.
Explanation
None
User Response:
No action is required. This is for information only.
WSCL0912E: Component failed to initialize.
Explanation
The application client runtime could not initialize a component.
User Response:
See the previously listed errors for the cause of the failure. To see which component failed, rerun the application client runtime with -CCverbose=true option.