GetWarnings on Connection throws exception if rollback = true

Question

I am trying to use hibernate within WLS 7SP4 and I get an exception everytime it
tries to close an exception.
inside
weblogic.jdbc.jts.Connection.getWarnings()
the first thing it does is call the method
checkIfRoleBack(). This essentially throws an exception if the Transaction is
currently in a roleback state
If you look at the java API for get warnings it says it should only throw an exception
if a database access error occurs. However a transaction being in a roleback state
is not exactly a database error it is a perfectly valid state.
THe problem I have is that when Hibernate tries to close a connection it also
tries to log all the warnings on the connection. This means that closing a rolledback
connection always throws an exception.
Is this a bug in the weblogic implementation of Connection or is this expected
beahviour.

Answer 1

In that case we will be fine and the change is not that important
Thanks
Carl
Joe Weinstein <[email protected]> wrote:
>
>
Carl wrote:
If the tx times out will I still be able to use sessionContext.getRollBackOnly()
or will this only work if manually set.That should certainly still work. It is only JDBC that is prevented after
the
tx is done.
Joe
Thanks
Carl
Joe Weinstein <[email protected]> wrote:
Carl Marais wrote:
Thanks Joe for the response.
My current solution is just to log and consume the exceptions if doinga close
when the SessionContext of the EJB is set to Rollback. Judging fromwhat you are
saying this should not have any impact on overall processing and theoriginal
business exception can still flow through to the clientCorrect. The exception from getWarnings() has no effect on any processing
and
can be ignored if it's meaning is understood. We will currently allow
no jdbc
to be done, as soon as the tx is done for any reason. This could occur
at any
time, if for instance the tx reached it's timeout limit in-flight.
Let me know how important the change I suggested is, or whether
you're
OK
as-is for now with the above explained.
thanks,
Joe
Joe Weinstein <[email protected]> wrote:
Carl Marais wrote:
I am trying to use hibernate within WLS 7SP4 and I get an exceptioneverytime it
tries to close an exception.
inside
weblogic.jdbc.jts.Connection.getWarnings()
the first thing it does is call the method
checkIfRoleBack(). This essentially throws an exception if the Transactionis
currently in a roleback state
If you look at the java API for get warnings it says it should onlythrow an exception
if a database access error occurs. However a transaction being in
a
roleback state
is not exactly a database error it is a perfectly valid state.
THe problem I have is that when Hibernate tries to close a connectionit also
tries to log all the warnings on the connection. This means that
closing
a rolledback
connection always throws an exception.
Is this a bug in the weblogic implementation of Connection or is
this
expected
beahviour.Hi. I can see it's being unexpected, but we must do all we can toensure
that
application code does no JDBC (which for the most part is intendedto
contribute
to the transaction) when the transaction is not in an accepting state.
For maximum
concurrency we actually reclaim the underlying pooled connection
as
soon
as the
fate of the transaction is sealed. This means that the warnings itmay
have accrued
are no longer accessible to the client. This is because we turn offthe
wrapper
object that the client has (generating that exception), and for pool
cleanliness
we always clear any warnings the connection may have collected during