Skip navigation.

JMS Subsystem Messages

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 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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"). Iinstance 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

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

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 verion are being converted.

Action

No action required.

BEA-040317

Error: Distributed Destination "name". All members must exist and be in the same cluster.

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

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

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

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

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

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

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

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

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

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

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

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

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 asssociated 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

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

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

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

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

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

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

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

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

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 inavlid 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

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

Info: Destination "Destination" has been resumed "

Description

Resume request has been issued for the specified destination. Destinatio n is now able to receive new messages.

Cause

Resume request has been issued for the specified destination.

Action

No action required.