This is expected behavior. OpenLink's 1.x and 3.x Multi-Tier connections spawn a JDBC-specific agent that spawns a database-specific agent. Hence, one JDBC connection results in two concurrent connections. OpenLink's latest drivers do not spawn both a JDBC agent and a database agent. OpenLink's new database agents are equipped to handle JDBC connections intheir entirety.
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML Microdata format. This time the service made zero such statements, sorry.