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

Last updated on JULY 11, 2016

Applies to:

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

Symptoms

ACTUAL BEHAVIOR
--------------------------
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
com.agile.er.axalant.AxalantRepository.readFromMap(AxalantRepository.java:16..



STEPS:
---------------------
1. Install and configure batchclient bundle
.
2. Configure file "LGVCall.groovy" to run a small LogiView procedure
like
  System.out.println("Starting SUP/BatchLgv");
  LGVBatch.callNativeUsx("lgv_nosel_run","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.er.axalant.AxalantRepository.readFromMap(AxalantRepository.java:1647)
  at com.agile.er.axalant.AxalantRepository.getEntry(AxalantRepository.java:4207)
  at com.agile.er.axalant.AxalantRepository.createAxalantEntity(AxalantRepository.java:2080)
  at com.agile.er.axalant.AxalantTrashcan.getInstance(AxalantTrashcan.java:159)
  at com.agile.testclient.TestClient.checkAndEmptyTrash(TestClient.java:207)
  at com.agile.testclient.TestClient.close(TestClient.java:188)
  at com.agile.testclient.TestClient.access$000(TestClient.java:39)
  at com.agile.testclient.TestClient$1.run(TestClient.java:64)

 

NOTE:

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

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