Index: appclient/server/core/src/main/resources/org/glassfish/appclient/server/core/LogStrings.properties =================================================================== --- appclient/server/core/src/main/resources/org/glassfish/appclient/server/core/LogStrings.properties (revision 34026) +++ appclient/server/core/src/main/resources/org/glassfish/appclient/server/core/LogStrings.properties (working copy) @@ -60,7 +60,7 @@ ACDEPL106.diag.cause.1=This is an internal error. ACDEPL106.diag.check.1=Please file an issue with a reproducible test case. -enterprise.deployment.appclient.jws.uriOutsideContextRoot=ACDEPL107: Attempt to add or retrieve content with URI {0} to HTTP adapter with context root {1} and user-friendly context root {2} rejected; URIs must fall within the adpater context root +enterprise.deployment.appclient.jws.uriOutsideContextRoot=ACDEPL107: Attempt to add or retrieve content with URI {0} to HTTP adapter with context root {1} and user-friendly context root {2} rejected; URIs must fall within the adapter context root ACDEPL107.diag.cause.1=This is an internal error. ACDEPL107.diag.check.1=Please file an error with a reproducible test case. Index: appclient/client/acc/src/main/resources/org/glassfish/appclient/client/acc/LogStrings.properties =================================================================== --- appclient/client/acc/src/main/resources/org/glassfish/appclient/client/acc/LogStrings.properties (revision 34026) +++ appclient/client/acc/src/main/resources/org/glassfish/appclient/client/acc/LogStrings.properties (working copy) @@ -26,7 +26,7 @@ appclient.notPublicOrNotStatic=ACC005: The main method is either not public or not static ACC005.diag.cause.1=The main method for the app client is not declared as "public." ACC005.diag.check.1=Declare the main method as "public." -ACC005.diag.cause.2=The main method for the app clientis not declared as "static." +ACC005.diag.cause.2=The main method for the app client is not declared as "static." ACC005.diag.check.2=Declare the main method as "static." appclient.notVoid=ACC006: The main method's return type is not void Index: deployment/common/src/main/resources/com/sun/logging/enterprise/system/tools/deployment/LogStrings.properties =================================================================== --- deployment/common/src/main/resources/com/sun/logging/enterprise/system/tools/deployment/LogStrings.properties (revision 34026) +++ deployment/common/src/main/resources/com/sun/logging/enterprise/system/tools/deployment/LogStrings.properties (working copy) @@ -93,7 +93,7 @@ # Start of part of bug 4974675 - missing message IDs enterprise.deployment.backend.optionalpkg.dependency.exception=DPL5400:Exception occurred : {0}.\ -enterprise.deployment.backend.optionalpkg.dependency.notexist=DPL5401:Optional package {0} does not exist or its Specification-Version doesnot match!! Unable to satisfy dependency for {1} +enterprise.deployment.backend.optionalpkg.dependency.notexist=DPL5401:Optional package {0} does not exist or its Specification-Version does not match!! Unable to satisfy dependency for {1} enterprise.deployment.backend.optionalpkg.dependency.satisfied=DPL5402:Optional package dependency satisfied for {0} enterprise.deployment.backend.optionalpkg.dependency.null.error=DPL5403:Either Extension-Name or Specification-Version for the optional package is not specified for {0}.\ @@ -208,7 +208,7 @@ enterprise.deployment.backend.norolemapperfactorydefine=DPL8015: This application has no role mapper factory defined # Deployment client side logging -retrieve_client_stub_not_applicable="Retrieve client stub operation does not apply to module [{0}] with module type [{1}]." +retrieve_client_stub_not_applicable=Retrieve client stub operation does not apply to module [{0}] with module type [{1}]. enterprise.deployment.backend.ejbRefTypeMismatch=DPL8017: Ejb-ref type mismatch for ejb reference {0}. Reference declares type {1} but target ejb {2} has {3} interface of type {4}. DPL8017.diag.cause.1=Possible type mismatch in ejb-ref/ejb-local-ref/@EJB Index: core/kernel/src/main/resources/com/sun/logging/enterprise/system/core/LogStrings.properties =================================================================== --- core/kernel/src/main/resources/com/sun/logging/enterprise/system/core/LogStrings.properties (revision 34026) +++ core/kernel/src/main/resources/com/sun/logging/enterprise/system/core/LogStrings.properties (working copy) @@ -42,10 +42,10 @@ core.file_io_exception=CORE5029: File IO exception : core.unsupported_javac_option=CORE5030: Unsupported Javac option [{0}] found in server configuration. core.error_while_loading_license=CORE5031: License exception occurred while loading license. -core.unexpected_exception_no_valid_licfile=CORE5032: UnExpected error occurred, license file is not valid. +core.unexpected_exception_no_valid_licfile=CORE5032: Unexpected error occurred, license file is not valid. core.unexpected_exception_while_checking_validity=CORE5033: Thank you for trying the Sun Java System Application Server. Your evaluation license has expired. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. core.unexpected_exception_while_setting_remote_permission=CORE5034: Unexpected error occurred while setting remote permissions -core.unexpected_exception_while_setting_instance_limit=CORE5035: UnExpected error occurred while setting instance limit +core.unexpected_exception_while_setting_instance_limit=CORE5035: Unexpected error occurred while setting instance limit core.invalid_license_error=CORE5036: Your license is invalid. Please go to http://www.sun.com/as7upgrade to get a valid license. core.license_expiring=CORE5037: Thank you for trying the Sun Java System Application Server. Your evaluation license will expire in [{0}] days. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. core.license_expired=CORE5038:Thank you for trying the Sun Java System Application Server. Your evaluation license has expired. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. @@ -77,7 +77,7 @@ core.no_resource_type=CORE5058: No such resource type {0} core.resource_loading_error=CORE5059: Error in loading resource core.shutting_down_resource_adapters=CORE5068 : Stopping all J2EE Connector 1.5 Compliant resource adapters ... -core.ra_shutdown_complete=CORE 5061 : Resource adapters Stop() Complete +core.ra_shutdown_complete=CORE5061 : Resource adapters Stop() Complete core.error_createrb_disabled=CORE5067:Error in creating root mbean for disabled application during deployment. server.ioexception=CORE5060: IOException : @@ -97,10 +97,10 @@ shutdown.started=Server shutdown in progress... # j2eerunner.cannotCreateServerContext=CORE5070:A server context could not be created -j2eerunner.initError=CORE5071: An error occured during initialization -j2eerunner.reconfigError=CORE5072: An error occured during startup/reconfig +j2eerunner.initError=CORE5071: An error occurred during initialization +j2eerunner.reconfigError=CORE5072: An error occurred during startup/reconfig j2eerunner.shuttingdown=CORE5073: Application server shutdown in progress -j2eerunner.shutdownError=CORE5074: An error occured during shutdown +j2eerunner.shutdownError=CORE5074: An error occurred during shutdown j2eerunner.licenseisinvalid=CORE5075: Your license is invalid. Please obtain a valid license. [{0}] j2eerunner.printstartinfo=CORE5076: Using [{0}, Version {1}] from [{2}] # @@ -118,7 +118,7 @@ application.default_locale=Application Server default locale is {0} server.shutdown_complete=Server shutdown complete. j2eerunner.pluggable_feature_noinit=SERVER0009: Pluggable features using class {0} could not be initialized. Server will run with default features. -shutdown.error=An error occured during server shutdown : {0} +shutdown.error=An error occurred during server shutdown : {0} # enterprise.orb_reference_exception=CORE5080: Exception resolving initial reference of ORB: enterprise.createorb_exception=CORE5081: Exception while creating ORB: [{0}] @@ -146,19 +146,19 @@ pemain.failureOnReadingSecurityIdentity=An exception was encountered when reading in the user's identity. socketservice.init_done=CORE5098: AS Socket Service Initialization has been completed. socketservice.unknown_ex=UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false -socketservice.port_conflict=A conflict occured on port {0} . Server is shutting down. -socketservice.stop_lc_ex=Exception while stoppping Lifecycle. +socketservice.port_conflict=A conflict occurred on port {0} . Server is shutting down. +socketservice.stop_lc_ex=Exception while stopping Lifecycle. mqra.start=Broker Type {0}. Starting RA # # Used in SystemAppLifecycle # core.loading_system_apps=CORE5100:Loading system apps -core.exception_while_deploying_system_apps=CORE5101:Exception occured while deploying system apps +core.exception_while_deploying_system_apps=CORE5101:Exception occurred while deploying system apps core.deploying_system_apps=CORE5102:Deploying system apps to target {0} from directory {1} core.deployed_system_apps=CORE5103:Deployed system apps to target {0} core.system_app_dir_not_found=CORE5104:Directory {0} not found or cannot read -core.exception_while_getting_targets=CORE5105:Exception occured while getting targets -error_occured_in_isreg=CORE5106:Exception occured while finding application registration +core.exception_while_getting_targets=CORE5105:Exception occurred while getting targets +error_occured_in_isreg=CORE5106:Exception occurred while finding application registration # # Used in com.sun.enterprise.server.ManagerFactory Index: jdbc/jdbc-ra/jdbc-core/src/main/java/com/sun/gjc/common/LocalStrings.properties =================================================================== --- jdbc/jdbc-ra/jdbc-core/src/main/java/com/sun/gjc/common/LocalStrings.properties (revision 34026) +++ jdbc/jdbc-ra/jdbc-core/src/main/java/com/sun/gjc/common/LocalStrings.properties (working copy) @@ -18,6 +18,6 @@ jdbc.cannot_enlist=Cannot enlist this ManagedConnection in this transaction because : {0} jdbc.cannot_assoc=Cannot associate this ManagedConnection because : {0} jdbc.error_during_setAutoCommit=SQL Exception : Unable to set AutoCommit property. -jdbc.statement-cache.datastructure.init.failure=Error while creating the Statement cache datastructure for type : {0} +jdbc.statement-cache.datastructure.init.failure=Error while creating the Statement cache data structure for type : {0} jdbc.statement-cache.datastructure.init.failure.exception=Exception : {0} jdbc.statement-cache.default.datastructure=LRUCacheImpl Index: jdbc/jdbc-ra/jdbc-core/src/main/resources/com/sun/gjc/spi/LogStrings.properties =================================================================== --- jdbc/jdbc-ra/jdbc-core/src/main/resources/com/sun/gjc/spi/LogStrings.properties (revision 34026) +++ jdbc/jdbc-ra/jdbc-core/src/main/resources/com/sun/gjc/spi/LogStrings.properties (working copy) @@ -59,7 +59,7 @@ jdbc.exc_table_validation=RAR5074 : Table based validation detected invalid connection. Querying the table {0} failed. Set resource-adapter log-level to FINE for exception stack trace. RAR5074.diag.cause.1=The Connection object is now invalid due to database restart RAR5074.diag.cause.2=The connection object is now invalid since the database is not up and running -RAR5074.diag.cause.3=The JDBC driver cannot excute the statement due to internal error +RAR5074.diag.cause.3=The JDBC driver cannot execute the statement due to internal error RAR5074.diag.check.1=Switch on the connection validation property of the connection pool and try again RAR5074.diag.check.2=If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up RAR5074.diag.check.3=Check the server log and please contact Sun Microsystems with the complete error log @@ -67,8 +67,8 @@ jdbc.exc_prepare_stmt=RAR5076 : Exception while preparing statement jdbc.exc_close_stmt=RAR5077 : Exception while closing statement jdbc.exc_beg_local_tx=RAR5078 : Exception while beginning local transaction -jdbc.exc_commit_local_tx=RAR5079 : Exception while commiting local transaction -jdbc.exc_commit_xa=RAR5080 : Exception while commiting xa transaction +jdbc.exc_commit_local_tx=RAR5079 : Exception while committing local transaction +jdbc.exc_commit_xa=RAR5080 : Exception while committing xa transaction jdbc.exc_rolbk_local_tx=RAR5081 : Exception while rolling back local transaction jdbc.exc_cci_mc_constr=RAR5082 : Exception while creating CciManagedConnection jdbc.exc_destroy=RAR5083 : Exception while destroying physical connection @@ -94,12 +94,12 @@ jdbc.exc_rs_con=RAR5097 : Exception while checking if RA supports concurrency in combo with give RS jdbc.exc_rs_type=RAR5098 : Exception while checking if RA supports a type of RS jdbc.exc_cnfe_ds=RAR5099 : Wrong class name or classpath for Datasource Object -RAR5099.diag.cause.1=Classpath is not propertly set in the domain.xml +RAR5099.diag.cause.1=Classpath is not properly set in the domain.xml RAR5099.diag.cause.2=The application server process does not have read permissions on the directory that holds the classes/jar RAR5099.diag.check.1=Check if the server classpath specified in the java-config element in the domain.xml has an entry for the jar containing this class RAR5099.diag.check.2=Check that the directory where the classes/jars reside have read permission for the application server process jdbc.exc_cnfe=RAR5100 : Wrong class name or classpath for {0} -RAR5100.diag.cause.1=Classpath is not propertly set in the domain.xml +RAR5100.diag.cause.1=Classpath is not properly set in the domain.xml RAR5100.diag.cause.2=The application server process does not have read permissions on the directory that holds the classes/jar RAR5100.diag.check.1=Check if the server classpath specified in the java-config element in the domain.xml has an entry for the jar containing this class RAR5100.diag.check.2=Check that the directory where the classes/jars reside have read permission for the application server process @@ -113,14 +113,14 @@ RAR5102.diag.cause.2=This is an internal server/JVM error. Please contact Sun Microsystems with the complete error log RAR5102.diag.check.1=See if the application server process has permission to read the directory where the class/jar resides RAR5102.diag.check.2=Check if all relevant JVM patches are installed on your machine. Please contact Sun Microsystems with the complete error log -jdbc.exc_re=RAR5105 : Connection Error Occured : {0} +jdbc.exc_re=RAR5105 : Connection Error occurred : {0} RAR5105.diag.cause.1=The connection validation method is incorrect, it should be one of auto-commit, meta-data, table RAR5105.diag.cause.2=The connection is no longer valid. It could have been rendered invalid due to database restart/shutdown RAR5105.diag.check.1=Check if the connection validation is one of : auto-commit, meta-data or table. If the method is table, check that the table name is correct. RAR5105.diag.check.2=If the database has been restarted, restart the application server as well. If the database is down, start it up jdbc.exc_autocommit_validation=RAR5106 : AutoCommit based validation detected invalid connection. Set resource-adapter log-level to FINE for exception stack trace RAR5106.diag.cause.1=Database server is not up thus rendering the connection invalid -RAR5106.diag.cause.2=The JDBC driver is unable to provide the autocommit status of the connection due to an internal error +RAR5106.diag.cause.2=The JDBC driver is unable to provide the auto-commit status of the connection due to an internal error RAR5106.diag.check.1=Check if the database server is up and running RAR5106.diag.check.2=This is an internal error. Please contact Sun Microsystems with the complete error log jdbc.exc_metadata_validation=RAR5107 : Meta-Data based validation detected invalid connection. Set resource-adapter log-level to FINE for exception stack trace @@ -135,7 +135,7 @@ RAR5108.diag.check.1=Please bring up the database if not up already. Check if the connection validation pool property is set, else set this property if the database server will be restarted in the future. jdbc.exc_tx_iso=RAR5109 : Error while setting transaction isolation level RAR5109.diag.cause.1=Jdbc driver has thrown an SQLException while setting the isolation level. -RAR5109.diag.check.1=Check your connection pool configuration and make sure that the isolationlevel is correct +RAR5109.diag.check.1=Check your connection pool configuration and make sure that the isolation level is correct RAR5109.diag.check.2=Check whether your driver supports the isolation level you have specified in the connection pool. jdbc.exc_create_mc=RAR5110 : Error creating managed Connection with user and password : {0} RAR5110.diag.cause.1=The URL specified is incorrect @@ -156,7 +156,7 @@ RAR5113.diag.check.2=Check if the size of your connection pool is sufficiently large for serving all requests RAR5113.diag.check.3=Check the server log and please contact Sun Microsystems with the full error log jdbc.exc_get_conn=RAR5114 : Error allocating connection : [{0}] -RAR5114.diag.cause.1=There was an SQLException while acquiring connection from the Database. Please see the detailed exception mesasage for more information +RAR5114.diag.cause.1=There was an SQLException while acquiring connection from the Database. Please see the detailed exception message for more information RAR5114.diag.cause.2=The Connection pool is full and incapable of serving more requests at this point. Please try later. RAR5114.diag.cause.3=There is an internal server error. Please contact Sun Microsystems with the complete log message RAR5114.diag.check.1=Check if the database server is correctly configured @@ -170,11 +170,11 @@ RAR5116.diag.check.1=Check that the Database server is up and running RAR5116.diag.check.2=Check if the size of your connection pool is sufficiently large for serving all requests RAR5116.diag.check.3=Check the server log and please contact Sun Microsystems with the full error log -jdbc.cannot_set_autocommit=RAR7009: Cannot set autocommit mode for physical connection +jdbc.cannot_set_autocommit=RAR7009: Cannot set auto-commit mode for physical connection jdbc.exc_custom_validation=RAR9000 : Custom validation detected invalid connection. Executing the isValid() of {0} class failed. Set resource-adapter log-level to FINE for exception stack trace. RAR9000.diag.cause.1=The Connection object is now invalid due to database restart RAR9000.diag.cause.2=The connection object is now invalid since the database is not up and running -RAR9000.diag.cause.3=The JDBC driver cannot excute the statement due to internal error +RAR9000.diag.cause.3=The JDBC driver cannot execute the statement due to internal error RAR9000.diag.check.2=If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up RAR9000.diag.check.3=Check the server log and please contact Sun Microsystems with the complete error log jdbc.set_custom_validation_class_name_failure=RAR9001 : Custom validation class name is invalid Index: webservices/jsr109-impl/src/main/resources/org/glassfish/webservices/LogStrings.properties =================================================================== --- webservices/jsr109-impl/src/main/resources/org/glassfish/webservices/LogStrings.properties (revision 34026) +++ webservices/jsr109-impl/src/main/resources/org/glassfish/webservices/LogStrings.properties (working copy) @@ -16,7 +16,7 @@ wsdl.parsing.error=WS00014: Error parsing WSDL {0} exception.manifest=WS00015: Exception : {0} when trying to process MANIFEST file under {1} io.exception=WS00016: IOException : {0} when trying to get list of files under {1} -wsgen.rtexception=WS00017: Exception occured in the wsgen process {0} +wsgen.rtexception=WS00017: Exception occurred in the wsgen process {0} enterprise.deployment.endpoint.registration=WS00018: Webservice Endpoint deployed\n {0} listening at address at {1} enterprise.deployment.ejbendpoint.registration=WS00019: EJB Endpoint deployed\n {0} listening at address at {1} catalog.resolver.error=WS00020: File {0} not found @@ -54,7 +54,7 @@ webservice.dispatcher.info=WS00047: JAXWS WebServiceDispatcher {0} entering for {1} and query string {2} ejb.endpoint.exception=WS00048: ejb endpoint exception -unable.find.adapter=WS00049: Unable to find adpater for endpoint {0} +unable.find.adapter=WS00049: Unable to find adapter for endpoint {0} exception.thrown=WS00050: Following exception was thrown client.unauthorized=WS00051: Client not authorized for invocation of {0} Index: transaction/jts/src/main/resources/com/sun/jts/LogStrings.properties =================================================================== --- transaction/jts/src/main/resources/com/sun/jts/LogStrings.properties (revision 34026) +++ transaction/jts/src/main/resources/com/sun/jts/LogStrings.properties (working copy) @@ -65,12 +65,12 @@ jts.recovery_in_doubt = JTS5026: Exception [{0}] recovering an in-doubt Coordinator. JTS5026.diag.check.1=This is an Unexpected Internal Error. Please contact Sun with the complete error log message. jts.resync_failed = JTS5027: Exception [{0}] on [{1}] operation during resync. -JTS5027.diag1.check.1=See the server log for more details. +JTS5027.diag.check.1=See the server log for more details. jts.xaexception_in_recovery = JTS5028: XAException occurred during recovery of XAResource objects; XA Error Code : [{0}] JTS5028.diag.cause.1=XAResource.recover has thrown an exception during recovery. JTS5028.diag.check.1=See the exception Stack trace for more details. jts.exception_during_resync = JTS5029: Exception [{0}] on [{1}] operation during resync. -JTS5029.diag1.check.1=See the server log for more details. +JTS5029.diag.check.1=See the server log for more details. jts.restart_write_failed = JTS5030: Unable to write restart record. JTS5030.diag.check.1=This is an Unexpected Internal Error. Please contact Sun with the complete error log message. jts.exception_on_resource_operation = JTS5031: Exception [{0}] on Resource [{1}] operation. Index: transaction/jta/src/main/resources/com/sun/enterprise/transaction/LogStrings.properties =================================================================== --- transaction/jta/src/main/resources/com/sun/enterprise/transaction/LogStrings.properties (revision 34026) +++ transaction/jta/src/main/resources/com/sun/enterprise/transaction/LogStrings.properties (working copy) @@ -7,26 +7,26 @@ # Messages in this file must be of the form # <4CharIntegerMessageId>: enterprise_distributedtx.excep_in_enlist=DTX5001:Exception in enlistComponentResources. -DTX5001.diag.cause.1=Exception occured while enlisting the resource. +DTX5001.diag.cause.1=Exception occurred while enlisting the resource. DTX5001.diag.check.1=Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message. enterprise_distributedtx.excep_in_delist=DTX5002:Exception in delistComponentResources. -DTX5002.diag.cause.1=Exception occured while delisting the resource. +DTX5002.diag.cause.1=Exception occurred while delisting the resource. DTX5002.diag.check.1=Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message. enterprise_distributedtx.rollbackexcep_in_regsynch=DTX5003:RollbackException in registerSynchronization. DTX5003.diag.cause.1=Trying to register the sync object while transaction is marked for rollback. DTX5003.diag.check.1=This is an Unexpected Internal Error. Please contact Sun with the complete error log message. enterprise_distributedtx.excep_in_utx_begin=DTX5004:RemoteException in UserTx.begin(). -DTX5004.diag.cause.1=Exception occured while enlisting the component resource. +DTX5004.diag.cause.1=Exception occurred while enlisting the component resource. DTX5004.diag.check.1=Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message. enterprise_distributedtx.excep_in_utx_commit=DTX5005:RemoteException in UserTx.commit(). -DTX5005.diag.cause.1=Exception occured while delisting the component resources. +DTX5005.diag.cause.1=Exception occurred while delisting the component resources. DTX5005.diag.check.1=Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message. enterprise_distributedtx.excep_in_utx_rollback=DTX5006:RemoteException in UserTx.rollback(). -DTX5006.diag.cause.1=Exception occured while delisting the component resources. +DTX5006.diag.cause.1=Exception occurred while delisting the component resources. DTX5006.diag.check.1=Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message. enterprise_distributedtx.some_excep=DTX5007:Exception : enterprise_distributedtx.pooling_excep=DTX5008: Pooling Exception: -DTX5008.diag.cause.1=Exception occured while closing the connection. +DTX5008.diag.cause.1=Exception occurred while closing the connection. DTX5008.diag.check.1=Check if DB is up and running. #com.sun.enterprise.transaction.* log messages transaction.reconfig_txn_timeout_failed=DTX5009:Reconfiguration of transaction timeout failed @@ -43,10 +43,10 @@ DTX5012.diag.check.1=This is an Unexpected Internal Error. Please contact Sun with the complete error log message. transaction.monitor.attribute_not_found=DTX5013:Attribute is not part of transaction monitoring enterprise_distributedtx.before_completion_excep=DTX5014: Caught exception in beforeCompletion() callback: -DTX5014.diag.cause.1=Exception occured while calling beforeCompletion() method of the registered synchronization +DTX5014.diag.cause.1=Exception occurred while calling beforeCompletion() method of the registered synchronization DTX5014.diag.check.1=Check exception message for the exact cause of the exception enterprise_distributedtx.after_completion_excep=DTX5015: Caught exception in afterCompletion() callback: -DTX5015.diag.cause.1=Exception occured while calling afterCompletion() method of the registered synchronization +DTX5015.diag.cause.1=Exception occurred while calling afterCompletion() method of the registered synchronization DTX5015.diag.check.1=Check exception message for the exact cause of the exception xaresource.recover_error=DTX5016:Error in XA recovery. See logs for more details DTX5016.diag.cause.1=Exceptions while trying to close connections of handlers. Index: flashlight/framework/src/main/java/org/glassfish/flashlight/impl/provider/LocalStrings.properties =================================================================== --- flashlight/framework/src/main/java/org/glassfish/flashlight/impl/provider/LocalStrings.properties (revision 34026) +++ flashlight/framework/src/main/java/org/glassfish/flashlight/impl/provider/LocalStrings.properties (working copy) @@ -1,3 +1,3 @@ dtrace_cantfind=Can not match the Probe method ({0}) with any method in the DTrace object. -dtrace_hidden=The probe is hidden. DTrace will ignore it. +dtrace_hidden=The probe is hidden. DTrace will ignore it. Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/tools/launcher/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/tools/launcher/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/tools/launcher/LogStrings.properties (working copy) @@ -1,4 +1,4 @@ -launcher.startup_exception=LAUNCHER001:The laucher wasn't able to execute due to the following Exception. +launcher.startup_exception=LAUNCHER001:The launcher wasn't able to execute due to the following Exception. launcher.security_script_exception=LAUNCHER002:The launcher wasn't able to launcher.config_exception=LAUNCHER003:The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request. launcher.logWriteFailure=LAUNCHER004:The log file {0} can't be created and/or written to. Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/tools/admin/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/tools/admin/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/tools/admin/LogStrings.properties (working copy) @@ -21,17 +21,17 @@ 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 artefacts like file permissions etc. to resolve the 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 reregister HttpListener with DomainRegistry. -core.domain_registry_exception_occured=ADM0012: A Domain Registry Exception occured. Details are: +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 probleme. +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 plugin incompatible with administration server. -core.set_admin_property_failed=ADM0017:Admin server could not be initialized with java home from j2ee plugin. +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. @@ -98,9 +98,9 @@ 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 - Detaile Message: +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 - Detaile Message: +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 @@ -123,8 +123,8 @@ 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 timedout for: [{0}] -mbean.stop_instance_timeout=ADM1055:Checking of STOP instance timedout for: [{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}] @@ -134,7 +134,7 @@ 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 alongwith all the other running non administrative SunONE Application Server instances +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 @@ -378,7 +378,7 @@ 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. -registr.delete_org_succeeded=Deleted Organization {0} successfully from registry for Web Service {1}. +registry.delete_org_succeeded=Deleted Organization {0} successfully from registry for Web Service {1}. 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. Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/activation/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/activation/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/activation/LogStrings.properties (working copy) @@ -10,7 +10,7 @@ #example.message1=TLS0001:Test Message. Parameter 1={0} parameter 2={1} #example.message2=TLS0002:Date Message. Parameter 1={0,date} Parameter 2={1,time} #example.message3=TLS0003:Number Message. Parameter 1={0,number,integer} -activation_viewer.error_loading_image=ACT5001: Error occured in image loading =[{0}] +activation_viewer.error_loading_image=ACT5001: Error occurred in image loading =[{0}] activation_viewer.invalid_outputstream=ACT5002:Invalid outputstream in TextEditor! not saving!. activation_viewer.texteditor_save_failed=ACT5003:TextEditor Save Operation failed with Exception. activation_viewer.mimetype_exception=ACT5004: Bad .mime.types entry: [{0}] Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/container/ejb/mdb/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/container/ejb/mdb/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/container/ejb/mdb/LogStrings.properties (working copy) @@ -27,7 +27,7 @@ containers.mdb.dest_notfound=MDB00015: [{0}]: Message-driven bean destination name [{1}] not found containers.mdb.name_notfound=MDB00016: [{0}]: Name not found exception: [{1}] containers.mdb.create_container_exception=MDB00017: [{0}]: Exception in creating message-driven bean container: [{1}] -MDB00017.diag.cause.1=An error occurred during the message-driven beancontainer initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces. +MDB00017.diag.cause.1=An error occurred during the message-driven bean container initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces. MDB00017.diag.check.1=Double-check that the JNDI name of the message-driven bean's resource in sun-ejb-jar.xml is correct. It is also useful to run the verifier to check that the code requirements for the message-driven bean class have been fulfilled. containers.mdb.container_connection_closing=MDB00018: [{0}]: Closing message-driven bean container connection containers.mdb.container_connection_closed=MDB00019: [{0}]: Message-driven bean container connection closed Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/container/ejb/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/container/ejb/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/container/ejb/LogStrings.properties (working copy) @@ -20,14 +20,14 @@ EJB5013.diag.check.1=Check the application classpath to ensure that all classes needed during deserialization are available. ejb.monitor_mbean_exception=EJB5015: Exception while adding method monitoring mbean ejb.basecontainer_exception=EJB5016: Exception creating BaseContainer : [{0}] -ejb.preinvoke_exception=EJB5017: Exception while running preinvoke : ejbName = [{0}] -EJB5017.diag.cause.1=An error occurred during the removal of an entitybean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean. +ejb.preinvoke_exception=EJB5017: Exception while running pre-invoke : ejbName = [{0}] +EJB5017.diag.cause.1=An error occurred during the removal of an entity bean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean. EJB5017.diag.check.1=Check the exception stack trace to see if the exception originated from the entity bean implementation class. ejb.some_unmapped_exception=EJB5018: An exception was thrown during an ejb invocation on [{0}] ejb.some_app_and_sys_exception=EJB5019: Some application or system exception occurred : [{0}] ejb.unregister_monitormbean_exception=EJB5020: Exception while unregistering monitormbean ejb.incomplete_sessionbean_txn_exception=EJB5021: Session bean transaction is incomplete : [{0}] -ejb.incomplete_msgdrivenbean_txn_exception=EJB5022: Messagedriven bean transaction is incomplete : [{0}] +ejb.incomplete_msgdrivenbean_txn_exception=EJB5022: Message-driven bean transaction is incomplete : [{0}] ejb.register_MonitoringMBean_exception=EJB5023: Exception while registering monitormbean ejb.register_ChildMonitorMBean_exception=EJB5024: Exception while registering child monitormbean ejb.unregister_ChildMonitorMBean_exception=EJB5024: Exception while unregistering child monitormbean : [{0}] @@ -86,13 +86,13 @@ ejb.numberformat_exception=EJB5088: Number format exception ejb.invalid_cleanup_interval=EJB5089: Error -- invalid cleanup interval prop = [{0}] ejb.create_container_exception=EJB5090: Exception in creating EJB container [{0}] -EJB5090.diag.cause.1=Problem during ejb container runtime intitialization. See stack trace for more details. Some common causes are global JNDI name conflicts, classnotfound errors, and configuration errors for resources needed by the ejb. -EJB5090.diag.check.1=If the ejb has a Remote view, check that its JNDIname does not clash with any other ejb's JNDI name or any other globalJNDI name. Check that all needed classes are available to the ejb. Also ensure that any resources needed by the ejb are available. If the ejb uses a datasource make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created. +EJB5090.diag.cause.1=Problem during ejb container runtime initialization. See stack trace for more details. Some common causes are global JNDI name conflicts, class-not-found errors, and configuration errors for resources needed by the ejb. +EJB5090.diag.check.1=If the ejb has a Remote view, check that its JNDI name does not clash with any other ejb's JNDI name or any other global JNDI name. Check that all needed classes are available to the ejb. Also ensure that any resources needed by the ejb are available. If the ejb uses a datasource make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created. ejb.some_remote_mapped_exception=EJB5091:Exception occurred in postInvoke : [{0}] ejb.postinvoketx_exception=EJB5092:Exception occurred in postInvokeTx : [{0}] -ejb.passivate_idle_exception=EJB5093:Exception occured in passiveIdleBeans +ejb.passivate_idle_exception=EJB5093:Exception occurred in passiveIdleBeans ejb.classloader_null_exception=EJB5094:container.getClassLoader() returned null -ejb.select_victims_exception=EJB5095:Exception occured in selectVictims() +ejb.select_victims_exception=EJB5095:Exception occurred in selectVictims() ejb.user_transaction_exception=EJB5096:Unable to lookup UserTransaction ejb.undeploy_exception=EJB5097:Exception during undeploy ejb.preInvokeTx_exception=EJB5098:Exception in preInvokeTx @@ -118,7 +118,7 @@ ejb.deliver_missed_timer=EJB5116:Delivering missed timer for timer id [{0}]. Timer should have fired at [{1}] ejb.create_timer_failure=EJB5117:Timer creation failed for container [{0}] primary key [{1}] and info [{2}] EJB5117.diag.cause.1=Error while creating the persistent representation of an ejb timer. This typically means there is some configuration error or runtime problem with the ejb timer service datasource. -EJB5117.diag.check.1=Double-check the JDBC datasource (and its associated connection pool) assigned to the timer-datasource element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that theconnection pool's JDBC driver URL information is incorrect. +EJB5117.diag.check.1=Double-check the JDBC data source (and its associated connection pool) assigned to the timer-datasource element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that the connection pool's JDBC driver URL information is incorrect. ejb.remove_timer_failure=EJB5118:Failure removing timer bean [{0}] ejb.timer_exceeded_max_deliveries=EJB5119:Expunging timer [{0}] after [{1}] failed deliveries ejb.timer_service_last_shutdown=EJB5120:EJB Timer Service last shutdown at [{0}] Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/LogStrings.properties (working copy) @@ -17,10 +17,10 @@ server.j2eestartup_error=SERVER5004: j2eerunner.startupError. # j2eerunner.cannotCreateServerContext=SERVER0001:A server context could not be created -j2eerunner.initError=SERVER0002: An error occured during initialization -j2eerunner.reconfigError=SERVER0003: An error occured during startup/reconfig +j2eerunner.initError=SERVER0002: An error occurred during initialization +j2eerunner.reconfigError=SERVER0003: An error occurred during startup/reconfig j2eerunner.shuttingdown=SERVER0004: Application server shutdown in progress -j2eerunner.shutdownError=SERVER0005: An error occured during shutdown +j2eerunner.shutdownError=SERVER0005: An error occurred during shutdown j2eerunner.licenseisinvalid=SERVER0007: Your license is invalid. Please obtain a valid license. [{0}] j2eerunner.printstartinfo=SERVER0008: Using [{0}, Version {1}] from [{2}] j2eerunner.pluggable_feature_noinit=SERVER0009: Pluggable features using class {0} could not be initialized. Server will run with default features. Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/core/classloading/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/core/classloading/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/core/classloading/LogStrings.properties (working copy) @@ -12,24 +12,22 @@ #example.message3=WEB0003: Number Message. Parameter 1={0,number,integer} loader.cannot_convert_classpath_into_url=LDR5001: ApplicationLoader: Cannot convert [{0}] into a URL. -loader.unexpected_error_while_unloading_ejb_container=LDR5002: UnExpected error occured while unloading ejb containers +loader.unexpected_error_while_unloading_ejb_container=LDR5002: Unexpected error occurred while unloading ejb containers loader.duplicate_unique_id=LDR5003: Duplicate unique id [{0}] found in ejb descriptor [{1}]. -loader.unexpected_error_while_creating_ejb_container=LDR5004: UnExpected error occured while creating ejb container +loader.unexpected_error_while_creating_ejb_container=LDR5004: Unexpected error occurred while creating ejb container loader.application_loader_exception=LDR5005: ApplicationLoader exception : loader.error_while_loading_app_desc=LDR5006: Failed to load deployment descriptor loader.exception=LDR5007: Exception : loader.configexception=LDR5008: ConfigException : -loader.unexpected_error_while_creating_urls=LDR5009: UnExpected error occurred while creating URL. Check if filename and path is correct. +loader.unexpected_error_while_creating_urls=LDR5009: Unexpected error occurred while creating URL. Check if filename and path is correct. loader.ejbs_loaded=LDR5010: All ejb(s) of [{0}] loaded successfully! loader.class_not_found=LDR5011: Class not found exception occurred while loading the ejbs loader.jndi_name_conflict=LDR5012: Jndi name conflict found in [{0}]. Jndi name [{1}] for bean [{2}] is already in use. loader.naming_exception_in_createcontainer=LDR5013: Naming exception while creating EJB container: loader.cannot_load_policy=LDR5014: Cannot load policy file while loading EJB. loader.register_ws_endpoint_exception=LDR5015: Exception : -loader.register_ws_endpoint_error=LDR5016: Cannot load web service monitoring -MBeans for application : [{0}] -loader.unregister_ws_endpoint_error=LDR5017: Cannot unload web service -monitoring MBeans for application : [{0}] +loader.register_ws_endpoint_error=LDR5016: Cannot load web service monitoring MBeans for application : [{0}] +loader.unregister_ws_endpoint_error=LDR5017: Cannot unload web service monitoring MBeans for application : [{0}] loader.connector_resource_initialization_error=LDR5018: ERROR while initializing ConnectorResourcesLoader [{0}] loader.module_dir_error=LDR5019: For module {0} the module directory {1} is missing or invalid Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/core/selfmanagement/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/core/selfmanagement/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/core/selfmanagement/LogStrings.properties (working copy) @@ -19,11 +19,11 @@ smgt.service_rule_disabled=SMGT0010: Rule : {0}, Description : {1} is disabled smgt.service_rule_enabled=SMGT0011: Rule : {0}, Description :{1} is enabled smgt.invalid_action=SMGT0012: Rule : {0} refers to invalid application ref : {1} -smgt.error_reg_action=SGMT0013: Error in registring action : {1} in Rule : {0}. Possbile error with action, try redeploying the application +smgt.error_reg_action=SGMT0013: Error in registering action : {1} in Rule : {0}. Possible error with action, try redeploying the application smgt.config_error=SMGT0014: Configuration Error encountered. Please verify your configuration file, domain.xml, for management rules -smgt.internal_error=SMGT0015: Internal error occured +smgt.internal_error=SMGT0015: Internal error occurred smgt.service_initialized=SMGT0016: Self Management service is initialized -smgt.errorenous_event=SGMT0017: Error creating and configuring the rule : {0} due to IlegalArguments specified for its event type : {1}. Create the rule with correct arugments for the configured event. +smgt.errorenous_event=SGMT0017: Error creating and configuring the rule : {0} due to IlegalArguments specified for its event type : {1}. Create the rule with correct arguments for the configured event. sgmt.ruleactiondisabled=SGMT0018: Configured action name={1} for Rule name={0} is disabled. The action would not be executed till it is enabled. sgmt.delete_invalidname=SGMT0019: Could not delete rule. No configured rule exists with name={0} sgmt.error_delete_rule=SGMT0020: Error encountered while trying to delete rule={0}. Reason - {1} @@ -41,16 +41,16 @@ sgmt.threadhangaction_nosuchobj=SGMT0212: {0}- Could not send mail alert due to invalid ref, {1} ,configured. Please ensure that the configured mail alert application is available. sgmt.threadhangaction_excep=SGMT0213: {0}- Error encountered while trying to send mail alert. Would proceed to log the detail. sgmt.threadhangaction_potentialcount=SGMT0214: {0}- Potential request/threads found to be non-responsive={1}. -sgmt.threadhangaction_securityex=SGMT0215: {0}- Error encountered while trying to stop/interrupt the potential unrepsonsive request/thread/ +sgmt.threadhangaction_securityex=SGMT0215: {0}- Error encountered while trying to stop/interrupt the potential unresponsive request/thread/ sgmt.threadhangaction_mbeanex=SGMT0216: {0}- Error encountered while trying to retrieve statistics to determine potential non-responsive requests/threads. sgmt.threadhangaction_potentialthread=SGMT0217: {0}- Found non-responsive http request/thread on listener port:{1}, for URI={2} -sgmt.threadhangaction_stopd=SGMT0218: {0}- Stopped non-repsonsive http request/thread on listener port={1}, for URI={2} -sgmt.threadhangacton_noalertref=SGMT0219: {0}- Cannot send mail alert on the check for non-responsive requests/threads, as applicatoin ref for mail alert is not provided. +sgmt.threadhangaction_stopd=SGMT0218: {0}- Stopped non-responsive http request/thread on listener port={1}, for URI={2} +sgmt.threadhangacton_noalertref=SGMT0219: {0}- Cannot send mail alert on the check for non-responsive requests/threads, as application ref for mail alert is not provided. sgmt.threadhangaction_statsenabled=SGMT0220: {0}- HttpService monitoring switched ON. Statistics for check for non-responsive http request/threads would now be enabled. sgmt.threadhangaction_statsdisabled=SGMT0221: {0}- HttpService monitoring switched OFF. It would not be possible to check for non-responsive http requests/threads, due to non-availability of internal statistics. sgmt.threadhangaction_deftimeout=SGMT0222: {0}- Due ThresholdWaitInMillis:{1} being less than load balancer default timeout value of:{2}; resetting it to load balancer default. sgmt.threadhangaction_lbtimeout=SGMT0223: {0}- Due ThresholdWaitInMillis:{1} being less than load balancer response timeout:{2}, resetting it to load balancer response timeout. -sgmt.instancehang_listener_notresponding=SGMT0224: Instance hang check - Listener: {1} of server :{0} is not responding to the for instance hang check request. The request timeout occured for the timeout value of={2}. +sgmt.instancehang_listener_notresponding=SGMT0224: Instance hang check - Listener: {1} of server :{0} is not responding to the for instance hang check request. The request timeout occurred for the timeout value of={2}. sgmt.instancehang_listenernotmaxd=SGMT0225: Instance hang check - Listener: {1} of server: {0} has not responded to the ping request for instance hang check. However it still has scope to receive further http requests, as it has not max'd out on threads. No. of busy http threads={2}. sgmt.instancehang_listenermaxd=SGMT0226: Instance hang check - Listener: {1} of server: {0} has not responded to instance hang check request. The listener has max'd out on threads. No. of busy http threads={2}. sgmt.instancehang_listenerresp=SGMT0227: Instance hang check - Listener: {1} of server: {0} is healthy for the instance hang check carried out. @@ -58,9 +58,7 @@ sgmt.instancehang_serverunhealthy=SGMT0229: Instance hang check - Server: {0} is not responding; is unhealthy. sgmt.instancehang_invalidname=SGMT0230: Instance hang check - Invalid name : {0} specified in the check list of the rule. Ignoring this value. sgmt.instancehang_clhctimeout=SGMT0231: Instance hang check - The threshold timeout= {1} specified for cluster: {0} is less than the load balancer health checker configured for it. Raising this timeout to its load balancer health checker value of {2}. -sgmt.instancehang_hctimeout=SGMT0232: Instance hang check - The threshold timeout= {1} specified for server: {0} is l -ess than the load balancer health checker configured for it. Raising this timeout to its load balancer health checker va -lue of {2}. +sgmt.instancehang_hctimeout=SGMT0232: Instance hang check - The threshold timeout= {1} specified for server: {0} is less than the load balancer health checker configured for it. Raising this timeout to its load balancer health checker value of {2}. sgmt.instancehang_noinstance=SGMT0233: Instance hang check - There are no instances specified in the check list to check for instance hang. sgmt.instancehang_clinstcheckstart=SGMT0234: Started instance hang check for server: {0} in cluster: {1} sgmt.instancehang_instcheckstart=SGMT0235: Started instance hang check for server: {0} @@ -87,15 +85,15 @@ # codes range 0301 - 0400 # sgmt.reconfig_handlecreatereceived=SGMT0301: Reconfig notification received for creation -sgmt.reconfig_handleupdatereceived=SGMT0302: Reconfig notification received for updation +sgmt.reconfig_handleupdatereceived=SGMT0302: Reconfig notification received for update sgmt.reconfig_handledeletereceived=SGMT0303: Reconfig notification received for deletion sgmt.reconfig_handlecreaterulereceived=SGMT0304: Reconfig notification received for handling rules creation -sgmt.reconfig_handleupdaterulereceived=SGMT0305: Reconfig notification received for handling rules updation +sgmt.reconfig_handleupdaterulereceived=SGMT0305: Reconfig notification received for handling rules update sgmt.reconfig_handlexpath=SGMT0306: Reconfig addition for rule - {0} sgmt.reconfig_handledeletereceived=SGMT0307: Reconfig notification received for handling rules deletion sgmt.reconfig_handledelxpath=SGMT0308: Reconfig deletion for - {0} sgmt.handleupdatexpath=SGMT0309: Reconfig update on - {0} -sgmt.disableservice=SGMT0310: Reconfig - Disabling self management service. All enabled rules would be implicitly disableld. +sgmt.disableservice=SGMT0310: Reconfig - Disabling self management service. All enabled rules would be implicitly disabled. sgmt.enableservice=SGMT0311: Reconfig - Enabling self management service. All enabled rules would be activated. sgmt.delete_invalidname=SGMT0312 Reconfig - Invalid name specified for management rule deletion, name= {0}. sgmt.error_delete_rule=SGMT0313: Reconfig - Error encountered while deleting rule, name= {0}. Reason for error : {1}. @@ -103,11 +101,11 @@ sgmt.updateruleattribute=SGMT0315: Reconfig - Updating management rule attribute={0}. Old value= {1}, new value= {2} sgmt.error_disablerule=SGMT0316: Error encountered while disabling rule, name= {0}. Reason is : {1}. sgmt.error_enableservice=SGMT0317: Error encountered while enabling management rules. Reason is :{0}. -sgmt.error_enablerule_noservice=SGMT0318: Reconfig - Cannot activate rule, name= {0}, Description= {1} as the management rules is disbaled. First enable the management rules to activate this rule. +sgmt.error_enablerule_noservice=SGMT0318: Reconfig - Cannot activate rule, name= {0}, Description= {1} as the management rules is disabled. First enable the management rules to activate this rule. sgmt.error_disablerule_noservice=SGMT0319: Reconfig - Cannot disable rule, name= {0}, Description= {1} as it is already not active due to the management rules being disabled. smgt.cannot_changesstate=SMGT0320: Reconfig - Cannot change state for rule, name= {0}, Description= {1}. Most probably the internal state of the rule is same since the last successfully applied change to it. -smgt.erroraddaction_notenabled=SMGT0321: Reconfig - Cannot activate the action, name={1} being added to management rule= {1}. Either the service or rule is disbaled. -smgt.successaddaction=SMGT0322: Reconfig - Succesfully added action= {1} to management rule= {0} +smgt.erroraddaction_notenabled=SMGT0321: Reconfig - Cannot activate the action, name={1} being added to management rule= {1}. Either the service or rule is disabled. +smgt.successaddaction=SMGT0322: Reconfig - Successfully added action= {1} to management rule= {0} smgt.handleactionadd=SMGT0323: Reconfig - Addition of action for management rule= {0} smgt.erroraddaction_notenabled=SMGT0324 : Reconfig - Cannot activate the action for rule= {0}, description= {1} as either the management rules service is disabled or the rule itself is disabled. smgt.error_add_noactionreceived=SMGT0325: Reconfig - Error in adding action to rule= {0}, description= {1}. No action config bean received from the config change notification received. Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/core/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/core/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/core/LogStrings.properties (working copy) @@ -42,10 +42,10 @@ core.file_io_exception=CORE5029: File IO exception : core.unsupported_javac_option=CORE5030: Unsupported Javac option [{0}] found in server configuration. core.error_while_loading_license=CORE5031: License exception occurred while loading license. -core.unexpected_exception_no_valid_licfile=CORE5032: UnExpected error occurred, license file is not valid. +core.unexpected_exception_no_valid_licfile=CORE5032: Unexpected error occurred, license file is not valid. core.unexpected_exception_while_checking_validity=CORE5033: Thank you for trying the Sun Java System Application Server. Your evaluation license has expired. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. core.unexpected_exception_while_setting_remote_permission=CORE5034: Unexpected error occurred while setting remote permissions -core.unexpected_exception_while_setting_instance_limit=CORE5035: UnExpected error occurred while setting instance limit +core.unexpected_exception_while_setting_instance_limit=CORE5035: Unexpected error occurred while setting instance limit core.invalid_license_error=CORE5036: Your license is invalid. Please go to http://www.sun.com/as7upgrade to get a valid license. core.license_expiring=CORE5037: Thank you for trying the Sun Java System Application Server. Your evaluation license will expire in [{0}] days. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. core.license_expired=CORE5038:Thank you for trying the Sun Java System Application Server. Your evaluation license has expired. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. @@ -96,10 +96,10 @@ shutdown.started=Server shutdown in progress... # j2eerunner.cannotCreateServerContext=CORE5070:A server context could not be created -j2eerunner.initError=CORE5071: An error occured during initialization -j2eerunner.reconfigError=CORE5072: An error occured during startup/reconfig +j2eerunner.initError=CORE5071: An error occurred during initialization +j2eerunner.reconfigError=CORE5072: An error occurred during startup/reconfig j2eerunner.shuttingdown=CORE5073: Application server shutdown in progress -j2eerunner.shutdownError=CORE5074: An error occured during shutdown +j2eerunner.shutdownError=CORE5074: An error occurred during shutdown j2eerunner.licenseisinvalid=CORE5075: Your license is invalid. Please obtain a valid license. [{0}] j2eerunner.printstartinfo=CORE5076: Using [{0}, Version {1}] from [{2}] # @@ -117,7 +117,7 @@ application.default_locale=Application Server default locale is {0} server.shutdown_complete=Server shutdown complete. j2eerunner.pluggable_feature_noinit=SERVER0009: Pluggable features using class {0} could not be initialized. Server will run with default features. -shutdown.error=An error occured during server shutdown : {0} +shutdown.error=An error occurred during server shutdown : {0} # enterprise.orb_reference_exception=CORE5080: Exception resolving initial reference of ORB: enterprise.createorb_exception=CORE5081: Exception while creating ORB: [{0}] @@ -145,19 +145,19 @@ pemain.failureOnReadingSecurityIdentity=An exception was encountered when reading in the user's identity. socketservice.init_done=CORE5098: AS Socket Service Initialization has been completed. socketservice.unknown_ex=UnknownException during startup. Disable quick startup by setting system property com.sun.enterprise.server.ss.ASQuickStartup to false -socketservice.port_conflict=A conflict occured on port {0} . Server is shutting down. -socketservice.stop_lc_ex=Exception while stoppping Lifecycle. +socketservice.port_conflict=A conflict occurred on port {0} . Server is shutting down. +socketservice.stop_lc_ex=Exception while stopping Lifecycle. mqra.start=Broker Type {0}. Starting RA # # Used in SystemAppLifecycle # core.loading_system_apps=CORE5100:Loading system apps -core.exception_while_deploying_system_apps=CORE5101:Exception occured while deploying system apps +core.exception_while_deploying_system_apps=CORE5101:Exception occurred while deploying system apps core.deploying_system_apps=CORE5102:Deploying system apps to target {0} from directory {1} core.deployed_system_apps=CORE5103:Deployed system apps to target {0} core.system_app_dir_not_found=CORE5104:Directory {0} not found or cannot read -core.exception_while_getting_targets=CORE5105:Exception occured while getting targets -error_occured_in_isreg=CORE5106:Exception occured while finding application registration +core.exception_while_getting_targets=CORE5105:Exception occurred while getting targets +error_occured_in_isreg=CORE5106:Exception occurred while finding application registration # # Used in com.sun.enterprise.server.ManagerFactory Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/core/naming/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/core/naming/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/core/naming/LogStrings.properties (working copy) @@ -24,7 +24,7 @@ NAM0003.diag.check.2=Check if ORB CosNaming Service initialised. enterprise_naming.serialctx_communication_exception=NAM0004: Exception during name lookup : {0} -NAM0004.diag.cause.1=App Server maynot be running at port intended. +NAM0004.diag.cause.1=App Server may not be running at port intended. NAM0004.diag.check.1=Check to see if the AppServer is up and running on the port intended. The problem could be because of incorrect port. NAM0004.diag.cause.2= Possible Network Error. NAM0004.diag.check.2=Check to see if you can access the host on which the AppServer running. Index: common/common-util/src/main/java/com/sun/logging/enterprise/system/util/LogStrings.properties =================================================================== --- common/common-util/src/main/java/com/sun/logging/enterprise/system/util/LogStrings.properties (revision 34026) +++ common/common-util/src/main/java/com/sun/logging/enterprise/system/util/LogStrings.properties (working copy) @@ -15,16 +15,16 @@ enterprise_util.excep_jaraccess_create=UTIL6006:Exception in JarAccess create(). enterprise_util.excep_legacyconfigconverter_convert=UTIL6007:Exception in LegacyConfigConverter convert(). enterprise_util.orbmgr_config_excep=UTIL6008:ConfigException in ORBManager. -enterprise_util.excep_in_createorb=UTIL6009:Unexcpected Exception in createORB. +enterprise_util.excep_in_createorb=UTIL6009:Unexpected Exception in createORB. enterprise_util.cannot_load_library=UTIL6010:Error Cannot load library. [{0}] enterprise_util.prop_jms_client_id_deprec=UTIL6011:'jms-client-id' is an obsolete property. Set client id on a JMS Connection Factory and use the 'mdb-connection-factory' property instead. enterprise_util.mdb_with_cmt_jms_ack=UTIL6012:message-driven beans with container-managed transactions can't have a jms acknowledge mode. -enterprise_util.entity_bmt_n_session_mlt=UTIL6013:You have chosen to make this bean manage its own transactions. This is illegal for entity beans, and the (session) bean cannot specifiy any method level container transactions. +enterprise_util.entity_bmt_n_session_mlt=UTIL6013:You have chosen to make this bean manage its own transactions. This is illegal for entity beans, and the (session) bean cannot specify any method level container transactions. enterprise_util.error_converting_prop_file=UTIL6014: error converting properties file. enterprise_util.excep_rescache_getres=UTIL6015: Unexpected Exception in ResourceCache getResource(). enterprise_util.excep_serverviewer_refresh=UTIL6016: Exception in ServerViewer refresh(). -enterprise_util.excep_suidgen_getgenbackendid=UTIL6017: Excpetion in SimpleUniqueValueGenerator getGeneratorBackendId(). -enterprise_util.excep_suidgen_nextnuminternal=UTIL6018: Excpetion in SimpleUniqueValueGenerator nextNumberInternal(). +enterprise_util.excep_suidgen_getgenbackendid=UTIL6017: Exception in SimpleUniqueValueGenerator getGeneratorBackendId(). +enterprise_util.excep_suidgen_nextnuminternal=UTIL6018: Exception in SimpleUniqueValueGenerator nextNumberInternal(). enterprise_util.runasrole_runasprincipal_conflict=UTIL6019:WARNING : runAsRole and runAsPrincipal cannot exist independent of each other. Ignore... enterprise_util.j2eecleanup_error=UTIL6020: Error in removing resource adapters enterprise_util.some_error=UTIL6021: Error [{0}] occurred Index: common/container-common/src/main/resources/org/glassfish/javaee/services/LogStrings.properties =================================================================== --- common/container-common/src/main/resources/org/glassfish/javaee/services/LogStrings.properties (revision 34026) +++ common/container-common/src/main/resources/org/glassfish/javaee/services/LogStrings.properties (working copy) @@ -8,7 +8,7 @@ resources.resource-manager.no-deployer-found=no deployer found for resource type [ {0} ] resources.resources-binder.bind-resource-failed=RAR9602: Cannot bind resource [ {0} ] to naming manager. Following exception occurred {1} resources.resource-manager.connector-descriptor.bind.failure=RAR9603: Unable to bind connector descriptor for resource-adapter [ {0} ]. Following exception occurred : {1} -ping_during_creation_exception=RAR9604: Exception while pinging pool during creation for pool {0}. Following exception occured {1} +ping_during_creation_exception=RAR9604: Exception while pinging pool during creation for pool {0}. Following exception occurred {1} RAR9604.diag.cause.1=The specified jdbc connection pool is unusable. ping_during_creation_failure=RAR9605: Ping pool during creation failed for pool : {0} . Pool has been created successfully but ping failed. RAR9605.diag.cause.1=There could be some erroneous values specified in jdbc connection pool configuration. Index: ejb/ejb-container/src/main/resources/com/sun/logging/enterprise/system/container/ejb/mdb/LogStrings.properties =================================================================== --- ejb/ejb-container/src/main/resources/com/sun/logging/enterprise/system/container/ejb/mdb/LogStrings.properties (revision 34026) +++ ejb/ejb-container/src/main/resources/com/sun/logging/enterprise/system/container/ejb/mdb/LogStrings.properties (working copy) @@ -27,7 +27,7 @@ containers.mdb.dest_notfound=MDB00015: [{0}]: Message-driven bean destination name [{1}] not found containers.mdb.name_notfound=MDB00016: [{0}]: Name not found exception: [{1}] containers.mdb.create_container_exception=MDB00017: [{0}]: Exception in creating message-driven bean container: [{1}] -MDB00017.diag.cause.1=An error occurred during the message-driven beancontainer initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces. +MDB00017.diag.cause.1=An error occurred during the message-driven bean container initialization at runtime. The most common cause for this is that the physical resource(e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces. MDB00017.diag.check.1=Double-check that the JNDI name of the message-driven bean's resource in sun-ejb-jar.xml is correct. It is also useful to run the verifier to check that the code requirements for the message-driven bean class have been fulfilled. containers.mdb.container_connection_closing=MDB00018: [{0}]: Closing message-driven bean container connection containers.mdb.container_connection_closed=MDB00019: [{0}]: Message-driven bean container connection closed Index: ejb/ejb-container/src/main/resources/com/sun/logging/enterprise/system/container/ejb/LogStrings.properties =================================================================== --- ejb/ejb-container/src/main/resources/com/sun/logging/enterprise/system/container/ejb/LogStrings.properties (revision 34026) +++ ejb/ejb-container/src/main/resources/com/sun/logging/enterprise/system/container/ejb/LogStrings.properties (working copy) @@ -21,13 +21,13 @@ ejb.monitor_mbean_exception=EJB5015: Exception while adding method monitoring mbean ejb.basecontainer_exception=EJB5016: Exception creating BaseContainer : [{0}] ejb.preinvoke_exception=EJB5017: Exception while running preinvoke : ejbName = [{0}] -EJB5017.diag.cause.1=An error occurred during the removal of an entitybean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean. +EJB5017.diag.cause.1=An error occurred during the removal of an entity bean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean. EJB5017.diag.check.1=Check the exception stack trace to see if the exception originated from the entity bean implementation class. ejb.some_unmapped_exception=EJB5018: An exception was thrown during an ejb invocation on [{0}] ejb.some_app_and_sys_exception=EJB5019: Some application or system exception occurred : [{0}] ejb.unregister_monitormbean_exception=EJB5020: Exception while unregistering monitormbean ejb.incomplete_sessionbean_txn_exception=EJB5021: Session bean transaction is incomplete : [{0}] -ejb.incomplete_msgdrivenbean_txn_exception=EJB5022: Messagedriven bean transaction is incomplete : [{0}] +ejb.incomplete_msgdrivenbean_txn_exception=EJB5022: Message-driven bean transaction is incomplete : [{0}] ejb.register_MonitoringMBean_exception=EJB5023: Exception while registering monitormbean ejb.register_ChildMonitorMBean_exception=EJB5024: Exception while registering child monitormbean ejb.unregister_ChildMonitorMBean_exception=EJB5024: Exception while unregistering child monitormbean : [{0}] @@ -76,7 +76,7 @@ EJB5069.diag.cause.1=The bean's Home or LocalHome does not define a no-arg create method. EJB5069.diag.check.1=Check the Home or LocalHome interface for the appropriate create method signature. Running the verifier will help identify the error as well. ejb.stateless_ejbcreate_exception=EJB5070: Exception creating stateless session bean : [{0}] -ejb.remote_or_txnrollback_exception=EJB5071: Some remote or transactional roll back exception occurred +ejb.remote_or_txnrollback_exception=EJB5071: Some remote or transactional rollback exception occurred EJB5071.diag.cause.1=Some problem occurred during the beforeCompletionphase of the transaction lifecycle. This error often happens when application code throws a system exception from its ejbStore method or if the transaction manager encounters a system exception. EJB5071.diag.check.1=Check the stack trace to see if the exception originated from the application's ejbStore method. Also check the resource configuration to ensure that all resource managers involved in the transaction are configured properly and healthy. ejb.initializehome_exception=EJB5072: Error initializing home of container: [{0}] @@ -86,13 +86,13 @@ ejb.numberformat_exception=EJB5088: Number format exception ejb.invalid_cleanup_interval=EJB5089: Error -- invalid cleanup interval prop = [{0}] ejb.create_container_exception=EJB5090: Exception in creating EJB container [{0}] -EJB5090.diag.cause.1=Problem during ejb container runtime intitialization. See stack trace for more details. Some common causes are global JNDI name conflicts, classnotfound errors, and configuration errors for resources needed by the ejb. +EJB5090.diag.cause.1=Problem during ejb container runtime initialization. See stack trace for more details. Some common causes are global JNDI name conflicts, class-not-found errors, and configuration errors for resources needed by the ejb. EJB5090.diag.check.1=If the ejb has a Remote view, check that its JNDIname does not clash with any other ejb's JNDI name or any other globalJNDI name. Check that all needed classes are available to the ejb. Also ensure that any resources needed by the ejb are available. If the ejb uses a datasource make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created. ejb.some_remote_mapped_exception=EJB5091:Exception occurred in postInvoke : [{0}] ejb.postinvoketx_exception=EJB5092:Exception occurred in postInvokeTx : [{0}] -ejb.passivate_idle_exception=EJB5093:Exception occured in passiveIdleBeans +ejb.passivate_idle_exception=EJB5093:Exception occurred in passiveIdleBeans ejb.classloader_null_exception=EJB5094:container.getClassLoader() returned null -ejb.select_victims_exception=EJB5095:Exception occured in selectVictims() +ejb.select_victims_exception=EJB5095:Exception occurred in selectVictims() ejb.user_transaction_exception=EJB5096:Unable to lookup UserTransaction ejb.undeploy_exception=EJB5097:Exception during undeploy ejb.preInvokeTx_exception=EJB5098:Exception in preInvokeTx @@ -118,7 +118,7 @@ ejb.deliver_missed_timer=EJB5116:Delivering missed timer for timer id [{0}]. Timer should have fired at [{1}] ejb.create_timer_failure=EJB5117:Timer creation failed for container [{0}] primary key [{1}] and info [{2}] EJB5117.diag.cause.1=Error while creating the persistent representation of an ejb timer. This typically means there is some configuration error or runtime problem with the ejb timer service datasource. -EJB5117.diag.check.1=Double-check the JDBC datasource (and its associated connection pool) assigned to the timer-datasource element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that theconnection pool's JDBC driver URL information is incorrect. +EJB5117.diag.check.1=Double-check the JDBC datasource (and its associated connection pool) assigned to the timer-datasource element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that the connection pool's JDBC driver URL information is incorrect. ejb.remove_timer_failure=EJB5118:Failure removing timer bean [{0}] ejb.timer_exceeded_max_deliveries=EJB5119:Expunging timer [{0}] after [{1}] failed deliveries ejb.timer_service_last_shutdown=EJB5120:EJB Timer Service last shutdown at [{0}] Index: security/core/src/main/resources/com/sun/logging/enterprise/system/core/security/LogStrings.properties =================================================================== --- security/core/src/main/resources/com/sun/logging/enterprise/system/core/security/LogStrings.properties (revision 34026) +++ security/core/src/main/resources/com/sun/logging/enterprise/system/core/security/LogStrings.properties (working copy) @@ -147,7 +147,7 @@ SEC5031.diag.check.1=Please check the if the Provider name is correct. SEC1114.diag.cause.1=There was an exception while installing the Policy Provider. SEC1114.diag.check.1=Please check the if the Policy Provider is correct -SEC1146.diag.cause.1=Policy Configuration Factory overriden +SEC1146.diag.cause.1=Policy Configuration Factory overridden SEC1146.diag.check.1=Please check if the system property javax.security.jacc.PolicyConfigurationFactory.provider has not been set. SEC1147.diag.cause.1=Policy Configuration Factory not defined SEC1147.diag.check.1=Please check if the Policy Configuration Factory has been defined. @@ -155,8 +155,8 @@ SEC1145.diag.check.1=No policy provider defined. Will use the default JDK Policy implementation. SEC1142.diag.cause.1=Error while reading policy-provider in domain.xml. SEC1142.diag.check.1=Please check if the policy provider defined is correct. -SEC1140.diag.cause.1=Policy Provider Configuration Property is overriden by property javax.security.jacc.auth.policy.provider. -SEC1140.diag.check.1=Policy Provider Configuration Property is overriden by property javax.security.jacc.auth.policy.provider. +SEC1140.diag.cause.1=Policy Provider Configuration Property is overridden by property javax.security.jacc.auth.policy.provider. +SEC1140.diag.check.1=Policy Provider Configuration Property is overridden by property javax.security.jacc.auth.policy.provider. SEC1141.diag.cause.1=JaccProvider class not found for name defined. SEC1141.diag.check.1=Please check if the name of the Jacc provider is defined correctly. SEC5038.diag.cause.1=There was an exception while authenticating the default caller principal @@ -169,8 +169,8 @@ SEC5049.diag.check.1=There was an unexpected exception while setting the security context SEC5051.diag.cause.1=null Subject used in SecurityContext construction. SEC5051.diag.check.1=null Subject used in SecurityContext construction. -SEC5039.diag.cause.1=An exception occured while processing username and password for security -SEC5039.diag.check.1=An exception occured while processing username and password for security +SEC5039.diag.cause.1=An exception occurred while processing username and password for security +SEC5039.diag.check.1=An exception occurred while processing username and password for security SEC5055.diag.cause.1=Principal-Group-Role Mapping conflicts in the application SEC5055.diag.check.1=Please check if the roles have been mapped to the same principals/groups consistently in all the descriptors. SEC1103.diag.cause.1=The Realm configured is not an instance of CertificateRealm, Certificate authentication requires certificate realm. Index: connectors/work-management/src/main/resources/com/sun/enterprise/connectors/work/LogStrings.properties =================================================================== --- connectors/work-management/src/main/resources/com/sun/enterprise/connectors/work/LogStrings.properties (revision 34026) +++ connectors/work-management/src/main/resources/com/sun/enterprise/connectors/work/LogStrings.properties (working copy) @@ -16,7 +16,7 @@ RAR2006.diag.cause.1=Requested work context is not supported, but a super type of the context is supported workcontext.context_class_not_found=RAR2007: Unable to load work context class {0} due to the following exception {1} RAR2007.diag.cause.1=Work Context class is not available to application server -RAR2007.diag.check.1=Make sure that the work context class ia available to server +RAR2007.diag.check.1=Make sure that the work context class is available to server workcontext.security_context_setup_failure=RAR2008: Unable to set security context RAR2008.diag.cause.1=Unable to set security context RAR2008.diag.check.1=Check the server.log for exceptions Index: connectors/connectors-runtime/src/main/resources/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties =================================================================== --- connectors/connectors-runtime/src/main/resources/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties (revision 34026) +++ connectors/connectors-runtime/src/main/resources/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties (working copy) @@ -22,7 +22,7 @@ RAR5042.diag.check.1=Check that the XA Resource and the pool it points to is still defined in the domain.xml RAR5042.diag.check.2=Check that the XA Resource is present in the list of resource-refs in the domain.xml RAR5042.diag.check.3=Check that the Database server is up and running -RAR5042.diag.check.4=Check if the config info of the XA resource and the pool it points to is sane. In particular check that the datasourceclassname in the pool is correct and the XA resource points to the correct pool +RAR5042.diag.check.4=Check if the config info of the XA resource and the pool it points to is sane. In particular check that the data source class name in the pool is correct and the XA resource points to the correct pool poolmgr.datasource_error=RAR5007:Error in creating data source object: [{0}] RAR5007.diag.cause.1=Exception while creating persistent manager resource. RAR5007.diag.check.1=Check whether the persistent manager factory class is configured properly and is available in the classpath. @@ -46,7 +46,7 @@ RAR5009.diag.check.1=Make sure that factory-class name is configured correctly. RAR5009.diag.check.2=Make sure that factory-class is available in the classpath of the application server jndi.factory_class_unexpected=RAR5010:external-jndi-resource factory-class ''[{0}]'' must be of type javax.naming.spi.InitialContextFactory -RAR5010.diag.cause.1=External JNDI resource has a worng factory-class configuration +RAR5010.diag.cause.1=External JNDI resource has a wrong factory-class configuration RAR5010.diag.check.1=Verify that factory class is an instance of javax.naming.spi.InitialContextFactory jndi.initial_context_error=RAR5011:Exception thrown creating initial context for external JNDI factory ''[{0}]'' RAR5011.diag.cause.1=Could not create Initial Context. @@ -60,29 +60,29 @@ jndi.factory_install_error=RAR5013:Error in installing connection factories poolmgr.load_error=RAR5014:Cannot load class [{0}]. classloader.load_class_fail=RAR5015:Unexpected exception in loading class [{0}] by classloader -RAR5015.diag.cause.1=Classpath is not propertly set in the domain.xml +RAR5015.diag.cause.1=Classpath is not properly set in the domain.xml RAR5015.diag.cause.2=The application server process does not have read permissions on the directory that holds the classes/jar RAR5015.diag.check.2=You do not have read permissions on the directory that holds the classes/jar -RAR5015.diag.check.1=Check that the classpath attribure in the java-config includes a reference to the jar/package directory for the class +RAR5015.diag.check.1=Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class classloader.load_class_fail_excp=RAR5046:Unexpected exception in loading class by classloader [{0}] -RAR5046.diag.cause.1=Classpath is not propertly set in the domain.xml +RAR5046.diag.cause.1=Classpath is not properly set in the domain.xml RAR5046.diag.cause.2=You do not have read permissions on the directory that holds the classes/jar -RAR5046.diag.check.1=Check that the classpath attribure in the java-config includes a reference to the jar/package directory for the class +RAR5046.diag.check.1=Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class RAR5046.diag.check.2=Check that the directory where the classes/jars reside have read permission for the application server process poolmgr.config_access_error=RAR5016:Error accessing configuration file. jndi.connection_cannot_get=RAR5017:Cannot locate connection descriptor by name jndi.connection_create_error=RAR5018:Cannot create connection factory rsrc.file_create_error=RAR5019:Unexpected exception in creating new file jndi.persistence_manager_config=RAR5020:Error in Persistence Manager Settings [{0}] -RAR5020.diag.cause.1=Could not configure persistent manager resource properly. +RAR5020.diag.cause.1=Could not configure persistence manager resource properly. RAR5020.diag.check.1=Make sure that the Jdbc resource name, you have configured is correct -RAR5020.diag.check.2=Check whether the perstenst manager factory class is proper. -RAR5020.diag.check.3=Check whether the perstenst manager factory class has a setConnectionFactoryName method. +RAR5020.diag.check.2=Check whether the persistence manager factory class is proper. +RAR5020.diag.check.3=Check whether the persistence manager factory class has a setConnectionFactoryName method. jndi.persistence_manager_config_excp=RAR5044:Error in Persistence Manager Settings -RAR5044.diag.cause.1=Could not configure persistent manager resource properly. +RAR5044.diag.cause.1=Could not configure persistence manager resource properly. RAR5044.diag.check.1=Make sure that the Jdbc resource name, you have configured is correct -RAR5044.diag.check.2=Check whether the perstenst manager factory class is proper. -RAR5044.diag.check.3=Check whether the perstenst manager factory class has a setConnectionFactoryName method. +RAR5044.diag.check.2=Check whether the persistence manager factory class is proper. +RAR5044.diag.check.3=Check whether the persistence manager factory class has a setConnectionFactoryName method. poolmgr.resource_adapter_error=RAR5021:Error in installing resource adapters jndi.bind_error=RAR5022:Error in binding to JNDI namespace jndi.remove_connection_factory_error=RAR5023:Error removing connection factory @@ -168,9 +168,9 @@ rardeployment.nullPointerException=RAR6012 : Null pointer Exception : {0} RAR6012.diag.check.1=There is an internal server error. Please contact Sun Microsystems with the complete log message RAR6012.diag.check.2=Check whether resource adapter threw a null pointer exception. -rardeployment.jndi_publish_failure=RAR6013 : Couldnot publish connector descriptor in JNDI : {0} +rardeployment.jndi_publish_failure=RAR6013 : Could not publish connector descriptor in JNDI : {0} RAR6013.diag.check.1=There is an internal server error. Please contact Sun Microsystems with the complete log message -rardeployment.connector_descriptor_notfound=RAR6014 : Couldnot find the connector descriptor in the rar : {0} +rardeployment.connector_descriptor_notfound=RAR6014 : Could not find the connector descriptor in the rar : {0} RAR6014.diag.cause.1=Incomplete or erroneous resource adapter deployment. RAR6014.diag.check.1=Check whether the RA deployment is proper and complete. rardeployment.connectionpool_object_null=RAR6015 : Obtained Null connection pool object from jndi : {0} @@ -306,9 +306,9 @@ jmservice.destination.autocreated=RAR7100: Physical destination {0} is autocreated by application server. jmservice.destination.autocreatefailed= RAR7101: Autocreation of physical destination {0} failed. RAR7101.diag.cause.1=Creation of physical destination in SJS MQ failed. Please look at SJS MQ log for more details. -RAR7101.diag.cause.2=You havent configured jms-service properly. Make sure that default-jms-host of jms-service points to a valid SJS MQ location. +RAR7101.diag.cause.2=You haven't configured jms-service properly. Make sure that default-jms-host of jms-service points to a valid SJS MQ location. jmsservice.defaulthost.notconfigured=RAR7102: Default-jms-host of jms-service is not configured properly. Using the first jms-host as the default-jms-host. -RAR7102.diag.cause.1=You havent configured default-jms-host in the jms-service. +RAR7102.diag.cause.1=You haven't configured default-jms-host in the jms-service. RAR7102.diag.cause.2=The jms-host configured as default-jms-host is not not available. jmservice.destination.already.autocreated=RAR7103: The physical destination {0} is already created. Derby.Shutdown.Exception=RAR7104: Exception while stopping Derby : Index: connectors/connectors-internal-api/src/main/resources/com/sun/appserv/connectors/internal/api/LogStrings.properties =================================================================== --- connectors/connectors-internal-api/src/main/resources/com/sun/appserv/connectors/internal/api/LogStrings.properties (revision 34026) +++ connectors/connectors-internal-api/src/main/resources/com/sun/appserv/connectors/internal/api/LogStrings.properties (working copy) @@ -1,13 +1,13 @@ classloader.load_class_fail=RAR5015:Unexpected exception in loading class [{0}] by classloader -RAR5015.diag.cause.1=Classpath is not propertly set in the domain.xml +RAR5015.diag.cause.1=Classpath is not properly set in the domain.xml RAR5015.diag.cause.2=The application server process does not have read permissions on the directory that holds the classes/jar RAR5015.diag.check.2=You do not have read permissions on the directory that holds the classes/jar -RAR5015.diag.check.1=Check that the classpath attribure in the java-config includes a reference to the jar/package directory for the class +RAR5015.diag.check.1=Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class classloader.load_class_fail_excp=RAR5046:Unexpected exception in loading class by classloader [{0}] -RAR5046.diag.cause.1=Classpath is not propertly set in the domain.xml +RAR5046.diag.cause.1=Classpath is not properly set in the domain.xml RAR5046.diag.cause.2=You do not have read permissions on the directory that holds the classes/jar -RAR5046.diag.check.1=Check that the classpath attribure in the java-config includes a reference to the jar/package directory for the class +RAR5046.diag.check.1=Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class RAR5046.diag.check.2=Check that the directory where the classes/jars reside have read permission for the application server process -error_reading_connectorservice_elt=RAR7014: Error reading Connector Service Element from domain.xml while trying to get shutdown-timeout-in-seconds value. Continuing wih the default shutdown timeout value +error_reading_connectorservice_elt=RAR7014: Error reading Connector Service Element from domain.xml while trying to get shutdown-timeout-in-seconds value. Continuing with the default shutdown timeout value RAR7014.diag.cause.1=Could not read shutdown-timeout-in-seconds from the domain.xml properly. RAR7014.diag.check.1=Make sure that domain.xml is configured correctly.