Guest

Preview Tool

Cisco Bug: CSCvs05022 - EAAS log does not show "GET_QUEUED_TASK_REQ" and "GET_QUEUED_TASK_RESP" with proper name

Last Modified

Nov 26, 2019

Products (1)

  • Cisco Enterprise Chat and Email

Known Affected Releases

12.0(1) 12.5(1)

Description (partial)

Symptom:
The EAAS log has to show the GET_QUEUED_TASK_REQ and GET_QUEUED_TASK_RESP with proper name. The same as we have for all other MR message types.

Current log With INFO trace level for GET_QUEUED_TASK_REQ and GET_QUEUED_TASK_RESP:

2019-09-20 20:19:33.589 GMT+0000 <@> INFO <@> [8833:RMI TCP Connection(4558)-192.168.33.56] <@> ProcessId:1360 <@> PID:1 <@> UID:12 <@> UserSessionId: <@> com.ipcc.arm.MRLogger <@> logOutgoingMessage() <@> Message sent from EAAS -> 0 0 0 24 0 0 4 89 0 0 0 2 0 0 0 3 0 0 0 0 0 0 19 -112 0 0 19 -119 0 0 0 8 <@>
2019-09-20 20:19:33.605 GMT+0000 <@> INFO <@> [80:Thread-15] <@> ProcessId:1360 <@> PID:1 <@> UID:12 <@> UserSessionId: <@> com.ipcc.arm.MRLogger <@> logIncomingMessage() <@> Message recieved in EAAS -> 0 0 0 12 0 0 4 90 0 0 0 2 0 0 0 3 0 0 0 -32 <@>

Should be:

2019-09-20 20:19:33.589 GMT+0000 <@> INFO <@> [8833:RMI TCP Connection(4558)-192.168.33.56] <@> ProcessId:1360 <@> PID:1 <@> UID:12 <@> UserSessionId: <@> com.ipcc.arm.MRLogger <@> logOutgoingMessage() <@> MSG_TYP_GET_QUEUED_TASK_REQ -> 0 0 0 24 0 0 4 89 0 0 0 2 0 0 0 3 0 0 0 0 0 0 19 -112 0 0 19 -119 0 0 0 8 <@>
2019-09-20 20:19:33.605 GMT+0000 <@> INFO <@> [80:Thread-15] <@> ProcessId:1360 <@> PID:1 <@> UID:12 <@> UserSessionId: <@> com.ipcc.arm.MRLogger <@> logIncomingMessage() <@> MSG_TYP_GET_QUEUED_TASK_RESP -> 0 0 0 12 0 0 4 90 0 0 0 2 0 0 0 3 0 0 0 -32 <@>

Conditions:
ECE 12.0 and 12.5
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.