E1: ORCH: AIS: Null Exception When Running V3/orchestrator/jde-login (Doc ID 2693633.1)

Last updated on AUGUST 01, 2023

Applies to:

Symptoms

Customer created a batch process which will run several hundred UBE's in sequential order. They built the process to kick off a UBE using the v2/report/execute command using basic authorization to keep everything stateless. Then take that return value and utilize it in the v2/report/status, again using basic authorization to keep everything stateless. However the status call keeps a session open no matter what. It does not work in a stateless manner with basic authorization.

Went ahead and started using the v3/orchestrator/jde-login to get a jde-AIS-Auth token to use for the entire transaction. This allowed to keep the calls stateless as could log the user out afterward using the v3/orchestrator/jde-logout. The issues now is that when the job runs the first session logs in just fine and executes the first UBE without any issue. However, the second call to v3/orchestrator/jde-login errors out 100% of the time with a null pointer exception.

However, the user has an active session as seen in server manager and have to terminate it that way.

Sequence of events: log in, execute UBE, check job status, logout, repeat.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.