My Oracle Support Banner

Since Agile e61.2.2 HF29 / Agile e61.3 HF07 Find Stopping Batch Client Returns Exception (Doc ID 1963546.1)

Last updated on JUNE 21, 2018

Applies to:

Oracle Agile Engineering Data Management - Version and later
Information in this document applies to any platform.


Since applying Agile e6.1.2.2 HF29 / e6.1.3.0 HF07 (testclient-base.jar)

batch client stop returns error

Exception in thread "Thread-1" java.lang.NullPointerException at

1. Install and configure batchclient bundle
2. Configure file "LGVCall.groovy" to run a small LogiView procedure
  System.out.println("Starting SUP/BatchLgv");
  System.out.println("Done SUP/BatchLgv");

The Small LogiView procedure has only one procedure line
  like RES = 555

3. start batchclient in console with command batchclient.cmd -c
4. Wait, until receiving output like this
  ... com.agile.LGVCall.LGVCall[user=EDBCUSTO]: Starting scenario ...
  Starting SUP/BatchLgv
  Done SUP/BatchLgv
  ... com.agile.LGVCall.LGVCall[user=EDBCUSTO]: disconnected from
5. Receive error
Exception in thread "Thread-1" java.lang.NullPointerException
  at com.agile.testclient.TestClient.checkAndEmptyTrash(
  at com.agile.testclient.TestClient.close(
  at com.agile.testclient.TestClient.access$000(
  at com.agile.testclient.TestClient$



Same error occurs for AutoVue Batch Client ( used to create metafiles )

Similar error occurs when stopping ECI Servers via eci function: eci_stp_edb
  Error ..[AxalantRepository@4ec632] Connection com.agile.eci.EciClient .. died


To view full details, 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 a vibrant support community of peers and Oracle experts.