| Author |
Message
|
| wbintegrator |
 Posted: Tue Jun 24, 2008 6:21 am Post subject: JDBC Adapter failed to close connection |
 |
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
Hello
We're using jdbc adapter 2.6.9 with Framework 2.6.0.11 on unix B.11.11.
The adapter connects to an Oracle DB 10.2.0.3.
Hundred thousand of messages run through this adapter, some of them regrading to the same lines in the DB. So we configured the property CloseDBConnection to TRUE.
When we use it that way, several of messages computes and after that we recieve an error "Failed while trying to close connection with application".
It happens 3 times and after that the adapter shuts down with an error message.
Has anyone encountered such problem?
Thanks. |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Jun 24, 2008 8:02 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| wbintegrator |
| Posted: Tue Jun 24, 2008 11:22 pm Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
hi
Thanks for the link but as I said, we're using Framework 2.6.0.11 already.. |
|
| Back to top |
|
|
| Il_Ciclone |
| Posted: Mon Jul 14, 2008 6:21 am Post subject: |
|
|
Novice
Joined: 21 Mar 2007
Posts: 24
|
We are running the JDBC adapter on the same versions (adapter 2.6.9, AF 2.6.0.11 and Oracle 10 DB)
We have reported a PMR on similar issue, but caught this error as well.
The IBM guys say its because the AF caught a NPE from Adapter terminate() after looking at our logs and trace files. I dont know if have that same behaviour. Anyway the PMR is at L3 support at the moment so hopefully thay can find some solution.
The PMR is about us having general problems with adapter resuming to process messages if the DB is restarted. |
|
| Back to top |
|
|
| Il_Ciclone |
| Posted: Mon Oct 06, 2008 4:15 am Post subject: |
|
|
Novice
Joined: 21 Mar 2007
Posts: 24
|
| Il_Ciclone wrote: |
The PMR is about us having general problems with adapter resuming to process messages if the DB is restarted. |
for the sake of documetation, the answer to this is:
1. Use Oracle JDBC driver 10.2.0.4 (at least)
2. Set ping query
3. Enable Auto restart
4. Use 2.6.9 TF2, which i think will make it into 2.6.10 |
|
| Back to top |
|
|
|
|
