The JMS1.0 catalog contains messages in the range
BEA40000 - BEA45000. Messages in this catalog are part of the
weblogic.jms
Internationalization package and the weblogic.i18n Localization package.
|
BEA-040000
|
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
|
Debug: JMS Debugging arg0
|
Description
| Uncataloged debug message - please do not change |
|
Cause
| Debugging - please do not change. |
|
Action
| No action required. |
|
|
BEA-040003
|
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
|
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
|
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
|
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 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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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 - aknowledgeMode: 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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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 1ueue 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
|
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
|
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
|
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
|
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
|
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 totalling 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
|
Info: JMSServer "server", Finished scan of file store "storeName" in directory "dirName". Found numRecords totalling 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
|
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
|
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
|
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 e.
|
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 e.
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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 |
