To stop concurrent manager server we use script adcmctl. The script has two options: stop and abort. When we use stop option, concurrent process is not stopped, until it executes already running concurrent request. New concurrent requests are pending. Abort option just shuts down all concurrent managers, not allowing already running requests to be completed. So what happens after CM server is brought up after abort? I performed tests on my sandbox system, and here's message that is displayed in internal manager's log:.
No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in.
By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account. We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox. Newsletter Topics Select minimum 1 topic.
Big Data. Anonymous December 14, 0 Comments. Anonymous Posted December 15, 0 Comments. Thanx a lot for the reply. Is it because of table space issue? Please check is there any concurrent process is there before starting concurrent processing server. If the concurrent process still exists after shutdown kindly wait for some time for clearing the requests.
The bellow command will tell you how many concurrent processes are running. Here applprod is the user for the application file system. Share this: Twitter Facebook. Like this: Like Loading Leave a Reply Cancel reply Enter your comment here
0コメント