UPDATE: WebSphere Adapter for JDBC: Superfluous RecordNotFound Exceptions
A while ago, I posted about the WebSphere Adapter for JDBC always writing an exception to the System.out when a record could not be found. At the time, we were being told that it was not something that would be fixed in the 6.x timeframe.
Suddenly, there has been a change of heart from IBM and we have been given a patch that will remove this exception from the log.
Go figure. I guess the moral of the story is that you need to keep pressing IBM to fix problems even when they just involve the removal of a System.out.println(…).
Related Posts
- WebSphere Adapter for JDBC: Superfluous RecordNotFound Exceptions
- WebSphere Adapter for JDBC: SetObjectKeys NullPointer Exception
- Enabling SCA-MQ integration via MQ bindings
- SCA, BPEL, Websphere Adapter for JDBC and Transactionality
- JDBC Adapter Export with events that comprise multiple rows
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
July 2nd, 2008 at 10:09 am
We have also had a PMR open for this. It is a right pain to get pages of java trace telling you a normal condition had been met (no rows, that is valid isn’t it). Has anyone tested the fix yet?
July 2nd, 2008 at 10:15 am
We have tested it and it works
Open a PMR and support should be able to give it to you.
July 10th, 2008 at 8:10 am
Do you know what the APAR number is?
Regards
Chris
July 10th, 2008 at 8:40 am
Unfortunately, no, I don’t have a APAR number. Is support telling you that a fix doesn’t exist?