IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1
CYNP Messages: Publish Server
The Publish Server is a Java component of the Managing Server that collects and publishes data. All such messages have IDs in the range CYNP0001E to CYNP0088W.
- CYNP0001E: An exception occurred while creating AaGateway.
- CYNP0002E: An exception occurred while creating PsGateway.
- CYNP0003I: The Publish Server is establishing a relationship between probe probe and Publish Server psId.
- CYNP0004E: An exception occurred while registering the Publish Server-data collector relationship with the Kernel.
- CYNP0005E: An exception occurred while creating and starting PMITask for probe octigateID.
- CYNP0006E: The Publish Server got a GC End event before getting a GC Start event for probe execCtx.
- CYNP0007W: The Publish Server got a GC Start event when there is already a GC Start event pending for execution context execCtx.
- CYNP0008W: The Publish Server failed sending data to the Archive Agent.
- CYNP0009E: An exception occurred processing Method Record.
- CYNP0010W: The Publish Server is removing the execution context for the request type requestType from the corrupted requests.
- CYNP0011W: The Publish Server is dropping the incoming record for execution context execCtx because this thread is corrupted.
- CYNP0012E: An exception occurred while processing RequestLevelRecord.
- CYNP0013W: The Publish Server dropped a record for the execution context execCtx.
- CYNP0014W: An exception occurred while sending the request to PsGateway.
- CYNP0015W: There is a missing main request for the nested request with type type on thread execCtx.
- CYNP0016W: There is a missing method trace for the end of the request on thread execCtx.
- CYNP0017W: The Publish Server got a new request when there was already another request pending on thread execCtx
- CYNP0018W: Matching Start is null for the request type type on thread execCtx.
- CYNP0019I: RequestRecord is corrupted. The matching request type is matchingrequesttype. The matching stack depth is matchingStackDepth. The current request type is currentRequestType. The current stack depth is currentStackDepth.
- CYNP0020W: The start request is missing for the method trace on thread execCtx.
- CYNP0021I: The Publish Server is inferring a request for method methodId.
- CYNP0022E: The Publish Server could not find the CLASSLOAD record corresponding to the method with ID methodId.
- CYNP0023I: The maximum number of records per request has been reached. So the Publish Server dropped noofrecords records for execution context execCtx.
- CYNP0024I: The Publish Server is deleting a request for thread of ID threadId, because the time limit of timeLimit has elapsed.
- CYNP0025I: The time difference between the Publish Server and probe probeId is timeDiffmilliseconds.
- CYNP0026E: A exception occurred while getting the time for probe probeId.
- CYNP0027W: The Publish Server could not retrieve the method detail corresponding to the method with ID methodId for the execution context execCtx.
- CYNP0028W: An exception occurred while parsing method of ID methodId for the execution context execCtx.
- CYNP0029E: The Publish Server was unable to load the system configuration from the Kernel.
- CYNP0030E: The Publish Server was unable to start ProbeStatsManager.
- CYNP0031E: The Publish Server was unable to start ResourceStatsManagerTimer.
- CYNP0032E: The Publish Server was unable to start AVMDataSource.
- CYNP0033E: The Publish Server was unable to start AAProducerResetTimer.
- CYNP0034I: The Publish Server daemon is listening on the socket at host host on port port.
- CYNP0035E: The Publish Server was unable to start. The socket is already bound to port port.
- CYNP0036E: An exception occurred when the Message Dispatcher was leaving the Kernel.
- CYNP0037I: The Publish Server is shutting down and leaving the Kernel service at host host on port port.
- CYNP0038E: An exception occurred while accepting the connection from the data collector.
- CYNP0039E: An exception occurred while reading INIT records from the data collector.
- CYNP0040W: An unknown initialization data type of recType was sent to the Publish Server.
- CYNP0041E: The socket attached to the Publish Server threw an exception. data, probeinfo
- CYNP0042E: An exception occurred while the Publish Server was reading data from the socket. data, probeinfo
- CYNP0043E: An exception occurred while the Publish Server was closing the data socket. data, probeinfo
- CYNP0044I: The Publish Server is shutting down and leaving the Kernel service serviceId.
- CYNP0045W: The Publish Server received an unexpected query of type queryType.
- CYNP0046E: The Publish Server got a null system configuration from the Kernel.
- CYNP0047E: The Publish Server received wrong record data for the packet header record record1, record2, record3.
- CYNP0048E: An exception occurred with the Publish Server during communication with probe probeId.
- CYNP0049E: A communication time out occurred when the probe was communicating with the Publish Server.
- CYNP0050I: An unexpected exception occurred with the socket of data collector probeId.
- CYNP0051I: An unexpected exception occurred with the socket of data collector probeId.
- CYNP0052E: An exception occurred while the Publish Server was being stopped.
- CYNP0053W: The Publish Server was unable to figure out the mod level from the request of the data collector, so it is using the default mod level.
- CYNP0054E: An exception occurred while the Publish Server was sending data to the Archive Agent.
- CYNP0055W: A format exception occurred while parsing property propName. The default value defaultValue is being used.
- CYNP0056W: An exception occurred while getting PMI data from the administrative server adminServer at port port of node nodeName of application server appserverName.
- CYNP0057E: An exception occurred while computing portal statistics in the Publish Server.
- CYNP0058E: The Publish Server was unable to get the command agent for probe probeId.
- CYNP0059E: An exception occurred while getting the time difference for the probe probeId.
- CYNP0060E: An exception occurred when the Publish Server was stopped.
- CYNP0061E: An exception occurred when the Publish Server was restarted.
- CYNP0062W: The Archive Agent buffer was exceeded.
- CYNP0063E: An exception occurred while communicating with the Kernel to look up the Archive Agent.
- CYNP0064E: An exception occurred while the Publish Server was communicating with the Archive Agent.
- CYNP0065E: An exception occurred while the timeout checker was pruning active requests in the Publish Server.
- CYNP0066E: An exception occurred when the Publish Server was started.
- CYNP0067I: The Publish Server received an availability notification from the Kernel regarding the status of data collector probeId. The status is staus.
- CYNP0068I: The Publish Server is closing a socket that is not valid for data collector probeId.
- CYNP0069W: The socket is still valid with data collector probeID, so the Publish Server is not closing the socket.
- CYNP0070W: The Publish Server got a GC End event without getting GC Start event execCtx.
- CYNP0071I: The Publish Server is registering probe probeId with DCAvailabilityChecker.
- CYNP0072I: An exception occurred while registering probe probeId with DCAvailabilityChecker.
- CYNP0073I: The Publish Server is unregistering probe probeId with DCAvailabilityChecker.
- CYNP0074E: An exception occurred in ProbeStatsManager.
- CYNP0075I: The Publish Server is creating an IMSComplex for complex.
- CYNP0076I: Probe probeId has joined complex complex.
- CYNP0077I: Probe probeId has left complex complex.
- CYNP0078I: The request is corrupted for message of ID msgId.
- CYNP0079W: SNMP Agent is not available.
- CYNP0080E: An exception occurred while the Publish Server was sending SNMP Trap.
- CYNP0081W: Email Engine is not available.
- CYNP0082E: An exception occurred while the Publish Server was sending Email Trap.
- CYNP0083W: The Publish Server is deleting the request of message ID msgId because the time limit of timeout has elapsed.
- CYNP0084W: The Publish Server is deleting the Global Publish Server request of message ID msgId because the time limit of timeout has elapsed.
- CYNP0085W: The Publish Server received a response of null for SMF Info for the probe probeId.
- CYNP0086E: The Publish Server received a response of null for SMFDaily Service for the probe probeIdn.
- CYNP0087E: An exception occurred while parsing SMF Info from the probe probeId.
- CYNP0088W: The Publish Server dropped a record for the execution context execCtx.
Parent topic:
System Messages for ITCAM Agent for WebSphere Applications