Hello. I'm having the same problem. Joe, you last wrote,
"That log entry shows that the DBMS (or network) has dropped
a connection out from under the AS400 driver, and that we caught
the failure during our test-on-reserve algorithm. What does the log
go on to show? Typically, we would close the dead connection and
try to create a new connection to give you. If we succeed (if the
driver gave us a new connection) we return it to you. If we failed,
(if the getConnection() call failed) we would send you an exception.
What happens in your application after this? The only oddity would
be if after the dead connection and retry, the driver gave us a
new connection *which was DOA*. When we create a new replacement
connection, we do not immediately test it with a new query. We
assume that a fresh connection is OK..."

Forgive me if I'm repeating text that will appear when I post this message, but this is my first time so I wanted to be sure this will appear so I can refer to it and have you understand my references.

How could I handle the DOA case, since I think that is happening? Any other parameters to use in the weblogic.properties file OR is my only alternative is to upgrade to a version that has this functionality?

Do you know if the COM.ibm.db2.jdbc.app driver has known problems in this area and maybe it's not weblogic server. Another words, maybe it's the db2 driver returning the DOA connections that it shouldn't.

Thank you in advance, Derrick

derrick wong wrote:

> Hello. I'm having the same problem. Joe, you last wrote,
> "That log entry shows that the DBMS (or network) has dropped
> a connection out from under the AS400 driver, and that we caught
> the failure during our test-on-reserve algorithm. What does the log
> go on to show? Typically, we would close the dead connection and
> try to create a new connection to give you. If we succeed (if the
> driver gave us a new connection) we return it to you. If we failed,
> (if the getConnection() call failed) we would send you an exception.
> What happens in your application after this? The only oddity would
> be if after the dead connection and retry, the driver gave us a
> new connection *which was DOA*. When we create a new replacement
> connection, we do not immediately test it with a new query. We
> assume that a fresh connection is OK..."
>
> Forgive me if I'm repeating text that will appear when I post this message, but this is my first time so I wanted to be sure this will appear so I can refer to it and have you understand my references.
>
> How could I handle the DOA case, since I think that is happening? Any other parameters to use in the weblogic.properties file OR is my only alternative is to upgrade to a version that has this functionality?
>
> Do you know if the COM.ibm.db2.jdbc.app driver has known problems in this area and maybe it's not weblogic server. Another words, maybe it's the db2 driver returning the DOA connections that it shouldn't.
>
> Thank you in advance, Derrick

Hi. Tell me your exact symptoms. The above stuff does sound like the connection
between the driver and DBMS is unreliabl.e... I don't know whether it's the
driver, network, or DBMS, but it's not WebLogic...
Joe