推荐订阅源

从mercury上找到的一些有用的信息

Are there any recommendations for starting/stopping BAC and its related services like the IIS service or the Apache service?

Is it recommended to start/stop BAC from the services.msc console (accessible from Computer Management -> Services and Applications console)?

What is the recommended order for starting BAC and its related services (i.e., BAC service/IIS service/World Wide Web Publishing (WWW) service/Apache service)?

Solution: Recommendations for starting/stopping BAC and its related services

• It is recommended to use the "Enable BAC" and "Disable BAC" shortcuts in Start -> Programs -> Mercury BAC -> Administration for starting/stopping BAC.
• It is not recommended to start/restart/stop BAC using the service.msc console (accessible from the Computer Management -> Services and Applications console).
• IIS/Apache can be started using the services.msc console, and that can be done before or after a BAC restart.
• While restarting BAC, it is recommended to ensure that BAC has been stopped fully before starting it again as explained in Problem ID 48167 - How to verify that BAC has shut down properly.

http://kb-web.mercury.com/KBA/KBAview.asp?Conceptid=48167&Product=TOPAZ

Problem Description: How to verify that BAC has shut down properly

BAC is unable to start properly and the following messages are seen in supervisor.txt:

"FLOW stopping nanny process:

.nanny - (process was not properly stopped on previous nanny run)"

How can the user verify that BAC has shut down properly when the service has been disabled?

---

Solution: Ensure BAC is properly shut down before starting it again

If BAC service has not been stopped properly and if it is attempted to start BAC again, there could be existing processes from the previous BAC session that are still running and could be occupying ports. When BAC sees that there are already some processes running from previous run it will try to stop these processes, while bringing the new processes up again at the same time, which may result in improper start up sequence.

So, it is recommended to ensure that BAC has been stopped fully before starting it again. To ensure BAC has stopped completely, the Task Manager can be checked to see if the MercuryAS.exe process is gone. Also the jboss_boot.last_run.log can be checked if the shut down is complete, which will be indicated by these messages:

"Shutting down
Shutdown complete
Halting VM"

To manually terminate any remaining processes, you may use kill.exe as explained in Problem ID 40809 - How to end BAC processes if they continue to run even after BAC is stopped.