MQWB2001I: A connection to the queue manager <insert_0> has been made successfully.
Explanation
The application was able to connect to the specified queue manager.
Response
No action.
MQWB2002E
MQWB2002E: The request could not be completed because of a problem with the web application server.
Explanation
The request could not be completed for reasons that are beyond the control of the HTTP client. This could be caused by a problem connecting to the queue manager.
Response
Contact the IBM service team to resolve the problem.
MQWB2003E
MQWB2003E: The request could not be completed due to an internal web application server error.
Explanation
The request could not be completed for reasons that are beyond the control of the HTTP client. This could be caused by a problem connecting to the queue manager.
Response
Contact the IBM service team to resolve the problem.
MQWB2004E
MQWB2004E: The body of the request could not be parsed.
Explanation
The body of the HTTP request could not be parsed, possibly due to bad formatting of the data.
Response
Ensure the request contains valid data that matches the data format expected for the specified HTTP resource, HTTP method, and HTTP content type.
MQWB2005E
MQWB2005E: The <insert_0> HTTP method is not allowed for the <insert_1> resource request.
Explanation
A recognized resource request has been made, but it does not support the specified method.
Response
Update the request to specify a different resource or specify a HTTP method that is supported for the request.
MQWB2006E
MQWB2006E: The requested resource is no longer available.
Explanation
The requested resource referred to in the request, could not be found. This may be because a resource which previously existed has been deleted.
Response
No user action.
MQWB2007E
MQWB2007E: The requested resource could not be found.
Explanation
A valid request for a resource was received but the resource does not exist.
Response
Update the request to specify a valid resource and retry.
MQWB2008E
MQWB2008E: The request contains data that is too large to be handled by the server.
Explanation
The server was unable to process the request because the data being passed to it is too large.
Response
Resubmit the request with a smaller request body.
MQWB2009E
MQWB2009E: An attempt to complete some part of the request has timed out.
Explanation
The request was accepted by system but could not be completed within a reasonable time.
Response
Try resubmitting the request or contact the IBM support team to resolve the problem.
MQWB2010E
MQWB2010E: User is not authenticated.
Explanation
The request for a resource was made by a user who could not be authenticated.
Response
Try resubitting the request with valid credentials such as a userid and password, X.509 certificate or LTPA2 token.
MQWB2011E
MQWB2011E: A request has been received with a media type which cannot be handled by MQ.
Explanation
The request specified a media type that is not supported by MQ.
Response
Resubmit the request with a request body that is formatted in a supported media type.
MQWB2012E
MQWB2012E: A PCF system request to the queue manager failed to return any reponses within the <insert_0> millisecond timeout.
Explanation
The Web tooling made a PCF inquiry to the queue manager but no response was returned within a reasonable amount of time. This could be because the queue manager is under particularly heavy load.
Response
Try resubmitting the request. If this fails, ensure the command server is running on the queue manager. If the queue manager is under heavy load, try increasing the time the Web tooling waits for PCF responses, by setting the PCF_WAIT_TIME_MS property in Liberty.
MQWB2013E
MQWB2013E: <insert_1>: <insert_0>
Explanation
The request failed with an MQ exception.
Response
Check the MQ exception for more details.
MQWB2014A
MQWB2014A: Queue manager <insert_0> created by <insert_1>.
Explanation
A queue manager was created by an authorized user.
Response
No action.
MQWB2015A
MQWB2015A: Queue manager <insert_0> started by <insert_1>.
Explanation
A queue manager was started by an authorized user.
Response
No action.
MQWB2016A
MQWB2016A: Queue manager <insert_0> stopped by <insert_1>.
Explanation
A queue manager was stopped by an authorized user.
Response
No action.
MQWB2017A
MQWB2017A: Queue manager <insert_0> deleted by <insert_1>.
Explanation
A queue manager was deleted by an authorized user.
Response
No action.
MQWB2018E
MQWB2018E: User lacks authority to access resource.
Explanation
The request for a resource was made by a user lacking appropriate authority.
Response
If access to this resource is required for this user, modify the runtime configuration to authorise them.
MQWB2019I
MQWB2019I: <insert_0> level: <insert_1>
Explanation
The level of the identified resource.
Response
No action.
MQWB2020E
MQWB2020E: The <insert_0> property has an unsupported value of <insert_1>.
Explanation
A property has been configured in the mqwebuser.xml file with an unsupported value. This message will be suppressed for the next minute.
Response
Review the documentation for the property in the KnowledgeCentre and set a supported value, or delete the property.
MQWB2021E
MQWB2021E: The web server cannot load a native library used by IBM MQ.
Explanation
The IBM MQ console web server could not load a native library which it needs. The library path is probably incorrect.
Response
Refer to the system administrator.
MQWB2022E
MQWB2022E: <insert_0> is not a valid HTTP method.
Explanation
The specified method is not supported.
Response
Update the request to specify a different resource or specify a HTTP method that is supported for the request.
MQWB2023E
MQWB2023E: Audit error: <insert_0>
Explanation
The IBM MQ console web server failed to create an audit record.
Response
Contact the IBM service team to resolve the problem.