Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The system has been configured so that bus security is enabled, but administrative security has been disabled. This configuration is inconsistent and the bus is not secure. |
Action | Either enable administrative security or disable bus security. |
Explanation | The supplied user name does not exist, or the password is not valid. |
Action | Ensure that the supplied user name is valid, and that the password is correct. |
Explanation | A client successfully authenticated to the bus. |
Action | None |
Explanation | A client that has not provided credentials has successfully authenticated to the bus. This user can only connect to the bus if the Everyone group is in the bus connector role. |
Action | None |
Explanation | An attempt was made to authenticate using an LTPA token, but the LTPA token was not valid. |
Action | Ensure that clients provide valid LTPA tokens for authentication. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The administrator has updated the authorization policy for the bus. |
Action | None |
Explanation | The user has not been granted the bus connector role for the bus. |
Action | If you want the user have access to the bus, add the user to the connector role for the bus. |
Explanation | A client attempted to connect to the bus without supplying any credentials,and the Everyone group does not have the bus connector role for the bus. |
Action | Ensure that the client provides credentials, or that the Everyone group has access to connect to the bus. |
Explanation | The user is not in the sender role for the destination. |
Action | If you want the user to send messages to the destination, add the user to the sender role for that destination. |
Explanation | The user is not in the receiver role for the destination. |
Action | If you want the user to receive messages from the destination, add the user to the receiver role for that destination. |
Explanation | The user is not in the creator role for the temporary destination prefix. |
Action | If you want the user to create temporary destinations using the temporary destination prefix, add the user to the creator role for the temporary destination prefix. |
Explanation | The user is not in the inquire role for the destination. A user has the inquire role if they are in the sender, receiver or browser role for the destination. |
Action | If the user should have inquire access, add the user to the sender, receiver or browser role. |
Explanation | The user is not in the browser role for the destination. |
Action | If you want the user to send messages to the destination, add the user to the browser role for that destination. |
Explanation | The user is not in the identityAdopter role for the destination. |
Action | If you want the user to assume the identity of other users when sending messages, add the user to the identityAdopter role for that destination. |
Explanation | The user is not in the sender role for the foreign destination. |
Action | If you want the user to send messages to the foreign bus, add the user to the sender role for that foreign bus. |
Explanation | The user is not in the sender role for the relevant temporary destination prefix. |
Action | If you want the user to send messages to the temporary destination, add the user to the sender role for that temporary destination prefix. |
Explanation | The user is not in the inquire role for the relevant temporary destination prefix. Users have the inquire role if they are in the sender, receiver or browser role for the temporary destination prefix. |
Action | If you want the user to have inquire access for the temporary destination prefix, add the user to the sender, receiver or browser role for that temporary destination prefix. |
Explanation | The user is not in the identityAdopter role for the relevant temporary destination prefix. |
Action | If you want the user to assume the identity of other users when sending messages, add the user to the identityAdopter role for that temporary destination prefix. |
Explanation | The user is not in the sender role for the default temporary destination prefix. |
Action | If you want the user to send messages to the temporary destination, add the user to the sender role for the default temporary destination. |
Explanation | The user is not in the inquire role for the relevant temporary destination prefix. Users have the inquire role if they are in the sender, receiver or browser role for the temporary destination prefix. |
Action | If the user should have inquire access add the user to the sender, receiver or browser role for the default destination prefix. |
Explanation | The user is not in the identityAdopter role for the default temporary destination prefix. |
Action | If you want the user to assume the identity of other users when sending messages, add the user to the identityAdopter role for the default temporary destination prefix. |
Explanation | The user is not in the creator role for the default temporary destination prefix. |
Action | If you want the user to create temporary destinations using that prefix, add the user to the creator role for the default temporary destination prefix. |
Explanation | The Everyone group is not in the sender role for the destination. |
Action | If you want anonymous users to send messages to the destination add the Everyone group to the sender role for that destination. |
Explanation | The Everyone group is not in the receiver role for the destination. |
Action | If you want anonymous users to receive from the destination, add the Everyone group to the receiver role for that destination. |
Explanation | The Everyone group is not in the creator role for the temporary destination prefix. |
Action | If you want anonymous users to create temporary destinations using that prefix, add the Everyone group to the creator role for that temporary destination prefix. |
Explanation | The Everyone group is not in the inquire role for the destination. |
Action | If anonymous users should have inquire access, add the Everyone group to the sender, receiver or browser role. |
Explanation | The Everyone group is not in the browser role for the destination. |
Action | If you want anonymous users to send messages to the destination, add the Everyone group to the browser role for that destination. |
Explanation | The Everyone group is not in the identityAdopter role for the destination. |
Action | If you want anonymous users to assume the identity of other users when sending messages, add the Everyone group to the identityAdopter role for that destination. |
Explanation | The Everyone group is not in the sender role for the foreign destination. |
Action | If you want anonymous users to send messages to the foreign bus, add the Everyone group to the sender role for that foreign bus. |
Explanation | The Everyone group is not in the creator role for the default temporary destination prefix. |
Action | If you want anonymous users to create temporary destinations using the default temporary destination prefix then add the Everyone group to the creator role for the default temporary destination prefix. |
Explanation | The Everyone group is not in the sender role for the relevant temporary destination prefix. |
Action | If you want anonymous users to send messages to the temporary destination, add the Everyone group to the sender role for that temporary destination prefix. |
Explanation | The Everyone group is not in the sender role for the default temporary destination prefix. |
Action | If you want anonymous users to send messages to the temporary destination, add the Everyone group to the sender role for the default temporary destination. |
Explanation | The Everyone group is not in the identityAdopter role for the relevant temporary destination prefix. |
Action | If you want anonymous users to assume the identity of other users when sending messages, add the Everyone group to the identityAdopter role for that temporary destination prefix. |
Explanation | The Everyone group is not in the identityAdopter role for the default temporary destination prefix. |
Action | If you want anonymous users to assume the identity of other users when sending messages, add the Everyone group to the identityAdopter role for the default temporary destination prefix. |
Explanation | The Everyone group is not in the inquire role for the relevant temporary destination prefix. Users have the inquire role if they are in the sender, receiver or browser role for the temporary destination prefix. |
Action | If you want anonymous users to have inquire access, add the Everyone group to the sender, receiver or browser role for that temporary destination prefix. |
Explanation | The Everyone group is not in the inquire role for the relevant temporary destination prefix. Users have the inquire role if they are in the sender, receiver or browser role for the temporary destination prefix. |
Action | If you want anonymous users to have inquire access, add the Everyone group to the sender, receiver or browser role for the default destination prefix. |
Explanation | The bus has been configured with an audit mode which is not valid. The valid audit modes are all, none, or failure. |
Action | Ensure that you set a valid mode for the audit.bus.authentication custom property in the bus configuration. |
Explanation | The user is not in the identity adopter role for the foreign destination. |
Action | If you want the user to assume the identity of another user when sending messages to the foreign bus, add the user to the identity adopter role for that foreign bus. |
Explanation | The Everyone group is not in the identity adopter role for the foreign destination. |
Action | If you want anonymous users to adopt another user's identity when sending messages to the foreign bus, add the Everyone group to the identity adopter role for that foreign bus. |
Explanation | The Server group is not in the sender role for the foreign destination. |
Action | If you want the servers to send messages to the foreign bus, add the Server group to the sender role for that foreign bus. |
Explanation | The Server group is not in the identity adopter role for the foreign destination. |
Action | If you want servers to adopt the identity of another user when sending messages to the foreign bus, add the Server group to the identity adopter role for that foreign bus. |
Explanation | The Server group is not in the creator role for the default temporary destination prefix. |
Action | If you want servers to create temporary destinations using the default temporary destination prefix, add the Server group to the creator role for the default temporary destination prefix. |
Explanation | The Server group is not in the sender role for the relevant temporary destination prefix. |
Action | If you want servers to send messages to the temporary destination, add the Server group to the sender role for that temporary destination prefix. |
Explanation | The Server group is not in the sender role for the default temporary destination prefix. |
Action | If you want servers to send messages to the temporary destination, add the Server group to the sender role for the default temporary destination. |
Explanation | The Server group is not in the identityAdopter role for the relevant temporary destination prefix. |
Action | If you want servers to assume the identity of other users when sending messages, add the Server group to the identityAdopter role for that temporary destination prefix. |
Explanation | The Server group is not in the identityAdopter role for the default temporary destination prefix. |
Action | If you want servers to assume the identity of other users when sending messages, add the Server group to the identityAdopter role for the default temporary destination prefix. |
Explanation | The Server group is not in the inquire role for the relevant temporary destination prefix. Users have the inquire role if they are in the sender, receiver or browser role for the temporary destination prefix. |
Action | If you want servers to have inquire access, add the Server group to the sender, receiver or browser role for that temporary destination prefix. |
Explanation | The Server group is not in the inquire role for the relevant temporary destination prefix. Users have the inquire role if they are in the sender, receiver or browser role for the temporary destination prefix. |
Action | If you want servers to have inquire access, add the Server group to the sender, receiver or browser role for the default destination prefix. |
Explanation | The Server group is not in the creator role for the temporary destination prefix. |
Action | If you want servers to create temporary destinations using that prefix, add the Server group to the creator role for that temporary destination prefix. |
Explanation | The Server group is not in the bus connector role for the bus. |
Action | If you want servers to connect to the bus, add the Server group to the bus connector role. |
Explanation | The Server group is not in the sender role for the destination. |
Action | If you want servers to send messages to the destination, add the Server group to the sender role for that destination. |
Explanation | The Server group is not in the receiver role for the destination. |
Action | If you want servers to receive messages from the destination, add the Server group to the receiver role for that destination. |
Explanation | The Server group is not in the inquire role for the destination. |
Action | If you want servers to have inquire access, add the Server group to the sender, receiver or browser role. |
Explanation | The Server group is not in the browser role for the destination. |
Action | If you want servers to send messages to the destination, add the Server group to the browser role for that destination. |
Explanation | The Server group is not in the identityAdopter role for the destination. |
Action | If you want servers to assume the identity of other users when sending messages, add the Server group to the identityAdopter role for that destination. |
Explanation | There has been an unsuccessful attempt to obtain a list of users in the user repository for the bus. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | There has been an unsuccessful attempt to obtain information about a user from the user repository for the bus. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | There has been an unsuccessful attempt to obtain a list of groups in the user repository for the bus. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | There has been an unsuccessful attempt to obtain information about a group from the user repository for the bus. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | There has been an unsuccessful attempt to find out if a user exists in the user repository for the bus. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | There has been an unsuccessful attempt to find out if a group exists in the user repository for the bus. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | There has been an unsuccessful attempt to find out to which groups a user belongs. The attempt failed. |
Action | Retry the query. If the retry is unsuccessful, the user repository may be unavailable and you should contact the user repository administrator. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | One or more entries in the authorization model for the bus do not have a unique name configured. If the unique name is not present then it is retrieved from the user repository whenever the authorization model is loaded. This places additional load on the user repository when starting servers or dynamically updating the bus configuration. |
Action | Run the populateUniqueNames wsadmin command. This will update the incomplete authorization entries with data from the user repository where possible. Any authorizations for users not present in the user repository should be updated to include a unique name using the relevant command. |
Explanation | If the message does not give sufficient information, check any previous messages for further information. |
Action | If you are unable to resolve the problem ask your system administrator to help resolve the problem. |