Osb jca adapter weird behaviour

Question

Hi gurus,
Im running OSB 11.1.1.5 having a db adapter polling an MSSQL2000 table (SELECT WITH (UPDLOCK, NOWAIT)..)
The table is being filled by a long running transaction.
I observe in the JCA logging the following error on every polling iteration while the table is being filled:
<Jan 10, 2012 2:00:45 PM CET> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <BEA-000000> <<oracle.tip.adapter.db.InboundWork handleException> Encountered a fatal exception while polling. Will continue polling but with minimal logging. Please investigate the fault and manually stop polling from the console if in development and this appears to be a modeling mistake. BINDING.JCA-11624
DBActivationSpec Polling Exception.
Query name: [O_Boeking_I_PollerSelect], Descriptor name: [O_Boeking_I_Poller.OBoeking]. Polling the database for events failed on this iteration.
Caused by java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Lock request time out period exceeded..
This exception is considered not retriable, likely due to a modelling mistake. To classify it as retriable instead add property nonRetriableErrorCodes with value "-1222" to your deployment descriptor (i.e. weblogic-ra.xml). This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).
The issue I'm experiencing occurs after the long running transaction is done. What I see is that in the next polling sweep 2 XML documents are delivered by the db adapter engine...I cannot figure out why. I do not want this
1 document contains only 1 record. The other document contains the rest of my records.
Have tried both WebLogic and MS JDBC drivers.
Some of mine properties:
MaxRaiseSize = 0 (I want all the records in 1 XML document)
MaxTransactionSize = unlimited
Thanks alot

Answer 1

Veejay,
Have done so...I tried some different setting like test-connections-on-reserve (was off)...no successes here.
I will give a try with another mssql driver version.
Another interesting thing I have observed is when I do not commit the long running transaction, the next db adapter polling event results in this exception:
<Jan 17, 2012 12:24:10 PM CET> <Error> <JCA_FRAMEWORK_AND_ADAPTER> <BEA-000000> <<oracle.tip.adapter.db.InboundWork handleException>
Encountered a fatal exception while polling. Will continue polling but with minimal logging. Please investigate the fault and manually stop polling from the console if in development and this appears to be a modeling mistake. BINDING.JCA-11624 DBActivationSpec Polling Exception.
Query name: [O_Boeking_I_PollerSelect], Descriptor name: [O_Boeking_I_Poller.OBoeking]. Polling the database for events failed on this iteration.
Caused by java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0.
This exception is considered not retriable, likely due to a modelling mistake. This polling process will shut down, unless the fault is related to processing a particular row, in which case polling will continue but the row will be rejected (faulted).
at oracle.tip.adapter.db.exceptions.DBResourceException.createNonRetriableException(DBResourceException.java:682)
at oracle.tip.adapter.db.exceptions.DBResourceException.createEISException(DBResourceException.java:648)
at oracle.tip.adapter.db.exceptions.DBResourceException.inboundReadException(DBResourceException.java:483)
at oracle.tip.adapter.db.InboundWork.handleException(InboundWork.java:922)
at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:826)
at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:578)
at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
at weblogic.work.ContextWrap.run(ContextWrap.java:41)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
at java.util.Vector.get(Vector.java:694)
at oracle.tip.adapter.db.InboundWork.vectorSubList(InboundWork.java:1860)
at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:713)
... 6 more
>
This lets me think it could be a bug..