ACC

ACC001 Using the only client {1} with main class {2} in {0} even though it does not match the specified main class name {3} or client name {4}

Cause: The command line specified a main class or a client name different from the main class and name of the only client found.

Solution: The error message lists the main classes and client names for the clients in the JAR. Make sure the command line specifies one of those.

ACC002 The application contains multiple app clients; please choose one using -mainclass {0} or -name {1}

Cause: The command line did not specify a main class or a client name to run, and the JAR contains more than one client.

Solution: Specify either -mainclass your-main-class-name or -name your-client-name on the appclient command.

ACC003 No app client in the app client group {0} matches the main class name "{1}" or the app client name "{2}";\nPlease choose one using -mainclass {3} or -name {4}

Cause: The JAR file contains multiple app clients and none matches the -mainclass value or the -name value that was specified on the appclient command.

Solution: Review the list of main classes and names in the original error message and make sure the appclient command specifies a main class or a name listed.

ACC004 No app clients are listed in the app client group {0}

Cause: The deployment which generated the downloaded JAR file might have failed partially.

Solution: Check the server.log file on the server for any deployment errors.

ACC005 The main method is either not public or not static

Cause: The main method for the app client is not declared as "public."

Cause: The main method for the app client is not declared as "static."

Solution: Declare the main method as "public."

Solution: Declare the main method as "static."

ACC006 The main method's return type is not void

Cause: The main method does not have a return type of "void."

Solution: Declare the main method so its return type is "void."

ACC007 The app client {0,choice,0#file|1#directory} {1} does not contain a manifest; the app client container cannot process it. Embedded programs should pass URIs with scheme "jar:" for JAR files and scheme "file:" for directories.

Cause: The file might not be a valid app client JAR or undeployed EAR. It might be another kind of file or have become corrupted.

Solution: Make sure to specify a valid app client JAR file or an EAR which contains at least one app client.

ACC008 The manifest in the app client facade {0} does not contain the expected entry for {1} or it is invalid; the app client container cannot process it.

Cause: The app client facade JAR file might have generated incorrectly.

Cause: The app client facade JAR file might have become corrupted.

Solution: Check the server's server.log file for any errors during deployment of the application.

Solution: Use the get-client-stubs command to retrieve the generated JAR files for the application again.

ACC009 \nThe credentials you provided (username and password) were not valid or do not\nallow access to the application. Please try again with a valid username and \npassword. If you are certain the username and password are correct please\ncontact your system administrator. The following information might be helpful:\n\n{0}

Cause: The user supplied a username and password combination that are not valid.

Cause: The user supplied a valid username and password but they are not authorized for access to the server-side resource requested.

Solution: Make sure the username and password are correct.

Solution: Make sure the username and password grant the desired access to the requested server-side resource.

ACC010 The user cancelled authentication.

Description: TBD

ACC011 The expected client file {0} is missing. The deployment of the application or retrieval of the app client might have failed.

Cause: The manifest of the generated facade JAR file refers to the specified app client JAR file but that file does not seem to exist.

Solution: Make sure the deployment of the application succeeded and that the download of the app client files (using either "deploy --retrieve" or "get-client-stubs" succeeded.

ACC012 In modifying known loggers, the LogManager reported the logger name {0} which does not have a corresponding logger; continuing

Cause: Somehow a logger name is registered with the LogManager with no corresponding logger.

Solution: Possibly the logging.properties file contains settings which cause this condition.

ACC013 The -password option is deprecated and will likely be removed in a future release. Please use -passwordfile or let the app client container prompt for the username and/or password if they are needed to access a remote resource.

Cause: Specifying the password on the command line exposes the password too easily and is a security risk.

Solution: Consider using the -passwordfile option instead, or allow the app client container to prompt for the username and/or password when access to a protected resource is requested.

ACC014 Launching client {1} with main class {2} in {0} although the client manifest specifies the Main-Class as {3}

Cause: The specified main class name exists in the app client but is different from the Main-Class setting in the app client itself.

Solution: Make sure you really want to launch the app client using a main class other than the one configured in the application