Global Context + Session Client Identifier = Strange Behaviour or Documentation BUG ?

Here I’ll describe some strange/interesting/ behaviour of Global Application Context connected with usage of Session Client Identifier, that is quite usually met in Application Express, J2EE Agent, Oracle Data Integrator starting from release and many other applications that uses JDBC Connection Pooling in conjunction with setting Session Client Identifier.

So what is the problem ?

The problem is that Global Application Context doesn’t work as expected and described in documentation – attributes’ VALUES ARE NOT VISIBLEContinue reading