weblogic9.2.2 CR322044_920mp2.jar

<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE message_catalog PUBLIC "weblogic-message-catalog-dtd" "http://www.bea.com/servers/wls710/dtd/msgcat.dtd"> <message_catalog i18n_package="weblogic.jms" l10n_package="weblogic.i18n" subsystem="JMSExceptions" version="1.0" baseid="45000" endid="50000" loggables="true" prefix="BEA" > <!-- --> <logmessage messageid="045001" datelastchanged="1037404028551" datehash="815686208" severity="warning" method="logForeignJMSAlreadyDeployed(String mBeanName)" stacktrace="false" > <messagebody> The foreign JMS server MBean &quot;{0}&quot; has already been deployed. </messagebody> <messagedetail> The specified MBean has been deployed more than once, and it will not be deployed again. </messagedetail> <cause> This is an internal error. </cause> <action> Undeploy and re-reploy the MBean that caused the error. If this does not solve the problem, restart the server. </action> </logmessage> <!-- --> <logmessage messageid="045002" datelastchanged="1037404079394" datehash="-1412937589" severity="error" method="logErrorInJNDIBind(String localName)" stacktrace="false" > <messagebody> Error occurred while binding the remote JNDI object to the local JNDI name &quot;{0}&quot;. </messagebody> <messagedetail> An error occurred while binding an object from a foreign JNDI provider, such as a foreign JMS server, into the local JNDI tree. </messagedetail> <cause> The local JNDI name you are attempting to bind to may not be valid. </cause> <action> Check the name to see if its syntax is correct. </action> </logmessage> <!-- --> <logmessage messageid="045003" datelastchanged="1037404101536" datehash="1310822354" severity="error" method="logErrorInJNDIUnbind(String localName)" stacktrace="false" > <messagebody> Error occurred while unbinding a remote JNDI object from local JNDI name &quot;{0}&quot; </messagebody> <messagedetail> An error occurred while removing an object from the local JNDI tree. </messagedetail> <cause> There may be an error in the JNDI subsystem. </cause> <action> Check the nested exception message for more detail. </action> </logmessage> <!-- --> <logmessage messageid="045004" datelastchanged="1037404134002" datehash="86250898" severity="error" method="logNotJNDIReference()" stacktrace="false" > <messagebody> The JNDI object used to perform foreign lookup is not a reference. </messagebody> <messagedetail> The server attempted to perform a lookup of an object from a foreign JNDI provider, such as a foreign JMS server, and the object it found internally cannot be used to perform the remote lookup. </messagedetail> <cause> This is an internal error. </cause> <action> If the lookup continually fails, restart the server. </action> </logmessage> <!-- --> <logmessage messageid="045005" datelastchanged="1037404166890" datehash="22160417" severity="error" method="logCannotFindMBean(String mBeanName)" stacktrace="false" > <messagebody> The configuration MBean &quot;{0}&quot; cannot be found, or it is of the wrong type. </messagebody> <messagedetail> A configuration MBean, such as a ForeignJMSServer, ForeignJMSDestination, or ForeignJMSConnectionFactory MBean, cannot be found, and a JNDI lookup cannot proceed. </messagedetail> <cause> There may be something wrong with the name of the MBean. </cause> <action> Un-deploy and re-deploy the MBean. If this does not fix the problem, restart the server. </action> </logmessage> <!-- --> <logmessage messageid="045006" datelastchanged="1037404195461" datehash="552534525" severity="error" method="logJNDILookupFailed(String name)" stacktrace="false" > <messagebody> A lookup of the foreign JNDI object &quot;{0}&quot; failed. </messagebody> <messagedetail> The server was unable to complete the lookup of the specified JNDI object from a foreign JNDI server, such as a foreign JMS server. </messagedetail> <cause> The foreign server may not be responding, or there may be a problem with the configuration parameters for the ForeignJMSServer MBean. </cause> <action> Make sure the foreign JNDI provider is working, and check the configuration parameters for the ForeignJMSServer MBean. </action> </logmessage> <logmessage messageid="045025" severity="error" method="logJMSDeploymentError(String appName, String uriName)" stacktrace="false" > <messagebody> Unable to deploy JMS module: {1} from {0}. </messagebody> <messagedetail> Unable to deploy JMS module: {1} from {0}. </messagedetail> <cause> Invalid configuration of the JMS resource in the JMS module descriptor. </cause> <action> Fix the entity JMS resourc configuration/conflict. </action> </logmessage> <logmessage messageid="045026" severity="error" method="logErrorInSAFJNDIBind(String localName)" stacktrace="false" > <messagebody> Error occurred while binding the imported destination to the local JNDI name &quot;{0}&quot;. </messagebody> <messagedetail> An error occurred while binding an imported destination into the local JNDI tree. </messagedetail> <cause> The local JNDI name you are attempting to bind to may not be valid. </cause> <action> Check the name to see if its syntax is correct. </action> </logmessage> <!-- --> <logmessage messageid="045027" severity="error" method="logErrorInSAFJNDIUnbind(String localName)" stacktrace="false" > <messagebody> Error occurred while unbinding an improted destination from local JNDI name &quot;{0}&quot; </messagebody> <messagedetail> An error occurred while removing an imported destination from the local JNDI tree. </messagedetail> <cause> There may be an error in the JNDI subsystem. </cause> <action> Check the nested exception message for more detail. </action> </logmessage> <logmessage messageid="045028" severity="warning" method="logMessagesThresholdTimeExceeded(String serverName)"> <messagebody> The messages threshold for the JMS server {0} has been exceeded for more than one hour </messagebody> <messagedetail> The messages threshold on a JMS server has been exceeded. This message is only generated when the "health state" of a JMS server is queried. </messagedetail> <cause> The threshold was exceeded </cause> <action> Verify that messages are being consumed and sufficient memory is available </action> </logmessage> <logmessage messageid="045029" severity="warning" method="logMessagesThresholdRunningTimeExceeded(String serverName)"> <messagebody> The messages threshold for the JMS server {0} has been exceeded for more than 90 percent of the running time of the server