![]() |
![]() |
|
|
040000 | Info: JMSServer "arg0", deleting subscription "arg1" no matching topic named "arg2". | |
Detail | While recovering, a durable subscriber entry, arg1, was found whose topic, arg2, no longer exists. The entry will be ignored. | |
Cause | The topic no longer exists. | |
Action | No action required. | |
040002 | Debug: JMS Debugging arg0 | |
Detail | Uncatalogued debug message - please do not change | |
Cause | Debugging - please do not change. | |
Action | No action required. | |
040003 | Error: JMSServer "arg0", SQL Error: arg1 | |
Detail | An SQL error occurred. | |
Cause | Check to see that the database is properly configured. | |
Action | Re-run the operation. | |
040004 | Info: JMSServer "arg0", SQL Error Code: arg1 | |
Detail | An SQL error occurred. | |
Cause | Check to see that the database is properly configured. | |
Action | Re-run the operation. | |
040005 | Info: JMSServer "arg0", SQL State: arg1 | |
Detail | An SQL error occurred. | |
Cause | Check to see that the database is properly configured. | |
Action | Re-run the operation. | |
040006 | Info: Server arg0, this server is not licensed to run JMS. To find out about JMS licensing, please contact sales@weblogic.com arg1 | |
Detail | The license file does not indicate that the JMS feature is available. | |
Cause | The license file does not indicate that the JMS feature is available. | |
Action | Contact sales to purchase JMS. | |
040008 | Info: Configured arg0 user connection factories}. | |
Detail | arg0 user connection factories were specified in the configuration. | |
Cause | This message indicates the number of user connection factories found while processing the configuration file. | |
Action | No action required. | |
040009 | Info: Configured arg0 JMSServers}. | |
Detail | arg0 JMSServers were specified in the configuration. | |
Cause | This message indicates the number of JMSServers found while processing the configuration file. | |
Action | No action required. | |
040010 | Info: JMSServer "arg0", configured arg1 session pools}. | |
Detail | arg1 session pools were configured for JMSServer "arg0" in the configuration. | |
Cause | This message indicates that arg1 session pools were configured for JMSServer "arg0" while processing the configuration file. | |
Action | No action required. | |
040011 | Info: JMSServer "arg0", configured arg1 destinations}. | |
Detail | arg1 destinations were configured for JMSServer "arg0" in the configuration. | |
Cause | This message indicates that arg1 destinations were configured for JMSServer "arg0" while processing the configuration file. | |
Action | No action required. | |
040013 | Info: JMS is successfully started. | |
Detail | JMS is successfully configured and started | |
Cause | This message indicates that All JMS objects configured in the configuration file have been successfully created and bound to JNDI names (if needed). JMS is ready to receive and send messages. | |
Action | No action required. | |
040014 | Error: Failed to start JMSServer, JMS is shutting down... | |
Detail | Failed to start JMSServer, JMS is shutting down... | |
Cause | This message indicates that the JMS server never reached the STATE_INITIALIZED state during startup. | |
Action | Check configuration file and reboot the system. | |
040015 | Info: JMS shutdown is complete. | |
Detail | JMS shutdown is complete and all the resources are cleared up. | |
Cause | This message indicates that JMS has been shut down either upon administrators request or due to configuration errors | |
Action | No action required. | |
040016 | Info: No JMS Mbeans configured for server arg0 | |
Detail | No JMS Mbeans configured for server arg0 | |
Cause | This message indicates that No JMS Mbeans configured for server arg0 therefore JMS is not available on this server | |
Action | No action required. | |
040017 | Error: JMSServer "arg0", connection factory JNDI binding failed, ex1, JMS is shutting down... | |
Detail | JMSServer "arg0", connection factory JNDI binding failed, ex1, JMS is shutting down... | |
Cause | This message indicates that an error was found when binding connection factory to a JNDI name during configuration. | |
Action | Check configuration file and reboot the system. | |
040018 | Error: Could not get a replicated or non-replicated InitialContext from the default provider, ex0 | |
Detail | Could not get a replicated or non-replicated InitialContext from the default provider, ex0 | |
Cause | This message indicates that Error was found when binding a JMS Server to a JNDI name during configuration. | |
Action | Check configuration file and reboot the server. | |
040019 | Error: JMSServer "arg0", failed to bind to jndi name: arg1 | |
Detail | JMSServer "arg0", failed to bind to jndi name: arg1 | |
Cause | This message indicates that Error was found when binding a JMS Server to a JNDI name during configuration. | |
Action | Check configuration file and reboot the system. | |
040020 | Debug: Debugging arg0 | |
Detail | Uncatalogued debug message - please do not change | |
Cause | Debugging - please do not change. | |
Action | No action required. | |
040024 | Alert: JMSServer "arg0", byte threshold for destination arg1 has been exceeded. | |
Detail | The total message byte count for destination arg1 has exceeded the bytesThresholdHigh attribute. | |
Cause | No cause | |
Action | No Action | |
040025 | Alert: JMSServer "arg0", byte threshold condition for destination arg1 has cleared. | |
Detail | The total message byte count for destination arg1 has dropped below the bytesThresholdLow attribute | |
Cause | No cause | |
Action | No Action | |
040026 | Alert: JMSServer "arg0", message threshold for destination arg1 has been exceeded. | |
Detail | The total message count for destination arg1 has exceeded the messagesThresholdHigh attribute. | |
Cause | No cause | |
Action | No action | |
040027 | Alert: JMSServer "arg0", message threshold condition for destination arg1 has cleared. | |
Detail | The total message count for destination arg1 has dropped below the messagesThresholdLow attribute. | |
Cause | No cause | |
Action | No Action | |
040028 | Alert: JMSServer "JMSServer", byte threshold for server has been exceeded. | |
Detail | The total message byte count for JMSServer "JMSServer" has exceeded the bytesThresholdHigh attribute. | |
Cause | No cause | |
Action | No Action | |
040029 | Alert: JMSServer "JMSServer", byte threshold for server has cleared. | |
Detail | The total message byte count for JMSServer "JMSServer" has been dropped below the bytesThresholdLow attribute. | |
Cause | No cause | |
Action | No Action | |
040030 | Alert: JMSServer "JMSServer", message threshold for server has been exceeded. | |
Detail | The total message count for JMSServer "JMSServer" has exceeded the messagesThresholdHigh attribute. | |
Cause | No cause | |
Action | No Action | |
040031 | Alert: JMSServer "JMSServer", message threshold for server has cleared. | |
Detail | The total message count for JMSServer "JMSServer" has dropped below the messagesThresholdLow attribute | |
Cause | No cause | |
Action | No Action | |
040033 | Error: JMSServer "arg0", arg1 license validation failed, arg2. | |
Detail | JMSServer "arg0", arg1 license validation failed, arg2. | |
040034 | Info: JMSServer "arg0", destination arg1 will be removed when JMS starts again. | |
Detail | JMSServer "arg0", destination arg1 will be removed when JMS starts again. | |
040035 | Info: JMSServer "arg0", cancel the destination arg1 remove operation. | |
Detail | JMSServer "arg0", cancel the destination arg1 remove operation. | |
040036 | Error: Failed to start JMSServer because there is no correct license, JMS is shutting down... | |
Detail | Failed to start JMSServer because there is no correct license, JMS is shutting down... | |
Cause | This message indicates that a correct license for running JMS was not found. | |
Action | Check or refresh license file WebLogicLicense.xml and reboot the system. | |
040037 | Error: JMSServer "arg0", count count1, failed to start JMSServer, ex2, JMS is shutting down... | |
Detail | JMSServer "arg0", failed to start JMSServer, ex2, JMS is shutting down... | |
Cause | This message indicates that the JMSServer BackEnd could not be started. | |
Action | Check configuration file and reboot the system. | |
040038 | Error: Failed to start JMSServer, unexpected state state0 at start(), JMS is shutting down... | |
Detail | Failed to start the JMSServer because it was in an unexpected state state0 when its start() method was called, JMS is shutting down... | |
Cause | This message indicates that the JMSServer could not be started. | |
Action | Check configuration file and reboot the system. | |
040040 | Error: JMSServer "arg0", failed to dynamically add a new server session pool, instance arg1 already exists. | |
Detail | 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. | |
Action | Give a new name to the server session pool to be created, and re-do the adding operation. | |
040041 | Error: JMSServer "arg0", server session pool closed for connection consumer: arg1 | |
Detail | Server session pool was found closed when a connection consumer tried to access sessions in the pool. | |
040042 | Error: JMSServer "arg0", connection closed for server session pool: arg1 | |
Detail | Server session pools connection was found closed when a connection consumer tried to get a server session from the pool . | |
040043 | Error: JMSServer "arg0", server session pool's Connection closed for connection consumer: arg1 | |
Detail | Server session pools connection was found closed when connection consumer tried to access a server session. | |
040045 | Error: JMSServer "arg0", connections were broken between connection consumer: arg1 and its server session. | |
Detail | JMSServer "arg0", connections were broken between a connection consumer and a server session. | |
Action | re-start the server. | |
040046 | Error: JMSServer "arg0", server session was closed for connection consumer arg1. | |
Detail | Server session was found closed when JMS server tried to deliver messages to a connection consumer. | |
Action | re-start the server. | |
040047 | Alert: JMSServer "server", store failure while deleting consumer consumer, t. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040048 | Alert: JMSServer "server", store failure while writing message for topic topic, t. | |
Detail | Message is still delivered, but may not be persistent. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040049 | Alert: JMSServer "server", store failure while writing message for queue queue, t. | |
Detail | Message is still delivered, but may not be persistent. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040050 | Alert: JMSServer "server", store failure while writing durable subscriber message for topic topic, t. | |
Detail | Message is still delivered, but may not be persistent. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040051 | Alert: JMSServer "server", store failure while deleting message for destination topic, t. | |
Detail | Message was delivered, but may not have been deleted. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040052 | Alert: JMSServer "server", store failed to open, t. | |
Cause | Disk failure, database failure. | |
Action | Check to see that the persistent store is available and properly configured. | |
040053 | Alert: JMSServer "server", failed to register JMS server with transaction manager. | |
Action | Check to see that there are no duplicate JMS store names. Check to see that the transaction manager successfully initialized. | |
040054 | Info: JMSServer "server", no persistent store configured. | |
Detail | Persistent messages will be automatically downgraded to non-persistent. | |
Cause | No persistent store specified in the server configuration. | |
Action | Check that there are no applications using destinations on this server that require persistent messaging. | |
040055 | Info: JMSServer "server", messages(s) with no matching destination "dest". | |
Detail | 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. | |
040056 | Info: JMSServer "server", deleting count messages(s) with no matching destination. | |
Detail | While recovering, message(s) were found for an unconfigured destination. | |
Cause | The destination no longer exists. | |
Action | No action required. | |
040057 | Info: JMSServer "arg0", expiring arg1 messages(s). | |
Detail | Expired messages are deleted. | |
Cause | While recovering, expired messages were found. | |
Action | No action required. | |
040058 | Alert: JMSServer "arg0", unhandled exeption, error code "arg1", t. | |
Detail | The server encountered an unexpected condition but may attempt to continue operation. | |
Action | Contact customer support. | |
040059 | Alert: JMSServer "arg0", unhandled exception during commit, t. | |
Detail | Commit may or may not have succeeded. | |
Action | Contact customer support. | |
040060 | Alert: JMSServer "arg0", unhandled exception during rollback, t. | |
Detail | Rollback may or may not complete. | |
Action | Contact customer support. | |
040061 | Alert: JMSServer "server", store failure while preparing a transaction, t. | |
Detail | Transaction will be rolled back. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040062 | Alert: JMSServer "server", store failure while preparing a receive transaction, t. | |
Detail | Transaction will be rolled back. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040063 | Alert: JMSServer "server", store failure while committing a receive transaction, t. | |
Detail | A delete request to the JMS store failed. Transaction may or may not rollback. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040064 | Alert: JMSServer "server", store failure while rolling back a receive transaction, t. | |
Detail | A request to the JMS store failed. The transaction will still roll back. | |
Cause | Disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040065 | Alert: JMSServer "server", store failure while preparing a send transaction, t. | |
Detail | The transaction will be rolled back and the send will not occur. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040066 | Alert: JMSServer "server", store failure while committing a send transaction, t. | |
Detail | A change request to the JMS store failed. Transaction may or may not rollback. | |
Cause | Disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
040067 | Info: JMSServer "arg0", exception closing subscriber arg1 with exception arg2 at JMS startup time. | |
Detail | JMSServer "arg0", exception closing subscriber arg1 with exception arg2 at JMS startup time. | |
040068 | Error: JMSServer "serverName", error unregistering back-end destination backend. | |
040069 | Error: JMSServer "serverName", error unregistering producer backend. | |
040070 | Error: JMSServer "serverName", error unregistering front-end connection frontend, | |
040071 | Error: JMSServer "serverName", error unregistering front-end session session. | |
040072 | Error: JMSServer "serverName", error unregistering consumer consumer. | |
040073 | Error: JMSServer "serverName", error creating JMS session with connection: connection - mbeanName: mbeanName - sessionID: sessionId - transacted: transacted - aknowledgeMode: acknowledgeMode | |
040074 | Error: JMSServer "serverName", error creating JMS consumer for session: session - mbeanName: mbeanName - clientId: clientId - name: name - destination: destination - selector: selector - noLocal: noLocal | |
040075 | Error: JMSServer "serverName", error creating JMS producer for session: session - mbeanName: mbeanName - producerId: producerId - destination: destination | |
040077 | Alert: JMSServer "server", store close failed, t. | |
Detail | A request to close the JMS store failed. | |
Cause | Disk failure, database failure. | |
Action | Ensure that no attempts are made to re-open the store until no server is using it. | |
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. | |
Detail | A migration of an old JMS persistent store has been started previously and did not complelte for some reason. 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. | |
040079 | Error: JMSServer "serverName", migration of a pre-6.0 JDBC store (poolName) failed with an Exception:t. | |
Detail | 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, database failure, missing or wrong jar file, non-empty new store was detected. | |
Action | No action is required. | |
040080 | Error: JMSServer "serverName", migration of an old JMS persistent store failed due to wrong jar file (version versionNumber). | |
Detail | A migration of an old JMS persistent store failed because the jarfile for the given version is not right. | |
Action | Contact customer service. | |
040082 | Error: JMSServer "serverName", JMS JDBC I/O failure (t) during migration of old JMS persistent store:poolName. | |
Cause | Database failure | |
Action | Re-start the server. Contact your DBA if the problem persists. | |
040083 | Info: JMSServer "serverName", count JMS messages were successfully migrated from an old store into store: poolName. | |
Action | No action is required. | |
040084 | Error: JMSServer "serverName", failed to migrate JMS durable subscribers in store: poolName for Topic:topicName. | |
Detail | 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 | Incomplete configuration | |
Action | Add the topic in the configuration file, and re-start the server. | |
040085 | Error: JMSServer "serverName", failed to migrate JMS messages in store: poolName for Queue:queueName. | |
Detail | There are JMS messages in the old store for queue queueName, but the queue is not configured in the new store. As a result, migration failed. | |
Cause | Incomplete configuration | |
Action | Add the queue in the configuration file, and re-start the server. | |
040086 | Info: JMSServer "serverName", count JMS message references were successfully migrated from an old store into store: poolName. | |
Action | No action is required. | |
040087 | Info: JMSServer "serverName", cannot migrate old JMS messages and durable subscribers into a non-empty store:poolName. | |
Action | Clean up the store and re-start the server. | |
040088 | Error: JMSServer "serverName", JMS Failed to find or instantiate weblogic.jms.server.upgrade.UpgradeHelperImpl in jar file:jarFile. The actual exception is e. | |
Detail | When migrating old JMS messages from earlier releases, failed to find the jarfile jarFile, 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, is placed in the wrong directory, or does not contain the required classes. | |
Action | Put the correct jarfile in the right place, and make sure it contains weblogic.jms.server.upgrade.UpgradeHelperImpl. Contact BEA customer support if the problem persists. | |
040089 | Info: JMSServer "serverName", JMS messages in store (poolName) were migrated from version versionNumber to 600. | |
040090 | Info: Deployed arg0 default connection factories}. | |
Detail | arg0 default connection factories were deployed on this WLS Server. | |
Cause | This message indicates the number of default connection factories deployed while processing the configuration file. | |
Action | No action required. | |
040091 | Alert: JMSServer "arg0", an error occurred while testing to see if the current operation was transactional, arg1. The current operation is aborted. | |
Cause | Unknown. | |
040092 | Info: JMSServer "serverName", an old store (poolName) of version versionNumber was detected, but has already been successfully migrated previously. | |
Action | If you do not want to see this message anymore, make sure that you do not need any data in the old database tables and remove the old tables from the database. | |
040093 | Alert: JMSServer "serverName", the reply destination (replyToDestName) of messages was not found in the same JMS server during migrating a pre-6.0 store (poolName). | |
Detail | During migrating messages in a pre-6.0 JMS store, the reply destination given by getJMSReplyTo() was not found in the same JMSServer. 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, configured on a different server, or is a foreign destination. | |
Action | Check configuration file. | |
040094 | Error: JMSServer "serverName", migration of a pre-6.0 JDBC store (poolName) failed with Exception:t. | |
Detail | Migration of an old JDBC store failed. Check previous log messages for details. | |
Cause | Inadequate configuration, missing or wrong jar file, non-empty new store was detected. | |
Action | Check previous log messages for details and act accordingly. | |
040095 | Alert: JMSServer "server", store I/O failure, t. | |
Detail | If the associated message(s) were involved in a transaction the transaction is usually rolled back. | |
Cause | Out of file space, disk failure, database failure. | |
Action | Restart database if applicable, restart JMS. | |
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. | |
Detail | This message occurs if a JMS store files length is detected to be wrong during startup. This could occur due to disk corruption or due to an abnormal shutdown of the server. | |
Cause | Out of file space, disk corruption, abnormal shutdown. | |
Action | Check for disk corruption or out of file space. | |
040097 | Info: JMSServer "serverName", store (poolName) migration is done and the old tables can be removed (see drop_serverName_oldtable.ddl). | |
Detail | Migration of the store has been successfully done. The old tables can be removed by running Utils.Schema on the given ddl file. | |
Action | Run the Utils.Schema utility on the DDL file in the current directory to remove the old database tables. | |
040098 | Error: JMSServer "serverName", partial migration of store (poolName) was found but the old tables were missing during re-try. | |
Detail | Migration of the store has been attempted but failed. However, the old tables were missing when another migration was attempted. | |
Action | Restore the old tables from the backup and start the server. | |
040099 | Alert: JMSServer "serverName", the old tables were found in the database (poolName), but migration is skipped since it is disabled in the configuration. | |
Detail | For internal use only. | |
040100 | Info: JMSServer "serverName", Topic: name in the old properties file is not configured in the new configuration (store poolName). | |
Detail | JMS store upgrade found an old topic that is not configured in the new configuration. | |
040101 | Info: JMSServer "serverName", Queue: name in the old properties file is not configured in the new configuration (store poolName). | |
Detail | JMS store upgrade found an old Queue that is not configured in the new configuration. | |
040102 | Info: JMSServer "serverName", Topic: name in the old properties file is configured as a Queue in the new configuration (store poolName). | |
Detail | JMS store upgrade found an old topic that is configured as a queue in the new configuration. | |
040103 | Info: JMSServer "serverName", Queue: name in the old properties file is configured as a Topic in the new configuration (store poolName). | |
Detail | JMS store upgrade found an old Queue that is configured as a Topic in the new configuration. | |
040104 | Info: JMSServer "serverName", count durable subscribers for Topic: name in store poolName were not migrated. | |
Detail | JMS store upgrade did not migrate some of the durable subscribers due to configruation changes. | |
Cause | Configuration change. | |
040105 | Info: JMSServer "serverName", count messages for topic: name in store poolName were not migrated. | |
Detail | JMS store upgrade did not migrate some of the messages in a topic due to configruation changes. | |
Cause | Configuration change. | |
040106 | Info: JMSServer "serverName", count persistent messages for queue: name in store poolName were not migrated. | |
Detail | JMS store upgrade did not migrate some of the messages in a queue due to configruation changes. | |
Cause | Configuration change. | |
040107 | Info: Undeployed arg0 default connection factories}. | |
Detail | arg0 default connection factories were undeployed on this WLS Server. | |
Cause | This message indicates the number of default connection factories undeployed. | |
Action | No action required. | |
040108 | Info: User connection factory "arg0" is started. | |
Action | No action required. | |
040109 | Info: JMSServer "arg0" is started. | |
Action | No action required. | |
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. | |
Action | Use a newer version of JMS to read the store. | |
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 | |
Cause | A corrupted JMS file store. | |
Action | None. Corrupted blocks are ignored except for this log message. | |
040112 | Alert: 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. | |
040113 | Info: JMSServer "server", Opening file store "storeName" in directory "dirName". Starting scan of numFiles files} totalling numBytes bytes. | |
Detail | A JMS server has opened its persistent file store and is about to scan its contents for messages. | |
040114 | Info: JMSServer "server", Finished scan of file store "storeName" in directory "dirName". Found numRecords records} totalling numBytes bytes. | |
Detail | 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 number of 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. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|