Explanation: This is a critical REP value which must be present for proper program function.
User response: None.
Explanation: This is a critical REP value which must be correct for proper program function.
User response: None.
Explanation: Exception caught during Aggregation Proxy init() function.
User response: None.
Explanation: TAI principal object received from Http request object is null.
User response: None.
Explanation: If all XDMS' xcap-caps response are empty, system does not have meaningful content.
User response: None.
Explanation: XDMS does not support directory auid Aggregation Proxy requested. URL information used for code location.
User response: None.
Explanation: The response from the XDMS timed out. URL information used for problem determination.
User response: None.
Explanation: Critical error in Aggregation Proxy auid/domain mapping.
User response: None.
Explanation: Aggregation Proxy does not have an XDMS for this specific user domain. Cannot serve user.
User response: None.
Explanation: Unknown exception caught in Aggregation Proxy servlet.
User response: None.
Explanation: Username extracted from TAI principal object is null.
User response: None.
Explanation: A bad HTTP response was received from XDMS for xcapcaps request. Critical error, because XDMS must support xcapcaps.
User response: None.
Explanation: The Aggregation Proxy needs a set of domains which correspond to a set of XDMS servers. This allows domain based routing.
User response: None.
Explanation: Two XDMSes with the same domain cannot support the same AUID.
User response: None.
Explanation: Each XCAPS file returned from an XDMS should have something in it. Otherwise, this is an error.
User response: None.
Explanation: Each directory file returned from an XDMS should have something in it. Otherwise, this is an error.
User response: None.
Explanation: Error adding a new XMDS. Critical error.
User response: None.
Explanation: Bad Http Response code received from XMDS. Critical error.
User response: None.
Explanation: When trying to parse the alarmInterval REP, an exception occurred.
User response: Please check the REP and ensure it is a valid integer.
Explanation: Aggregation Proxy Exception caught in Aggregation Proxy servlet.
User response: None.
Explanation: Exception caught when issuing alarm.
User response: Make sure admin username/password is correct in REP.
Explanation: Error processing XDMS response.
User response: Check and make sure XDMSes are online and can receive XCAP requests.
Explanation: Empty xcap caps returned to client.
User response: Check and make sure XDMSes are online and can receive XCAP cap requests.
Explanation: IOException occurred when writing results to response stream.
User response: Make sure the system has available memory.
Explanation: IOException occurred when processing xcap response from XDMS.
User response: If the problem continues and hinders normal function, restart server.
Explanation: Exception caught while updating route map.
User response: Make sure backend XDMSes are reachable by Aggregation Proxy.