AWSBDJ - Appserverman messages
This section lists error and warning appserverman messages that might be issued.
The message component code is BDJ.
AWSBDJ003E The application server has stopped unexpectedly or failed.
Explanation
The application server monitor (appservman) has detected that the application server is no longer running, but that it has not been stopped by the user.
System action
The application server monitor checks the policies defined in the localopts file to decide whehter the application server should be restarted.
Operator response
See the application server logs to diagnose the problem that is causing the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDJ005E Cannot restart the application server. See the application server log for the reason.
Explanation
See message.
System action
The application server monitor has failed to restart the application server. The application server monitor (appservman) stops.
Operator response
See the application server logs to diagnose the problem that has caused the start of the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To restart the application server run a conman startappserver or StartUp command.
AWSBDJ006E Cannot stop the application server. See the application server log for the reason.
Explanation
See message.
System action
The application server monitor (appservman) has failed to stop the application server.
The application server monitor stops. However, the application server is probably still running.
Operator response
See the application server logs to diagnose the problem that is causing the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To manually stop the application server run the following command:wastools/stopWas -direct -user <username> -password <password>.
AWSBDJ007W The auto-restart flag (see localopts) is set to false, so the application server is not restarted by the application server monitor.
Explanation
The application server monitor (appservman) has detected that the application server has failed.
However, the policies in the localopts files indicate that the application server is not to be restarted.
System action
The application server monitor does not restart the application server. It stops.
Operator response
See the application server logs to diagnose the problem that is causing the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To restart the application server run a conman startappserver or StartUp command.
To permit the application server monitor to automatically restart the application server, change the value of the Appserver auto restart option in the localopts file.
AWSBDJ008E The application server has been restarted more times than the configured maximum (see localopts), so the application server will not be restarted by the application server monitor.
Explanation
The application server monitor (appservman) has detected that the application server has failed.
The application server monitor has already restarted the application server one or more times, and the policies in the localopts files indicate that the application server should no longer be restarted automatically by the application server monitor (it might be failing repeatedly for the same reason).
System action
The application server monitor does not attempt to restart the application server. It stops.
Operator response
See the application server logs to diagnose the problem that is causing the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To restart the application server run a conman startappserver or StartUp command.
To allow the application server monitor to continue restarting the application server automatically in these circumstances, change the value of the Appserver max restarts option in the localopts file. You might also want to change the value of the Appserver count reset interval option.
AWSBDJ009E The application server was up before failing for less time than the configured minimum (see localopts), so the application server will not be restarted by the application server monitor.
Explanation
The application server monitor (appservman) has detected that the application server has failed. The monitor restarted the application server, which failed again in a shorter time than the minimum restart time as determined by the policies in the localopts files.
System action
The application server monitor does not attempt to restart the application server. It stops.
Operator response
See the application server logs to diagnose the problem that is causing the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To restart the application server run a conman startappserver or StartUp command.
To allow the application server monitor to continue restarting the application server automatically in these circumstances, change the value of the Appserver min restart time option in the localopts file.
AWSBDJ010E Cannot restart the dynamic workload broker application. For details, see the application server log.
Explanation
See message.
System action
The application server monitor has failed to restart the dynamic workload broker application.
Operator response
To diagnose the problem that has caused the start of the dynamic workload broker application to fail, see the application server logs. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To restart the application server run a conman startappserver or StartUp command.
AWSBDJ011E Cannot stop the dynamic workload broker application. For details, see the application server log.
Explanation
See message.
System action
The application server monitor (appservman) has failed to stop the dynamic workload broker application.
The dynamic workload broker application is probably still running.
Operator response
See the application server logs to diagnose the problem that is causing the application server to fail. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
To manually stop the dynamic workload broker application, run the command wastools/stopBrokerApplication -user <username> -password <password>.
AWSBDJ012E An internal error occurred while opening the Appserverbox message queue.
Explanation
The application server monitor (appservman) was not able to open the Appserverbox message queue.
System action
The application server monitor stops.
Operator response
Check the access permissions of the Appserverbox.msg file. If you have solved the problem, stop and restart the application server, which automatically restarts the application server monitor. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDJ013E An internal error occurred while opening the Mailbox message queue.
Explanation
The application server monitor (appservman) was not able to open the Mailbox message queue.
System action
The application server monitor stops.
Operator response
Check the access permissions of the Mailbox.msg file. If you have solved the problem, stop and restart the application server, which automatically restarts the application server monitor. If you cannot solve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.
AWSBDJ016E An internal error occurred while reading the Appservrbox message queue.
Explanation
An internal error has occurred.
System action
The application server monitor stops.
Operator response
This is an internal error. If you cannot resolve the problem, search the HCL Support database for a solution at https://hclpnpsupport.hcltech.com/csm.