Glassfish example source code file (LogStrings.properties)

This example Glassfish source code file (LogStrings.properties) is included in the DevDaily.com "Java Source Code Warehouse" project. The intent of this project is to help you "Learn Java by Example" ^TM.

Java - Glassfish tags/keywords

detailed, detailed, mbean, mbean, mbeans, mbeanserver, message, server, service, service, the, the, this, web

The Glassfish LogStrings.properties source code

#
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS HEADER.
#
# Copyright (c) 2004-2010 Oracle and/or its affiliates. All rights reserved.
#
# The contents of this file are subject to the terms of either the GNU
# General Public License Version 2 only ("GPL") or the Common Development
# and Distribution License("CDDL") (collectively, the "License").  You
# may not use this file except in compliance with the License.  You can
# obtain a copy of the License at
# https://glassfish.dev.java.net/public/CDDL+GPL_1_1.html
# or packager/legal/LICENSE.txt.  See the License for the specific
# language governing permissions and limitations under the License.
#
# When distributing the software, include this License Header Notice in each
# file and include the License file at packager/legal/LICENSE.txt.
#
# GPL Classpath Exception:
# Oracle designates this particular file as subject to the "Classpath"
# exception as provided by Oracle in the GPL Version 2 section of the License
# file that accompanied this code.
#
# Modifications:
# If applicable, add the following below the License Header, with the fields
# enclosed by brackets [] replaced by your own identifying information:
# "Portions Copyright [year] [name of copyright owner]"
#
# Contributor(s):
# If you wish your version of this file to be governed by only the CDDL or
# only the GPL Version 2, indicate your decision by adding "[Contributor]
# elects to include this software in this distribution under the [CDDL or GPL
# Version 2] license."  If you don't indicate a single choice of license, a
# recipient has the option to distribute your version of this file under
# either the CDDL, the GPL Version 2 or to extend the choice of license to
# its licensees as provided above.  However, if you add GPL Version 2 code
# and therefore, elected the GPL Version 2 license, then the option applies
# only if the new code is made subject to such option by the copyright
# holder.
#

#
# Log messages used by the com.sun.enterprise.admin.server.* sources
# LogDomains.ADMIN_LOGGER, subsystem tools. At present, it is weird that
# admin messages are configured with tools, but that will change.
# The server.xml setting that will modify the logging output is
# <log-service> element's attribute:level.
# See java.text.MessageFormat for details on constructing messages.
# Messages in this file must be of the form 
# <Subsystem><4CharIntegerMessageId>:
#
#example.message1=ADM0001:Test Message. Parameter 1={0} parameter 2={1}
#example.message2=ADM0002:Date Message. Parameter 1={0,date} Parameter 2={1,time}
#Common admin log messages from MBeanServer/AdminService start at 0001
#
core.sunone_interceptor_enabled=ADM0001:SunoneInterceptor is now enabled
core.system_mbean_init_ok=ADM0002:System MBean initialized:[{0}]
core.mbs_init_exception=ADM0003:MBeanServer initialization failed
core.mbs_invoked=ADM0004:MBeanServer method invocation:[{0}]
core.ts_files_ok=ADM0005:Timestamp files for configuration created for:[{0}]
core.ts_files_failed=ADM0006:Timestamp files not created - Detailed Message:
core.tmp_folder_exists=ADM0007: The folder [{0}] where admin server uploads the remote files for deployment already exists. This is probably because admin-server could not delete this folder during last shutdown. This should not be cause of any problem
core.tmp_folder_creation_failed=ADM0008: Admin Server could not create the temporary folder for internal purposes at [{0}]. This may cause problems with deployment etc. It is alright if some space is freed at this location without shutting down the Admin Server. Also look at the operating systems artifacts like file permissions etc. to resolve the problem
core.tmp_folder_created_ok=ADM0009: Created temporary folder at [{0}] for internal purpose
core.tmp_folder_deleted_ok=ADM0010: Deleted temporary folder at [{0}] successfully
core.domain_reregistration_failed=ADM0011: Could not re-register HttpListener with DomainRegistry.
core.domain_registry_exception_occured=ADM0012: A Domain Registry Exception occurred. Details are:
core.config_exception_occurred=ADM0013: A config exception occurred. Details are:

core.gui_tmp_folder_creation_failed=ADM0014: The temporary folder required by the administrative console (graphical user interface) could not be created at [{0}]. This will pose some problems while trying to deploy archives from the console. Some space can be freed at this location without restarting the administrative server to correct this problem.
core.gui_tmp_folder_creation_ok=ADM0015: The temporary folder required by the administrative console (graphical user interface) was created at [{0}]. This is where the archives to be deployed will be uploaded.
core.no_java_home=ADM0016:Unable to determine java home. This suggests that you are using a version of J2EE plug-in incompatible with administration server.
core.set_admin_property_failed=ADM0017:Admin server could not be initialized with java home from j2ee plug-in.
core.no_batch_reconfig=ADM0018:Support for batched reconfiguration is disabled.
core.context_not_set=ADM0019:Admin service is running without server context.
# 8.0 - Adding the general initialization messages after this.
core.mbs_info=ADM0020:Following is the information about the JMX MBeanServer used:
core.mbs_implementation=ADM0021:MBeanServer Implementation Name:[{0}]
core.mbs_vendor=ADM0022:MBeanServer Implementation Vendor:[{0}]
core.jmx_impl_version=ADM023:JMX Implementation Version:[{0}]
core.mbs_id=ADM024:MBeanServer ID:[{0}]
core_mbs_classname=ADM025:MBeanServer Implementation Classname:[{0}]
core.html_adaptor_state=ADM026:Using HtmlAdaptorServer for viewing MBeans, its state is:[{0}]
core.html_adaptor_port=ADM027:Using HtmlAdaptorServer for viewing MBeans, its port is: [{0}]. Connect the Browser to this port
core.create_and_register=ADM028:The MBean with ObjectName[{0}] was created anew and registered with the MBeanServer
core.mbean_exists=ADM029:The MBean with ObjectName[{0}] already exists, accessing its management interface
core.not_in_config=ADM030:The ObjectName [{0}] can''t be registered as the configuration does not have it
core.stop_html_adaptor=ADM031:Html Adaptor Server stopped
core.release_mbs=ADM032:The System MBeanServer released
core.admin_service_default_config=ADM0033:Admin Service configuration could not be read and Admin Service type is being defaulted to [{0}]
core.interceptor_preinvoke_fail=ADM0034:Preinvoke failed for MBeanServer interceptor [{0}].
core.interceptor_preinvoke_exception=ADM0035:Preinvoke exception for MBeanServer interceptor.
core.interceptor_postinvoke_fail=ADM0036:Postinvoke failed for MBeanServer interceptor [{0}].
core.interceptor_postinvoke_exception=ADM0037:Preinvoke exception for MBeanServer interceptor.
core.admin_config_read_error=ADM0038:A read-write version of configuration files could not be loaded. Server can not be administered. Root cause: [{0}]
core.admin_config_read_error_trace=ADM0039:Read/Write version of configuration files not loaded because of exception.
core.log_config_id_runtime=ADM0040:Config context for runtime initialized to [{0}]
core.log_config_id_admin=ADM0041:Config context for admin initialized to [{0}]
core.logmgr_mbean_not_registered=ADM0042:Log Manager MBean could not be registered, the changes to logger log levels will be effective after server restart.
core.logmgr_mbean_register_error=ADM0043:Log Manager MBean registration aborted because of exception.
core.auth_failed_error=ADM0044:Admin authentication using realm [{0}] did not work.
core.auth_failed_exception=ADM0045:Error in admin authentication.
core.callflow_agent_init_failed=ADM0046:Error during callflow agent creation.
core.notification_for_nodeagents_could_not_be_invoked=ADM0047:Error during initialization of mechanism to notify Node Agents associated with this Domain Administration Server
core.could_not_determine_whether_instance_is_das=ADM0048: Could not determine from the config context if the instance is a DAS instance
core.system.service.mbean.not.registered=ADM0049: System Services MBean [{0}] could not be registered.
core.core.custom.mbean.registration.failure=ADM0050: Custom (user or system defined) MBeans could not be registered in MBeanServer. Check the configuration of these MBeans.
core.jvm.mbeans.not.registered=ADM051: MBeans that provide additional JVM monitoring information like system memory could not be registered.
#
# used in ManualChangeTracker.java 
core.error_getting_manual_changes=ADM0101: Error getting manual changes
core.tracker_thread_starting=ADM0102: Starting a thread for tracking manual changes
core.tracker_thread_stopping=ADM0103: Stopping the thread for tracking manual changes

#
#Common admin log messages from config mbeans start at 1001
#start with ServerController.
mbean.created_instance=ADM1001:New Server Instance [{0}] created successfully
mbean.create_instance_failed=ADM1002:Create Instance failed
mbean.del_instance_ok=ADM1003:Deleted Server Instance [{0}] successfully
mbean.del_instance_failed=ADM1004:Delete Instance failed
mbean.shutdown_started:ADM1005: Admin Server will shutdown in few seconds
mbean.begin_upload=ADM1006:Uploading the file to:[{0}]
mbean.upload_done=ADM1007:Uploaded the remote file at: [{0}]
mbean.upload_failed=ADM1008:Upload failed for file at: [{0}]
mbean.mbeaninfo_failed=ADM1009:Can''t get MBeanInfo for: [{0}]
mbean.prep_download=ADM1010:Preparing to download the file:[{0}]
mbean.begin_download=ADM1011:Starting the download ...
mbean.download_failed=ADM1012:Downloading the file to client failed
#start with ManagedServerInstance.
mbean.begin_deploy=ADM1021:Deploying the archive:[{0}]
mbean.deploy_failed=ADM1022:Deployment failed - Detailed Message:
mbean.begin_undeploy=ADM1023:Undeploying the deployed archive:[{0}]
mbean.undeploy_failed=ADM1024:Undeployment failed - Detailed Message:
mbean.begin_redeploy=ADM1025:Redeploying the deployed archive:[{0}]
mbean.redeploy_failed=ADM1026:Redeployment failed - Detailed Message:
mbean.list_components=ADM1027:Listing entities
mbean.list_failed=ADM1028:List operation failed - Detailed Message:
mbean.create_resource=ADM1029:Creating resource:[{0}]
mbean.create_resource_failed=ADM1030:Resource creation failed - Detailed Message:
mbean.delete_resource=ADM1031:Deleting resource:[{0}]
mbean.delete_resource_failed=ADM1032:Resource creation failed - Detailed Message:
mbean.delete_jdbc_pool=ADM1033:Deleting JDBC Connection Pool: [{0}]
mbean.delete_jdbc_pool_failed=ADM1034:Deletion of Connection Pool failed - Detailed Message:
mbean.instance_up:ADM1035:Server Instance [{0}] is running
mbean.instance_down:ADM1035:Server Instance [{0}] is not running
mbean.create_lifecycle=ADM1036:Created lifecycle module:[{0}]
mbean.create_lifecycle_failed=ADM1037:Lifecycle module creation failed - Detailed Message:
mbean.delete_lifecycle=ADM1038:Deleted lifecycle module:[{0}]
mbean.delete_lifecycle_failed=ADM1039:Lifecycle module deletion failed - Detailed Message:
mbean.cl_jar_loc=ADM1040:Client-jar location:[{0}]
mbean.send_event=ADM1041:Sent the event to instance:[{0}]
mbean.event_res=ADM1042:Status of dynamic reconfiguration event processing:[{0}]
mbean.event_reply=ADM1043:Response of instance on listening event:[{0}]
mbean.skip_on_apply=ADM1044:This event will not be applied:[{0}]. This is because it was applied as a part of a prior event.
mbean.event_sent=ADM1045:Sent the event:[{0}]
mbean.notif_failed=ADM1046:A change notification was not handled successfully. The server will need a restart for the change to be effective.
mbean.set_debug_failed=ADM1047:Setting jvm debug options in configuration file failed
mbean.stop_instance=ADM1048:Stopping the server instance:[{0}]
mbean.start_instance=ADM1049:Starting the server instance:[{0}]
mbean.start_instance_failed=ADM1050:Starting instance [{0}] failed. See instance logs for more details
mbean.debug_options=ADM1051:Debug options for the instance are set to:[{0}]
mbean.check_start_instance=ADM1052:Beginning to check status of START instance:[{0}]
mbean.check_stop_instance=ADM1053:Beginning to check status of STOP instance:[{0}]
mbean.start_instance_timeout=ADM1054:Checking of START instance timed out for: [{0}]
mbean.stop_instance_timeout=ADM1055:Checking of STOP instance timed out for: [{0}]
mbean.start_instance_success=ADM1056:Successfully started instance: [{0}]
mbean.stop_instance_success=ADM1057:Successfully stopped instance: [{0}]
mbean.restart_instance=ADM1058:Restarting the server instance : [{0}]
mbean.security_check_failed=ADM1059:Security check failed - Detailed Message:
mbean.is_debug_failed=ADM1060:isDebug check failed. Detailed Message: 
mbean.inst_down_skip_event=ADM1061:Skipping notifications because instance [{0}] is not running.
mbean.delete_temp_file_ok=ADM1062:The temporary file uploaded at [{0}] deleted. This does not necessarily imply that the deployment request from an administrative interface was served successfully
mbean.delete_temp_file_failed=ADM1063:The temporary file [{0}] used to upload before deployment could not be deleted, most likely because the file handle is occupied by admin server runtime. If a file with the same name is to be deployed again, this file will be overwritten during upload, which should not be a problem in future deployments. Please try deleting this file, if you see this message.
mbean.temp_upload_file_exists=ADM1064:The upload file at [{0}] exists and will be overwritten.
domain.stop_domain_admin=ADM1065:Beginning to stop the domain [{0}]. The administrative server will also be shutdown along with all the other running non administrative SunONE Application Server instances 
domain.stop_domain_noadmin=ADM1066:Beginning to stop the domain [{0}]. The administrative server will not be shutdown. Only the non administrative SunONE Application Server instances will be shutdown
mbean.del_jms_instance_failed=ADM1067:Deletion of JMS service instance failed.
mbean.stop_instance_failed=ADM1068:Stopping instance [{0}] failed. See instance logs for more details
mbean.start_instance_failed_details=ADM1069: Starting the server instance failed. Detailed message:
mbean.start_instance_debug=ADM1070:Starting the server instance:[{0}] in debug mode with JPDA port number [{1}]
mbean.deploy_chown_failed=ADM1071: Ownership of deployment directories could not be changed. [{0}]
mbean.filesize_notverified=ADM1072: Size of the file [{0}] could not be verified
mbean.get_local_host_error=ADM1073: Error while trying to determine fully qualified name of this host.
mbean.use_default_host=ADM1074: Could not determine fully qualified name of current host, will use localhost.
mbean.event_failed=ADM1075:Error on listening event:[{0}]
mbean.use_default_port=ADM1076: Could not determine port to form web service endpoint, will use default port [{0}].
mbean.autostart_ioexception=ADM1077: IOException while accessing autostart file.
mbean.autostart_enable_error=ADM1078: Autostart could not be enabled. Access to file [{0}] failed with error [{1}].
mbean.init_amx_success=ADM1079: Initialization of AMX MBeans started
mbean.init_amx_failed=ADM1080: Initialization of AMX MBeans failed. Detailed message:
mbean.create_app_reference=ADM1081:Creating the application reference [{0}]
mbean.create_app_reference_failed=ADM1082:Creating the application reference failed - Detailed Message:
mbean.delete_app_reference=ADM1083:Deleting the application reference [{0}]
mbean.delete_app_reference_failed=ADM1084:Deleting the application reference failed - Detailed Message:
mbean.start=ADM1085:Starting the application [{0}]
mbean.start_failed=ADM1086:Starting the application failed - Detailed Message:
mbean.stop=ADM1087:Stopping the application [{0}]
mbean.stop_failed=ADM1088:Stopping the application failed - Detailed Message:
mbean.event_result_error=ADM1089:A change notification was not handled successfully. Details about each server instance and its corresponding notification success status [{0}].
mbean.event_result_exception=ADM1090:A change notification was not handled successfully. Details about each server instance and its corresponding notification exceptions and messages [{0}].

# the following message is for keyfile modification from  security system 
# -- moved here because admin server is the only way to modify keyfile.
filerealm.write=SEC1107: Writing file realm data to [{0}].
filerealm.writeerror=SEC1108: Error writing file realm data.
#
#ADM1500 Onwards for JMX Connector
rjmx.lc.init=ADM1500:Initializing the lifecycle module for JMX Connector
rjmx.lc.address=ADM1501: Here is the JMXServiceURL for the JMXConnectorServer: [{0}]. This is where the remote administrative clients should connect using the standard JMX Connectors.
rjmx.lc.status=ADM1502: Status of System JMX Connector: Active = [{0}]
rjmx.lc.not_enabled=ADM1503: The system-jmx-connector port [{0}] is not enabled to start with server startup. Thus JSR 160 JMX Connector will not be started.
rjmx.std.address=ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [{0}].  This is where the remote administrative clients should connect using the standard JMX connectors
rjmx.std.status=ADM1506: Status of Standard JMX Connector: Active = [{0}]
rjmx.lc.stopping=ADM1509: JSR 160 JMX Connector Server at address [{0}] is now stopping
rjmx.lc.shutdown=ADM1510: JSR 160 JMX Connector Server is now shutdown

#Common admin log messages from monitoring related mbeans start at 5001
monitor.reg_root_mbean=ADM5001:Root Monitoring MBean [{0}] registered successfully
monitor.non_compliant_mbean=ADM5002:Attempt to register non-compliant monitoring mbean [{0}]
monitor.mbs_init_error=ADM5003:MBean Server initialization for monitoring failed.
monitor.channel_init_error=ADM5004:Monitoring channel initialization error. Monitoring will be disabled.
monitor.comp_init_error=ADM5005:Initialization of monitoring failed for component [{0}]
monitor.purge_mbean_failed=ADM5006: Monitoring MBean for component [{0}] could not be purged.
monitor.purge_mbean_failed_trace=ADM5007: Monitoring MBean could not be purged.
monitor.user_orb_mbean_name_used=ADM5008:User ORB monitoring component name [{0}] is in use.
monitor.orb_mbean_registered=ADM5009:ORB monitoring mbean named [{0}] registered
monitor.invalid_user_orb_name_hint=ADM5010:Invalid hint [{0}] for user ORB monitoring component name will be ignored.
#
#Common admin log messages from notification start at 5601
event.multicast_not_supported=ADM5601:Multicast event from instance [{0}] to [{1}] not supported.
event.handler_init_error=ADM5602:Event handler initialization error [{0}]
event.handler_error=ADM5603:Event listener error [{0}]
event.process_change=ADM5604:Processing config change [{0}]
event.change_null=ADM5605:Config Change or its xpath is null! Ignoring [{0}]
event.extract_change=ADM5606:Extracting changes to [{0}]
event.config_change_xpath=ADM5607:Config change xpath is [{0}]
event.purge_noop=ADM5608:Purging NO-OP event [{0}]
event.unknown_serverctx_type=ADM5609: Unknown server context type [{0}]. Unable to set the config context from the event multicaster. 
ADM5609.diag.cause.1=Event subsystem does not recognize the new implementation of the server context found in runtime. 
event.null_updated_attrs=ADM5610: List of updated attributes is null for xpath [{0}].
event.invalid_xpath_tokenization=ADM5611: Attempt to extract token number [{1}] from [{0}] when it contains only [{2}] tokens.
event.replace_ctx_failed=ADM5612: Attempt to replace config context in ConfigFactory Failed.
event.event_key_type_not_supported=ADM5613: The key type of the following class, is not allowed in admin event: [{0}]
event.event_key_is_malformed=ADM5614: The object key in the current event is malformed : [{0}]
event.object_name_in_event_is_invalid=ADM5615: The following object name is malformed: [{0}]
event.rmi_client_not_found=ADM5616: Admin channel did not return RMI client. Could not reset restart required.
event.exception_during_restart_reset=ADM5617: Unexpected error during resetting of restart required flag.
event.no_target_for_xpath=ADM5618: Restart required status is not updated correctly for the following configuration change (XPath is [{0}]).
event.taget_creation_failed=ADM5619: Target [{0}] could not be resolved. Invalid Name.
event.no_servers_in_target=ADM5620: Target [{0}] does not contain any servers. Restart required is not set for this target.
event.delete_prior_ctx_failed=ADM5621: Delete of prior config element failed.
event.config_add_ctx_failed=ADM5622: Update for the ConfigAdd event failed.
event.mbean_registry_entry.attribute.not.found=ADM5623: Attribute {0} not found in the MBean Registry.
#
#Common admin log messages from channel start at 5801
channel.creation_error=ADM5801:Admin server channel creation failed.
channel.key_read_error=ADM5802:Error reading key file.
channel.key_write_error=ADM5803:Error writing key file.
channel.client_host_null=ADM5804:Client host is null.
channel.local_access=ADM5805:Local access to admin server channel.
channel.addr_mismatch=ADM5806:Address mismatch: client/[{0}] server/[{1}]
channel.no_local_host=ADM5807:Unable to determine local host.
channel.key_mismatch=ADM5808:Shared key mismatch: client/[{0}] server/[{1}]
channel.reconfig_error=ADM5809:Error sending reconfig signal.
channel.clinet_nullargs=ADM5810:Attempt to initialize admin channel client with null arguments.
channel.auto_refresh_intr=ADM5811:Admin channel auto refresh thread interrupted.
channel.event_notify_error=ADM5812:Event notification fialed.
channel.event_renotify_error=ADM5813:Event notification retry failed.
channel.file_read_error=ADM5814:File [{0}] does not exist or can not be read.
channel.client_init_error=ADM5815:Error initializing admin channel client.
channel.comm_error=ADM5816:Communication error over admin channel [{0}].
channel.reconfig_enable_error=ADM5817:Dynamic Reconfiguration module for web tier could not be enabled.
channel.seed_file_older=ADM5818:Shared key file (last modified [{0}) is older than channel file (last modified [{1}]).
#
#Common admin log messages from admin app serving remote clients start at 6001
comm.init_ok=ADM6001:Remote client communication started
comm.recd_request=ADM6002:Received remote administration request
comm.remote_invoke_ok=ADM6003:Invoked the mbean:[{0}]
comm.remote_invoke_failed=ADM6004:Remote invocation failed - Detailed Message:
comm.get_attr_ok=ADM6005:Got attribute from the mbean:[{0}]
comm.get_attr_failed=ADM6006:Get attribute failed - Detailed Message:
comm.set_attr_ok=ADM6007:Set attribute in the mbean:[{0}]
comm.set_attr_failed=ADM6008:Set attribute failed - Detailed Message:
comm.get_attrs_ok=ADM6005:Got attributes from the mbean:[{0}]
comm.get_attrs_failed=ADM6006:Get attributes failed - Detailed Message:
comm.set_attrs_ok=ADM6007:Set attributes in the mbean:[{0}]
comm.set_attrs_failed=ADM6008:Set attributes failed - Detailed Message:
#
#Other messages start from 7001
general.print_attr_name=ADM7001:Name of the attribute:[{0}]
general.print_instance_name=ADM7002:Name of the instance:[{0}]
general.no_java_home=ADM7003:JAVA_HOME value can not be derived from admin server's configuration file, instance can not be created
general.instance_create_failed=ADM7003:Instance creation failed - Detailed Message:
general.exec_cmd=ADM7004:Executing the command in a subprocess:[{0}]
general.delete_stop_failed=ADM7005:Stopping the Server Instance failed. Deleting the configuration folder, please kill the processes
general.free_port_failed=ADM7006:Process of finding out free port on this system failed. Generally not being able to find a free port indicates a current or potential problem. Administration server will try to proceed by using default ports. See dtd/manuals for default port assignments
general.perm_certs=ADM7007:Permanent certs in certdb:[{0}]
general.ca_certs=ADM7008:CA certs in certdb:[{0}]
general.cert_name=ADM7009:Cert nickname:[{0}]
general.unexpected_exception=ADM7010:Unexpected exception or error.
general.delete_instance_not_complete=ADM7011:Although instance {0} was removed, it was not deleted completely. Some files or directories may have been in use at the time. Please manually delete the instance directory to ensure complete deletion.
general.free_port=ADM7012:The port [{0}] is currently free. This will be used to bind, when the Server Instance starts
general.port_derivation_failed=ADM7013:Process of finding out for clashing ports from other instances failed. This instance will use the given port without checking whether it clashes with HTTP ports of other instances - Detailed Message:
general.port_occupied=ADM7014:This port is already occupied by an element or attribute in this Server Instance:[{0}]

mbean.config.attribute_not_found=ADM2001:Attribute [{0}]  is not found
mbean.config.getmbeaninfo_failed=ADM2002:Can not get MBean Info.
mbean.config.get_attribute=ADM2003:GenericConfigurator: getting attribute for dotted name: [{0}]
mbean.config.set_attribute=ADM2004:GenericConfigurator: setting attribute for dotted name: [{0}]=[{1}]
mbean.config.base_get_attribute=ADM2005:ConfigMBeanBase:getting value for attribute [{0}]
mbean.config.base_set_attribute=ADM2006:ConfigMBeanBase:set attribute [{0}]=[{1}]
mbean.config.base_got_attribute=ADM2007:ConfigMbeanBase:Returned value for attribute [{0}] is [{1}](string)/[{2}](after conversion)
mbean.config.base_get_property=ADM2008:ConfigMBeanBase: getting property [{0}]
mbean.config.base_set_property=ADM2009:ConfigMBeanBase: setting property [{0}]=[{1}]
mbean.config.get_def_attr_value=ADM2010:ConfigMBeanBase:getting default value for attribute [{0}]
mbean.config.admin.apply_failed=ADM2011:Apply Changes failed for admin instance. Root cause: [{0}
mbean.config.admin.canapply_failed=ADM2012:Check to determine whether changes can be applied failed, assuming can not apply changes. Root cause: [{0}]
mbean.config.admin.usemanual_failed=ADM2013:Unable to use manual changes to configuration. Root Cause: [{0}]
mbean.config.admin.applyneeded_failed=ADM2014:Unable to determine whether admin instance configuration has been changed and not applied. Root cause: [{0}]
mbean.config.get_confbeanbyxpath=ADM2015:Get config bean by xpath: [{0}]
mbean.config.list_names_continuations=ADM2016:Get list continuations for dotted name: [{0}]
mbean.config.malformed_dotted_name=ADM2017:Malformed dotted name: [{0}]
mbean.config.list_names_failed=ADM2018:Exception during List names continuation operation. Detailed message:
mbean.config.get_attribute_default=ADM2019:Getting default values for instance: {0}; MBean Type: {1}
admin.dotted_names_init_exception=ADM2020:Error initializing dotted Names
mbean.config.log_config_id=ADM2021:MBean class [{0}] using is config id [{1}]

addPasswordAliasException=ADM3000:Exception adding password alias {0}
removePasswordAliasException=ADM3000:Exception removing password alias {0}
updatePasswordAliasException=ADM3000:Exception updating password for alias {0}
listPasswordAliasException=ADM3000:Exception listing password aliases 


diagnostic-service.copy_failed=DIAG9001:Could not copy {0} due to {1}
diagnostic-service.copy_config_instances_failed=DIAG9002:Could not copy config files to dir {0} due to {1}
diagnostic-service.dest_log_file=DIAG9003:Destination log file is {0}
diagnostic-service.dtd_file_name=DIAG9004:domain.xml DTD file name is {0}
diagnostic-service.generated_report_name=DIAG9005:Generated report name is {0}
diagnostic-service.attribute_name=DIAG9006:diagnostic-service Attribute Name is {0}
diagnostic-service.attribute_value=DIAG9007:diagnostic-service Attribute value is {0}
diagnostic-service.capture_app_dd=DIAG9008:diagnostic-service capture-app-dd value is {0}
diagnostic-service.capture_hadb_info=DIAG9009:diagnostic-service capture-hadb-info value is {0}
diagnostic-service.capture_install_log=DIAG9010:diagnostic-service capture-install-log value is {0}
diagnostic-service.capture_checksum=DIAG9011:diagnostic-service compute-checksum value is {0}
diagnostic-service.min_log_level=DIAG9012:diagnostic-service min-log-level value is {0}
diagnostic-service.max_log_entries=DIAG9013:diagnostic-service max-log-entries value is {0}
diagnostic-service.target_type=DIAG9014:Report Generation target is {0}
diagnostic-service.error_loading_xml=DIAG9015:Error loading domain.xml due to {0}
diagnostic-service.loadxml_configfile=DIAG9016:Loading domain.xml at {0}
diagnostic-service.error_collecting_data=DIAG9017: Error while collecting data due to {0}
diagnostic-service.compute_checksum_failed=DIAG9018:Could not compute checksum of  {0} due to {1}
diagnostic-service.invalid_target=DIAG9019: Invalid target {0} 
diagnostic-service.validate_local_target=DIAG9020:Target while validating local target : {0} & targetDir {1}
diagnostic-service.target_details=DIAG9021:target {0}, targetDir {1} , type {2} ,instances {3}
diagnostic-service.error_initalize_client_pluggable_factory=DIAG9022:Error initializing client pluggable factory {0}
diagnostic-service.resolver_targetDir=DIAG9033:While resolving target dir, instanceRoot = {0 } and targetDir = {1} 
diagnostic-service.execution_context_das=DIAG9034:Execution Context is DAS
diagnostic-service.execution_context_nondas=DIAG9035:Execution Context is not DAS
diagnostic-service.target_dir=DIAG9036:Target Dir is {0}
diagnostic-service.target=DIAG9037:Target is {0}
diagnostic-service.target_type=DIAG9038:Target type is {0}
diagnostic-service.execution_context=DIAG9039:Execution Context is {0}
diagnostic-service.local_target_resolver=DIAG9040:Using EE local Target resolver for resolving target details
diagnostic-service.local_target_resolver=DIAG9041:Using EE remote Target resolver for resolving target details
diagnostic-service.instances=DIAG9042: During invocation of report generation using Node Agent MBean instances are{0}
diagnostic-service.error_retrieving_na=DIAG9043:Exception in retrieving node agent name for a server 
diagnostic-service.create_na_diagnostic_mbean=DIAG9044:Creating NodeAgent Diagnostic MBean for node agent : {0}
diagnostic-service.error_creating_na_diagnostic_mbean=DIAG9045:Error creating NodeAgent Diagnostic MBean
diagnostic-service.error_generating_report_na=DIAG9046:Error generating report on nodeagent 
diagnostic-service.repository_dir=DIAG9047:Repository Dir is {0}
diagnostic-service.error_initalize_pluggable_factory=DIAG9048:Unable to retrieve Pluggable Feature Factory
diagnostic-service.no_data_collected=DIAG9049:No Diagnostic data has been collected
DIAG9049.diag.check.1=Check whether the target [domain, node-agent, instance, cluster] is running.

registry.publish_failure=ADM8001:Failed to publish Web Service {0} to registries.
registry.publish_failure_exception=ADM8002: Failed to publish Web Service to registries.
registry.publish_success=ADM8003:Web Service {0} published successfully to registries.
registry.unpublish_failure=ADM8004:Failed to unpublish Web Service {0} from registries.
registry.unpublish_failure_exception=ADM8005:Failed to unpublish Web Service from registries.
registry.unpublish_success=ADM8006:Unpublished Web Service {0} from registries.
registry.deploy_registry_connector_resource=ADM8007:Cannot find a connector module of type {0}. Deploy a connector module with type {0}
registry.specify_registry_type =ADM8008: Registry type unspecified. Registry type has to be either {0} or {1}.
registry.cannot_add_to_domain_xml=ADM8009 : Cannot add Registry Location to Web Service End point in domain.xml
registry.invalid_webservice_name_publish_failure=ADM8010: Invalid Web Service Name {0}. Cannot publish Web Service to registries.
registry.wsdl_absent_publish_failure=ADM8011: WSDL not found for Web Service {0}. Cannot publish Web Service to registries.
registry.registry_location_absent_publish_failure=ADM8012: Registry Location {0} not found. Cannot publish Web Service to it.
registry.registry_location_naming_exception_publish_failure=ADM8013: Registry Location not found. Cannot publish Web Service to it.
registry.not_published=ADM8014: Web Service {0} not published. Look at preceding errors for probable causes.
registry.invalid_webservice_name_unpublish_failure=ADM8015: Invalid Web Service Name {0}. Cannot publish Web Service from registries.
registry.registry_location_absent_unpublish_failure=ADM8016: Registry Location {0} not found. Cannot unpublish Web Service from it.
registry.registry_location_naming_exception_unpublish_failure=ADM8017: Registry Location not found. Cannot unpublish Web Service to it.
registry.not_published=ADM8018: Web Service {0} not unpublished. Look at preceding errors for probable causes.
registry.list_failure=ADM8019: Cannot list registry location.
registry.wsdl_absent=ADM8020: WSDL not found for Web Service {0}.
registry.access_url=ADM8021: Access URI for Web Serivce {0} is {1}.
registry.service_creation_failed=ADM8022: Cannot create Service Object in the registry.
registry.service_binding_creation_failed=ADM8023: Cannot create Service Binding Object in the registry.
registry.slot_creation_failed=ADM8024: Failed to create Slots to categorize categories in the registry.
registry.classification_creation_failed=ADM8025: Failed to create Classification and ClassificationScheme Object in the registry/
registry.successful_publish=ADM8026: Organization {0} successfully published to registry.
registry.organization_not_published=ADM8027: Organization {0} could not be published to registry. Look at the following exceptions for probable causes.
registry.cannot_find_classification_scheme=ADM8028: Cannot find Classification Scheme for Web Service {0}. Cannot unpublish from registry. Please unpublish manually.
registry.about_to_unpublish=ADM8029: Issuing request to unpublish {0} from Organization {1}.
registry.unpublish_failed=ADM8030: Failed to unpublish Web Service from Registry.
registry.classification_scheme_delete_unsuccessful=ADM8031: Failed to delete Classification Scheme Object {0} from the registry. Please delete manually.
registry.classification_scheme_delete_successful=ADM8032: Deleted Classification Scheme Object {0} successfully for Web Service {1}.
registry.cleanup_services_first=ADM8033:Organization {0} has services - cannot delete it. Please delete all services from registry first.
registry.delete_org_failed=ADM8044:Delete Organization {0} operation failed. Please delete it manually from the registry.
registry.delete_services_failed=ADM8045:Delete Services {0} operation failed. Please delete it manually from registry.
registry.delete_servicebindings_failed=ADM8046: Delete ServiceBinding {0} operation failed. Delete it manually from registry.
callflow.table_already_exists_error=ADM11001: Error creating table {0} as table already exists
callflow.table_creation_error=ADM11002: Error creating table {0}. Most likely cause is that table already exists. Please look at the following exception.
callflow.enable_failed=ADM11003:Error enabling callflow.
callflow.connection_obtain_failed=ADM11004: Failed getting a connection to the callflow database
callflow.error_get_request_info=ADM11005: Error executing query request information to the database.
callflow.error_get_callstack_info=ADM11006: Error executing query callstack information to the database.
callflow.error_get_pie_info=ADM11007: Error executing query pie information to the database.
callflow.turn_off_callflow_before_clearData=ADM11008: ClearData disabled. Turn Call Flow off before calling clearData.
callflow.enable_succeeded=ADM11009: CallFlow enable successful.
callflow.disable_succeeded=ADM11010: CallFlow disable successful
callflow.request_start_operation_failed=ADM11011: Call flow request start operation failed.
callflow.add_request_info_operation_failed=ADM11012: Call flow add request info operation failed.
callflow.add_request_info_disallowed=ADM11013: Adding request information is disallowed after request initialization is completed. Request initialization is completed during the first startTime operation.
callflow.request_end_operation_failed=ADM11014: Call flow request end operation failed.
callflow.start_time_operation_failed=ADM11015: Call flow start time operation failed.
callflow.end_time_operation_failed=ADM11016: Call flow end time operation failed.
callflow.ejb_method_start_operation_failed=ADM11017: Call flow EJB method start operation failed.
callflow.ejb_method_end_operation_failed=ADM11018: Call flow EJB method end operation failed.
callflow.web_method_start_operation_failed=ADM11019: Call flow web method start operation failed.
callflow.web_method_end_operation_failed=ADM11020: Call flow web method end operation failed.
callflow.async_thread_interrupted=ADM11021: Call flow asynchronous writer thread interrupted.
callflow.async_db_write_failed=ADM11022: Database write operation by call flow asynchronous thread failed.
callflow.transfer_to_async_thread_interrupted=ADM11023: Data transfer to call flow asynchronous thread interrupted.

####################################################################################################################
#####  Custom MBean starts at 1600
####################################################################################################################
cmb.successfulDelete=ADM1600: The MBean, {0}, was successfully deleted dynamically.

cmb.unsuccessfulRegistration=ADM1601: Received a request for registration of MBean, {0}, but it is already registered in the MBeanServer.
ADM1601.diag.cause.1=Registration of the MBean was unsuccessful because it is already registered.
ADM1601.diag.check.1=Run 'asadmin list-mbeans' to see a list of registered MBeans

cmb.successfulRegistration=ADM1602: The MBean, {0}, was successfully registered in the MBeanServer.

cmb.unsuccessfulUnRegistration=ADM1603: Unable to unregister the MBean, {0}. This MBean was never registered in the MBeanServer. In general, this should not be a problem.
ADM1603.diag.cause.1=Unregistration of the MBean failed because it is not registered.
ADM1603.diag.check.1=Run 'asadmin list-mbeans' to see a list of registered MBeans

cmb.successfulUnRegistration=ADM1604: The MBean, {0}, was successfully unregistered from the MBeanServer.
cmb.gotConfigChange=ADM1605: Received a ConfigChange event for: [{0}]

cmb.illegalHandleUpdate=ADM1606: Can''t handle updating an MBean element itself ({0}).  The MBean is updated in terms of its xml-attributes, none of which are dynamically reconfigurable.
ADM1606.diag.cause.1=Can't handle updating an MBean element
ADM1606.diag.check.1=Note that none of the attributes of "mbean" element except 'enabled' and 'object-name' are modifiable dynamically. Only the properties in this element that are actually the attributes of the runtime mbean are modifiable dynamically. 

cmb.mbeanIsDisabled=ADM1607: Received an MBean change event, but the MBean, {0}, is disabled.  Disabled MBeans can''t have their state changed.
ADM1607.diag.cause.1=Disabled MBeans are not allowed to have their state changed
ADM1607.diag.check.1=Try enabling the MBean

cmb.registerError=ADM1608: An MBean with name: {0} could not be loaded. Continuing to load other MBeans";
ADM1608.diag.cause.1=The MBeanServer refused to load the MBean
ADM1608.diag.check.1=Try redeploying the MBean

cmb.loadingMBean1=ADM1609: Attempting to load mbean: {0}
cmb.loadingMBean2=ADM1610: The real mbean object-name would be: {0}
cmb.loadingMBean3=ADM1611: The Class: {0} could not be loaded by class loader: {1} or any of its parents.
cmb.loadingMBean4=ADM1612: The Class: {0} could not be initialized by class loader: {1} or any of its parents.
cmb.loadingMBean5=ADM1613: The Class: {0} could not be instantiated because it appears to be an interface or abstract class. Check MBean code.
cmb.loadingMBean6=ADM1614: The Class: {0} could not be could not be instantiated because of illegal access or default constructor not being available. Check MBean code.
cmb.loadingMBean7=ADM1615: The Class: {0} could not be instantiated because of an error in static initializer. Check MBean code.
cmb.loadingMBean8=ADM1616: MBean Class: {0} initiating class loader: {1}, defining class loader: {2} 
cmb.initMBean=ADM1617: Setting attribute: {0} on mbean: {1}

cmb.unloadMBeanError=ADM1618: Can''t unregister MBean: {0} 
ADM1618.diag.cause.1=Can not unregister the MBean.  This is a non-fatal error.
ADM1618.diag.check.1=Try restarting the AppServer

cmb.ee.handleUpdate=ADM1619: handleUpdate ..... Remote Server: received -- {0} {1}
cmb.ee.handleDelete=ADM1620: handleDelete ..... Remote Server: received -- {0} {1}
cmb.ee.handleCreate=ADM1621: handleCreate ..... Remote Server: received -- {0} {1}
cmb.ee.mkdirGood=ADM1622: The parent directory was created successfully: {0}
cmb.ee.mkdirBad=ADM1623: The parent directory could not be created: {0}
cmb.ee.downloadClass=ADM1624: The MBean class file was downloaded here: {0}
cmb.ee.downloadInterfaceGood=ADM1625: The Standard MBean interface file was downloaded from: {0}
cmb.ee.downloadInterfaceBad=ADM1626: This is not a standard MBean, because the corresponding standard MBean interface could not be found
cmb.ee.instanceRoot=ADM1627: Instance Root for DAS: {0}
cmb.ee.remoteLocation=ADM1628: DAS MBeans are stored at this DAS location: {0}
cmb.ee.remotePath=ADM1629: MBean just created is at this DAS location: {0}
cmb.ee.copyLocation=ADM1630: MBean will be copied here: {0}
cmb.ee.defExists=ADM1631: The MBean Definition: {0} already exists in the domain
cmb.ee.objNameExists=ADM1632: The ObjectName: {0} already exists in target: {1}
cmb.badAttribute=ADM1633:The attribute [{0}] doesn''t exist in the MBean.  Here is a list of accessible attributes: {1}
cmb.badCharAttribute=ADM1634:The attribute [{0}] is a character attribute.  You can set it with a String of length=1 only.  You tried to set it to [{1}]