Don’t worry about this one either…
This is either the standard JDE interface, or going to WSJ:
You see that the session has not been “hung up” properly from the client.
The duration is 15 minutes, but .4s on the database
You can also see from above that the database is waiting for a message from the client… interestingly the object is the user overrides index, so this might need to be looked at in more detail. Logging out of JDE still leaves this hanging.
Again, not to sorry – but a shame it looks like it’s causing problems – when it is not.
If you come across this situation, clicking on the SQL ID will not help, click on the user and look into that information.
Easy to ignore when you know what is going on.