Batch Client Running Loop Scenario Does Not Shutdown the Agile / Axalant Server Process(es) (Doc ID 1941434.1)

Last updated on JULY 11, 2016

Applies to:

Oracle Agile Engineering Data Management - Version 6.1.3.0 to 6.1.3.0 [Release 6.1.0]
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
-------------------
Batchclient LgvLoop scenario does not stop the corresponding axalant server
process when stopping the batchclient

Does not stop when running in console,
 started with batchclient.cmd -c, stopped with key CTRL+C

Does not stop when running as service,
 started with batchclient.cmd -t , stopped with batchclient.cmd -p

Stop process starts but does not execute LGV / SQL to set the STOP value

At the end two axalant processes are remaining,
 one to execute jobs
 second started via stop

Both server debug traces show ECI-NO-DATA, because batchclient terminates,
without stopping server processes

Batchclient wrapper log shows error:
Shutdown failed: Timed out waiting for signal from JVM.
JVM did not exit on request, terminated


Steps to Reproduce:
-------------------------
1. Install batchclient bundle as described in
  Batch Client Guide for Agile e6.1.3.0 (file: E50961_02.pdf)

2. Load example loader files : lgv-batch-example.bin, batch-example-cfg.bin

3. start batchclient in console with command batchclient.cmd -c

4. Wait, until receiving output like
Scenario: Message received: I: execute job
 I:  execute job

5. Use CTRL+C to stop the batchclient

6. Receive error
Shutdown failed: Timed out waiting for signal from JVM.
JVM did not exit on request, terminated

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms