Callable Statement wot working properly

Question

I have a situation where using CallableStatement only executes the stored proc intermittenly,
while utilizing Statement works all the time. This didn't happen under WLS 5.1 SP
6. Does anyone else have the same problems.
Also in both cases the jdbc log produces the following message:
SQLWarning: reason(010P4: An output parameter was received and ignored.) SQLState(010P4)
But we have nothing being returned from the stored proc and no OUT parameters.
We are using Jconnect native jdbc drivers with Sybase 11.9.2
Thanks a lot, Alex

Answer 1

Lev wrote:
We are using WebLogic 7.0 and we downloaded the latest version
of Sybase Driver. Previously we used WebLogic 5.1 sp 9 and
excatly the same sybase driver and code and it worked.Yes. The change in our code is that we now cache PreparedStatements
with their pooled connections, and when a pool connection is re-used,
if the requestor prepares a statement with the same parameters including the SQL,
as before, they get a cached statement which has had it's prior arguments cleared.
This is a big performance win, but it has had the side effect of revealing bugs
in various JDBC drivers when statements are re-used for an indefinite period
of time.
As I said, the first thing to do is to stop the symptoms, byt setting the cache size
to 0, to stop us caching. If you are willing to help us debug the driver, the test would
be a standlaone program that used the sybase driver to make a connection and
prepare a statement like your code uses, then run a long-running loop that
sets the arguments, executes the statement, calls clearParameters(), and repeats.
This duplicates what we make the driver do, and should eventually demonstrate
the driver bug. Is there any chance that the same prepared statement is being
used in different ways, such that the same SQL is used for a CallableStatement
getting back output parameters (even just the procedure status) sometimes, and
as a PreparedStatement other times?
Joe
>
>
Joseph Weinstein <[email protected]> wrote:
Alex wrote:
Joeseph,
We had jconn2.jar in front of weblogic classpath all the time
and it does not help.make sure it's the latest.
We are about to open a case with WebLogic.
Could you please help us ASAP.Understood. What version of the server are you running now? The first
step is to avoid the sybase driver problem by turning off our statement
cache.
Thanks, Alex
Joseph Weinstein <[email protected]> wrote:
>
Hi. This probably has to do with our caching of prepared statements and
a bug in the version of the sybase driver that we ship. Please download
sybase's latest driver and put it ahead of all weblogic stuff in the
server
classpath, and let me know...
Joe
"Alex" <[email protected]> wrote in message
news:[email protected]...
I have a situation where using CallableStatement only executes the
stored
proc intermittenly,
while utilizing Statement works all the time. This didn't happen
under
WLS
5.1 SP
6. Does anyone else have the same problems.
Also in both cases the jdbc log produces the following message:
SQLWarning: reason(010P4: An output parameter was received and ignored.)SQLState(010P4)
But we have nothing being returned from the stored proc and no OUTparameters.
We are using Jconnect native jdbc drivers with Sybase 11.9.2
Thanks a lot, Alex