Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session application context is not reset after utPLSQL run #951

jgebal opened this issue Jun 21, 2019 · 0 comments · Fixed by #963


Copy link

commented Jun 21, 2019

Describe the bug
After execution of, when I look into v$session to look at my session, it still indicates that my session is running utPLSQL. All the information about application connected (like SQLdeveloper/SQLPlus/jdbc client is lost forever.
The only way to recover is to reconnect.

Provide version info
It's been there for a long time

Expected behavior
having information about currently running utPLSQL test / package is very valuable however it should be handled differently.
utPLSQL should grab information about application info before it starts and should recover that information when it finishes.

We could use events mechanism to trigger registration of application context and send it into application_context event handler so we could:

  • grab and hold application context before run,
  • set new context on every before... event
  • recover grabbed context on after_run event
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
1 participant
You can’t perform that action at this time.