IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
CYNG Messages: Global Publish Server
The following messages relate to the Global Publish Server. All such messages have IDs in the range CYNG0001E to CYNG0127E.
- CYNG0001E: The Global Publish Server cannot determine whether the database is DB2 or Oracle.
- CYNG0002E: The Global Publish Server was unable to establish a database connection.
- CYNG0003I: The Global Publish Server's DbConnectionPool monitoring thread is awake and running.
- CYNG0004W: The Global Publish Server's monitoring thread in the database connection pool is replacing an inactive connection.
- CYNG0005E: The Global Publish Server's DbConnectionPool monitoring thread was unable to replace an inactive connection.
- CYNG0006W: The Global Publish Server's DbConnectionPool monitoring thread is reclaiming a hung connection.
- CYNG0007E: The Global Publish Server's DbConnectionPool monitoring thread was unable to reclaim a hung connection.
- CYNG0008E: An exception occurred while attempting to get a database connection from the pool.
- CYNG0009E: An exception occurred while attempting to return a database connection to the pool.
- CYNG0010E: The Global Publish Server was unable to open a Global Publish Server properties file.
- CYNG0011E: The Global Publish Server was unable to determine the IP address to listen on.
- CYNG0012E: The Global Publish Server was unable to determine the port number to listen on.
- CYNG0013E: The Global Publish Server was unable to determine the component ID to register with the Kernel.
- CYNG0014E: The Global Publish Server was unable to determine the socket backlog value from the properties file.
- CYNG0015E: The Global Publish Server was unable to determine the connection pool size value from the properties file.
- CYNG0016E: The Global Publish Server was unable to determine the JDBC driver name from the system environment.
- CYNG0017E: The Global Publish Server was unable to determine the database URL from the system environment.
- CYNG0018E: The Global Publish Server was unable to determine the database user from the system environment.
- CYNG0019E: The Global Publish Server was unable to determine the database password from the system environment.
- CYNG0020E: The Global Publish Server was unable to determine the value of the backup thread timer from the properties file.
- CYNG0021E: The Global Publish Server was unable to determine the value of the cleanup thread timer from the properties file.
- CYNG0022E: The Global Publish Server was unable to determine the value of the dequeueing thread timer from the properties file.
- CYNG0023E: The Global Publish Server was unable to determine the value of the sampling thread timer from the properties file.
- CYNG0024E: The Global Publish Server was unable to determine the value for the token resolution timeout from the properties file.
- CYNG0025E: The Global Publish Server was unable to determine the value of the orphan resolution timeout from the properties file.
- CYNG0026E: The Global Publish Server was unable to determine the value of the thread end timeout from the properties file.
- CYNG0027E: The Global Publish Server was unable to determine the value of the resolved transaction timeout from the roperties file.
- CYNG0028E: The Global Publish Server was unable to determine the value of the insert batch size from the properties file.
- CYNG0029E: The Global Publish Server was unable to determine the value of the maximum socket writes from the properties file.
- CYNG0030E: The Global Publish Server was unable to determine the value of the write timeout from the properties file.
- CYNG0031I: The Global Publish Server successfully started.
- CYNG0032E: An error occurred while attempting to start the Global Publish Server.
- CYNG0033E: An error occurred while attempting to stop the Global Publish Server.
- CYNG0034E: An error occurred while attempting to change the Global Publish Server log level.
- CYNG0035E: An error occurred while attempting to ping the Global Publish Server.
- CYNG0036E: An error occurred while attempting to run dumpState against the Global Publish Server.
- CYNG0037E: An error occurred while attempting to contact the Kernel.
- CYNG0038E: The system was unable to create a proxy object to join the Kernel.
- CYNG0039E: The Global Publish Server was unable to join the Kernel as a result of an incorrectly specified IP address.
- CYNG0040E: The Global Publish Server was able to create a proxy object, but it failed to join the Kernel.
- CYNG0041E: The Global Publish Server was unable to start a server socket.
- CYNG0042W: The Global Publish Server is attempting to process a thread end event for an unknown thread.
- CYNG0043W: The Global Publish Server is attempting to process a RequestRecord event for an unknown thread.
- CYNG0044E: An exception was encountered while the Global Publish Server was attempting to process a RequestRecord event.
- CYNG0045I: Token Token is timing out as a result of a parent call without a child call.
- CYNG0046I: Token Token is timing out as a result of a child call without a parent call.
- CYNG0047I: Token Token is timing out because a missing Global Publish Server thread end event is missing.
- CYNG0048E: An exception was caught while the Global Publish Server was attempting to restore data from the last database backup image.
- CYNG0049I: The Global Publish Server was initialized with data stored in the database. The Token map size is size1, and the Thread map size is size2.
- CYNG0051E: The Global Publish Server encountered an exception while attempting to retrieve a request record from the in-memory cache.
- CYNG0052I: The Global Publish Server has mapped in-flight tokens tokenList to permanent tokens returnList.
- CYNG0053I: A stop request was received. The Global Publish Server backs up its information to the database.
- CYNG0054E: The Global Publish Server caught an exception while attempting to back up the Token map as part of a standard shutdown.
- CYNG0055E: The Global Publish Server caught an exception while attempting to back up the Thread Map as part of a standard shutdown.
- CYNG0056I: The Global Publish Server successfully backed up data to the database.
- CYNG0057E: The Global Publish Server caught an exception while attempting a graceful shutdown.
- CYNG0058I: Shutdown of the Global Publish Server completed successfully.
- CYNG0059I: The Dequeueing Thread started.
- CYNG0060I: The Dequeueing Thread is now attempting to dequeue count records.
- CYNG0061I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsInvokeStart record: processGpsInvokeStart server server id, thread thread id, token token.
- CYNG0062I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsInvokeEnd record: processGpsInvokeEnd server server id, thread thread id, token token, star time startTime.
- CYNG0063I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsReceiveStart record: processGpsReceiveStart server server id, thread thread id, token token, start time startTime.
- CYNG0064I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsReceiveEnd record: processGpsReceiveEnd server server id, thread thread id, token token, start time startTime.
- CYNG0065I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsPutStart record: processGpsPutStart server server id, thread thread id, token token, start time startTime.
- CYNG0066I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsPutEnd record: processGpsPutEnd server server id, thread thread id, token token, start time startTime.
- CYNG0067I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsGetStart record: processGpsGetStart server server id, thread thread id, token token, start time startTime.
- CYNG0068I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsGetEnd record: processGpsGetEnd server server id, thread thread id, token token, start time startTime.
- CYNG0069I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsGetEnd record: processRequestRecord server server id, thread thread id, start time: startTime.
- CYNG0070I: The Global Publish Server's Dequeueing Thread is attempting to process a gpsGetEnd record: processThreadEnd server server id, thread thread id, start time startTime.
- CYNG0071I: Dequeueing took number milliseconds.
- CYNG0072E: The Global Publish Server received a corrupt message from the Publish Server.
- CYNG0073I: The Global Publish Server's Dequeueing Thread is exiting now.
- CYNG0074I: The Global Publish Server's Dequeueing Threadhas was killed as a result of a user action.
- CYNG0075I: The BackupThread started.
- CYNG0076E: An error occurred while trying to drop the table GPSTOKEN from the database.
- CYNG0077E: An error occurred while trying to drop the table GPSTOKENINFO from the database.
- CYNG0078E: An error occurred while trying to drop the table GPSUOE from the database.
- CYNG0079E: An error occurred while trying to drop the table GPSUOEINFO from the database.
- CYNG0080E: An error occurred while trying to drop the table GPSREQUEST from the database.
- CYNG0081E: An exception was caught while attempting to create the tables in which the Global Publish Server backs up its data structures.
- CYNG0082I: BackupThread stopped.
- CYNG0083I: BackupThread been killed as a result of user action.
- CYNG0084E: An error occurred while attempting to back up the Token map.
- CYNG0085E: Backing up the Token map took number milliseconds.
- CYNG0086E: An error occurred while attempting to back up the Token map.
- CYNG0087E: An error occurred while attempting to back up the Thread map.
- CYNG0088I: Backing up the Thread map took number milliseconds.
- CYNG0089E: An error occurred while attempting to back up the Thread map.
- CYNG0090I: The Global Publish Server's CleanupThread started.
- CYNG0091I: The Global Publish Server's CleanupThread declined to prune thread threadId on server ServerId because the Publish Server had not yet been notified of sampling values.
- CYNG0092I: Token token is fully resolved, so the system is removing it from memory.
- CYNG0093I: Thread ThreadId on server ServerId has no unresolved tokens, so the system is removing it from memory.
- CYNG0094I: The Global Publish Server's CleanupThread took number milliseconds.
- CYNG0095E: An exception was caught during the CleanupThread operation while attempting clean up the Token and Thread maps.
- CYNG0096I: The Global Publish Server's CleanupThread finished executing.
- CYNG0097I: The Global Publish Server's CleanupThread was killed.
- CYNG0098I: The Global Publish Server's SamplingThread started.
- CYNG0099I: The Global Publish Server's SamplingThread could not find information in memory for a thread end event.
- CYNG0100I: During a sampling check, the Global Publish Server failed to find a linked thread. It is sending it back to queue.
- CYNG0101I: The Global Publish Server is notifying Publish Server componentId that thread threadId on server serverId: boolean
- CYNG0102E: An exception was caught during SamplingThread operation.
- CYNG0103I: SamplingThread execution took number milliseconds.
- CYNG0104E: An exception was caught during SamplingThread operation.
- CYNG0105I: SamplingThread is exiting.
- CYNG0106I: SamplingThread was killed as a result of user action.
- CYNG0107I: The Global Publish Server's MonitoringThread started.
- CYNG0108I: BackupThread is dead. The Global Publish Server will start a new one.
- CYNG0109I: The Global Publish Server is unable to contact or stop BackupThread, which is null or does not exist.
- CYNG0110I: CleanupThread is dead. The Global Publish Server will start a new one.
- CYNG0111I: The Global Publish Server is unable to contact or stop CleanupThread, which is null or does not exist.
- CYNG0112I: DequeueingThread is dead. The Global Publish Server will start a new one.
- CYNG0113I: The Global Publish Server is unable to contact or stop DequeueingThread, which is null or does not exist.
- CYNG0114I: SamplingThread is dead. The Global Publish Server will start a new one.
- CYNG0115I: The Global Publish Server is unable to contact or stop SamplingThread, which is null or does not exist.
- CYNG0116E: An exception was caught during MonitorThread operation.
- CYNG0117I: SamplingThread is exiting.
- CYNG0118I: The Global Publish Server's SamplingThread was killed by user action.
- CYNG0119E: A client has attempted to connect to the Global Publish Server and failed as a result of a network error.
- CYNG0120I: Publish Server psId connected to the Global Publish Server.
- CYNG0121I: An exception occurred in the Socket Listener.
- CYNG0122E: The Global Publish Server was unable to open a server socket on port Port.
- CYNG0123I: A VEGateway connected to the Global Publish Server.
- CYNG0124E: Communication between the front-end and the Global Publish Server failed.
- CYNG0125E: Communication between the front-end and the Global Publish Server failed.
- CYNG0126W: A format exception occurred while parsing property propName. The default value is being used.
- CYNG0127E: An exception occurred while the Global Publish Server was sending data to the Archive Agent.
Parent topic:
System Messages for ITCAM Agent for WebSphere Applications