Glassfish server open source edition 4.1.1 – error report

NCLS-CFGAPI-00121 Failed to get active configuration for {0} under the target {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CFGAPI-00122 Failed to create a ClassLoader for modules directory.

Cause: The modules directory ClassLoader could not be created due toan I/O error.
Action: Take appropriate action based on the error stack tracereported.

NCLS-CFGAPI-00123 Cannot add new configuration extension to the extension point.

Cause: An I/O error occurred during configuration extension addition.
Action: Take appropriate action based on the error stack tracereported.

NCLS-CFGAPI-00124 Can not read default configuration.

Cause: An I/O error occurred.
Action: Take appropriate action based on the error stack tracereported.

NCLS-CFGAPI-00125 Exception while creating the command model for the generic command {0}.

Cause: An error occurred.
Action: Take appropriate action based on the error details in the log.

NCLS-CFGAPI-00126 The Config Bean {0} cannot be loaded by the generic command implementation.

Cause: The config bean class could not be loaded.
Action: Take appropriate action based on the error stack tracereported.

NCLS-CFGAPI-00127 Invalid annotated type {0} passed to InjectionResolver:getValue()

Cause: Invalid annotated type.
Action: Take appropriate action based on the error message details inthe log.

NCLS-CFGAPI-00128 Failure while getting List<?> values from component

Cause: Generic CRUD command invocation failure
Action: Take appropriate action based on the error message details inthe log.

NCLS-CFGAPI-00129 The List type returned by {0} must be a generic type.

Cause: Generic CRUD command invocation failure
Action: Take appropriate action based on the error message details inthe log.

NCLS-CFGAPI-00130 The generic type {0} is not supported, only List<? extends ConfigBeanProxy> is supported.

Cause: Generic CRUD command invocation failure
Action: Provide a supported generic type.

NCLS-CFGAPI-00131 Failure while instrospecting {0} to find all getters and setters.

Cause: Generic CRUD command invocation failure
Action: Provide a supported generic type.

NCLS-CFGAPI-00132 Transaction exception while injecting {1}.

Cause: Generic CRUD command invocation failure
Action: Take appropriate action based on the error message details inthe log.

NCLS-CFGAPI-00133 The CrudResolver {0} could not find the configuration object of type {1} where instances of {2} should be removed.

Cause: Generic delete command invocation failure
Action: Take appropriate action based on the error message details inthe log.

NCLS-CFGAPI-00134 Exception while creating access checks for generic command {0}.

Cause: An error occurred.
Action: Take appropriate action based on the error details in the log.

NCLS-CFGAPI-00135 Cannot identify getter method for ListingColumn

Cause: An error occurred.
Action: Take appropriate action based on the error details in the log.

NCLS-CFGAPI-00136 An error occurred while invoking getter {0} on ConfigBeanProxy.

Cause: An error occurred.
Action: Take appropriate action based on the error details in the log.

NCLS-CFGAPI-00137 Failure while upgrading http-service properties.

Cause: An error occurred.
Action: Take appropriate action based on the error details in the log.

NCLS-GFLAUNCHER-00001 Single and double quote characters are not allowed in the CLASSPATH environmental variable. They were stripped out for you.nBefore: {0}nAfter: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-GFLAUNCHER-00002 Error Launching: {0}

Cause: As described in the message.
Action: Fix the CLASSPATH

NCLS-GFLAUNCHER-00003 Could not locate the flashlight agent here: {0}

Cause: As described in the message.
Action: Find the agent file.

NCLS-GFLAUNCHER-00004 Will copy glassfish/lib/templates/server.policy file to domain before upgrading.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-GFLAUNCHER-00005 JVM invocation command line:{0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00000 Caught an Exception: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00001 Caught an Exception: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00005 Missing Module ({0}) From Xml Probe Providers

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00104 Unable to load the ProbeProvider

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00105 Unable to load the ProbeProvider

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00109 mbean-enabled flag is turned on. Enabling all the MBeans

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00110 mbean-enabled flag is turned off. Disabling all the MBeans

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00111 dtrace-enabled flag is turned on/off. Enabling/Disabling DTrace

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00112 monitoring-enabled flag is turned on. Enabling all the Probes and Stats

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00113 monitoring-enabled flag is turned off. Disabling all the Stats

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00201 Flashlight listener registration failed for listener class: {0} , will retry later

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00202 Invalid statsProvider (very likely a duplicate request), cannot unregister: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00203 Cannot find node {0} for statsProvider {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00204 {0} is not a ManagedObject and will not be registered with Gmbal to create an MBean

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00205 Gmbal registration failed

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00206 Gmbal unregistration failed

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00207 module-monitoring-level or container-monitoring config element for {0} does not exist

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00208 Error unregistering the stats provider {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00209 Error resetting the stats provider: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-MNTG-00210 Unable to create container-monitoring for {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-RSTCN-00001 The REST connector has been started

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-RSCL-00001 An unsupported encoding was requested: {0}.

Cause: The input supplied can not be encoded in the requestedencoding.
Action: Verify that the input is valid.

NCLS-RSCL-00002 An error occurred while processing an XML document.

Cause: The input provided could not be read as an XML document.
Action: Verify that the document provided is a valid XML document.

NCLS-RSCL-00003 An I/O exception occurred.

Cause: An error occured while closing an InputStream.
Action: The error is not recoverable.

NCLS-RSCL-00004 An error occurred while processing a JSON object.

Cause: An invalid JSON string was provided and could not be read.
Action: Verify that the JSON string is valid and retry the request.

NCLS-REST-00001 Listening to REST requests at context: {0}/domain.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00002 Incorrectly formatted entry in {0}: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00003 An error occurred while processing the request. Please see the server logs for details.

Cause: A runtime error occurred. Please see the log file for moredetails
Action: See the log file for more details

NCLS-REST-00004 The class specified by generator does not implement DefaultsGenerator

Cause: The generator does not implement the DefaultsGeneratorinterface
Action: Modify the generator to implement the DefaultsGeneratorinterface

NCLS-REST-00005 Unsupported fixed value. Supported types are String, boolean, Boolean, int, Integer, long, Long, double, Double, float, and Float

Cause: The RestModel property has specified an unsupported data type
Action: Modify the model to use one of the supported types

NCLS-REST-00006 Fixed value type does not match the property type

Cause: The value for the given property can not be converted to theproperty’s type
Action: Check the input data

NCLS-REST-00007 Cannot marshal

Cause: The system is unable to generate XML for the given object
Action: Check the logs for more details

NCLS-REST-00008 Unexpected exception during command execution. {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00009 Unable to delete directory {0}. Will attempt deletion again upon JVM exit.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00010 Unable to delete file %s. Will attempt deletion again upon JVM exit.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00012 Compilation failed.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00013 File creation failed: {0}

Cause: The system was unable to create the specified file.
Action: Verify that the filesystem is writable and has sufficient diskspace

NCLS-REST-00014 Directory creation failed: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-REST-00015 Unexpected exception during initilization.

Cause: The system is unable to init ReST interface
Action: Check the logs for more details

Cause: See server log for details
Action: See server log for details.

NCLS-SRVRMGMT-00000 Caught an Exception: {0}

Cause: see Exception message
Action: see Exception message

NCLS-SRVRMGMT-00001 Error attemping to delete temporary certificate file: {0}

Cause: As described in the message.
Action: Delete the file manually.

NCLS-SRVRMGMT-00002 Renaming {0} to {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00003 Failed to rename {0} to {1}

Cause: As described in the message.
Action: Check the file system.

NCLS-SRVRMGMT-00004 Failure while upgrading jvm-options from V2 to V3

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00005 JVM Monitoring

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00007 Heap and NonHeap Memory(bytes)

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00008 Failure while upgrading log-service. Could not create logging.properties file.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00009 Failure while upgrading log-service. Could not update logging.properties file.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00010 Failure while upgrading log-service

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00011 Could not create directory {0}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00012 Could not create domain info XML file {0}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00013 Missing file : {0}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00014 Default port {1} for {0} is in use. Using {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00015 Port for {0} is not specified. Using {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00016 Invalid Port for {0}, should be between 1 and 65535. Using {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00017 Port {1} for {0} is in use. Using {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00018 Using default port {1} for {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00019 Using port {1} for {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-SRVRMGMT-00020 On Unix platforms, port numbers below 1024 may require special privileges.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00021 Failed to update jar {0} with the substitutable files

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00022 File {0} not present inside archive {1}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00023 Error occurred while closing the stream for file {0}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00024 Could not rename temporary jar {0} file to {1}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00025 Could not locate file or resource {0}

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00026 No processing defined for {0} mode

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00027 Component {0} is not present.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00028 Group {0} is not present.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00029 Change-Pair {0} referred by group {1} is not defined.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00030 Invalid Mode Type {0}.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00031 Found an empty <change-pair/>.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00032 IO Error occurred while retrieving substitutable entries from archive {0}.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00033 In-memory string substitution file size is not defined.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00034 Key already exist in tree, Current Value : {0} New Value : {1}.

Cause: As described in the message.
Action: Check documentation.

NCLS-SRVRMGMT-00035 Parent node: {0} contains child node: {1} whose key starts with same character as the key of given node: {2}

Cause: As described in the message.
Action: Check documentation.

NCLS-ADMIN-00001 Could not find state of instance registered in the state service

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-ADMIN-00002 Error during command replication: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-ADMIN-00003 unable to read instance state file {0}, recreating

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-ADMIN-00004 unable to create instance state file: {0}, exception: {1}

Cause: The instance state file is missing and the system is tryingtorecreated it but and exception was raised.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00005 error while adding new server state to instance state: {0}

Cause: An attempt to add a new server to the instance state filefailed.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00006 error while adding failed command to instance state: {0}

Cause: An attempt to add a failed command to the instance state filefailed.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00007 error while removing failed commands from instance state: {0}

Cause: An attempt to remove a failed command from the instance statefile failed.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00008 error while setting instance state: {0}

Cause: An attempt to set the state of a server in the instance statefile failed.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00009 error while removing instance: {0}

Cause: An attempt to remove a server from the instance state filefailed.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00010 It appears that server [{0}:{1}] does not accept secure connections. Retry with –secure=false.

Cause: An attempt to invoke a command on another server failed.
Action: Check that the server is configured to accept secureconnections.

NCLS-ADMIN-00011 An unexpected exception occurred.

Cause: An unexpected exception occurred.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00012 The server requires a valid admin password to be set before it can start. Please set a password using the change-admin-password command.

Cause: For security reason, the server requires a valid admin passwordbefore it can start.
Action: Set a password using the change-admin-password command.

NCLS-ADMIN-00013 Can not put data to cache under key {0}

Cause: While invoking a command on another server, this server isunable to cache the meta data related to the command.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00014 An admin request arrived from {0} with the domain identifier {1} which does not match the domain identifier {2} configured for this server’s domain; rejecting the request

Cause: There is a error in the cluster or network configuration.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00015 Error searching for a default admin user

Cause: An unexpected exception occurred wihle searching for thedefault admin user.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00016 Cannot read admin cache file for {0}

Cause: An error occured while reading the admin command model cachefile.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00017 Cannot write data to cache file for {0}

Cause: An error occured while writing the admin command model cachefile.
Action: Check the server logs and contact Oracle support

NCLS-ADMIN-00018 Unexpected exception from command event listener.

Cause: An error occured while calling registered listener.
Action: Check the server logs and contact Oracle support

NCLS-CLSTR-10101 no clustername to lookup

Cause: Required information was not passed into method.
Action: File issue with all relevant information.

NCLS-CLSTR-10102 Multiple gms-adapter service for cluster {0}

Cause: GMs module is being initialized more than once for the samecluster.
Action: File issue with all relevant information.

NCLS-CLSTR-10103 GMS cannot initialize with unknown cluster

Cause: No cluster was found with this name in the domainconfiguration.
Action: Check that domain exists in domain.xml.

NCLS-CLSTR-10104 Started GMS for instance {0} in group {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-10105 Member {0} joined group {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-10107 AliveAndReady for signal: {0} for member: {1} of group: {2} current:[{3}] previous:[{4}]

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-10108 GMSAdapter for member: {0} group: {1} received GlassFishEventType: {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-10109 An exception occurred while creating the HealthHistory object: {0}

Cause: An unexpected exception occurred.
Action: See server log for more details.

NCLS-CLSTR-10110 An exception occurred while processing GMS configuration properties: {0}

Cause: An unexpected exception occurred.
Action: See server log for more details.

NCLS-CLSTR-10111 Ignoring group-management-service property {0} with value of {1} due to {2}

Cause: An illegal argument was passed into the Shoal GMSimplementation.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-10112 Error processing cluster property:{0} value:{1} due to exception {2}

Cause: An unexpected exception occurred.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-10113 Exception in getting GMS module for group {0}: {1}

Cause: An unexpected exception occurred.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-10114 An exception occurred while updating the instance health history table: {0}

Cause: An unexpected exception occurred.
Action: Check the log file for more information from Shoal-GMS.

NCLS-CLSTR-10115 start failure recovery callback for component: {0} failed member: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-10116 complete failure recovery callback for component: {0} failed member: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-10117 GMS failed to start. See stack trace for additional information.

Cause: An unexpected exception occurred.
Action: Check the log file for more information

NCLS-CLSTR-10118 GMS failed to start due to a runtime exception. See stack trace for additional information.

Cause: An unexpected exception occurred.
Action: Check the log file for more information

NCLS-CLSTR-10119 GMS bind interface address {0} is invalid. Will use default value instead.

Cause: The specified bind interface address is not an active localaddress, so it cannot be used on this node.
Action: Check that you have specified the proper address. See serverlog for more details from GMS subsystem.

NCLS-CLSTR-10120 GMS listener port is required for cluster {0}. Will attempt to use default of {1}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-30001 GMSAnnounceAfterStartClusterCommand: exitCode:{0} members {1} clusterMembers:{2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-30002 An exception occurred while announcing GMS group startup: {0}

Cause: An unexpected exception occurred in the GMS implementation.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-30003 An exception occurred while announcing GMS group shutdown: {0}

Cause: An unexpected exception occurred in the GMS implementation.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-30004 An exception occurred while announcing GMS group startup: {0}

Cause: An unexpected exception occurred in the GMS implementation.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-30005 An exception occurred while announcing GMS group shutdown: {0}

Cause: An unexpected exception occurred in the GMS implementation.
Action: Check the server log file for more information from Shoal-GMS.

NCLS-CLSTR-10001 Unable to load GMS classes. Group management service is not available.

Cause: GMS implementation classes are not present. Seehttps://glassfish.dev.java.net/issues/show_bug.cgi?id=12850.
Action: Check that shoal-gms-impl.jar file is present.

NCLS-CLSTR-20001 Adding instance {0} to health history table.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-20002 Instance {0} was not in map when deleted from health history table.

Cause: More than one call may have been made to remove this instancefrom the cluster. This has no other effect on the health historyinformation.
Action: No action is necessary.

NCLS-CLSTR-20003 Deleting instance {0} from health history table.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-20004 Duplicate instance {0} ignored in health history.

Cause: There may be more than one instance in the cluster with thesame name.
Action: Check that instance names are unique within the cluster.

NCLS-CLSTR-20005 State already known for instance {0}. Not adding to health history table.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CLSTR-20006 New state {0} added for unknown instance {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00002 AMX Startup Service Shutdown. MBeans have not been unregistered: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00004 Fatal error loading AMX {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00008 AMX Startup Service: AMXLoader failed to load {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00009 AMX Startup Service: AMX ready for use, DomainRoot {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00010 AMXLoader failed to unload: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00011 ConfigBean not processed, something wrong with it {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00012 In AMXConfigLoader : Loading {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00019 Can’t unregister MBean: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00020 Non-singleton ConfigBean {0} has empty key value (name), supplying {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00021 AMX ComplianceMonitor: ValidationLevel = {0}, UnregisterNonCompliant = {1}, LogInaccessibleAttributes = {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00022 AMX ComplianceMonitor thread has unexpectedly quit {0}

Cause: A JMX validation thread has unexpectedly terminated due to anexception.
Action: Check the server logs and contact Oracle support.

NCLS-COM-00023 Validating MBean {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00024 Exception validating MBean {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00025 Register children for instance name {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00027 AMX Attribute Change Notification for {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00030 Attribute {0} not found for object {1}

Cause: An attempt to resolve an attribute failed.
Action: Check the server logs and contact Oracle support.

NCLS-COM-00031 Can’t find child of type {0}

Cause: While removing a child, the child was not found.
Action: Check the server logs and contact Oracle support.

NCLS-COM-00032 MBeans exist in AMX domain prior to DomainRoot (violates Parent requirement): {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00033 Can’t register config MBean: type={0}, name={1}, exception={2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00034 Unexpected thread death of AMXConfigLoaderThread

Cause: The AMX configuration loader thread received an unexpectedexception.
Action: Check the server logs and contact Oracle support.

NCLS-COM-00035 Can’t create children

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00036 AMXConfigStartupService.preDestroy(): stopping AMX

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00037 Illegal non-string type for {0}.{1}(): {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00038 Can’t get field value for {0}: exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00039 Can’t getTypesImplementing for {0}: exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00040 Can’t get childrenSet() from MBean: {0}, exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00041 Problem with MBean: {0}, exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00042 PathnamesImpl.getAllPathnames(): unexpected Throwable: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00043 Can’t get path() for MBean: {0}, exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00044 Can’t instantiate realm: {0}, exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00045 getRealmNames(): Can’t get realm names, exception:

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00046 Cannot find primordial com.sun.enterprise.osgi-adapter

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00047 Stopping server forcibly

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00048 Can’t get cipher suites

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00049 MBeanInfoSupport: @ManagedAttribute cannot also be @ManagedOperation: {0}.{1}()

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-00050 MBeanInfoSupport: @ManagedAttribute not a getter or setter: {0}.{1}()

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00001 Failed to process class {0} with bytecode preprocessor {1}

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00002 Class {0} is being reset to its original state

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00003 Class {0} is being reset to the last successful preprocessor

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00004 The supplied preprocessor class {0} is not an instance of org.glassfish.api.BytecodePreprocessor

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00005 Bytecode preprocessor disabled

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00006 Initialization failed for bytecode preprocessor {0}

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00007 Error setting up preprocessor

Cause: As described in the message.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00008 Illegal max-entries [{0}]; please check your cache configuration.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00009 Illegal MaxSize value [{0}]

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00010 Error closing zip file for class path entry {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00011 An error occurred while adding URL [{0}] to the EJB class loader. Please check the content of this URL.

Cause: An unexpected exception occurred while processing a URL.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00012 The URL entry is missing while contructing the classpath.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00013 Error closing zip file for duplicate class path entry {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00014 Exception in ASURLClassLoader

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00015 ASURLClassLoader {1} was requested to find resource {0} after done was invoked from the following stack trace

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00016 Error: Request made to load class or resource [{0}] on an ASURLClassLoader instance that has already been shutdown. [{1}]

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00017 {0} actually got transformed

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00018 ASURLClassLoader {1} was requested to find class {0} after done was invoked from the following stack trace

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00019 Illegal call to close() detected

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00020 Error processing file with path {0} in {1}

Cause: An unexpected exception occurred while processing a file.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00021 Error checking for existing of {0} in {1}

Cause: An unexpected exception occurred while checking for theexistence of a file.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00022 Error closing an open stream during loader clean-up

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00023 Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00024 Unable to create client data directory: {0}

Cause: An unexpected failure occurred while creating the directory forthe file.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00025 Exception in invokeApplicationMain [{0}].

Cause: An unexpected exception occurred.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00026 The main method signature is invalid.

Cause: While invoking a main class, an invalid method was found.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00027 Error while caching the local string manager – package name may be null.

Cause: An unexpected exception occurred.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00028 Error while constructing the local string manager object.

Cause: An unexpected exception occurred.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00029 Error in local string manager – resource bundle is probably missing.

Cause: An unexpected exception occurred.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00030 Error while formating the local string.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00031 Some IOException occurred

Cause: An unexpected exception occurred.
Action: Check the system logs and contact Oracle support.

NCLS-COMUTIL-00032 Attempt to delete {0} failed; the file is reported as non-existent

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00033 Error attempting to delete {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00034 Performing gc to try to force file closures

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00035 Attempt to rename {0} to {1} succeeded after {2} retries

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00036 Attempt to rename {0} to {1} succeeded without any retries

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00037 Attempt to rename {0} to {1} failed after {2} retries

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00038 Failed to open jar file: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00039 Attempt to use non-existent auth token {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00040 File Lock not released on {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COMUTIL-00041 Bad Network Configuration. DNS can not resolve the hostname: n{0}

Cause: The hostname can’t be resolved.
Action: Set the hostname correctly.

NCLS-COMUTIL-00042 BundleTracker.removedBundle null bundleID for {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-01001 Exception {0} resolving password alias {1} in property {2}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-COM-01002 Unknown property {0} found unresolving {1}.

Cause: No value was found for a property. This indicates a softwareproblem.
Action: Check the server logs and contact Oracle support.

NCLS-COM-01003 System property reference missing trailing “}” at {0} in domain.xml.

Cause: A system property reference in domain.xml is invalid.
Action: Check the domain.xml file for an invalid system propertyreference.

NCLS-COM-01004 System property reference missing starting “${” at {0} in domain.xml.

Cause: A system property reference in domain.xml is invalid.
Action: Check the domain.xml file for an invalid system propertyreference.

NCLS-JMX—​00008 Error while shutting down AMX

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00001 JMXStartupService and JMXConnectors have been shut down.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00002 JMXStartupService: Stopped JMXConnectorServer: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00003 MBean Registration Exception thrown {0}

Cause: JMX Connector Server MBean could not be unregistered.
Action: Take appropriate action based on the exception message.

NCLS-JMX-00004 Instance Not Found Exception thrown {0}

Cause: JMX Connector Server MBean instance not found.
Action: Take appropriate action based on the exception message.

NCLS-JMX-00005 JMXStartupService has started JMXConnector on JMXService URL {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00006 JMXStartupService has disabled JMXConnector {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00007 Cannot start JMX connector {0} due to exception {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00008 Booting AMX Listener, connection made for {0}, now booting AMX MBeans

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00009 Security enabled

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00010 Attempted access to method {0} on object {1} rejected; user was granted {2} but the operation reports its impact as “{3}”

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00011 Error stopping RMIConnector

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00012 MyRMIJRMPServerImpl: exported on address {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00013 MyRMIJRMPServerImpl: makeClient on address = {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00014 Error preparing SSL context

Cause: As described in the message.
Action: Please refer to the stack trace

NCLS-JMX-00015 No Key store found for {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00016 No keystores defined

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00017 Bad maxCertLength: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00018 JSSE keystoreload failed for type = {0} path = {1} {2}

Cause: As described in the message.
Action: Please refer to the stack trace

NCLS-JMX-00019 All SSL protocol variants disabled for network-listener, using SSL implementation specific defaults

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00020 All SSL cipher suites disabled for network-listener(s). Using SSL implementation specific defaults

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00021 Unknown cipher error for cipher {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00022 Creating a SecureRMIClientSocketFactory @ {0}with ssl config = {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00023 Setting SSLParams @ {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00024 Creating a SecureRMIServerSocketFactory @ {0} with ssl config = {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00025 SSLServerSocket {0} and {1} created

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-JMX-00026 Binding RMI port to single IP address = {0}, port {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00001 GlassFish requires JDK {0}, you are using JDK version {1}.

Cause: Incorrect JDK version is used.
Action: Please use correct JDK version.

NCLS-BOOTSTRAP-00002 Using {0} as the framework configuration file.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00003 Could not extract archive {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00004 Could not find RAR [{0}] location [{1}] after extraction.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00005 Can not start bundle {0} because it is not contained in the list of installed bundles.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00006 Failed to start {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00007 Can’t uninstall bundle = {0} as it’s already uninstalled.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00008 Uninstalled bundle {0} installed from {1}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00009 Can’t update bundle = {0} as it’s already uninstalled.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00010 Updated bundle {0} from {1}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00011 Failed to uninstall bundle {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00012 Failed to update {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00013 Failed to install {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00014 Can not set the start level for {0} to {2} as it is already set to {1}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00015 Skipping entry {0} because it is not an absolute URI.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00016 Skipping entry {0} due to exception:

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00017 Starting BundleProvisioner.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00018 Time taken to locate OSGi framework = {0} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00020 Time taken to initialize OSGi framework = {0} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00021 Time taken to finish installation of bundles = {0} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00022 Time taken to finish starting bundles = {0} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00023 Total time taken to start = {0} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00024 Time taken to stop = {0} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00025 Total time taken = {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00026 Create bundle provisioner class = {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00027 Registered {0} as OSGi service registration: {1}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00028 Unregistered {0} from service registry.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00029 Exception while unregistering:

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00030 installLocations = {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00031 Unable to determine if {0} is a fragment or not due to

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00032 Skipping starting of bundles bundles have been provisioned already.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00033 {0} : latest file in installation location = {1} and latest installed bundle = {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00034 Updating system bundle.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00035 Provisioning options have changed, recreating the framework with a clean OSGi storage(aka cache).

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00036 Unable to locate bundle {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00037 Storage support not available in framework bundle, so can’t store bundle ids. This may lead to slower start up time.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00038 Storage support not available in framework bundle, so can’t store provisioning options. This may lead to slower start up time.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-BOOTSTRAP-00039 Got an unexpected exception.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00001 Cannot decode parameter {0} = {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00002 Cannot instantiate model for command {0}

Cause: The service that implements the command could not be loaded.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00003 Exception while running a command

Cause: An unexpected exception occurred while running a command.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00004 Unable to get an instance of ClusterExecutor; Cannot dynamically reconfigure instances

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00005 Can’t delete local password file: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00006 Can’t create local password file: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00007 Timeout occurred when processing Admin Console request.

Cause: A request for a lock timed out while processing an adminconsole request.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00008 Cannot process admin console request.

Cause: InterruptedException occurred while the service thread isrunning.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00009 Unable to serve resource: {0}. Cause: {1}

Cause: An I/O error occurred while serving a resource request.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00010 Resource not found: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00011 Console cannot be initialized due to an exception.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00012 Cannot write property ‘{0} = {1}’ for AdminService in domain.xml, exception: {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00013 Shutdown procedure finished

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00014 Shutdown required

Cause: An unexpected exception occurred while changing run levels. Ashutdown is required.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00015 Shutdown requested

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00016 Startup service failed to start

Cause: An unexpected exception occurred while starting the startupservice. A shutdown is required.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00017 {0} ({1}) startup time : {2} ({3}ms), startup services({4}ms), total({5}ms)

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00018 TOTAL TIME INCLUDING CLI: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00019 Shutting down server due to startup exception

Cause: An unexpected exception occurred while starting the server. Ashutdown is required.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00020 Timed out, ignoring some startup service status

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00021 Unexpected exception during startup

Cause: An unexpected exception occurred while starting the server.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00022 Loading application {0} done in {1} ms

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00023 Enable of application {0} completed with a warning: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00024 Error during enabling

Cause: An unexpected exception occurred while enabling an application.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00025 Error during disabling

Cause: An unexpected exception occurred while disabling anapplication.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00026 Exception during lifecycle processing

Cause: An unexpected exception occurred during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00027 ApplicationMetaDataProvider {0} requires {1} but no other ApplicationMetaDataProvider provides it

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00028 Inconsistent state – nothing is providing {0} yet it passed validation

Cause: An unexpected condition during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00029 Cannot start container {0}, exception: {1}

Cause: An unexpected condition during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00030 Cannot release container {0}, exception {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00031 Error while closing deployable artifact {0}, exception: {1}

Cause: An unexpected exception occurred during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00032 Error while expanding archive file

Cause: An unexpected exception occurred during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00033 Cannot find sniffer for module type: {0}

Cause: An unexpected condition occurred during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00034 Cannot find any sniffer for deployed app: {0}

Cause: An unexpected condition occurred during lifecycle processing.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00035 Exception occurred while satisfying optional package dependencies

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00036 Cannot delete created temporary file {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00037 Source is not a directory, using temporary location {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00038 Cannot find the application type for the artifact at: {0}. Was the container or sniffer removed?

Cause: An unexpected condition occurred while loading an application.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00039 Exception during application deployment

Cause: An unexpected exception occurred while deploying anapplication.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00040 Cannot determine original location for application: {0}

Cause: A URL syntax error occurred.
Action: Check the application for proper syntax.

NCLS-CORE-00041 Application deployment failed: {0}

Cause: The deployment command for an application failed as indicatedin the message.
Action: Check the application and redeploy.

NCLS-CORE-00042 IOException while opening deployed artifact

Cause: An unexpected exception occurred while deploying anapplication.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00043 Application previously deployed is not at its original location any more: {0}

Cause: An unexpected exception occurred while loading an application.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00044 System property called {0} is null, is this intended?

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00045 Invalid classpath entry for common class loader ignored: {0}, exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00046 Cannot find javadb client jar file, derby jdbc driver will not be available by default.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00047 CommonClassLoaderServiceImpl is unable to process {0} because of an exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00048 Invalid InputStream returned for {0}

Cause: Unable to retrieve an entry from the archive.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00049 Exception while processing {0} inside {1} of size {2}, exception: {3}

Cause: An unexpected exception occurred while processing an archive.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00050 Cannot open sub-archive {0} from {1}

Cause: An unexpected exception occurred while processing an archive.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00051 Cannot close sub archive {0}, exception: {1}

Cause: An unexpected exception occurred while closing an archive.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00052 Exception loading lifecycle module [{0}]; [{1}]

Cause: An unexpected exception occurred while loading a lifecyclemodule.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00053 Lifecycle module [{0}] threw ServerLifecycleException, exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00054 Lifecycle module [{0}] threw an Exception; please check your lifecycle module. Exception: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00055 GrizzlyService stop-proxy problem

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00056 Unable to start the server. Closing all ports

Cause: An unexpected exception occurred while starting the grizzlyservice.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00057 Exception closing port: {0}, exception: {1}

Cause: An unexpected exception occurred while closing a port.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00058 Network listener {0} on port {1} disabled per domain.xml

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00059 GrizzlyService endpoint registration problem

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00060 Skip registering endpoint with non existent virtual server: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00061 Attempting to start the {0} container.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00062 Done with starting {0} container in {1} ms.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00063 Could not start container, no exception provided.

Cause: The container could not be started.
Action: Ensure the libraries for the container are available.

NCLS-CORE-00064 Exception while starting container {0}, exception: {1}

Cause: An exception occurred while attempting to start the container.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00065 Exception while mapping the request.

Cause: An exception occurred while mapping a request to the container.
Action: Please resolve issues mentioned in the stack trace.

NCLS-CORE-00066 Cannot add new configuration to the Config element

Cause: An exception occurred while adding the container configurationto the domain.xml.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00067 Exception while enabling or disabling the autodeployment of applications

Cause: An exception occurred while enabling or disabling theautodeployment of applications.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00068 Exception while sending an event.

Cause: An exception occurred while sending an event.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00069 Exception while dispatching an event

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00070 An exception occurred while stopping the server, continuing.

Cause: An exception occurred while stopping the server.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00071 The ManagedJobConfig bean {0} was changed by {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00072 Cleaning Job {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00073 Initializing Job Cleanup service

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00074 Initializing Managed Config bean

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00075 Scheduling Cleanup

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00076 Exception when cleaning jobs caused

Cause: An exception occured when cleaning the managed jobs
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00077 -passwordfile specified, but the actual file was not, ignoring …​

Cause: A software error is causing an incorrect argument sequence.
Action: No action necessary.

NCLS-CORE-00078 Invalid context root for the admin console application, using default: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00079 Admin Console Adapter: context root: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00080 Failed to configure the ManagedJobConfig bean

Cause: While running the configure-managed-jobs command, a writetransaction to the ManagedJobConfig bean failed.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00081 Unable to get the ManagedJobConfig bean.

Cause: While running the configure-managed-jobs command, access to theManagedJobConfig bean failed.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00082 Exiting after upgrade

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00083 Exception while attempting to shutdown after upgrade

Cause: An exception occured when shutting down the server after anupgrade.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00084 Cannot find port information from domain.xml

Cause: No port value is available in the NetworkListener config bean
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00085 Cannot parse port value: {0}, using port 8080

Cause: There is an invalid port value in the domain.xml file.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00086 Unknown address {0}

Cause: There is an invalid address value in the domain.xml file.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00087 Grizzly Framework {0} started in: {1}ms – bound to [{2}]

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00088 Exception during postConstruct of DynamicReloadService

Cause: An unexpected exception occured.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00089 Cannot determine host name, will use localhost exclusively

Cause: An unexpected exception occured.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00090 Internal Server error: {0}

Cause: An unexpected exception occured.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00091 Unable to set customized error page

Cause: An unexpected exception occured.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00092 Server shutdown initiated

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00093 Problem while attempting to install admin console!

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00094 Unable to load checkpoint

Cause: An unexpected exception occured.
Action: Check the system logs and contact Oracle support.

NCLS-CORE-00095 Resuming command {0} from its last checkpoint.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-CORE-00096 Automatically resumed command {0} finished with exit code {1}. nMessage: {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00001 Cannot read logging configuration file.

Cause: An exception has occurred while reading the loggingconfiguration file.
Action: Take appropriate action based on the exception message.

NCLS-LOGGING-00002 Could not apply the logging configuration changes.

Cause: There was an exception thrown while applying the loggingconfiguration changes.
Action: Take appropriate action based on the exception message.

NCLS-LOGGING-00003 Updated logger levels successfully.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00004 The logging configuration file {0} has been deleted.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00005 Error executing query to fetch log records.

Cause: There was an exception thrown while executing log query.
Action: Take appropriate action based on the exception message.

NCLS-LOGGING-00006 The syslog handler could not be initialized.

Cause: There was an exception thrown while initializing the sysloghandler.
Action: Take appropriate action based on the exception message.

NCLS-LOGGING-00007 There was an error sending a log message to syslog.

Cause: There was an exception thrown while sending a log message tothe syslog.
Action: Take appropriate action based on the exception message.

NCLS-LOGGING-00008 The log file {0} for the instance does not exist.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00009 Running GlassFish Version: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00010 Server log file is using Formatter class: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00011 Failed to parse the date: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00012 An invalid value {0} has been specified for the {1} attribute in the logging configuration.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-LOGGING-00013 The formatter class {0} could not be instantiated.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00040 Error occurred: {0}

Cause: An exception was caught when the operation was attempted
Action: See the exception to determine how to fix the error

NCLS-DEPLOYMENT-02025 Exception caught: {0}

Cause: An exception was caught when the application was autodeployed.
Action: See the exception to determine how to fix the error

NCLS-DEPLOYMENT-02026 Autoundeploying application: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02027 Selecting file {0} for autodeployment

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02028 Error parsing configured polling-interval-in-seconds {0} as an integer; {1} {2}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02029 Exception caught: {0}

Cause: An exception was caught when the application was autodeployed.
Action: See the exception to determine how to fix the error

NCLS-DEPLOYMENT-02030 Error processing configuration change of {0} from {1} to {2}; {3} {4}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02031 Configured timeout value of {0} second{0,choice,0#seconds|1#second|1<seconds} will be used but seems very large

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02032 Configured timeout value of {0} second{0,choice,0#seconds|1#second|1<seconds} is too small; using previous value of {1}second {1,choice,0#seconds|1#second|1<seconds}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02033 Could not convert configured timeout value of “{0}” to a number; using previous value of {1} second{1,choice,0#seconds|1#second|1<seconds

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02034 Attempt to create file {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02037 Error occurred:

Cause: An exception was caught when the operation was attempted
Action: See the exception to determine how to fix the error

NCLS-DEPLOYMENT-02038 Attempt to delete file {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02039 Attempt to create file {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02041 Attempt to create file {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02042 Attempt to set last modified date/time of file {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02043 Attempt to delete file {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-02044 Attempt to create directory {0} failed; no further information.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00001 Exception while scanning {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00002 Error scan jar entry {0} {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00003 Failed to scan archive for annotations

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00004 Exception caught: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00005 Could not expand entry {0} into destination {1}

Cause: An exception was caught when the entry was expanded
Action: See the exception to determine how to fix the error

NCLS-DEPLOYMENT-00006 Cannot find archive {0} referenced from archive {1}, it will be ignored for annotation scanning

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00007 Exception caught {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00008 Error in jar entry {0}: {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00009 Failed to scan archive for annotations: {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00010 Exception caught {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00011 Optional package {0} does not exist or its Specification-Version does not match. Unable to satisfy dependency for {1}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00012 Optional package dependency satisfied for {0}

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00013 Error in opening optional package file {0} due to exception: {1}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

NCLS-DEPLOYMENT-00014 Exception occurred : {0}.

Cause: As described in the message.
Action: Resolve the situation described in the message, if necessary.

Written by Jane