Frequent BEA-001131 errors caused by JZ0S1 in Weblogic 9/10 + jConnect6

Question

The pasted error messages are shown frequently in Weblogic console log. The same errors happen in either Weblogic 9/10.0/10.3.
cashdatasource is a JDBC data source to Sybase ASE server using jConnect 6.5.
I have checked the description for these two error codes. jConnect recommends closing the statement and reopen one. However, it seems Weblogic didn't do anything about it and keep trying to close the statement every 1 hour. The frequency 1 hour is set by shrink-frequency-seconds parameters in the jdbc-data-source xml configuration file.
It doesn't seem to harm our application. However these error messages are really annoying and not sure whether it indicates potential problem.
Any idea to get rid of those is really appreciated.
===========================================================================================
BEA-001131
Error: Received an exception when closing a cached statement for the pool "pool": err.
Description
When closing a prepared statement in the prepared statement cache for the specified pool, an error occurred.
Cause
When closing a prepared statement in the prepared statement cache for the specified pool, an error occurred.
Action
Check the associated error that is printed and correct the problem if possible.
===========================================================================================
JZ0S1
Statement state machine: Trying to FETCH on IDLE statement.
Description: An internal error occurred on the statement.
Action: Close the statement and open another one.
===========================================================================================
<Jan 5, 2009 1:25:05 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 1:25:05 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 1:25:05 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 1:25:05 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 1:25:05 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 2:25:10 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 2:25:10 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 2:25:10 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 2:25:10 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>
<Jan 5, 2009 2:25:10 PM GMT> <Error> <JDBC> <BEA-001131> <Received an exception when closing a cached statement for the pool "cashdatasource": java.sql.SQLException: JZ0S1: Statement state machine: Trying to FETCH on IDLE statement..>

Answer 1

Try getting Sybase's latest from their site. It's not likely that WLS
is going to change to avoid an exception when we're simply closing
a statement, but if you make an official SR anything is possible....
Joe