com.sun.logging.enterprise.resource.jms.LogStrings.properties Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of common-util
There is a newer version: 10.0-b28
# Copyright 2004 Sun Microsystems, Inc. All rights reserved.
# SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
#
# Log messages used by the javax.enterprise.core.security logger
# LogDomains.SECURITY_LOGGER, subsystem SEC.
# See java.text.MessageFormat for details on constructing messages.
# Messages in this file must be of the form
# <4CharIntegerMessageId>:
#
#example.message1=JMS0001:Test Message. Parameter 1={0} parameter 2={1}
#example.message2=JMS0002:Date Message. Parameter 1={0,date} Parameter 2={1,time}
#example.message3=JMS0003:Number Message. Parameter 1={0,number,integer}
jms.start=JMS5001: Starting JMS service...
jms.binding=JMS5002: Binding [{0}]
jms.start_failed=JMS5003: Couldn't start JMS service...
jms.session_not_closed=JMS5004: Session cannot be closed
jms.resource_handle_create_failed=JMS5005: resource handle could not be created
jms.resource_handle_register_failed=JMS5006: resource handle could not be registered
jms.incorrect_cf_access=JMS5007: Illegal connection factory access to [{0}]. J2EE Components should access JMS Connection Factories through a resource-ref in java:comp/env
jms.no_resource_principal=JMS5008: A resource-reference for JMS Connection Factory specifies container authorization but no username/password is available [{0}]
jms.not_container_auth_queue=JMS5009: Calling createQueueConnection() on resource-ref with APPLICATION authentication. Should use createQueueConnection(username, password) instead
jms.connection_container_auth_error=JMS5010: JMS Connection with container authentication cannot programmatically set username and password
jms.not_container_auth_topic=JMS5011: Calling createTopicConnection() on resource-ref with APPLICATION authentication. Should use createTopicConnection(username, password) instead
jms.connectionfactory_not_found_msg=JMS5012: Connection Factory [{0}] not found
jms.connectionfactory_not_found_excp=JMS5013: Connection Factory not found
jms.create_resource_failed=JMS5014: Unexpected pooling exception creating resource
jms.install_resources=JMS5015: Install JMS resources ...
jms.install_resources_error=JMS5016: Install JMS resources error: [{0}] 
jms.install_resources_exception=JMS5017: Install JMS resources throw Exception
jms.delete_connectionfactory_resource_error=JMS5018: Delete Connection factory resource error: [{0}]
jms.delete_connectionfactory_resource_exception=JMS5019: Delete connection factory resource got exception
jms.delete_destination_resource_error=JMS5020: Delete destination resource error: [{0}]
jms.delete_destination_resource_exception=JMS5021: Delete destination resource got exception
jms.broker_already_up=JMS5022: A Message Queue broker instance [{0}] is already running at port [{1}]. Please configure a different port number for the JMS service.
jms.broker_started=JMS5023: JMS service successfully started. Instance Name = {0}, Home = [{1}].
jms.broker_startup_failed=JMS5024: JMS service startup failed.
jms.broker_shutting_down=JMS5025: JMS service shutting down.
jms.broker_shutdown_complete=JMS5026: JMS service shutdown complete.
jms.create_dest_obj_error=JMS5027: Exception in creating JMS destination administered object [{0}]:  [{1}]
jms.create_connfactory_resource_error=JMS5028: Exception in creating JMS connection factory resource [{0}]: [{1}]
jms.broker_found=JMS5029: Successfully attached to an existing Message Queue broker. Instance Name = {0}
jms.resource_disabled=JMS5030: JMS resource {0} [Type: {1}] is disabled.
jms.create_dest_obj_exception=JMS5031: Exception in creating JMS destination administered object
jms.create_connfactory_resource_exception=JMS5032: Exception in creating JMS connection factory resource
jms.broker_attach_failed=JMS5033: Could not attach to an existing JMS service broker process.
jms.broker_exec_failed=JMS5034: Could not start the JMS service broker process.
jms.broker_ping_failed=JMS5035: Timed out after {0} milliseconds while trying to verify if the JMS service startup succeeded.
jms.broker_log_location=JMS5036: More details may be available in the log file for the JMS service broker instance {0}. Please refer to the JMS provider documentation for the exact location of this log file.
jms.broker_instance_dir=JMS5037: Check permissions of MQ instance directory {0}
jms.broker_notlocal=JMS5038: jms-service element in domain.xml is configured to have type={0}. JMS service will be started locally only if type is LOCAL.