Index: connectors/connectors-runtime/src/main/java/com/sun/enterprise/connectors/util/ConnectorClassLoader.java =================================================================== --- connectors/connectors-runtime/src/main/java/com/sun/enterprise/connectors/util/ConnectorClassLoader.java (revision 40360) +++ connectors/connectors-runtime/src/main/java/com/sun/enterprise/connectors/util/ConnectorClassLoader.java (working copy) @@ -60,7 +60,7 @@ public class ConnectorClassLoader extends ASURLClassLoader { - private static final Logger _logger = LogDomains.getLogger(ConnectorClassLoader.class, LogDomains.CORE_LOGGER); + private static final Logger _logger = LogDomains.getLogger(ConnectorClassLoader.class, LogDomains.RSR_LOGGER); private static ConnectorClassLoader classLoader = null; @@ -164,10 +164,8 @@ classLoaderToRemove = null; _logger.log( Level.WARNING, - "The Connector module " - + moduleName - + " has been removed. Please redeploy all applications that " - + "are using this connector module's resources"); + "enterprise_util.remove_connector", + moduleName); } } 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 40360) +++ connectors/connectors-runtime/src/main/resources/com/sun/logging/enterprise/resource/resourceadapter/LogStrings.properties (working copy) @@ -283,8 +283,8 @@ jmsra.upgrade_failed=RAR7001 : Upgrading a MQ resource adapter failed : {0} RAR7001.diag.cause.1=Could not unzip the MQ resource adapter archive from upgraded MQ. RAR7001.diag.check.1=Check whether new MQ resource adapter archive in imq_home/lib is accessible. -jmsra.upgrade_started=RAR7002 : MQ Resource adapter upgradation started. -jmsra.upgrade_completed=RAR7003 : MQ Resource adapter upgradation completed. +jmsra.upgrade_started=RAR7002 : MQ Resource adapter upgrade started. +jmsra.upgrade_completed=RAR7003 : MQ Resource adapter upgrade completed. endpointfactory.unavailable=RAR7004 : MDB deployment is still happening. Cannot create end point now. RAR7004.diag.cause.1=Resource Adapter is requesting endpoints to the MDB, before MDB deployment is complete. endpointfactory.loader_not_found=RAR7005 : Class loader not found : [{0}] @@ -343,8 +343,8 @@ RAR7099.diag.cause.1=The configuration parameters like username/password for the Pool being accessed are changed and the application has not been redeployed RAR7099.diag.cause.2=The MCF equals method is improperly implemented RAR7099.diag.check.2=Ensure that your resource adapter properly implements the equals method -jmservice.destination.autocreated=RAR7100: Physical destination {0} is autocreated by application server. -jmservice.destination.autocreatefailed= RAR7101: Autocreation of physical destination {0} failed. +jmservice.destination.autocreated=RAR7100: Physical destination {0} is auto-created by application server. +jmservice.destination.autocreatefailed= RAR7101: Auto-creation 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 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. @@ -373,9 +373,9 @@ RAR7110.diag.cause.3=Error loading the embedded RAR. RAR7110.diag.check.1=See server log for more information resource_pool.remove_max_used_conn=RAR7113: destroying connection since it has reached the maximum usage of : {0} -pool.datastructure.init.failure.exception=RAR7123: Unable to initalize custom pool data-structure. Exception occurred : -pool.waitqueue.init.failure.exception=RAR7124: Unable to initalize connection pool wait-queue. Exception occurred : -pool.resource.gateway.init.failure.exception=RAR7125: Unable to initalize connection pool resource-gateway. Exception occurred : +pool.datastructure.init.failure.exception=RAR7123: Unable to initialize custom pool data-structure. Exception occurred : +pool.waitqueue.init.failure.exception=RAR7124: Unable to initialize connection pool wait-queue. Exception occurred : +pool.resource.gateway.init.failure.exception=RAR7125: Unable to initialize connection pool resource-gateway. Exception occurred : CCP.ValidateAtmostEveryIdleSecs.Set=ValidateAtmostEveryIdleSecs property set for pool : {0} endpoint.determine.destinationtype=RAR7126: Assuming destination type {0} for MDB {2} from administered object {1} resource_pool.failed_creating_resource=RAR7127: Unable to create a new resource : {0} @@ -385,7 +385,7 @@ poolmgr.err_enlisting_res_in_getconn=RAR7132: Unable to enlist the resource in transaction. Returned resource to pool. Pool name: [ {0} ] rardeployment.connectorresource_removal_from_jndi_error=RAR7133: Unable to remove resource [ {0} ] from jndi rardeployment.no_module_deployed=RAR7134: RAR [ {0} ] is not deployed -rardeployment.connector_descriptor_jndi_removal_failure=RAR7135: Unable to remove connector-descritor of resource-adatper [{0}] from jndi +rardeployment.connector_descriptor_jndi_removal_failure=RAR7135: Unable to remove connector-descriptor of resource-adapter [{0}] from jndi method.name.nogetterforproperty=No getter for property [ {0} ] of class [ {1} ] rardeployment.defaultpoolresourcecreation.failed=RAR7137: Unable to create default resource for the resource-adapter rar.undeployment.default_pool_delete_fail=RAR7138: Unable to undeploy the default pool [ {0} ] @@ -394,6 +394,7 @@ rar.undeployment.sun_ra_pool_delete_fail=RAR7141: Unable to undeploy the sun-ra pool [ {0} ] enterprise_util.connector_malformed_url=RAR7142: Connector classloader unable to add files to classpath no_resource=RAR7143: could not find a resource by name : {0} +enterprise_util.remove_connector=RAR7144: The Connector module {0} has been removed. Please redeploy all applications that are using this connector module's resources. workmanager.instantiation_error=RAR7145: Unable to obtain work manager : tx.sync.registry.lookup.failed=RAR7146: Unable to obtain transaction synchronization registry : jdbc.pool_not_reachable=RAR7010: Pool not reachable. @@ -410,8 +411,8 @@ RAR8014.diag.cause.1=Connection Pool properties, Associate with thread is true and Pooling is disabled which is not allowed. conn_pool_obj_utils.pooling_disabled_conn_validation_invalid_combination=RAR8015: Connection validation is set to true and Pooling is disable, for pool: {0} RAR8015.diag.cause.1=Connection validation is useful only in a pooled environment. -conn_pool_obj_utils.pooling_disabled_validate_atmost_once_invalid_combination=RAR8016: Validate Atmost once period is set when Pooling is disabled, for pool : {0} -RAR8016.diag.cause.1=Validate atmost once period is useful only in a pooled environment. +conn_pool_obj_utils.pooling_disabled_validate_atmost_once_invalid_combination=RAR8016: Validate At most once period is set when Pooling is disabled, for pool : {0} +RAR8016.diag.cause.1=Validate at most once period is useful only in a pooled environment. conn_pool_obj_utils.pooling_disabled_match_connections_invalid_combination=RAR8017: Match Connections is set to true when Pooling is disabled, for pool : {0} RAR8017.diag.cause.1=Match Connections is useful only in a pooled environment. conn_pool_obj_utils.pooling_disabled_max_conn_usage_invalid_combination=RAR8018: Max Connection usage is set when Pooling is disabled, for pool : {0} @@ -420,7 +421,7 @@ RAR8019.diag.cause.1=Idle Timeout is useful only in a pooled environment. pool.get_validation_table_names_mc_destroy= Exception while destroying Managed Connection while getting validation table names, for pool : {0} validation.constraints.violation=RAR8021: Following validation constraints violated for Java Bean of type [ {0} ] of resource-adapter [ {1} ] : Message = {2}) -RAR8021.diag.cause.1=There could be erraneous values (not acceptable according to the constraints) specified in the bean +RAR8021.diag.cause.1=There could be erroneous values (not acceptable according to the constraints) specified in the bean pool.get_invalid_connections_resourceexception= RAR8022: Failed to get invalid connections from Managed Connection Factory {0}. Exception = {1}; Message = {2} RAR8022.diag.cause.1=Resource Adapter threw a ResourceException. RAR8022.diag.check.1=Check the resource adapter's documentation. @@ -433,9 +434,9 @@ pool.flush_pool_failure=RAR8025: Flush Connection Pool failed for pool - {0}. Reason - {1} RAR8025.diag.cause.1=Database server is not up and Flush tries to access the pool. RAR8025.diag.check.1=Make sure database server is up and running. -pool.datastructure.init.failure=RAR8026: Unable to initalize custom pool data-structure : {0} -pool.waitqueue.init.failure=RAR8027: Unable to initalize custom connection pool wait-queue : {0} -pool.resource.gateway.init.failure=RAR8028: Unable to initalize custom connection pool resource-gateway : {0} +pool.datastructure.init.failure=RAR8026: Unable to initialize custom pool data-structure : {0} +pool.waitqueue.init.failure=RAR8027: Unable to initialize custom connection pool wait-queue : {0} +pool.resource.gateway.init.failure=RAR8028: Unable to initialize custom connection pool resource-gateway : {0} core.resource_disabled=RAR8029: Resource [ {0} ] of type [ {1} ] is not enabled pool.get_validation_table_names=RAR8030: Exception while getting validation table names. Set resource-adapter log-level to FINE for exception stack trace. RAR8030.diag.cause.1=Database access error