Database Software

We run Oracle eBusiness Suite on database 9.2.0.7. There are two db instances. For integration purposes we have several queues/topics in Oracle AQ. Both incoming and outgoing. We use AQ JMS (aqapi13.jar) interface on client side and jdbc thin drivers v. 10.0.2.0.1.

Our connect string is now:
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=host1)(PORT=1522))(ADDRESS=(PROTO
COL=tcp)(HOST=host2)(PORT=1522))(LOAD_BALANCE=yes)(FAILOVER=true))(CONNECT_DATA=(SERVICE_NAME=CRMP)(failover_mode=(type=select)(method=basic)(
retries=20)(delay=15))))

My question is does AQ JMS benefit from
- JDBC-OCI drivers on client side
- switching TAF on

The problem that we see is occasional client side hang, with very little clues what goes wrong. Our clients don't close the connections, but rather keep them open for ever.

Any advice for which jdbc drivers and AQ jars to use?
Or should we study TCP related timeouts etc. ?

I'm considering using following connect string:

jdbc:oracle:oci:@ (DESCRIPTION=
(LOAD_BALANCE=off) /* OFF for AQ, use first addr. */
(FAILOVER=on) /* connect time failover */
(ADDRESS=(PROTOCOL=tcp)(HOST= host1)(PORT=1522))
(ADDRESS=(PROTOCOL=tcp)(HOST= host2)(PORT=1522))
(CONNECT_DATA=
(SERVICE_NAME= CRMP) /* For TAF you need service name and failover_mode */
(FAILOVER_MODE=
(TYPE=session)
(METHOD=basic)
(RETRIES=20)
(DELAY=15))))

Matti