Skip navigation.
Downloads | Product Documentation | Support

MessagingBridge Subsystem Messages The MessagingBridge1.0 catalog contains messages in the range BEA200000 - BEA299999. Messages in this catalog are part of the `weblogic.jms` Internationalization package and the `weblogic.i18n` Localization package.
BEA-200000 | Error: Failed to initialize the messaging bridge service.
Description | Errors were detected during the initialization of the messaging bridge service, and the startup of the service was terminated.
Cause | Most of the time, this results from configuration errors.
Action | Check the configuration file and reboot the system.
BEA-200001 | Info: The messaging bridge service has successfully shut down.
Description | The messaging bridge shut down is complete and all the resources are cleaned up.
Cause | This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.
Action | No action required.
BEA-200002 | Error: Failed to deploy the messaging bridge "name" because the messaging bridge service is shut down.
Description | This message indicates that the messaging bridge service is shut down, and therefore no new bridge can be deployed.
Cause | This message indicates that the messaging bridge service has been shut down, either at the request of the administrator or due to errors.
Action | Reboot the system.
BEA-200003 | Error: Failed to deploy the messaging bridge "name" due to error: e.
Description | This message indicates that an error has occurred during the deployment of a bridge.
Cause | This is likely due to configuration errors or an internal error as indicated in the message body.
Action | Check the configuration file and reboot the server.
BEA-200004 | Info: The messaging bridge "name" has been successfully deployed.
Description | This message indicates that the messaging bridge has been successfully deployed.
Cause | This message indicates that the messaging bridge has been successfully deployed.
Action | No action required.
BEA-200005 | Error: Failed to start messaging bridge "name" due to error: e.
Description | This message indicates that an error has occurred during the startup of a bridge.
Cause | This is likely due to configuration errors or an internal error as indicated in the message body.
Action | Check the configuration file and reboot the server.
BEA-200006 | Debug: Messaging bridge debugging arg0.
Description | Uncataloged debug message - please do not change
Cause | Debugging - please do not change.
Action | No action required.
BEA-200007 | Info: Debugging arg0
Description | Uncatalogued debug message - please do not change.
Cause | Debugging - please do not change.
Action | No action required.
BEA-200008 | Error: Bridge "arg0" does not have a configured source destination.
Description | Each messaging bridge should have a source and a target destination configured. This message indicates that there is no source destination configured for a bridge.
Cause | This is likely due to configuration errors.
Action | Update the configuration and restart the server.
BEA-200009 | Error: Bridge "arg0" does not have a configured target destination.
Description | Each messaging bridge should have a source and a target destination configured. This message indicates that there is no target destination configured for a bridge.
Cause | This is likely due to configuration errors.
Action | Update the configuration and restart the server.
BEA-200010 | Info: Bridge "arg0" successfully connected to the source adapter "arg1".
Description | This message indicates that the messaging bridge has successfully connected to the source adapter.
Cause | This message indicates that the messaging bridge has successfully connected to the source adapter.
Action | No action required.
BEA-200011 | Info: The bridge "arg0" failed to find the adapter "arg1".
Description | The bridge needs to find the adapter used by its source and target destinations, before it can start transferring messages. The adapters are deployed separately. This message indicates that one of the adapters is not found. The bridge will try again once it detects the existence of the adapter.
Cause | One of the adapters is not deployed.
Action | Deploy the required adapters.
BEA-200012 | Info: Bridge "arg0" successfully found the adapters that are configured for it.
Description | The bridge needs to find the adapter(s) used by its source and target destinations, before it can start transferring messages. The adapters are deployed separately. This message indicates that the bridge successfully found the adapters.
Cause | This message indicates that the bridge successfully found the adapters.
Action | No action required.
BEA-200013 | Error: Invalid properties are defined for the source destination of bridge "arg0".
Description | This message indicates that invalid properties are configured for the source destination of bridge "arg0".
Cause | Invalid configuration.
Action | Update the configuration and restart the server.
BEA-200014 | Error: Invalid properties are defined for the target destination of bridge "arg0".
Description | This message indicates that invalid properties are configured for the target destination of bridge "arg0".
Cause | Invalid configuration.
Action | Update the configuration and restart the server.
BEA-200015 | Error: An error occurred in bridge "arg0" during the transfer of messages (e).
Description | The bridge detected an error during the transfer of messages. If the bridge works in a quality of service that requires transactions, the transaction will be rolled back.
Cause | An error occurred on one of the bridge destinations.
Action | Check the system on both the source and target sides, and restart the server.
BEA-200016 | Error: Bridge "arg0" failed to roll back the transaction (e) when an error occurred during the message transfer.
Description | The bridge detected an error during the transfer of messages, and it failed to roll back the current transaction.
Cause | An error occurred on one of the bridge destinations.
Action | Check the system on both the source and target side, and restart the server.
BEA-200017 | Info: Bridge "arg0" failed to connect to the source destination and will try later. (e)
Description | The bridge failed to establish a connection to the source destination. The bridge will reconnect after a certain delay time. You can configure the delay time for each bridge.
Cause | An error occurred on the source destination of the bridge. The source destination may not exist or is not yet active.
Action | Check the source system and its configuration. Also, make sure the destination is configured in the system, and the system is running.
BEA-200018(retired) | Error: Bridge "arg0" failed to register the adapters XAResource with the transaction manager (e).
Description | This message is no longer used.
Cause | This message is no longer used.
Action | This message is no longer used.
BEA-200019 | Info: Bridge "arg0" is started.
Description | This message indicates that the messaging bridge is started.
Cause | This message indicates that the messaging bridge is started.
Action | No action required.
BEA-200020 | Info: Bridge "arg0" is stopped.
Description | This message indicates that the messaging bridge is stopped.
Cause | This message indicates that the messaging bridge is stopped.
Action | No action required.
BEA-200021 | Info: Bridge "arg0" failed to get one of the adapters from JNDI (e).
Description | The bridge performed a JNDI lookup for the two adapters, and the lookup failed.
Cause | At least one adapter was not deployed when the bridge started. It is also possible that the JNDI name configured in the bridge destinations do not match the ones in the adapter deployment descriptor file.
Action | Check to see if the adapter(s) required by the source and target destinations are deployed on the server where the bridge is configured. Make sure that the JNDI name in the adapter deployment descriptor file matches the one in the configuration of the bridge destinations. Otherwise, no action is required. The bridge will automatically try again later.
BEA-200022 | Error: Bridge "arg0" failed to obtain adapter metadata (e).
Description | Bridge "arg0" failed to obtain adapter metadata (e).
Cause | This is an internal error that should not occur.
Action | No action required. This error should not occur.
BEA-200023 | Error: Bridge "arg0" failed to set up a timer to retry the lookup of adapters (e).
Description | The bridge failed in the JNDI lookup of adapters and tried to set up a timer for a later retry. However, the timer setup failed.
Cause | This is due to an internal error.
Action | Contact BEA support.
BEA-200024 | Info: Bridge "arg0" refused to obtain connections and transfer any messages, because it has been stopped or suspended, or is shutting down.
Description | The bridge is shutting down, suspended, or stopped. As a result, it refused to do any more work.
Cause | The administrator has shut down or stopped the bridge, or the bridge is suspended for migration.
Action | No action required.
BEA-200025 | Error: Bridge "arg0" failed to start, because the quality of service configured (arg1) is unreachable. This is likely due to an invalid configuration or adapter limitations.
Description | This message indicates that the required quality of service is unreachable. This is likely because the configurations of the underlying systems or their bridge destinations do not meet the requirement of the quality of service. It is also possible that the adapters or the underlying systems do not have sufficient supports. The bridge failed to start, because it is configured to disallow degradation of the quality of service.
Cause | The configuration does not match the ability of the adapters and underlying systems.
Action | Change the configuration of the bridge with a reachable quality of service, or turn on the QOSDegrationAllowed boolean.
BEA-200026 | Warning: Bridge "arg01" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was t.)
Description | This message indicates that errors occurred during the process of transferring messages. The bridge stopped its connections to both adapters and will attempt reconnect soon.
Cause | There was a problem in receiving or sending messages to one of the sides of the bridge.
Action | No action required.
BEA-200027 | Info: Bridge "arg01" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.
Description | This message indicates that the bridge has been idle for quite some time. It is time to check the sanity of the connections to the adapters and reestablish them.
Cause | This may occur because the source destination is empty or because the connection to the source is stale and needs to be reestablished.
Action | Check the source system.
BEA-200028 | Info: The bridge "arg01" has started transferring messages.
Description | This message indicates that the bridge has just started transferring messages. This may indicate that the bridge has just started transferring messages. This may also indicate that the bridge work has somehow stopped and has just restarted.
Cause | This message indicates that the bridge has just started transferring messages.
Action | No action required.
BEA-200029 | Info: Bridge "arg0" failed to connect to the target destination and will try again later. (e)
Description | The bridge failed to establish a connection to the target destination. The bridge will reconnect after a certain delay time. You can configure this delay time for each bridge.
Cause | An error occurred on the target destination of the bridge. The error may occur because the target destination does not exist or has not yet been active.
Action | Check the target system and its configuration, and make sure the destination is configured in the system and the system is running.
BEA-200030 | Info: Bridge "arg0" is configured to work in "arg1" mode, and it is actually working in "arg2" mode.
Description | This message reveals the quality of service the bridge is providing. The actual quality of service may not be the same as what is configured. This only occurs when the configured quality of service is unreachable and the bridge is configured to allow the degradation of quality of service.
Cause | This message reveals what quality of service the bridge is actually providing.
Action | No action required.
BEA-200031 | Info: Bridge "arg0" is configured to allow degradation of its quality of service in cases where the configured quality of service can not be reached.
Description | This message indicates that the quality of service of this bridge is allowed to be downgraded if the required one is unreachable.
Cause | This message indicates that the quality of service of this bridge is allowed to be downgraded if the required one is unreachable.
Action | No action required.
BEA-200032 | Info: Bridge "arg0" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.
Description | This message indicates that the quality of service of the bridge is not allowed to be downgraded. The bridge will not work if the required quality of service is unreachable.
Cause | This message indicates that the quality of service of the bridge is not allowed to be downgraded.
Action | No action required.
BEA-200033 | Info: Bridge "arg0" is obtaining connections to the two adapters.
Description | This message indicates that the messaging bridge is obtaining connections to the two adapters.
Cause | This message indicates that the messaging bridge is obtaining connections to the two adapters.
Action | No action required.
BEA-200034 | Info: Bridge "arg0" is shut down.
Description | This message indicates that the messaging bridge is shut down.
Cause | This message indicates that the messaging bridge is shut down.
Action | No action required.
BEA-200035 | Info: Bridge "arg01" has been started from the stopped mode.
Description | This message indicates that the bridge was in stopped mode and has just been restarted.
Cause | This message indicates that the bridge was in stopped mode and has just been restarted.
Action | No action required.
BEA-200036 | Info: The Started attribute of Bridge "arg01" has been changed from "old" to "new".
Description | This message indicates that the Started attribute of the messaging bridge has been changed.
Cause | This is due to a configuration change.
Action | No action required.
BEA-200037 | Info: The "attr" attribute of Bridge "arg01" has been changed from "old" to "new".
Description | The "attr" attribute of Bridge "arg01" has been changed from "old" to "new".
Cause | This is due to a configuration change.
Action | No action required.
BEA-200038 | Info: Bridge "arg01" is inactive because it is configured to be stopped.
Description | The message indicates that the named bridge is not active and will not transfer messages until it is started from the Console.
Cause | The bridge is configured to be stopped.
Action | No action required.
BEA-200039 | Error: Bridge "arg01" has the same destination as its source and target.
Description | The message indicates that the source and target destinations configured for a bridge are actually the same physical destination.
Cause | This is due to a configuration error.
Action | Update the configuration.
BEA-200040 | Error: Bridge destination arg01: connection URL cannot be null if the initial context factory is not weblogic.jndi.WLInitialContextFactory.
Description | Bridge destination arg01: connection URL cannot be null if the initial context factory is not weblogic.jndi.WLInitialContextFactory.
Cause | This is due to a configuration error.
Action | Update the configuration.
BEA-200041 | Error: Bridge destination arg01: a bridge destination for JMS must have a connection factory JNDI name and a destination JNDI name configured.
Description | Bridge destination arg01: a bridge destination for JMS must have a connection factory JNDI name and a destination JNDI name configured.
Cause | This is due to a configuration error.
Action | Update the configuration.
BEA-200042 | Info: Bridge arg0 failed to connect to the source destination and will try again in time seconds. (e)
Description | The bridge failed to establish a connection to the source destination. The bridge will reconnect after a certain delay time. The delay time can be configured for each bridge.
Cause | An error occurred on the source destination of the bridge. The error may occur because the source destination does not exist or has not been active yet.
Action | Check the source system and its configuration. Make sure the destination is configured in the system and the system is running.
BEA-200043 | Info: Bridge "arg0" failed to connect to the target destination and will try again in time seconds. (e)
Description | The bridge failed to establish a connection to the target destination. The bridge will re-connect after a certain delay time. You can configure a delay time for each bridge.
Cause | The error occurred on the target destination of the bridge. The error may occur because the target destination does not exist or has not been active yet.
Action | Check the target system and its configuration. Make sure the destination is configured in the system and the system is running.
BEA-200044 | Warning: Bridge arg0 failed to obtain an execute thread from the Messaging Bridge Thread Pool, not enough available threads configured.
Description | The bridge failed to obtain an execute thread from the Messaging Bridge Thread Pool. The bridge will attempt to obtain an execute thread from the default execute thread pool instead.
Cause | The warning occurred on bridge startup when the bridge was attempting to gain an available thread from the Messaging Bridge Thread Pool.
Action | Check the number of configured threads for the Messaging Bridge Thread Pool and increase the value to match the number of running bridges on the WebLogic Server.