|
BEA-040000(retired)
|
Info: JMSServer "arg0" deleting subscription "arg1". No matching topic named "arg2".
|
Description
| During recovery, a durable subscriber entry, arg1, was found containing a topic, arg2, that no longer exists. The entry will be ignored.
|
|
Cause
| The topic no longer exists in the current configuration and the durable subscription is ignored.
|
|
Action
| No action required.
|
|
|
BEA-040002(retired)
|
Debug: JMS Debugging arg0
|
Description
| Uncatalogued debug message - please do not change
|
|
Cause
| Debugging - please do not change.
|
|
Action
| No action required.
|
|
|
BEA-040003(retired)
|
Error: JMSServer "arg0" SQL Error: arg1
|
Description
| SQL error has occurred.
|
|
Cause
| Check to see that the database is properly configured.
|
|
Action
| Re-run the operation.
|
|
|
BEA-040004(retired)
|
Info: JMSServer "arg0" SQL Error Code: arg1
|
Description
| SQL error has occurred.
|
|
Cause
| Check to see that the database is properly configured.
|
|
Action
| Re-run the operation.
|
|
|
BEA-040005(retired)
|
Info: JMSServer "arg0" SQL State: arg1
|
Description
| SQL error has occurred.
|
|
Cause
| Check to see that the database is properly configured.
|
|
Action
| Re-run the operation.
|
|
|
BEA-040006(retired)
|
Info: Server arg0. This server is not licensed to run JMS. To find out about JMS licensing, please contact sales@weblogic.com arg1
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040008(retired)
|
Info: Configured arg0.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040009(retired)
|
Info: Configured arg0.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040010
|
Info: JMSServer "arg0" configured arg1.
|
Description
| arg1 session pool(s) configured for JMSServer "arg0" in the configuration.
|
|
Cause
| This message indicates the number of session pools configured or deployed for the JMSServer while processing the configuration file.
|
|
Action
| No action required.
|
|
|
BEA-040011(retired)
|
Info: JMSServer "arg0" configured arg1.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040013(retired)
|
Info: JMS is successfully started.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040014
|
Error: Failed to start JMSServer. JMS is shutting down.
|
Description
| Failed to start JMSServer. JMS is shutting down.
|
|
Cause
| This message indicates that the JMS server failed to initialize.
|
|
Action
| Modify the configuration and restart the server file and reboot the system. There should be earlier messages printed indicating the cause of the failure.
|
|
|
BEA-040015
|
Info: JMS shutdown is complete.
|
Description
| JMS shutdown is complete and all the resources are cleaned up.
|
|
Cause
| This message indicates that JMS has been shutdown, either at the request of the administrator or due to configuration errors.
|
|
Action
| No action required.
|
|
|
BEA-040016(retired)
|
Info: No JMS MBeans are configured for server arg0.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040017
|
Error: JMSServer "arg0" connection factory JNDI binding failed, ex1. JMS is shutting down.
|
Description
| JMSServer "arg0" connection factory JNDI binding failed, ex1. JMS is shutting down.
|
|
Cause
| This message indicates that an error was found when binding the connection factory to a JNDI name during configuration.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040018
|
Error: Could not obtain a replicated or non-replicated InitialContext from the default provider, ex0.
|
Description
| Could not obtain a replicated or non-replicated InitialContext from the default provider, ex0.
|
|
Cause
| This message indicates that an error was encountered when binding a JMS Server to a JNDI name during configuration.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the server.
|
|
|
BEA-040019
|
Error: JMSServer "arg0" failed to bind to JNDI name: arg1.
|
Description
| JMSServer "arg0" failed to bind to JNDI name: arg1.
|
|
Cause
| This message indicates that an error was encountered when binding a JMS Server to a JNDI name during configuration.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040020(retired)
|
Debug: Debugging arg0
|
Description
| Uncatalogued debug message - please do not change
|
|
Cause
| Debugging - please do not change.
|
|
Action
| No action required.
|
|
|
BEA-040024
|
Alert: JMSServer "arg0" byte threshold for destination arg1 has been exceeded.
|
Description
| The total message byte count for destination arg1 has exceeded the bytesThresholdHigh attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040025
|
Alert: JMSServer "arg0" byte threshold condition for destination arg1 has cleared.
|
Description
| The total message byte count for destination arg1 has dropped below the bytesThresholdLow attribute
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040026
|
Alert: JMSServer "arg0" message threshold for destination arg1 has been exceeded.
|
Description
| The total message count for destination arg1 has exceeded the messagesThresholdHigh attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action
|
|
|
BEA-040027
|
Alert: JMSServer "arg0" message threshold condition for destination arg1 has cleared.
|
Description
| The total message count for destination arg1 has dropped below the messagesThresholdLow attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040028
|
Alert: JMSServer "JMSServer" byte threshold for the server has been exceeded.
|
Description
| The total message byte count for JMSServer "JMSServer" has exceeded the bytesThresholdHigh attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040029
|
Alert: JMSServer "JMSServer" byte threshold for server has cleared.
|
Description
| The total message byte count for JMSServer "JMSServer" has been dropped below the bytesThresholdLow attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040030
|
Alert: JMSServer "JMSServer" message threshold for the server has been exceeded.
|
Description
| The total message count for JMSServer "JMSServer" has exceeded the messagesThresholdHigh attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040031
|
Alert: JMSServer "JMSServer" message threshold for the server has cleared.
|
Description
| The total message count for JMSServer "JMSServer" has dropped below the messagesThresholdLow attribute.
|
|
Cause
| This is an informational message.
|
|
Action
| No action required.
|
|
|
BEA-040033(retired)
|
Error: JMSServer "arg0" arg1 license validation failed, arg2.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040034(retired)
|
Info: JMSServer "arg0" destination arg1 will be removed when JMS starts again.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040035(retired)
|
Info: JMSServer "arg0". Cancel the destination arg1. Remove operation.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040036(retired)
|
Error: Failed to start JMSServer, as no valid license was found. JMS is shutting down.
|
Description
| Failed to start JMSServer, as no valid license was found. JMS is shutting down.
|
|
Cause
| This message indicates that a valid license for running JMS was not found.
|
|
Action
| Check or refresh the license file WebLogicLicense.xml and reboot the system.
|
|
|
BEA-040037(retired)
|
Error: JMSServer "arg0" count count1 failed to start JMSServer ex2. JMS is shutting down.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040038(retired)
|
Error: Failed to start JMSServer. Unexpected state state0 at start(). JMS is shutting down.
|
Description
| Failed to start JMSServer. Unexpected state state0 at start(). JMS is shutting down.
|
|
Cause
| This message indicates that the JMSServer could not be started.
|
|
Action
| Review earlier printed messages. These should indicate the exact nature of the problem. Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040040(retired)
|
Error: JMSServer "arg0" failed to dynamically add a new server session pool "arg1". Exception is "e".
|
Description
| Failed to dynamically add a new server session pool with a name that has already been used by one of the existing server session pools.
|
|
Cause
| A duplicate name was used for a server session pool.
|
|
Action
| Provide a new name for the server session pool to be created, and re-run the adding operation.
|
|
|
BEA-040041(retired)
|
Error: JMSServer "arg0" server session pool closed for connection consumer: arg1
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040042(retired)
|
Error: JMSServer "arg0" connection closed for server session pool: arg1
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040043(retired)
|
Error: JMSServer "arg0" server session pool connection closed for connection consumer: arg1
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040045(retired)
|
Error: JMSServer "arg0" connections were broken between connection consumer: arg1 and its server session.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040046(retired)
|
Error: JMSServer "arg0" server session was closed for connection consumer arg1.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040047(retired)
|
Alert: JMSServer "server" store failure occurred while deleting consumer consumer, t.
|
Description
| An error occurred while deleting a consumer.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database if applicable and restart JMS.
|
|
|
BEA-040048(retired)
|
Alert: JMSServer "server" store failure occurred while writing message for topic topic, t.
|
Description
| Message is still delivered, but may not be persistent.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040049(retired)
|
Alert: JMSServer "server" store failure occurred while writing message for queue queue, t.
|
Description
| Message is still delivered, but may not be persistent.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040050(retired)
|
Alert: JMSServer "server" store failure occurred while writing durable subscriber message for topic topic, t.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040051(retired)
|
Alert: JMSServer "server" store failure occurred while deleting message for destination topic, t.
|
Description
| The message was delivered, but may not have been deleted.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040052(retired)
|
Alert: JMSServer "server" store failed to open t.
|
Description
| An error occurred while trying to open a JMS store.
|
|
Cause
| Disk failure or database failure.
|
|
Action
| Check to see that the persistent store is available and properly configured.
|
|
|
BEA-040053(retired)
|
Alert: JMSServer "server" failed to register a JMS server with the transaction manager.
|
Description
| An error occurred while trying to register a JMS server with the transaction manager.
|
|
Cause
| This might be due to the specification of a duplicate JMS store name.
|
|
Action
| Check to see that there are no duplicate JMS store names. Check to see that the transaction manager successfully initialized.
|
|
|
BEA-040054(retired)
|
Info: JMSServer "server". No persistent store configured.
|
Description
| Persistent messages will be automatically downgraded to non-persistent.
|
|
Cause
| No persistent store specified in the server configuration.
|
|
Action
| Make sure there are no applications using destinations on this server that require persistent messaging.
|
|
|
BEA-040055(retired)
|
Info: JMSServer "server" messages(s) with no matching destination "dest".
|
Description
| While recovering, message(s) were found for an unconfigured destination. The messages will be deleted.
|
|
Cause
| The destination no longer exists.
|
|
Action
| No action required.
|
|
|
BEA-040056(retired)
|
Info: JMSServer "server". Deleting count messages(s) with no matching destination.
|
Description
| While recovering, message(s) were found for an unconfigured destination.
|
|
Cause
| The destination no longer exists.
|
|
Action
| No action required.
|
|
|
BEA-040057(retired)
|
Info: JMSServer "arg0". Expiring arg1 messages(s).
|
Description
| Expired messages are deleted.
|
|
Cause
| While recovering, expired messages were found.
|
|
Action
| No action required.
|
|
|
BEA-040058(retired)
|
Alert: JMSServer "arg0". Unhandled exception. Error code "arg1", t.
|
Description
| The server encountered an unexpected condition but may attempt to continue operation.
|
|
Cause
| Look for earlier messages that might explain what caused the error.
|
|
Action
| Contact customer support.
|
|
|
BEA-040059(retired)
|
Alert: JMSServer "arg0". Unhandled exception occurred during commit, t.
|
Description
| Commit may or may not have succeeded.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Contact customer support.
|
|
|
BEA-040060(retired)
|
Alert: JMSServer "arg0". Unhandled exception occurred during rollback, t.
|
Description
| Rollback may or may not complete.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Contact customer support.
|
|
|
BEA-040061(retired)
|
Alert: JMSServer "server". Store failure occurred while preparing a transaction t.
|
Description
| Transaction will be rolled back.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040062(retired)
|
Alert: JMSServer "server" store failure occurred while preparing a receive transaction t.
|
Description
| Transaction will be rolled back.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040063(retired)
|
Alert: JMSServer "server" store failure occurred while committing a receive transaction t.
|
Description
| A delete request to the JMS store failed. Transaction may or may not rollback.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040064(retired)
|
Alert: JMSServer "server" store failure occurred while rolling back a receive transaction, t.
|
Description
| A request to the JMS store failed. The transaction will still roll back.
|
|
Cause
| Disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040065(retired)
|
Alert: JMSServer "server" store failure occurred while preparing a send transaction t.
|
Description
| The transaction will be rolled back and the send will not occur.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040066(retired)
|
Alert: JMSServer "server", store failure occurred while committing a send transaction t
|
Description
| A change request to the JMS store failed. Transaction may or may not rollback.
|
|
Cause
| Disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040067(retired)
|
Info: JMSServer "arg0" exception occurred while closing subscriber arg1 with exception arg2 at JMS startup time.
|
Description
| JMSServer "arg0" exception occurred while closing subscriber arg1 with exception arg2 at JMS startup time.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040068
|
Error: JMSServer "serverName" error occurred while unregistering destination backend.
|
Description
| An error occurred while unregistering a destination.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040069
|
Error: JMSServer "serverName" error occurred while unregistering producer backend.
|
Description
| An error occurred while unregistering a producer.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040070
|
Error: JMSServer "serverName" error occurred while unregistering connection frontend.
|
Description
| An error occurred while unregistering a connection.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040071
|
Error: JMSServer "serverName" error occurred while unregistering session session.
|
Description
| An error occurred while unregistering a session.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040072
|
Error: JMSServer "serverName" error occurred while unregistering consumer consumer.
|
Description
| An error occurred while unregistering a consumer.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040073(retired)
|
Error: JMSServer "serverName", error creating JMS session with connection: connection - mbeanName: mbeanName - sessionID: sessionId - transacted: transacted - acknowledgeMode: acknowledgeMode
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040074(retired)
|
Error: JMSServer "serverName", error creating JMS consumer for session: session - mbeanName: mbeanName - clientId: clientId - name: name - destination: destination - selector: selector - noLocal: noLocal
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040075(retired)
|
Error: JMSServer "serverName", error creating JMS producer for session: session - mbeanName: mbeanName - producerId: producerId - destination: destination
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040077(retired)
|
Alert: JMSServer "server" store close failed t.
|
Description
| A request to close the JMS store failed.
|
|
Cause
| Disk failure, or database failure.
|
|
Action
| Ensure that no attempts are made to re-open the store until no server is using it.
|
|
|
BEA-040078(retired)
|
Alert: JMSServer "serverName". Partial JMS migration was found in JDBC store: poolName. The records previously migrated from an old release are to be removed and another migration is starting.
|
Description
| A migration of an old JMS persistent store has been started previously and did not complete. The records left from the previous will be removed, and a new migration will start.
|
|
Cause
| Disk failure, Database failure, or human interruption (Ctrl-c)
|
|
Action
| No action is required.
|
|
|
BEA-040079(retired)
|
Error: JMSServer "serverName". Migration of a pre-6.0 JDBC store (poolName) failed with an exception:t.
|
Description
| A migration of an old JMS JDBC store has been started, but failed for some reason. Check previous log messages for details.
|
|
Cause
| Inadequate configuration or database failure. Missing or incorrect JAR file, incorrect CLASSPATH, non-empty new store was detected.
|
|
Action
| Fix the CLASSPATH or the configuration and re-try the operation.
|
|
|
BEA-040080(retired)
|
Error: JMSServer "serverName". Migration of an old JMS persistent store failed due to incorrect JAR file (version versionNumber).
|
Description
| A migration of an old JMS persistent store failed because the JAR file for the given version is incorrect or the CLASSPATH is not set correctly.
|
|
Cause
| The CLASSPATH is not set correctly, so the migration software was not able to find the JAR file associated with the old store.
|
|
Action
| Check the CLASSPATH to see that it includes the migration jar file.
|
|
|
BEA-040082(retired)
|
Error: JMSServer "serverName". JMS JDBC I/O failure (t) occurred during migration of an old JMS persistent store:poolName.
|
Description
| An error occurred while migrating a persistent store from an older release to the current release.
|
|
Cause
| Database failure occurred.
|
|
Action
| Re-start the server. Contact your DBA if the problem persists.
|
|
|
BEA-040083(retired)
|
Info: JMSServer "serverName", count JMS messages were successfully migrated from an old store into store: poolName.
|
Description
| All messages from a JMS store for an older release were migrated to the current release.
|
|
Cause
| When starting JMS and a persistent store exists for an older release, the messages are automatically migrated to the current release.
|
|
Action
| No action is required.
|
|
|
BEA-040084(retired)
|
Error: JMSServer "serverName" failed to migrate JMS durable subscribers in store: poolName for topic:topicName.
|
Description
| There are JMS durable subscribers in the old store, but the topic is not configured in the new store. As a result, migration failed.
|
|
Cause
| The configuration is incomplete. It is missing the definition of a topic.
|
|
Action
| Add the topic in the configuration file, and re-start the server.
|
|
|
BEA-040085(retired)
|
Error: JMSServer "serverName" failed to migrate JMS messages in store: poolName for queue:queueName.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040086(retired)
|
Info: JMSServer "serverName", count JMS message references were successfully migrated from an old store into store: poolName.
|
Description
| JMS messages references were successfully migrated from an old JMS store into the current store.
|
|
Cause
| Message migration happens automatically when starting JMS and an old store exists.
|
|
Action
| No action is required.
|
|
|
BEA-040087(retired)
|
Info: JMSServer "serverName" cannot migrate old JMS messages and durable subscribers into a non-empty store:poolName.
|
Description
| A failure occurred during migration because the store already has some partially migrated durable subscribers and/or messages.
|
|
Cause
| Message migration happens automatically when starting JMS and an old store exists. In this case, the migration probably occurred partially and failed.
|
|
Action
| Clean up the store and re-start the server.
|
|
|
BEA-040088(retired)
|
Error: JMSServer "serverName". JMS failed to find or instantiate weblogic.jms.server.upgrade.UpgradeHelperImpl in JAR file:jarFile. The actual exception is e.
|
Description
| When migrating old JMS messages from earlier releases, failed to find the JAR file jarFile in the CLASSPATH, or failed to find or instantiate class weblogic.jms.server.upgrade.UpgradeHelperImpl in the JAR file. For actual error, see exception e.
|
|
Cause
| The JAR file does not exist in the CLASSPATH, is placed in the wrong directory, or does not contain the required classes.
|
|
Action
| Put the correct JAR file in the CLASSPATH, and make sure it contains weblogic.jms.server.upgrade.UpgradeHelperImpl. Contact BEA customer support if the problem persists.
|
|
|
BEA-040089
|
Info: JMSServer "serverName". JMS messages in store (poolName) were migrated from version versionNumber to 600.
|
Description
| Message migration was successful.
|
|
Cause
| Message migration happens automatically when starting JMS and an old store exists.
|
|
Action
| No action required.
|
|
|
BEA-040090
|
Info: Deployed arg0.
|
Description
| arg0 default connection factories were deployed on this WebLogic Server.
|
|
Cause
| This message indicates the number of default connection factories deployed while processing the configuration file.
|
|
Action
| No action required.
|
|
|
BEA-040091(retired)
|
Alert: JMSServer "arg0". An error occurred while testing to see if the current operation was transactional, arg1. The current operation is aborted.
|
Description
| An error occurred while testing to see if the current operation was transactional.
|
|
Cause
| Look for earlier messages that might explain the error.
|
|
Action
| Call customer support.
|
|
|
BEA-040092(retired)
|
Info: JMSServer "serverName". An old store (poolName) of version versionNumber was detected, but has previously been successfully migrated.
|
Description
| During migration, an old store was detected in addition to a new store.
|
|
Cause
| A JMS store migration occurred but did not complete.
|
|
Action
| If you do not want to see this message any longer, make sure that you do not need any data in the old database tables and remove the old tables from the database.
|
|
|
BEA-040093(retired)
|
Alert: JMSServer "serverName". The reply destination (replyToDestName) of messages was not found in the same JMS server during the migration of a pre-6.0 store (poolName).
|
Description
| During the migration of messages in a pre-6.0 JMS store, the reply destination given by getJMSReplyTo() was not found in the same JMS server. The JMSReplyTo field of the message will be set to null after migration.
|
|
Cause
| The destination used for reply is missing in the new configuration file, is configured on a different server, or is a foreign destination.
|
|
Action
| Modify the configuration and restart the server file.
|
|
|
BEA-040094(retired)
|
Error: JMSServer "serverName". Migration of a pre-6.0 JDBC store (poolName) failed with exception:t.
|
Description
| Migration of an old JDBC store failed. Check previous log messages for details.
|
|
Cause
| Inadequate configuration. Missing or incorrect JAR file from the CLASSPATH. Non-empty new store was detected.
|
|
Action
| Check previous log messages for details and act accordingly.
|
|
|
BEA-040095
|
Alert: JMSServer "server". Store I/O failure, t.
|
Description
| If the associated message(s) were involved in a transaction, the transaction is usually rolled back.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040096(retired)
|
Alert: JMSServer "server". JMS store file=fileName path=pathName had an unexpected length of origLength bytes. The file will be truncated to finalLength bytes and the remaining bytes will be discarded.
|
Description
| This message occurs if a JMS store file length is detected to be incorrect during startup. This might occur due to disk corruption or an abnormal server shutdown.
|
|
Cause
| Out of file space, disk corruption, abnormal shutdown.
|
|
Action
| Check for disk corruption or out of file space.
|
|
|
BEA-040097(retired)
|
Info: JMSServer "serverName". Store (poolName) migration is done and the old tables can be removed (see drop_serverName_oldtables.ddl).
|
Description
| Migration of the store has successfully completed. The old tables can be removed by running Utils.Schema on the given DDL file.
|
|
Cause
| A successful store migration occurred, but the tables have not yet been removed.
|
|
Action
| Run the Utils.Schema utility on the DDL file in the current directory to remove the old database tables.
|
|
|
BEA-040098(retired)
|
Error: JMSServer "serverName". A partial migration of store (poolName) was found, but the old tables were missing during re-try.
|
Description
| Migration of the store has been attempted but failed. However, the old tables were missing when another migration was attempted.
|
|
Cause
| A JMS store migration failed, since one or more tables were missing.
|
|
Action
| Restore the old tables from the backup and start the server.
|
|
|
BEA-040099(retired)
|
Alert: JMSServer "serverName". The old tables were found in the database (poolName), but migration was skipped since it is disabled in the configuration.
|
Description
| For internal use only.
|
|
Cause
| When starting a JMS server, old JMS store tables were found but were not migrated because the configuration indicated the store migration should not be performed.
|
|
Action
| No action required.
|
|
|
BEA-040100(retired)
|
Alert: JMSServer "serverName". Topic: name in the old properties file is not configured in the new configuration (store poolName).
|
Description
| The JMS store upgrade found an old topic that is not configured in the new configuration. However, this destination was empty, so no messages needed migration.
|
|
Cause
| During store migration from an older release, a topic was found that is not configured in the new configuration. In this case, there are no related messages, so no data will be lost.
|
|
Action
| Check to see if the topic should be added to the configuration. Since not messages will be lost, no further action is required.
|
|
|
BEA-040101(retired)
|
Alert: JMSServer "serverName". Queue: name in the old properties file is not configured in the new configuration (store poolName).
|
Description
| The JMS store upgrade found an old queue that is not configured in the new configuration. However, this destination was empty, so no messages needed migration.
|
|
Cause
| During store migration from an older release, a queue was found that is not configured in the new configuration. In this case, there are no related messages. Therefore, no data will be lost.
|
|
Action
| Check to see if the queue should be added to the configuration. Since no messages will be lost, no further action is required.
|
|
|
BEA-040102(retired)
|
Alert: JMSServer "serverName". Topic: name in the old properties file is configured as a queue in the new configuration (store poolName).
|
Description
| The JMS store upgrade found an old topic that is configured as a queue in the new configuration. However, this destination was empty, so no messages needed migration.
|
|
Cause
| The JMS store upgrade found an old topic that is configured as a queue in the new configuration. However this destination was empty, so no messages needed migration.
|
|
Action
| Check the configuration to ensure that the specified destination should be a queue in the new configuration.
|
|
|
BEA-040103(retired)
|
Alert: JMSServer "serverName". Queue: name in the old properties file is configured as a topic in the new configuration (store poolName).
|
Description
| The JMS store upgrade found an old queue that is configured as a topic in the new configuration. However, this destination was empty, so no messages needed migration.
|
|
Cause
| The JMS store upgrade found an old queue that is configured as a topic in the new configuration. However, this destination was empty, so no messages needed migration.
|
|
Action
| Check the configuration to ensure that the specified destination should be a topic in the new configuration.
|
|
|
BEA-040104(retired)
|
Info: JMSServer "serverName", count for Topic: name in store poolName not migrated.
|
Description
| JMS store upgrade did not migrate some of the durable subscribers due to configuration changes.
|
|
Cause
| Configuration change.
|
|
Action
| No action required.
|
|
|
BEA-040105(retired)
|
Info: JMSServer "serverName", count for topic: name in store poolName not migrated.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040106(retired)
|
Info: JMSServer "serverName", count for queue: name in store poolName not migrated.
|
Description
| JMS store upgrade did not migrate some of the messages in a queue due to configuration changes.
|
|
Cause
| Configuration change.
|
|
Action
| No action required.
|
|
|
BEA-040107
|
Info: Undeployed arg0.
|
Description
| arg0 default connection factories were undeployed on this WebLogic Server.
|
|
Cause
| This message indicates the number of default connection factories that were undeployed.
|
|
Action
| No action required.
|
|
|
BEA-040108
|
Info: User connection factory "arg0" is started.
|
Description
| The specified user connection factory has been started.
|
|
Cause
| The specified user connection factory has been started.
|
|
Action
| No action required.
|
|
|
BEA-040109
|
Info: JMSServer "arg0" is started.
|
Description
| The specified JMS Server has been started.
|
|
Cause
| The specified JMS Server has been started.
|
|
Action
| No action required.
|
|
|
BEA-040110(retired)
|
Alert: JMSServer "server". Store name storeName, directory dir. A JMS store version field contained a version higher than expected. It is likely an older version of JMS attempted to read messages that were written using a newer version of JMS.
|
Description
| A JMS store version field contained a version higher than expected. It is likely an older version of JMS attempted to read messages that were written using a newer version of JMS.
|
|
Cause
| JMSServer "server". Store name storeName, directory dir. A JMS store version field contained a version higher than expected.
|
|
Action
| Use a newer version of WLS JMS to read the store.
|
|
|
BEA-040111(retired)
|
Alert: JMSServer "server". Store name storeName, directory dirName. Corruption detected in file fileName at byte position bytePos. The corresponding file block will be zeroed out on disk, and this corruption will no longer be reported in the future. t
|
Description
| A corruption was detected in file fileName at byte position bytePos. The corresponding file block will be zeroed out on disk, and this corruption will no longer be reported in the future. t
|
|
Cause
| A corrupted JMS file store was detected.
|
|
Action
| Ensure hard-drive is not failing. Also ensure only one open JMS store has access to the file. Ensure no other process is writing to the file. Note that corrupted blocks are zeroed out and re-used by the JMS store after this log message is printed.
|
|
|
BEA-040112(retired)
|
Alert: JMSServer "server". Store name storeName, store directory dirName. File not found fileName.
|
Description
| For JMSServer "server". Store name storeName, store directory dirName. File not found fileName.
|
|
Cause
| The JMS file store could not find a required file.
|
|
Action
| Replace the missing file, or delete all of the store files.
|
|
|
BEA-040113
|
Info: JMSServer "server", Opening file store "storeName" in directory "dirName". Starting scan of numFiles totaling numBytes bytes.
|
Description
| A JMS server has opened its persistent file store and is about to scan its contents for messages.
|
|
Cause
| A JMS server has opened its persistent file store and is about to scan its contents for messages.
|
|
Action
| No action required.
|
|
|
BEA-040114(retired)
|
Info: JMSServer "server", Finished scan of file store "storeName" in directory "dirName". Found numRecords totaling numBytes bytes.
|
Description
| A JMS server has finished scanning its persistent file store for messages. It will proceed to associate these messages with their corresponding destinations. Note that the reported number of records and bytes may change between boots even without any JMS client activity. This is because messages may expire, and destinations may have been added or removed. Note that the total record size may be less than the total file size.
|
|
Cause
| A JMS server has finished scanning its persistent file store for messages. It will proceed to associate these messages with their corresponding destinations. Note that the reported number of records and bytes may change between boots even without any JMS client activity. This is because messages may expire, and destinations may have been added or removed. Note that the total record size may be less than the total file size.
|
|
Action
| No action required.
|
|
|
BEA-040115(retired)
|
Info: JMSServer "server". Migrating JDBC store (connection pool "poolName") from version versionNumber to 600.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040116(retired)
|
Error: JMSServer "server". Failed to delete existing DDL file (fileName).
|
Description
| After migrating a pre-6.0 JDBC store into a 6.0 store, a DDL file is created for an administrator to remove old database tables. This message indicates that there is a DDL file created by an earlier migration, which cannot be deleted for some reason.
|
|
Cause
| Inadequate permissions. This rarely happens.
|
|
Action
| Check the working directory and remove the file manually, and re-start the server. This will start another attempt of migrating the pre-6.0 store.
|
|
|
BEA-040117(retired)
|
Info: JMSServer "server". Opening JDBC store tables "storeTableName" and "stateTableName" using connection pool "poolName".
|
Description
| A JMS server has opened its persistent JDBC store and is about to scan its contents for messages.
|
|
Cause
| A JMS server has opened its persistent JDBC store and is about to scan its contents for messages.
|
|
Action
| No action required.
|
|
|
BEA-040118(retired)
|
Info: JMSServer "server". Finished scan of JDBC store. Found count.
|
Description
| A JMS server has finished scanning its persistent JDBC store for messages. It will proceed to associate these messages with their corresponding destinations. Note that the reported number of records may change between boots even without any JMS client activity. This is because messages may expire, and destinations may have been added or removed.
|
|
Cause
| A JMS server has finished scanning its persistent JDBC store for messages. It will proceed to associate these messages with their corresponding destinations. Note that the reported number of records may change between boots even without any JMS client activity. This is because messages may expire, and destinations may have been added or removed.
|
|
Action
| No action required.
|
|
|
BEA-040119
|
Error: Failed to deploy a JMS connection factory "name" due to e.
|
Description
| Failed to deploy a JMS connection factory due to an exception.
|
|
Cause
| This message indicates that the JMS connection factory failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new connection factory.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040120
|
Error: Failed to bind JMS connection factory "name" with its JNDI name due to e.
|
Description
| Failed to bind a connection factory due to an exception.
|
|
Cause
| JNDI failure.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040121
|
Error: JMSServer "name". Cannot be deployed on multiple servers.
|
Description
| A JMS server was deployed on more than one WebLogic Server.
|
|
Cause
| A JMS Server was deployed on more than one WebLogic Server, and this is not allowed.
|
|
Action
| Change the configuration file and reboot the system.
|
|
|
BEA-040122
|
Error: Failed to deploy JMS Server "name" due to t.
|
Description
| Failed to deploy a JMS server due to an exception.
|
|
Cause
| This message indicates that the JMS server failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040123
|
Error: Failed to start JMS Server "name" due to t.
|
Description
| Failed to start a JMSServer due to an Exception.
|
|
Cause
| JNDI failure or failure in starting destinations, server session pools and/or connection consumers.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040124
|
Error: JMSServer "serverName". Failed to create JMS server session pool "name" due to e.
|
Description
| Failed to create a JMS server session pool due to an exception.
|
|
Cause
| This message indicates that the JMS server session pool failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS server session pool.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040125
|
Error: JMSServer "serverName". Failed to create JMS connection consumer "name" due to e.
|
Description
| Failed to create a JMS connection consumer due to an exception.
|
|
Cause
| This message indicates that the JMS connection consumer failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS connection consumer.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040126(retired)
|
Error: JMSServer "serverName". Failed to create JMS destination "name" due to e.
|
Description
| Failed to create a JMS destination due to an exception.
|
|
Cause
| This message indicates that the JMS destination failed to initialize. Usually this is a configuration error. This may also happen when the server is shutting down but JMS still attempts to create a new JMS destination.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040127
|
Error: Failed to create JMS multicast socket due to e.
|
Description
| Failed to create a JMS multicast socket due to an exception.
|
|
Cause
| This message indicates that the JMS multicast socket failed to initialize.
|
|
Action
| Reboot the system.
|
|
|
BEA-040128(retired)
|
Error: JMSServer "serverName". Failed to create JMS server session pool due to e.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040129(retired)
|
Info: JMSServer "arg0". Multiple threads are updating JMS consumer "arg1" info.
|
Description
| There is more than one thread setting JMS consumer information. The consumer name will be null if it is not a durable subscriber.
|
|
Cause
| There is more than one thread setting JMS consumer information. The consumer name will be null if it is not a durable subscriber.
|
|
Action
| No action required.
|
|
|
BEA-040130(retired)
|
Alert: JMSServer "server", file store "storeName". The JMS file store directory "dirName" was not found relative to the server root directory "rootDir" but was found relative to the working directory "workDir". The directory "finalDir" will be used. To make this message go away, please change your JMS file store configuration to use an absolute path or a path relative to the server root directory; and if the new directory is different from the old directory, be sure to move any JMS store files to the new directory.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040131(retired)
|
Alert: JMSServer "server", file store "storeName". The JMS file store directory "dirName" was found in two places. First - relative to the server root directory "rootDir" but with no data files and second - relative to the working directory "workDir" with data files. The directory "finalDir" will be used.
|
Description
| JMSServer "server", file store "storeName". The JMS file store directory "dirName" was found in two places. First - relative to the server root directory "rootDir" but with no data files and second - relative to the working directory "workDir" with data files. The directory "finalDir" will be used. To make this message go away, please change your JMS file store configuration to use an absolute path or a path relative to the server root directory; and if the new directory is different from the old directory, be sure to move any JMS store files to the new directory.
|
|
Cause
| The JMS file store was changed in WLS 6.0 service pack 1 to use the WebLogic Server root directory rather than the working directory as its base path.
|
|
Action
| Ensure that the correct directory is being used for the file store.
|
|
|
BEA-040132(retired)
|
Warning: JMSServer "server". Synchronous writes disabled for file store "storeName" in directory "dirName".
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040201(retired)
|
Error: JMSServer "serverName". Error unregistering Durable Subscriber: ClientId "clientId", subscriber name "subscriberName", topic "TopicName".
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040202(retired)
|
Error: JMSServer "serverName". Error occurred while creating Durable Subscriber: ClientId "clientId", subscriber name "subscriberName", topic "TopicName".
|
Description
| An error occurred while creating a durable subscriber on JMSServer "serverName", ClientId "clientId", subscriber name "subscriberName", topic "TopicName".
|
|
Cause
| Check the log for earlier messages indicating the nature of the error. This is sometimes due to the fact that a durable subscription requires that the JMS server have a persistent store configured. The existence of a durable subscription must be persisted even if the subscription consumes only non-persistent messages so that the durable subscription may be recreated after shutdown and restart.
|
|
Action
| Correct the error indicated in the error messages.
|
|
|
BEA-040203(retired)
|
Error: JMSServer "serverName". A message originating on destination "sourceDestination" reached its redelivery limit and an error occurred while moving it to error destination "targetDestination". If the message is non-persistent, it is permanently destroyed. If the message is persistent, the message is dropped but will remain in the JMS store. It will be restored to its originating destination the next time the JMS Server is shutdown and restarted. This log message will only get reported once per five minutes per error destination. It is not necessarily printed for every originating destination. This error has occurred a total of totalFailures for this error destination.
|
Description
| This message is deprecated. It can not occur in post 7.0 WebLogic Server releases.
|
|
Cause
| This error may occur due to a quota failure on the error destination or less commonly due either to a failure in the transaction subsystem or in the JMS store.
|
|
Action
| Increase quotas on the error destination and/or ensure that there is an active application that is draining the error destination.
|
|
|
BEA-040204(retired)
|
Alert: JMSServer "serverName". An error occurred while trying to do a SQL SELECT on table "tableName". This error occurs during automated migration from an earlier version of WLS JMS. Check privileges on this table. You may need to specify [schema.[catalog.]] in your configured prefix.
|
Description
| The metadata for the database indicates that the table exists but an error occurred while doing a SQL SELECT on the table. This usually indicates that the necessary privileges have not been granted to the user.
|
|
Cause
| Insufficient privileges have been granted to the user.
|
|
Action
| Grant the necessary privileges for the JMS tables and restart the server.
|
|
|
BEA-040205(retired)
|
Alert: JMSServer "serverName". An error occurred while trying to do a SQL SELECT on table "tableName". Check privileges on this table. You may need to specify [schema.[catalog.]] in your configured prefix.
|
Description
| The metadata for the database indicates that the table exists but an error occurred while doing a SQL SELECT on the table. This usually indicates that the necessary privileges have not been granted to the user.
|
|
Cause
| Insufficient privileges have been granted to the user.
|
|
Action
| Grant the necessary privileges for the JMS tables and restart the server.
|
|
|
BEA-040206(retired)
|
Error: JMSServer "serverName". Error occurred while parsing Durable Subscriber: Name "name", Topic "TopicName"
|
Description
| This message will only occur during boot.
|
|
Cause
| Unknown.
|
|
Action
| Contact customer support.
|
|
|
BEA-040207(retired)
|
Info: JMSServer "serverName". Migration JMS messages in store: poolName for queue: queueName not found.
|
Description
| There are JMS messages in the old store for queue queueName, but the queue is not configured in the new store or the queue was a temporary queue.
|
|
Cause
| Incomplete configuration or old message in temporary queue.
|
|
Action
| No action required.
|
|
|
BEA-040208(retired)
|
Alert: JMSServer "serverName". Cannot enable "pagingType" because there is no PagingStore configured. pagingType is not turned on.
|
Description
| This message indicates that the PagingStore attribute is not set while either MessagesPagingEnabled or BytesPagingEnabled is set to true. Therefore, the MessagesPaging/BytesPaging is forced to be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040209(retired)
|
Alert: JMSServer "serverName". Cannot enable "MessagesPaging" because either MessagesThresholdHigh or MessagesThresholdLow is not set.
|
Description
| This message indicates that the MessagesThresholdHigh/MessagesThresholdLow attribute is not set for the JMSSever while its MessagesPagingEnabled is set to true. Therefore, MessagesPaging is forced to be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040210(retired)
|
Alert: JMSServer "serverName". Cannot enable "BytesPaging" because either BytesThresholdHigh or BytesThresholdLow is not set.
|
Description
| This message indicates that the BytesThresholdHigh/BytesThresholdLow attribute is not set for the JMSSever while its BytesPagingEnabled is set to true. Therefore, BytesPaging will be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040211(retired)
|
Alert: JMS Server "serverName". Cannot enable "pagingType" for destination "destName" because no PagingStore is configured. destName is not turned on for the destination.
|
Description
| This message indicates that the JMS Server PagingStore attribute is not set while either MessagesPagingEnabled or BytesPagingEnabled is set to true for one of the destinations configured in the JMSServer. Therefore, MessagesPaging/BytesPaging will be turned off for the destination.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040212(retired)
|
Alert: JMS server "serverName". Cannot enable "MessagesPaging" for destination "destName" because either MessagesThresholdHigh or MessagesThresholdLow is not set.
|
Description
| This message indicates that the MessagesThresholdHigh/MessagesThresholdLow attribute is not set for the destination while its MessagesPagingEnabled is set to true. Therefore, MessagesPaging will be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040213(retired)
|
Alert: JMS server "serverName". Cannot enable "BytesPaging" for destination "destName" because either BytesThresholdHigh or BytesThresholdLow is not set.
|
Description
| This message indicates that the BytesThresholdHigh/BytesThresholdLow attribute is not set for the destination while its BytesPagingEnabled is set to true. Therefore, BytesPaging will be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040214(retired)
|
Alert: JMS server "serverName". Store failure while paging out message for queue destName, e.
|
Description
| This message indicates that there was an IO failure while paging out a message. As a result, the message was not paged out.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040215
|
Error: JMS server "serverName". Cannot set "attribute" to -1 when paging is enabled. The value of the attribute remains unchanged.
|
Description
| This message indicates that the dynamic change of a threshold value failed due to an inconsistent configuration.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Disable paging before setting this value to -1.
|
|
|
BEA-040216(retired)
|
Error: JMS server "serverName". Cannot set "attribute" to -1 for destination "destName" when paging is enabled. The value of the attribute remains unchanged.
|
Description
| This message indicates that the dynamic change of a threshold value failed due to inconsistent configuration.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Disable paging before setting this value to -1.
|
|
|
BEA-040217(retired)
|
Error: Paging store failure occurred while paging in message e.
|
Description
| This message indicates that there was an IO failure while paging in a message. As a result, the message was not paged in.
|
|
Cause
| Out of file space, disk failure, or database failure.
|
|
Action
| Restart the database, if applicable, and restart JMS.
|
|
|
BEA-040218(retired)
|
Alert: Cannot enable "MessagesPaging" for template "templateName" because either MessagesThresholdHigh or MessagesThresholdLow is not set.
|
Description
| This message indicates that the MessagesThresholdHigh/MessagesThresholdLow attribute is not set for the template while its MessagesPagingEnabled is set to true. Therefore, MessagesPaging is forced to be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040219(retired)
|
Alert: Cannot enable "BytesPaging" for template "templateName" because either BytesThresholdHigh or BytesThresholdLow is not set.
|
Description
| This message indicates that the BytesThresholdHigh/BytesThresholdLow attribute is not set for the template while its BytesPagingEnabled is set to true. Therefore, BytesPaging will be turned off.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040220(retired)
|
Error: Template "templateName". Cannot set "attribute" to -1 when paging is enabled. The value of the attribute remains unchanged.
|
Description
| This message indicates that the dynamic change of a threshold value failed due to inconsistent configuration.
|
|
Cause
| This is caused by an invalid configuration.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040221(retired)
|
Alert: MIGRATION: Found message [messageID] in WLS 5.1 that had a priority of [priority]. Resetting this priority to [9].
|
Description
| This message indicates that a JMS 5.1 message was detected in the migration process that has a priority beyond the legal bounds. The migration will reset the priority to the highest legal value of 9.
|
|
Cause
| A bug exists in JMS 5.1 that allows messages to be stored with a priority greater than 9.
|
|
Action
| No action required.
|
|
|
BEA-040301(retired)
|
Info: JMS service is suspended and in standby mode.
|
Description
| This message indicates that the JMS service has been suspended and it is now in standby mode.
|
|
Cause
| The JMS service has been suspended and it is now in standby mode.
|
|
Action
| No action required.
|
|
|
BEA-040302(retired)
|
Error: JMS service failed to start or resume. Exception e.
|
Description
| This message indicates that the JMS service failed to start or resume from the suspended state.
|
|
Cause
| Possibly JNDI errors, management infrastructure errors, and other internal errors.
|
|
Action
| Shutdown and restart the server. Contact BEA support if problem persists.
|
|
|
BEA-040303(retired)
|
Error: JMS service failed to add a new distributed queue/topic "name" because JMS service is shutdown.
|
Description
| This message indicates that an attempt to add a distributed queue or distributed topic has failed because JMS service is shutdown or is shutting down.
|
|
Cause
| An attempt to add a distributed queue or distributed topic has failed because JMS service is shutdown or is shutting down.
|
|
Action
| No action required. You need to restart the server before adding the distributed destination.
|
|
|
BEA-040304(retired)
|
Error: Failed to add a member to a distributed queue or distributed topic (member "memberName" has already been a member of another distributed queue or distributed topic).
|
Description
| This message indicates that there are at least two distributed destinations that have membership conflicts. One physical queue/topic can only be a member of one distributed destination.
|
|
Cause
| Invalid configuration.
|
|
Action
| Correct the configuration and restart the server.
|
|
|
BEA-040305
|
Info: JMS service is initialized and in standby mode.
|
Description
| This message indicates that the initialization phase of the JMS service is completed and the JMS service is in standby mode.
|
|
Cause
| The initialization phase of JMS service is completed and the JMS service is in standby mode.
|
|
Action
| No action required.
|
|
|
BEA-040306
|
Info: JMS service is active now.
|
Description
| This message indicates that the activation phase of the JMS service is completed, and the JMS service is in active mode.
|
|
Cause
| The activation phase of the JMS service is completed, and the JMS service is in active mode.
|
|
Action
| No action required.
|
|
|
BEA-040307
|
Info: JMS service is suspending gracefully.
|
Description
| This message indicates that the JMS service has started the suspension phase. No new work will be accepted and the JMS service will attempt to complete all existing work before it brings itself to the standby mode.
|
|
Cause
| The JMS service has started the suspension phase. No new work will be accepted and JMS Service will attempt to complete all existing work before it brings itself to standby mode.
|
|
Action
| No action required.
|
|
|
BEA-040308
|
Info: JMS service is suspending.
|
Description
| This message indicates that the JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.
|
|
Cause
| The JMS service has started the suspension phase. No new work will be accepted and all the existing work will be terminated immediately before the JMS service brings itself to standby mode.
|
|
Action
| No action required.
|
|
|
BEA-040309(retired)
|
Info: JMS server "name" is activated.
|
Description
| This message indicates that the JMS server has been activated from standby mode.
|
|
Cause
| The JMS server has been activated from standby mode.
|
|
Action
| No action required.
|
|
|
BEA-040310(retired)
|
Info: JMS Server "name" is deactivated for migration.
|
Description
| This message indicates that the JMS server has been deactivated and is in standby mode now.
|
|
Cause
| The JMS server has been deactivated and is in standby mode now.
|
|
Action
| No action required.
|
|
|
BEA-040311(retired)
|
Info: JMS server "name" is deployed as a migratable on "targetName".
|
Description
| This message indicates that the JMS server is configured and deployed as a migratable server.
|
|
Cause
| The JMS server is configured and deployed as a migratable server.
|
|
Action
| No action required.
|
|
|
BEA-040312(retired)
|
Info: An error occurred in suspending the JMS service. The first Throwable is "t".
|
Description
| This message indicates that errors were encountered when suspending the JMS service. The JMS service is in the suspended state even when this message occurs.
|
|
Cause
| Errors were encountered when suspending the JMS service. Check the log for prior error messages.
|
|
Action
| No action required.
|
|
|
BEA-040313(retired)
|
Error: Failed to add a new distributed destination (name="name"). Instance exists already.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040314(retired)
|
Error: Failed to add a new distributed destination (name="name") . Has to be deployed to a cluster.
|
Description
| This message is no longer used.
|
|
Cause
| This message is no longer used.
|
|
Action
| This message is no longer used.
|
|
|
BEA-040315(retired)
|
Info: JMS server "serverName". JMS messages in store (poolName) were migrated from version versionNumber to versionNumber2.
|
Cause
| Informational message.
|
|
Action
| No action required.
|
|
|
BEA-040316(retired)
|
Info: JMS server "server". Migrating JDBC store (connection pool "poolName") from version versionNumber to versionNumber2.
|
Description
| JMS server "server". Migrating JDBC store (connection pool "poolName") from version versionNumber to versionNumber2.
|
|
Cause
| A newer version of WebLogic Server JMS is being started and messages associated with an earlier version are being converted.
|
|
Action
| No action required.
|
|
|
BEA-040317(retired)
|
Error: Distributed Destination "name". All members must exist and be in the same module. The problematic member is "memberName".
|
Description
| This message indicates that the members of a JMS distributed queue or distributed topic are not valid. Either a member does not have a JMS queue or a topic associated with it, or the members are in different clusters.
|
|
Cause
| Configuration error.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040318(retired)
|
Info: Distributed Destination "name". Member "memberName" already exist.
|
Description
| This message indicates that one of the members of a JMS distributed queue or distributed topic is already a member of the distributed destination.
|
|
Cause
| Configuration error.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040319(retired)
|
Error: Could not page-in messages for a system subscription.
|
Description
| While attempting to forward messages to a system subscriber on behalf of a distributed queue or topic, the system encountered an error. It could not page the messages back into memory from disk. Messages may have been lost.
|
|
Cause
| The server may be low on memory or the disk record may be corrupted.
|
|
Action
| Shut the server down.
|
|
|
BEA-040320(retired)
|
Alert: JMS server "serverName". An error occurred while trying to do a SQL UPDATE on table "tableName". Check privileges on this table. You may need to specify [schema.[catalog.]] in your configured prefix.
|
Description
| The metadata for the database indicates that the table exists, but an error occurred while doing a SQL SELECT on the table. This usually indicates that the necessary privileges have not been granted to the user.
|
|
Cause
| Insufficient privileges have been granted to the user.
|
|
Action
| Grant the necessary privileges for the JMS tables and restart the server.
|
|
|
BEA-040321
|
Info: JMSServer "arg0" is resuming.
|
Description
| JMSServer "arg0" is resuming.
|
|
Cause
| The JMSServer "arg0" is resuming.
|
|
Action
| No action required.
|
|
|
BEA-040322(retired)
|
Info: JMSServer "arg0" is activating for migration.
|
Description
| JMSServer "arg0" is activating for migration.
|
|
Cause
| The JMSServer "arg0" is activating for migration.
|
|
Action
| No action required.
|
|
|
BEA-040323(retired)
|
Info: JMSServer "arg0" is deactivating for migration.
|
Description
| JMSServer "arg0" is deactivating for migration.
|
|
Cause
| The JMSServer "arg0" is deactivating for migration.
|
|
Action
| No action required.
|
|
|
BEA-040324
|
Info: JMSServer "arg0" is suspending.
|
Description
| JMSServer "arg0" is suspending.
|
|
Cause
| The JMSServer "arg0" is suspending.
|
|
Action
| No action required.
|
|
|
BEA-040325
|
Info: JMSServer "arg0" is suspended.
|
Description
| JMSServer "arg0" is suspended.
|
|
Cause
| The JMSServer "arg0" is suspended.
|
|
Action
| No action required.
|
|
|
BEA-040326(retired)
|
Error: JMS Distributed Destination "dist" member "member" failed to create consumer resources due to t.
|
Description
| Failed to initialize a Distributed Destination member due to an exception. Internal consumers are used internally between destination members.
|
|
Cause
| JNDI failure or failure in starting destinations, errors creating or removing durable system subscribers.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040327(retired)
|
Error: JMS Distributed Destination member "localMember" was unable to connect to the remote member "remoteMember" in "distDest" due to exception t.
|
Description
| Failed to setup connection between JMS Distributed Destination members due to an exception. Internal consumers are used internally between destination members.
|
|
Cause
| JNDI failure occurred or failure occurred while starting destinations, creating errors, or removing durable system subscribers.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040351
|
Info: ExpiredJMSMessage JMSMessageID=msgid >\n Header\n Property\n
|
Description
| A message has been expired and the policy is to log the message header fields and messages properties so they are printed.
|
|
Cause
| A message has been expired and the policy is to log the message header fields and messages properties so they are printed.
|
|
Action
| No action required.
|
|
|
BEA-040352
|
Info: ExpiredJMSMessage JMSMessageID=msgid >\n Header\n
|
Description
| A message has been expired and the policy is to log the message header fields so they are printed.
|
|
Cause
| A message has been expired and the policy is to log the message header fields so they are printed.
|
|
Action
| No action required.
|
|
|
BEA-040353
|
Info: ExpiredJMSMessage JMSMessageID=msgid >\n Property\n
|
Description
| A message has been expired and the policy is to log the messages properties so they are printed.
|
|
Cause
| A message has been expired and the policy is to log the messages properties so they are printed.
|
|
Action
| No action required.
|
|
|
BEA-040354
|
Info: ExpiredJMSMessage JMSMessageID=msgid >\n
|
Description
| A message has been expired and the policy is to log only the MessageId, or there are no matching message header fields or message properties.
|
|
Cause
| A message has been expired and the policy is to log only the MessageId, or there are no matching message header fields or message properties.
|
|
Action
| No action required.
|
|
|
BEA-040332(retired)
|
Info: JMSServer "server", messages(s) with destination "dest" has creation time oldGeneration, which is older the current creation time existingGeneration.
|
Description
| While recovering, message(s) were found for a destination, which has older creationTime("oldGeneration") than the current one("existingGeneration"). The messages will be deleted.
|
|
Cause
| The destination no longer exists.
|
|
Action
| No action required.
|
|
|
BEA-040355(retired)
|
Alert: JMS server "serverName". File store "storeName". The deprecated command line property -Dweblogic.JMSFileStore.SynchronousWritesEnabled or -Dweblogic.JMSFileStore.storeName.SynchronousWritesEnabled was detected. This command line property overrides the preferred method for configuring synchronous write policies. For information on the preferred method, refer to the javadoc for weblogic.management.configuration.JMSFileStoreMBean or the WebLogic Server Console online help.
|
Description
| JMS server "serverName". File store "storeName". The deprecated command line property -Dweblogic.JMSFileStore.SynchronousWritesEnabled or -Dweblogic.JMSFileStore.storeName.SynchronousWritesEnabled was detected. This command line property overrides the preferred method for configuring synchronous write policies. For information on the preferred method, refer to the javadoc for weblogic.management.configuration.JMSFileStoreMBean or the WebLogic Server Console online help.
|
|
Cause
| The indicated command line property is deprecated.
|
|
Action
| Refer to the indicated information on how to configure this now.
|
|
|
BEA-040356(retired)
|
Alert: JMS server "serverName". The JMS file store is unable to load the native file driver to support the "oldPolicy" synchronous write policy. The file store will use the java file driver and the "newPolicy" policy instead, without any loss of reliability.
|
Description
| JMS server "serverName". The JMS file store is unable to load the native file driver to support the "oldPolicy" synchronous write policy. The file store will use the java file driver and the "newPolicy" policy instead, without any loss of reliability. It may be that WebLogic does not support native file I/O on this operating system. For information on synchronous write policies, refer to the weblogic.management.configuration.JMSFileStoreMBean javadoc or WebLogic Server Console online help.
|
|
Cause
| The native file driver is missing or not supported.
|
|
Action
| If the native file driver is supported on the current operating system, ensure that the indicated file exists.
|
|
|
BEA-040357(retired)
|
Info: JMS server "serverName". Opening file store "storeName", driver version "driverVersion", synchronous write policy "policy".
|
Description
| For information on synchronous write policies, refer to the weblogic.management.configuration.JMSFileStoreMBean javadoc or the WebLogic Server Console online help.
|
|
Cause
| This message is for information purposes only.
|
|
Action
| No action required.
|
|
|
BEA-040358(retired)
|
Error: JMS Server "server" can not start, The configuration version for destination "dest" (version time-stamp configCreationTime) should not be older than the corresponding version in the JMS store record (version time-stamp storeCreationTime). To correct this condition, and keep the JMS message(s), edit the config.xml file to change the time-stamp for the associated destination to match the store record version. To correct this condition, and delete the JMS message(s), edit the config.xml file to change the time-stamp for the associated destination to be higher than the store record version.
|
Description
| While recovering, message(s) were found for a destination, which has a newer creation time ("storeCreationTime") than the current one("configCreationTime").
|
|
Cause
| An older config.xml is used that has an older creation time for the associated destination, or the machine clock was rolled back and the destination was deleted and then recreated while the JMS server was not up.
|
|
Action
| To save the message, change the CreationTime for the associated destination in the config.xml file to match the newer value. To discard the message, change the CreationTime for the associated destination in the config.xml file to a value newer than the one in the JMS store record.
|
|
|
BEA-040359
|
Warning: Distributed Destination "name", member "memberName" is not associated with a physical destination.
|
Description
| This message indicates that one of the members of a JMS distributed queue or distributed topic is not associated with any physical destination. To associate a member with a physical destination, set the JMSQueue/JMSTopic attribute of the JMSDistributeQueueMemberMBean/JMSDistributedTopicMemberMBean properly.
|
|
Cause
| Configuration error.
|
|
Action
| Modify the configuration and restart the server.
|
|
|
BEA-040360(retired)
|
Error: JMS server "server". Destination "dest" with creation time storeCreationTime has been deleted from store. However, a destination with the same name in the config.xml has a creation time that is not newer than the deleted one from store.
|
Description
| JMS server "server". Destination "dest" with creation time storeCreationTime has been deleted from store. However, a destination with the same name in the config.xml has a creation time that is not newer than the deleted one from store.
|
|
Cause
| An older config.xml is used that has an older creation time for the given destination, or the machine clock was rolled back and the destination was deleted and then recreated while the JMS server was not up.
|
|
Action
| To keep the destination, specify the CreationTime with a value newer than the deleted one in the config.xml file. Otherwise, remove the destination in the config.xml file.
|
|
|
BEA-040361(retired)
|
Error: JMS server "server". A failure occurred while moving a message from destination "sourceDest" to destination "targetDest". Message moves occur due to either expired messages that have a redirect policy, or redelivered messages that have reached their redelivery limit and fail into an error destination. The JMS server will retry in secs seconds.
|
Description
| JMS server "server". A failure occurred while moving a message from destination "sourceDest" to destination "targetDest". Message moves occur due to either expired messages that have a redirect policy, or redelivered messages that have reached their redelivery limit and fail into an error destination. The JMS server will retry in secs seconds.
|
|
Cause
| This error usually occurs due to a file store disk failure or a JDBC store database failure.
|
|
Action
| If the JMS store uses JDBC, make sure that the backing database is up. If this error repeats, shutdown and restart the JMS server.
|
|
|
BEA-040362(retired)
|
Warning: JMS server "server". A failure occurred while moving a message from destination "sourceDest" to destination "targetDest". This problem is recoverable and reported for informative purposes only. The message move succeeded.
|
Description
| Message moves occur due to either expired messages that have a redirect policy, or redelivered messages that have reached their redelivery limit and fail into an error destination.
|
|
Cause
| This error usually occurs due to a file store disk failure or a JDBC store database failure.
|
|
Action
| If the JMS store uses JDBC, make sure the backing database is up. If this error repeats, shutdown and restart the JMS server.
|
|
|
BEA-040363(retired)
|
Error: JMS server "server". An unexpected exception occurred while moving a message from destination "sourceDest" to destination "targetDest". Message moves occur due to either expired messages that have a redirect policy, or redelivered messages that have reached their redelivery limit and fail into an error destination. Message moves will no longer be serviced.
|
Description
| JMS server "server". An unexpected exception occurred while moving a message from destination "sourceDest" to destination "targetDest". Message moves occur due to either expired messages that have a redirect policy, or redelivered messages that have reached their redelivery limit and fail into an error destination. Message moves will no longer be serviced.
|
|
Cause
| Unknown.
|
|
Action
| Contact customer support.
|
|
|
BEA-040364(retired)
|
Info: A JMS Distributed Destination member "localMember" is connected to a remote member "remoteMember" in "distDest".
|
Description
| This is a normal part of initializing JMS Distributed Destinations.
|
|
Cause
| This is a normal part of initializing JMS Distributed Destinations.
|
|
Action
| No action required. This is a normal part of initializing JMS Distributed Destinations.
|
|
|
BEA-040365(retired)
|
Info: JMS Distributed Destination proxy member "localMember" in "distDest" is connected to remote proxy member "remoteMember".
|
Description
| This is a normal part of initializing JMS Distributed Destinations. The connection factory had no local member, so a proxy member was automatically generated for non-durable subscriptions. The proxy member was not manually configured by the administrator. It was automatically configured by the system.
|
|
Cause
| This is a normal part of initializing JMS Distributed Destinations. The connection factory had no local member, so a proxy member was automatically generated for non-durable subscriptions. The proxy member was not manually configured by the administrator. It was automatically configured by the system.
|
|
Action
| No action required. This is a normal part of initializing JMS Distributed Destinations.
|
|
|
BEA-040366(retired)
|
Error: JMS Distributed Destination member "localMember" in "distDest" unable to accept connection from remote member "remoteMember" due to exception t.
|
Description
| Failed to setup connection between JMS Distributed Destination members due to an exception.
|
|
Cause
| JNDI failure or failure in starting destinations, errors creating, or removing durable system subscribers.
|
|
Action
| Check the configuration file and reboot the system.
|
|
|
BEA-040367(retired)
|
Info: JMS server "server". File store "storeName". The JMS file store directory "dirName" was automatically created in development mode, and its absolute path is "finalDir".
|
Description
| In development mode, JMS subsystem will automatically create the file store directory if needed.
|
|
Cause
| The specified directory for the JMS file store does not exist.
|
|
Action
| No action required.
|
|
|
BEA-040368
|
Error: The following exception has occurred: \n
|
Description
| A stack trace is being printed for an exception that occurred.
|
|
Cause
| An error condition has occurred.
|
|
Action
| Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help in debugging an existing problem.
|
|
|
BEA-040369(retired)
|
Debug: The following exception has occurred: \n
|
Description
| A stack trace is being printed for an exception that occurred as part of debugging output.
|
|
Cause
| An error condition has occurred.
|
|
Action
| Look for the associated exception in the log or your program to see what the results are. In general, this stack trace will help in debugging an existing problem.
|
|
|
BEA-040370
|
Info: Linked Exception ----------- \n
|
Description
| A linked exception for a previously logged exception is being printed.
|
|
Cause
| An error condition was reported.
|
|
Action
| No action required.
|
|
|
BEA-040371
|
Error: JMSServer "arg0" JMS Server Session Pool is invalid and has not been started "arg1". Exception is "e".
|
Description
| JMS Server session pool is invalid and has not been started.
|
|
Cause
| Server Session Pool is invalid because it has an invalid Connection Factory or Listener.
|
|
Action
| Edit JMS Session Pool and verify that it has valid attributes and reboot the server or delete and add a new valid JMS Session Pool.
|
|
|
BEA-040372
|
Warning: JMSServer "name" failed to un-register when deactivated for migration, e.
|
Description
| The JMS Server is deactivated before it is migrated to another WebLogic Server. It failed to un-register the run time MBean with the admin server, which may cause problem when the JMS Server migrates back to this WebLogic Server in the future.
|
|
Cause
| Security failure, and etc.
|
|
Action
| No action required.
|
|
|
BEA-040373
|
Error: Could not find a license for JMS. Please contact BEA to get a license.
|
Description
| Could not find a license for JMS. Please contact BEA to get a license.
|
|
Cause
| Unable to get license for JMS.
|
|
Action
| Contact BEA to get a license.
|
|
|
BEA-040374(retired)
|
Info: Destination "Destination" has been paused "
|
Description
| Pause request has been issued for the specified destination. Destination cannot receive any new messages while it is paused.
|
|
Cause
| Pause request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040375(retired)
|
Info: Destination "Destination" has been resumed "
|
Description
| Resume request has been issued for the specified destination. Destination is now able to receive new messages.
|
|
Cause
| Resume request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040376
|
Info: Destination "Destination" has been paused for new message production"
|
Description
| Production Pause request has been issued for the specified destination. Destination cannot receive any new messages while it is paused for production.
|
|
Cause
| Production Pause request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040377
|
Info: Destination "Destination" has been resumed for new message production"
|
Description
| Production Resume request has been issued for the specified destination. Destination is now able to accept new messages.
|
|
Cause
| Production Resume request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040378
|
Info: Destination "Destination" has been paused for insertion of messages from in-flight work completion"
|
Description
| Insertion Pause request has been issued for the specified destination. Any messages that are result of the in-flight work completion will not be available for consumption.
|
|
Cause
| Insertion Pause request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040379
|
Info: Destination "Destination" has been resumed for insertion of messages from in-flight work completion"
|
Description
| Insertion Resume request has been issued for the specified destination. Any messages that are result of the in-flight work completion will be available for consumption.
|
|
Cause
| Insertion Resume request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040380
|
Info: Destination "Destination" has been paused for consumption"
|
Description
| Consumption Pause request has been issued for the specified destination. No messages will be delivered to the consumers.
|
|
Cause
| Consumption Pause request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040381
|
Info: Destination "Destination" has been resumed for consumption"
|
Description
| Consumption Resume request has been issued for the specified destination. Messages will be delivered to the consumers.
|
|
Cause
| Consumption Resume request has been issued for the specified destination.
|
|
Action
| No action required.
|
|
|
BEA-040382
|
Info: JMSServer "JMSServer" has been paused for new message production"
|
Description
| Production Pause request has been issued for the specified JMSServer. The destinations that are hosted by this JMSServer cannot receive any new messages while this JMSServer paused for production.
|
|
Cause
| Production Pause request has been issued for the specified JMSServer.
|
|
Action
| No action required.
|
|
|
BEA-040383
|
Info: JMSServer "JMSServer" has been resumed for new message production"
|
Description
| Production Resume request has been issued for the specified JMSServer. The destinations on this JMSServer are now able to accept new messages.
|
|
Cause
| Production Resume request has been issued for the specified JMSServer.
|
|
Action
| No action required.
|
|
|
BEA-040384
|
Info: JMSServer "JMSServer" has been paused for insertion of messages from in-flight work completion"
|
Description
| Insertion Pause request has been issued for the specified JMSServer. Any messages that are result of the in-flight work completion will not be available for consumption.
|
|
Cause
| Insertion Pause request has been issued for the specified JMSServer.
|
|
Action
| No action required.
|
|
|
BEA-040385
|
Info: JMSServer "Destination" has been resumed for insertion of messages from in-flight work completion"
|
Description
| Insertion Resume request has been issued for the specified JMSServer. Any messages that are result of the in-flight work completion will be available for consumption.
|
|
Cause
| Insertion Resume request has been issued for the specified JMSServer.
|
|
Action
| No action required.
|
|
|
BEA-040386
|
Info: JMSServer "JMSServer" has been paused for consumption"
|
Description
| Consumption Pause request has been issued for the specified JMSServer. No messages will be delivered to the consumers from the destinations on this JMSServer.
|
|
Cause
| Consumption Pause request has been issued for the specified JMSServer.
|
|
Action
| No action required.
|
|
|
BEA-040387
|
Info: JMSServer "JMSServer" has been resumed for consumption"
|
Description
| Consumption Resume request has been issued for the specified JMSServer. Messages will be delivered to the consumers from the destinations on this JMSServer.
|
|
Cause
| Consumption Resume request has been issued for the specified JMSServer.
|
|
Action
| No action required.
|
|
|
BEA-040400(retired)
|
Info: JMS Deploying file: jmsDescriptor
|
Description
| JMS Deploying file: jmsDescriptor
|
|
Cause
| JMS module descriptor deployed
|
|
Action
| No action required.
|
|
|
BEA-040402(retired)
|
Error: JMS Module "uri" failed to un-load, e.
|
Description
| Unable to un-load the JMS module by the container.
|
|
Cause
| Internal error.
|
|
Action
| No action required.
|
|
|
BEA-040403(retired)
|
Error: JMS Module "uri" failed to de-activate, e.
|
Description
| Unable to de-activate the JMS module by the container.
|
|
Cause
| Internal error.
|
|
Action
| No action required.
|
|
|
BEA-040404
|
Info: Foreign JMS Server "arg0" is started.
|
Description
| The specified foreign JMS server has been started.
|
|
Cause
| The specified foreign JMS server has been started.
|
|
Action
| No action required.
|
|
|
BEA-040405
|
Error: Failed to bind an entity of Foreign JMS Server "name" with their JNDI names due to e.
|
Description
| Failed to bind an entity of a foreign JMS server due to an exception.
|
|
Cause
| JNDI failure.
|
|
Action
| Modify the JMS module descriptor of the corresponding application and re-deploy the application.
|
|
|
BEA-040406
|
Info: Distributed destination "arg0" is started.
|
Description
| The specified distributed destination has been started.
|
|
Cause
| The specified distributed destination has been started.
|
|
Action
| No action required.
|
|
|
BEA-040407
|
Info: Default connection factory "arg0" with its JNDI name "arg1" is started.
|
Description
| The specified default connection factory has been started.
|
|
Cause
| The specified default connection factory has been started.
|
|
Action
| No action required.
|
|
|
BEA-040408
|
Error: Failed to bind default connection factory "name" with its JNDI name "jndiName" due to e.
|
Description
| Failed to bind a default connection factory due to an exception.
|
|
Cause
| JNDI failure.
|
|
Action
| Modify the configuration and restart the server file. Then reboot the system.
|
|
|
BEA-040409
|
Info: FailedJMSMessage for store-and-forward: JMSMessageID=msgid >\n Header\n Property\n
|
Description
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log the message header fields and messages properties so they are printed.
|
|
Cause
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log the message header fields and messages properties so they are printed.
|
|
Action
| No action required.
|
|
|
BEA-040410
|
Info: FailedJMSMessage for store-and-forward: JMSMessageID=msgid >\n Header\n
|
Description
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log the message header fields and messages properties so they are printed.
|
|
Cause
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log the message header fields and messages properties so they are printed.
|
|
Action
| No action required.
|
|
|
BEA-040411
|
Info: FailedJMSMessage for store-and-forward: JMSMessageID=msgid >\n Property\n
|
Description
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log the message header fields and messages properties so they are printed.
|
|
Cause
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log the message header fields and messages properties so they are printed.
|
|
Action
| No action required.
|
|
|
BEA-040412
|
Info: FailedJMSMessage for store-and-forward: JMSMessageID=msgid >\n
|
Description
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log only the MessageId, or there are no matching message header fields or message properties.
|
|
Cause
| A message has been expired before it is successfully forwarded by SAF agent, and the policy is to log only the MessageId, or there are no matching message header fields or message properties.
|
|
Action
| No action required.
|
|
|
BEA-040420
|
Info: The JMS transaction branch xid for destination dest was administratively committed.
|
Description
| An administrator requested that the specified JMS transaction branch be committed. Other participants in the global transaction may have rolled back in which case the transaction is considered to have a mixed or heuristic outcome.
|
|
Cause
| Administrative action.
|
|
Action
| No action required.
|
|
|
BEA-040421
|
Info: An administrative request to commit the JMS transaction branch xid on destination dest failed with the following exception. e
|
Description
| An administrator requested that the specified JMS transaction branch be committed, yet the commit operation failed. The JMS transaction branch may still be pending.
|
|
Cause
| The cause of the failure may be indicated by the exception provided in the error message.
|
|
Action
| The transaction may be in an invalid state to allow commit processing. Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
|
|
|
BEA-040422
|
Info: The JMS transaction branch xid for destination dest was administratively rolled back.
|
Description
| An administrator requested that the specified JMS transaction branch be rolled back. Other participants in the global transaction may have committed in which case the transaction is considered to have a mixed or heuristic outcome.
|
|
Cause
| Administrative action.
|
|
Action
| No action required.
|
|
|
BEA-040423
|
Info: An administrative request to rollback the JMS transaction branch xid on destination dest failed with the following exception. e
|
Description
| An administrator requested that the specified JMS transaction branch be rolled back, yet the rollback operation failed. The JMS transaction branch may still be pending.
|
|
Cause
| The cause of the failure may be indicated by the exception provided in the error message.
|
|
Action
| Attempt the operation again or wait for the Transaction Manager to resolve the transaction branch.
|
|
|
BEA-040430
|
Warning: The "UserTransactionsEnabled" attribute on the JMSConnectionFactory "name" has been deprecated and replaced by "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
|
Description
| This logs the usage of the deprecated attribute "UserTransactionsEnabled" as a warning message in the server log .
|
|
Cause
| Deprecated attribute is used.
|
|
Action
| Use the XAConnectionFactoryEnabled attribute instead.
|
|
|
BEA-040431
|
Warning: The "XAServerEnabled" attribute on the JMSConnectionFactory "name" has been deprecated and replaced by "XAConnectionFactoryEnabled" attribute. The changes are propagated to/from this new attribute.
|
Description
| This logs the usage of the deprecated attribute "XAServerEnabled" as a warning message in the server log.
|
|
Cause
| Deprecated attribute is used.
|
|
Action
| Use the XAConnectionFactoryEnabled attribute instead.
|
|
|
BEA-040440(retired)
|
Error: Failed to serialize the XML message.
|
Description
| Failed to serialize an XML message because an invalid XML document was specified.
|
|
Cause
| Attempted to serialize an invalid XML document.
|
|
Action
| Please make sure a valid XML document is passed.
|
|
|
BEA-040441(retired)
|
Error: Failed to parse the XML message.
|
Description
| Failed to parse an XML message because an invalid XML document was specified.
|
|
Cause
| Attempted to serialize an invalid XML document.
|
|
Action
| Please see the exception for the cause of the parse failure.
|
|
|
BEA-040442
|
Warning: While attempting to bind JNDI name arg0 for destination arg1 in module arg2 a JNDI name conflict was found. This destination has not been bound into JNDI.
|
Description
| While attempting to bind JNDI name arg0 for destination arg1 in module arg2 a JNDI name conflict was found. This destination has not been bound into JNDI.
|
|
Cause
| Some other entity has already bound this JNDI name globally.
|
|
Action
| Find out who owns the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
|
|
|
BEA-040443
|
Warning: While attempting to change JNDI name from arg0 to arg1 for destination arg2 in module arg3 a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.
|
Description
| While attempting to change JNDI name from arg0 to arg1 for destination arg2 in module arg3 a JNDI name conflict was found. This destination is no longer globally bound into JNDI under any name.
|
|
Cause
| Some other entity has already bound this JNDI name globally.
|
|
Action
| Find out who owns the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
|
|
|
BEA-040444
|
Warning: While attempting to unadvertise the JNDI name arg0 for destination arg1 in module arg2 an error occurred. The name may or may not be unadvertised globally.
|
Description
| While attempting to unadvertise the JNDI name arg0 for destination arg1 in module arg2 an error occurred. The name may or may not be unadvertised globally.
|
|
Cause
| A network connection between the local server and the administrative server may have gone down.
|
|
Action
| Make sure that network connectivity is working properly and that the administrative server is reachable.
|
|
|
BEA-040445
|
Warning: While attempting to change JNDI name from arg0 to arg1 for destination arg2 in module arg3 a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.
|
Description
| While attempting to change JNDI name from arg0 to arg1 for destination arg2 in module arg3 a JNDI name conflict was found. This destination is no longer locally bound into JNDI under any name.
|
|
Cause
| Some other entity has already bound this JNDI name locally.
|
|
Action
| Find out who owns the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
|
|
|
BEA-040446
|
Warning: While attempting to unadvertise the JNDI name arg0 for destination arg1 in module arg2 an error occurred. The name may or may not be unadvertised locally.
|
Description
| While attempting to unadvertise the JNDI name arg0 for destination arg1 in module arg2 an error occurred. The name may or may not be unadvertised locally.
|
|
Cause
| A network connection between the local server and the administrative server may have gone down.
|
|
Action
| Make sure that network connectivity is working properly and that the administrative server is reachable.
|
|
|
BEA-040447
|
Warning: While attempting to bind JNDI name arg0 for destination arg1 in module arg2 a JNDI name conflict was found. This destination has not been bound into JNDI locally.
|
Description
| While attempting to bind JNDI name arg0 for destination arg1 in module arg2 a JNDI name conflict was found. This destination has not been bound into JNDI locally.
|
|
Cause
| Some other entity has already bound this JNDI name locally.
|
|
Action
| Find out who owns the currently bound JNDI name and remove it if it should not be there or change the JNDI name of this destination so that it does not conflict with the existing one.
|
|
|
BEA-040448
|
Warning: JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "name" has been replaced in the configuration with a FileStoreMBean with the same name.
|
Description
| JMSFileStoreMBean has been deprecated, and has been replaced with FileStoreMBean. The JMSFileStoreMBean "name" has been replaced in the configuration with a FileStoreMBean with the same name.
|
|
Cause
| A deprecated MBean is being replaced in the configuration.
|
|
Action
| No action required.
|
|
|
BEA-040449
|
Warning: JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "name" has been replaced in the configuration with a JDBCStoreMBean with the same name.
|
Description
| JMSJDBCStoreMBean has been deprecated, and has been replaced with JDBCStoreMBean. The JMSJDBCStoreMBean "name" has been replaced in the configuration with a JDBCStoreMBean with the same name.
|
|
Cause
| A deprecated MBean is being replaced in the configuration.
|
|
Action
| No action required.
|
|
|
BEA-040450
|
Warning: The "PagingStore" attribute on the JMSServerMBean "name" has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.
|
Description
| The "PagingStore" attribute on the JMSServerMBean name has been deprecated. It is being replaced in the configuration with the new "PagingDirectory" attribute.
|
|
Cause
| A deprecated MBean attribute has been replaced in the configuration.
|
|
Action
| No action required.
|
|
|
BEA-040451
|
Warning: The "PagingStore" attribute on the JMSServerMBean "name" has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory.
|
Description
| The "PagingStore" attribute on the JMSServerMBean name has been deprecated. Since it currently refers to a JMSJDBCStoreMBean, and paging to a JDBC store is not supported, the JMS server will page messages to its local working directory. To change the location of paging, use the new "PagingDirectory" parameter on the JMSServerMBean.
|
|
Cause
| A deprecated MBean attribute has been replaced in the configuration.
|
|
Action
| No action required.
|
|
|
BEA-040452
|
Warning: The server session pool feature has been deprecated, and it will be removed in an upcoming release. New applications should use message-driven beans instead.
|
Description
| The JMS server session pool feature, represented by the "JMSSessionPool" and "JMSConnectionConsumer" MBeans, will be removed in a future release of the product. Message-driven beans provide similar functionality and fully comply with the J2EE standard.
|
|
Cause
| A deprecated feature was detected in the configuration.
|
|
Action
| Plan to replace use of server session pools in your application.
|
|
|
BEA-040453
|
Warning: The "BytesPagingEnabled" and "MessagesPagingEnabled" parmeters on the JMSServer "name" have been deprecated. These parameters are now ignored. The "MessageBufferSize" parameter should be used to configure paging in this release.
|
Description
| The "BytesPagingEnabled" and "MessagesPagingEnabled" parmeters on the JMSServer "name" have been deprecated. These parameters are now ignored. The "MessageBufferSize" parameter should be used to configure paging in this release.
|
|
Cause
| A deprecated parameter was encountered.
|
|
Action
| Plan to use the new "MessageBufferSize" to control paging.
|
|
|
BEA-040454(retired)
|
Warning: While shutting down JMSServer name an error occurred while attempting to remove all the temporary destinations. The reason for this failure is reason.
|
Description
| The reason reason may provide more information about why this failed.
|
|
Cause
| Inspect the reason for the cause of this failure.
|
|
Action
| If this causes a problem contact BEA Systems, Inc. customer support
|
|
|
BEA-040455
|
Warning: Flow control has been enabled on JMS server "name" because memory is low
|
Description
| The server has determined that overall memory usage is too high, so flow control has been enabled so that JMS will have an opportunity to deliver messages to consumers or page them out to reduce memory usage. Flow control may not affect message producers if it has been explicitly disabled for their connection factories.
|
|
Cause
| Too much memory is being used.
|
|
Action
| Either increase the amount of memory available to the server, or decrease the MessageBufferSize parameter on the JMS server so fewer messages remain in memory.
|
|
|
BEA-040456
|
Warning: An entity of type "entityType" with name "entityName" in JMS module "moduleName" is not targeted. There is no sub-deployment with name "subDeploymentName" in the configuration repository (config.xml), and so this entity will not exist anywhere in the domain.
|
Description
| Every entity that can be targeted in the JMS module has a sub-deployment-name element. If the sub-deployment-name element is not set, it defaults to the name of the entity itself. There must be a corresponding sub-deployment element in the configuration repository, which is used by the JMS module to determine where this entity should be targeted.
|
|
Cause
| The entity of the given name and type in the given JMS module does not have a corresponding sub-deployment in the configuration repository (config.xml). In order for this entity to exist in the domain it must be targeted with a sub-deployment element.
|
|
Action
| Add a sub-deployment stanza to the appropriate deployment descriptor in config.xml. This will either be a jms-system-resource for a system module, or an app-deployment for a stand-alone JMS deployable module. If the JMS module is inside a J2EE application (an EAR file) then add the sub-deployment stanza to the sub-deployment that represents this JMS module in the J2EE application. You do not necessarily have to target the sub-deployment yet - simply adding the sub-deployment with no targets will remove this warning. However, if you wish for this entity to exist somewhere in your domain target the sub-deployment.
|
|
|
BEA-040457
|
Warning: The Template named "tName" element of Distributed Destination "dName" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.
|
Description
| The Template named "tName" element of Distributed Destination "dName" is not supported and hence ignored. Please consider using a Uniform Distributed Destination.
|
|
Cause
| An unsupported attribute JMSTemplate is used in a Distributed Destination.
|
|
Action
| Use a Uniform Distributed Destination instead
|
|
|
BEA-040458
|
Warning: Unable to unprepare en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to unprepare itself in a failed attempt to prepare the module.
|
|
Cause
| The prepared entity could not unprepare itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040459
|
Warning: Unable to deactivate en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to deactivate itself in a failed attempt to activate the module.
|
|
Cause
| The activated entity could not deactivate itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040460
|
Warning: Unable to close the JMS component of module mn due to exc
|
Description
| While attempting to remove the JMS module mn there was an error while attempting to close the JMS component.
|
|
Cause
| The JMS component could not close itself
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040461
|
Warning: Unable to deactivate en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to deactivate itself in a rollback of a dynamic change
|
|
Cause
| The activated entity could not deactivate itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040462(retired)
|
Warning: Unable to unprepare en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to unprepare itself in a rollback of a dynamic change
|
|
Cause
| The prepared entity could not unprepare itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040463(retired)
|
Warning: Unable to destroy en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to destroy itself in a rollback of a dynamic change
|
|
Cause
| The initialized entity could not destroy itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040464
|
Warning: Unable to destroy en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to destroy itself after it failed to prepare. This occurred while the entity was being dynamically added to the module either through a targeting or module change.
|
|
Cause
| The initialized entity could not destroy itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040465(retired)
|
Warning: Unable to unprepare en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to unprepare itself after it failed to activate. This occurred while the entity was being dynamically added to the module either through a targeting or module change.
|
|
Cause
| The prepared entity could not unprepare itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040466(retired)
|
Warning: Unable to destroy en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to destroy itself after it failed to prepare. This occurred while the entity was being dynamically added to the module either through a targeting or module change.
|
|
Cause
| The initialized entity could not destroy itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040467
|
Warning: Unable to deactivate en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to deactivate itself after a failure to initialize or update the module.
|
|
Cause
| The activated entity could not deactivate itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040468(retired)
|
Warning: Unable to unprepare en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to unprepare itself after a failure to initialize or update the module.
|
|
Cause
| The prepared entity could not unprepare itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040469(retired)
|
Warning: Unable to destroy en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to destroy itself after a failure to initialize or update the module.
|
|
Cause
| The initialized entity could not destroy itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040470
|
Warning: Unable to deactivate en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to deactivate itself while attempting to remove it dynamically.
|
|
Cause
| The activated entity could not deactivate itself during dynamic deletion
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040471(retired)
|
Warning: Unable to unprepare en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to unprepare itself while attempting to remove it dynamically.
|
|
Cause
| The activated entity could not unprepare itself during dynamic deletion
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040472(retired)
|
Warning: Unable to destroy en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to destroy itself while attempting to remove it dynamically.
|
|
Cause
| The initialized entity could not destroy itself during dynamic deletion
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040473(retired)
|
Warning: Unable to remove en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to remove itself while attempting to remove it dynamically.
|
|
Cause
| The entity could not remove itself during dynamic deletion
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040474(retired)
|
Warning: Unable to activate en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to activate itself while attempting to create it dynamically.
|
|
Cause
| The entity could not activate itself during dynamic creation
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040475
|
Warning: The destination en does not have an associated quota object. The setting of bytesMaximum to val will have no affect
|
Description
| An attempt was made to modify a destination through a deprecated MBean. Quotas have been reworked. The set of this value on this destination will not take effect because the destination does not have an associated quota object. Consider moving this destination to another module and using the new quota feature.
|
|
Cause
| Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
|
|
Action
| Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
|
|
|
BEA-040476
|
Warning: The destination en does not have an associated quota object. The setting of messagesMaximum to val will have no affect
|
Description
| An attempt was made to modify a destination through a deprecated MBean. Quotas have been reworked. The set of this value on this destination will not take effect because the destination does not have an associated quota object. Consider moving this destination to another module and using the new quota feature.
|
|
Cause
| Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
|
|
Action
| Please consider removing this destination from the interop module. Put it in another module. This will allow you to use the new quota features.
|
|
|
BEA-040477
|
Warning: Error occurred while unbinding a remote JNDI object from local JNDI name "localName" The exception encountered was exception
|
Description
| An error occurred while removing an object from the local JNDI tree.
|
|
Cause
| There may be an error in the JNDI subsystem. See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040478
|
Warning: The JMS subsystem could not deploy or undeploy the default JMS connection factories due to exception
|
Description
| An error occurred while attempting to deploy or undeploy the default JMS connection factories
|
|
Cause
| There may be an error in the JNDI subsystem. See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040479
|
Warning: The system failed to roll back an added connection consumer of name name. The exception received was exception.
|
Description
| A proposed change involving the connection consumer name did not succeed and is in the process of being rolled back. During the rollback a connection consumer that was started could not be rolled back properly
|
|
Cause
| See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040480
|
Warning: The system failed to remove a connection consumer of name name. The exception received was exception.
|
Description
| An attempt was made to remove the connection consumer name. However, the operation did not complete successfully. The exception received is exception.
|
|
Cause
| See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040487(retired)
|
Warning: The modification of property key failed during the activate phase because of exception
|
Description
| During a dynamic change of property key an error was encountered. This occurred while trying to invoke the setter of the property.
|
|
Cause
| See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040488(retired)
|
Warning: The modification of property key failed during the activate phase because of exception
|
Description
| During a dynamic change of property key an error was encountered. This occurred while trying to invoke the setter of the property.
|
|
Cause
| See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040489(retired)
|
Warning: The modification of property key failed during the activate phase because of exception
|
Description
| During a dynamic change of property key an error was encountered. This occurred while trying to invoke the setter of the property.
|
|
Cause
| See the exception for more information.
|
|
Action
| Check the exception message for more detail.
|
|
|
BEA-040490
|
Warning: destinationType destinationName has conflicting name attribute value, which is now changed to have unique name with its JMSServer name. The new destination-name attribute now holds the original name value
|
Description
| Name of conflict detected during upgrade for JMS destinations, maybe because in pre-Diablo we used to allow more than one destination to have the same as long as they belong to different JMSServers.
|
|
Cause
| Name of conflict detected during upgrade for JMS destinations, maybe because in pre-Diablo we used to allow more than one destination to have the same as long as they belong to different JMSServers.
|
|
Action
| Destinations are created with their name decorated with the target JMSServer Name to avoid conflict.
|
|
|
BEA-040491
|
Warning: A deploymentType deploymentName with multiple targets has been split into multiple deployments one for each unique target
|
Description
| A JMS Deployment MBean (JMSConnectionFactory/ForeignJMSServer) with multiple targets has been split into multiple deployments one for each unique target.
|
|
Cause
| A JMS Deployment found with multiple unique targets configured.
|
|
Action
| In pre-Diablo, both JMSConnectionFactory and ForeignJMSServer were allowed to be targeted to more than one server, and or cluster. During upgrade of this configuration to Diablo, these configuration entities are split into more than one entity, one for each unique target.
|
|
|
BEA-040492(retired)
|
Error: The JMSServer named beName has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is modName, and the template name is templateName. However, a JMSSystemResourceMBean of name modName could not be found. The JMS Server beName will not boot until this problem has been fixed.
|
Description
| The JMSServer named beName has a temporary template configured. The JMSSystemResourceMBean name of the module containing the temporary template is modName, and the template name is templateName. However, a JMSSystemResourceMBean of name modName could not be found. The JMS Server beName will not boot until this problem has been fixed.
|
|
Cause
| The temporary template for a JMS server must come from a JMSSystemResourceMBean. A common mistake is to put the temporary template into an AppDeployment. However, because the temporary template must be owned by the administrator, all temporary templates must come from JMSSystemResourceMBeans, not AppDeployments.
|
|
Action
| Put the temporary template into a JMSSystemResource.
|
|
|
BEA-040493(retired)
|
Warning: Unable to remove en in module mn due to exc
|
Description
| The JMS entity named en in JMS module mn failed to remove itself after a failure to initialize or update the module.
|
|
Cause
| The initialized entity could not remove itself in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040494
|
Warning: An error occurred while shutting down the JMS server name: msg
|
Description
| An exception was encountered while shutting down. See the detail message for more information.
|
|
Cause
| See the detail message.
|
|
Action
| The server should still shut down normally. No action required.
|
|
|
BEA-040495(retired)
|
Warning: An error occurred while informing the distributed destination "name" membership change : msg
|
Description
| An exception was encountered while informing the distributed destination membership change. See the detail message for more information.
|
|
Cause
| Either the remote DistributedDestinationManager is down or the registered DDMembershipChangeListener may not be alive.
|
|
Action
| No action required.
|
|
|
BEA-040496
|
Warning: The template en does not have an associated quota object. The setting of bytesMaximum to val will have no affect
|
Description
| An attempt was made to modify a template through a deprecated MBean. Quotas have been reworked. The set of this value on this template will not take effect because the template does not have an associated quota object. Consider moving this template to another module and using the new quota feature.
|
|
Cause
| Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
|
|
Action
| Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
|
|
|
BEA-040497
|
Warning: The template en does not have an associated quota object. The setting of MessagesMaximum to val will have no affect
|
Description
| An attempt was made to modify a template through a deprecated MBean. Quotas have been reworked. The set of this value on this template will not take effect because the template does not have an associated quota object. Consider moving this template to another module and using the new quota feature.
|
|
Cause
| Quotas have been reworked. They are no longer hierarchical in nature. Instead, they are objects that can be pointed to explicitly and can be optionally shared between destinations. Hence quotas no longer work as they did in previous releases. When converting from older releases a decision is made about how to handle quotas based on the setting of the old parameters. These decisions may have been wrong, which would cause this warning to happen.
|
|
Action
| Please consider removing this template from the interop module. Put it in another module. This will allow you to use the new quota features.
|
|
|
BEA-040498
|
Warning: An error occurred while forwarding a message for distributed destination member name: msg
|
Description
| Something went wrong while forwarding a message for a distributed destination. The system will retry message forwarding after a delay.
|
|
Cause
| There may be a temporary network problem, or one of the members of the cluster may be unavailable.
|
|
Action
| See the detail message.
|
|
|
BEA-040499
|
Warning: An error occurred while pushing messages to a JMS client: msg
|
Description
| The JMS server was unable to deliver messages asynchronously to a JMS client.
|
|
Cause
| There may be a network failure.
|
|
Action
| The JMS protocol will recover automatically from such a problem eventually. Check for networking issues or crashed clients.
|
|
|
BEA-040500
|
Warning: Unable to deactivate entity "en" in module "mn" due to exc
|
Description
| The JMS entity named en in JMS module mn failed to rollback a change to the target list after a failure to initialize or update the module.
|
|
Cause
| The activated entity could not rollback the proposed targeting change
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040501
|
Warning: Unable to rollback targeting change of the entity "en" in module "mn" due to exc
|
Description
| The JMS entity named en in JMS module mn failed to rollback a proposed changed to its targeting in a rollback of a dynamic change
|
|
Cause
| The changed entity could not rollback in a failure case
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040502
|
Error: While attempting to change the targeting of JMS module "modName" an error occurred while activating the change. The exception returned is \nexc\n
|
Description
| While attempting to change the targeting of JMS module "modName" an error occurred while activating the change. The exception returned is \nexc\n
|
|
Cause
| The JMS Module failed to activate a prepared change during a targeting update.
|
|
Action
| More information may be available from the exception thrown
|
|
|
BEA-040503
|
Warning: The delivery mode override value of destination "dest" hosted on JMS Server "jmsServer" has been changed from from to to.
|
Description
| The delivery mode override value of destination "dest" hosted on JMS Server "jmsServer" has been changed from from to to. This has been done because the older configuration never supported persistent messages and hence all messages were downgraded to non-persistent. During the upgrade process a configuration was detected that would force all messages through the given destination to be non-persistent, so the upgrade process made that override explicit.
|
|
Cause
| During the upgrade process a configuration was detected that would force all messages through the given destination to be non-persistent, so the upgrade process made that override explicit.
|
|
Action
| Review your application code and configuration. If you need some behavior other than the one the upgrade process chose, you can modify the resulting configuration using the DeliveryMode parameter of the OverridesParams of the destination, or with the HasStore or AllowsPersistentDowngrade parameters of the JMSServer on which the destination is targeted.
|
|
|
BEA-040504
|
Warning: While attempting to add an entity with name "name" an error occurred while trying to convert the old style entity to the new style entity. The error was "exception".
|
Description
| While attempting to add an entity with name "name" an error occurred while trying to convert the old style entity to the new style entity. The error was "exception".
|
|
Cause
| See the description of the exception that occurred for more information on the cause of this failure.
|
|
Action
| See the description of the exception that occurred for more information on the cause of this failure.
|
|
|
BEA-040505
|
Warning: The JMS module named "moduleName" inside application "module" does not have a sub-deployment stanza named "moduleName". Without such a stanza no entities inside the module will be deployed, since the sub deployments inside of the sub-deployment stanza named "moduleName" control where JMS entities inside this module are targeted.
|
Description
| The JMS module named "moduleName" inside application "module" does not have a sub-deployment stanza named "moduleName". Without such a stanza no entities inside the module will be deployed, since the sub deployments inside of the sub-deployment stanza named "moduleName" control where JMS entities inside this module are targeted.
|
|
Cause
| When a JMS module is inside an EAR file, the targeting information for entities inside that module are nested within a sub-deployment named after the name of the JMS module found in the weblogic-application.xml file of the EAR file. If no sub-deployment exists with the name of the JMS module, then no targeted entities inside the module will become available. This is usually an oversight on the part of the administrator.
|
|
Action
| Add a sub-deployment stanza with the name of the JMS module as specified in the weblogic-application.xml file to the app-deployment stanza. Nested inside that sub-deployment you can target the entities in the module normally.
|
|
|
BEA-040506
|
Info: The JMS SAF forwarder has successfully connected to the remote destination "url".
|
Description
| This log messages indicates that the JMS SAF forwarder has just either initially connected to a remote destination, or successfully reconnected after a failure.
|
|
Cause
| Nothing.
|
|
Action
| No action required.
|
|
|
BEA-040507
|
Info: The JMS SAF forwarder failed to connect to the remote destination "url", because of statckTrace.
|
Description
| This log messages indicates that the JMS SAF forwarder have just failed to connect to the remote destination. The stack trace of the Exception that has caused the failure is given.
|
|
Cause
| This is either due to a configuration error, or a network failure, or the remote destination is temporarily unavailable.
|
|
Action
| Check configuration, network connection, or the remote destination.
|
|
|
BEA-040508
|
Warning: BridgeDestinationMBean has been deprecated. The BridgeDestination "name" has been replaced in the configuration with a JMSBridgeDestination with the same name.
|
Description
| BridgeDestinationMBean has been deprecated. The BridgeDestination "name" has been replaced in the configuration with a JMSBridgeDestination with the same name.
|
|
Cause
| A deprecated MBean is being replaced in the configuration.
|
|
Action
| No action required.
|
|
|
BEA-040509
|
Error: Failed to $operation JMS Server "name" because the earlier attempt to $cause was failed.
|
Description
| Failed to deploy JMS Server because one of the deployment operation failed.
|
|
Cause
| Error occurred during deployment of the JMS Server.
|
|
Action
| Fix any deployment errors related to this JMS Servers.
|
|
|
BEA-040510
|
Error: While attempting to rename a connection factory named "name" an error occurred while attempting to establish a JNDI listener. The cause was cause
|
Description
| While attempting to rename a connection factory named "name" an error occurred while attempting to establish a JNDI listener. The cause was cause
|
|
Cause
| There was an error while attempting to establish a JNDI listener. The description of the cause may provide more information about the true cause of the error.
|
|
Action
| The cause of this problem may give an indication of the source of this problem. If this problem persists, please call BEA Systems, Inc. customer support.
|
|
|
BEA-040511
|
Info: The system is waiting to unbind connection factory "name". An attempt is being made to change the JNDI name of this connection factory from "old" to "aNew".
|
Description
| The system is waiting to unbind connection factory "name". An attempt is being made to change the JNDI name of this connection factory from "old" to "aNew".
|
|
Cause
| An attempt is being made to unbind a connection factory from a JNDI name in order to dynamically change the JNDI from one name to another. This message will repeat every twenty seconds for five minutes.
|
|
Action
| This message is shown for information only.
|
|
|
BEA-040512
|
Error: An attempt is being made to change the JNDI name of connection factory "name" from "old" to "aNew". The system has waited to unbind "old" for five minutes. The new JNDI name "aNew" may or may not be bound properly.
|
Description
| An attempt is being made to change the JNDI name of connection factory "name" from "old" to "aNew". The system has waited to unbind "old" for five minutes. The new name "aNew" may or may not be bound properly.
|
|
Cause
| The connection factory was not fully unbound after five minutes. Some error may have occurred while attempting to unbind this connection factory.
|
|
Action
| In order to maintain the integrity of the connection factory it is recommended you untarget and retarget the connection factory that failed. Otherwise the connection factory is in an indeterminate state.
|
|
|
BEA-040513
|
Warning: While attempting to rename a connection factory named "name" an error occurred while attempting to remove a JNDI listener. The cause was cause
|
Description
| While attempting to rename a connection factory named "name" an error occurred while attempting to remove a JNDI listener. The cause was cause
|
|
Cause
| There was an error while attempting to remove a JNDI listener. The description of the cause may provide more information about the true cause of the error.
|
|
Action
| The cause of this problem may give an indication of the source of this problem. If this problem persists, please call BEA Systems, Inc. customer support.
|
|
|
BEA-040514
|
Warning: While attempting to rename a connection factory named "name" an error occurred in the JNDI listener. The error was cause
|
Description
| While attempting to rename a connection factory named "name" an error occurred in the JNDI listener. The error was cause
|
|
Cause
| While attemptint to dynamic change the JNDI name of a connection factory a JNDI error was thrown. The error itself will tell more about the cause of this failure.
|
|
Action
| The cause of this problem may give an indication of the source of this problem. If this problem persists, please call BEA Systems, Inc. customer support.
|
|
|
BEA-040515
|
Warning: A failured occured while attempting to unregister an InterceptionPoint, e
|
Description
| While attempting to unregister an InterceptionPoint an exception occured. The execption was null
|
|
Cause
| While attempting to unregister an InterceptionPoint an exception occured. The error itself will tell more about the cause of this failure.
|
|
Action
| The cause of this problem may give an indication of the source of this problem. If this problem persists, please call BEA Systems, Inc. customer support.
|
|
