SESSION_ID Value Using Old Value (Doc ID 2581797.1)

Last updated on FEBRUARY 19, 2024

Applies to:

Goal

SESSION_ID value using old value

For a CSDL, after failure, while rolling back, we are observing SESSION_ID value not using the new SESSION_ID instead its using old SESSION_ID used earlier in same work order. We have observed new session id set by login ASDL and same used by logout ASDL but intermediate ASDLS's are using old session resulting INVALID Session error from the network.

<CSDL>

[Jul 20, 2019 5:37:12 PM GST] [<WO>] [<LOGIN_ASDL>] SESSION_ID=5662a8ecb4b8434c8d4aab22a162ca8c

[Jul 20, 2019 5:37:12 PM GST] [<WO>] [<ASDL_REMOVE>] SESSION_ID=43aff9b6e2b14e7e9aeca231b3f033eb

[Jul 20, 2019 5:37:12 PM GST] [<WO>] [<ASDL_DELETE>] SESSION_ID=43aff9b6e2b14e7e9aeca231b3f033eb

[Jul 20, 2019 5:37:12 PM GST] [<WO>] [<LOGOUT_ASDL>] SESSION_ID=5662a8ecb4b8434c8d4aab22a162ca8c


Invalid sessionId Error:

################ Response XML Value ##############
[Jul 20, 2019 5:37:12 PM GST] [<WO>] [<ASDL_REMOVE>] 43aff9b6e2b14e7e9aeca231b3f033eb4885352248853522ns2:ClientThis is a client fault1001Invalid sessionId.MF1010Invalid sessionId.Invalid session id.

Solution

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