<http://data.openlinksw.com/oplweb/faq/UDA/My1x3xJDBCType3ConnectionsSpawnMultipleAgentsThatConsumeMyLicenses.WhatDoIDoAnswer#this>	<http://schema.org/answerExplanation>	"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 in their entirety." .
<http://data.openlinksw.com/oplweb/faq/UDA/My1x3xJDBCType3ConnectionsSpawnMultipleAgentsThatConsumeMyLicenses.WhatDoIDoAnswer#this>	<http://www.w3.org/1999/02/22-rdf-syntax-ns#type>	<http://schema.org/Answer> .
<http://data.openlinksw.com/oplweb/faq/UDA/My1x3xJDBCType3ConnectionsSpawnMultipleAgentsThatConsumeMyLicenses.WhatDoIDoAnswer#this>	<http://www.w3.org/2007/05/powder-s#describedby>	<https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/uda-faq.ttl> .
<http://data.openlinksw.com/oplweb/faq/UDA/My1x3xJDBCType3ConnectionsSpawnMultipleAgentsThatConsumeMyLicenses.WhatDoIDoAnswer#this>	<http://www.w3.org/2007/05/powder-s#describedby>	<https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/uda-faq.ttl> .