WebSphere brand IBM WebSphere XML Document Management Server, Version 7.0

Messages

GLSA0001E: REP value: {0} not present in servlet initialization.

Explanation: This is a critical REP value which must be present for proper program function.

User response: None.

GLSA0002E: REP value: {0} found to be incorrect during servlet initialization.

Explanation: This is a critical REP value which must be correct for proper program function.

User response: None.

GLSA0003E: Error, exception caught in Aggregation Proxy init() with message value: {0}.

Explanation: Exception caught during Aggregation Proxy init() function.

User response: None.

GLSA0004E: TAI Principal object equals null.

Explanation: TAI principal object received from Http request object is null.

User response: None.

GLSA0005E: All XDMSes returned empty XCAP-CAPS to Aggregation Proxy for XCAP-CAP request.

Explanation: If all XDMS' xcap-caps response are empty, system does not have meaningful content.

User response: None.

GLSA0006E: XDMS server does not support DIRECTORY AUID Aggregation Proxy uses. XDMS error messgage: {0}. URL contains: {1}.

Explanation: XDMS does not support directory auid Aggregation Proxy requested. URL information used for code location.

User response: None.

GLSA0007E: Response from XDMS with URI: {0}, timed out. XDMS may be inactive. URL contains: {1}.

Explanation: The response from the XDMS timed out. URL information used for problem determination.

User response: None.

GLSA0008E: Error in Aggregation Proxy domain mapping. User domain: {0} maps to XDMS domain: {1}, but auid: {2} does not map to XDMS domain: {1}. URI contains: {3}.

Explanation: Critical error in Aggregation Proxy auid/domain mapping.

User response: None.

GLSA0009E: No matching XDMS found for user domain: {0}. URL contains: {1}.

Explanation: Aggregation Proxy does not have an XDMS for this specific user domain. Cannot serve user.

User response: None.

GLSA0010E: Unknown exception caught in Aggregation Proxy servlet. Exception message: {0}. Method name: {1}. Error code returned to client {2}.

Explanation: Unknown exception caught in Aggregation Proxy servlet.

User response: None.

GLSA0011E: Username extracted from TAI Principal object equals null.

Explanation: Username extracted from TAI principal object is null.

User response: None.

GLSA0012E: XDMS with URI: {0} returned a bad/empty xcapcaps for user: {1} with Http Status code: {2}. URL contains: {3}.

Explanation: A bad HTTP response was received from XDMS for xcapcaps request. Critical error, because XDMS must support xcapcaps.

User response: None.

GLSA0013E: There are no XDMS domains configured for the Aggregation Proxy. Aggregation Proxy cannot function.

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.

GLSA0014E: Error while adding XDMS: {0} using admin user: {1}. The domain: {2} already exists in domain mapping for auid: {3}.

Explanation: Two XDMSes with the same domain cannot support the same AUID.

User response: None.

GLSA0015E: Error occurred while merging XCAP files. Empty XCAPS file encountered.

Explanation: Each XCAPS file returned from an XDMS should have something in it. Otherwise, this is an error.

User response: None.

GLSA0016E: Error occurred while merging directory files. Empty directory file encountered.

Explanation: Each directory file returned from an XDMS should have something in it. Otherwise, this is an error.

User response: None.

GLSA0017E: Error adding XDMS with URI: {0}. Requesting user: {1}. Http Status code returned: {2}. URL contains: {3}.

Explanation: Error adding a new XMDS. Critical error.

User response: None.

GLSA0018E: Bad return code, {0}, received from XDMS with URI: {1}. Message body returned: {2}. Request suffix: {3}.

Explanation: Bad Http Response code received from XMDS. Critical error.

User response: None.

GLSA0019E: The Alarm Interval REP is not a valid integer.

Explanation: When trying to parse the alarmInterval REP, an exception occurred.

User response: Please check the REP and ensure it is a valid integer.

GLSA0020E: Exception caught in servlet. Method name: {0}. Exception message: {1}.

Explanation: Aggregation Proxy Exception caught in Aggregation Proxy servlet.

User response: None.

GLSA0021E: Exception caught when issuing alarm. Message: {0}.

Explanation: Exception caught when issuing alarm.

User response: Make sure admin username/password is correct in REP.

GLSA0022E: IOException occurred while processing XDMS response. Return code: {0}, Response body: {1}.

Explanation: Error processing XDMS response.

User response: Check and make sure XDMSes are online and can receive XCAP requests.

GLSA0023E: Error: empty xcap caps cache returned to client.

Explanation: Empty xcap caps returned to client.

User response: Check and make sure XDMSes are online and can receive XCAP cap requests.

GLSA0024E: IOException occurred when writing results to response stream.

Explanation: IOException occurred when writing results to response stream.

User response: Make sure the system has available memory.

GLSA0025E: IOException occurred when processing xcap response from XDMS.

Explanation: IOException occurred when processing xcap response from XDMS.

User response: If the problem continues and hinders normal function, restart server.

GLSA0026E: Exception caught while updating route map. Exception message: {0}.

Explanation: Exception caught while updating route map.

User response: Make sure backend XDMSes are reachable by Aggregation Proxy.




Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.