uCosminexus Application Server, Application Development Guide
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
During the batch processing, you can forcibly terminate the batch applications that are being debugged or executed. The following is the procedure to forcibly terminate the batch applications that are being debugged or executed:
- In the Debug view, choose start-configuration-name Cosminexus Batch Application.
- In the Debug view, click
(Terminate) on the tool bar.
The batch applications will be terminated.
- Note
- The following points are to be considered when forcefully terminating batch applications:
- If the end value of the cjkilljob.exe process that is displayed in Debug view is 2, reference the console of the cjkilljob.exe process that exists in the Console view, remove the cause of the abnormal termination or warning termination, and then stop the batch server.
- In the Debug view, if the Terminate button is continuously clicked, the debug connection of the batch server might be disconnected. If the debug connection of the batch server is disconnected, stop the batch server, and then debug or execute the batch application.
- If an attempt to forcefully terminate a batch application fails, the batch application is automatically re-executed using the Management Server settings. If you start Eclipse after restarting the batch server, the restarted batch server becomes the batch server that is started externally, and you can debug or execute batch applications. In such cases, stop the batch server using the Management Server management portal.
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.