wierd error

Jen

unread,

Sep 19, 2003, 12:48:42 PM9/19/03

to

hi,
I am testing wls81. today I got the following error, it happened when I try to
start the weblogic. What does means? Thanks

####<Sep 19, 2003 9:15:24 AM PDT> <Info> <JDBC> <Refresher> <<anonymous>> <> <BEA-001068>
<Connection for pool "dev_pool" created.>
####<Sep 19, 2003 9:15:24 AM PDT> <Info> <JDBC> <Refresher> <<anonymous>> <> <BEA-001132>
<Initialized statement cache of size "10" for connection in pool "dev_pool".>

####<Sep 19, 2003 9:15:24 AM PDT> <Info> <Common> <Refresher> <<anonymous>> <>
<BEA-000628> <Created "1" resources for pool "dev_pool", out of which "1" are
available and "0" are unavailable.>
####<Sep 19, 2003 9:15:36 AM PDT> <Error> <T3Services> <ExecuteThread: '4' for
queue: 'weblogic.kernel.System'> <<anonymous>> <> <000000> <ResultSQL: java.sql.SQLException:
[BEA][SQLServer JDBC Driver]Unhandled token type: Unknown token: 0x72>
####<Sep 19, 2003 9:15:36 AM PDT> <Error> <JDBC> <ExecuteThread: '4' for queue:
'weblogic.kernel.System'> <<anonymous>> <> <BEA-001131> <Received an exception
when closing a cached statement for the pool "dev_pool": java.sql.SQLException:
[BEA][SQLServer JDBC Driver]Request cannot be submitted due to wire contention..>

####<Sep 19, 2003 9:15:36 AM PDT> <Error> <T3Services> <ExecuteThread: '4' for
queue: 'weblogic.kernel.System'> <<anonymous>> <> <000000> <ResultSQL: java.sql.SQLException:
[BEA][SQLServer JDBC Driver]Unhandled token type: Unknown token: 0x2e>
####<Sep 19, 2003 9:15:36 AM PDT> <Error> <T3Services> <ExecuteThread: '4' for
queue: 'weblogic.kernel.System'> <<anonymous>> <> <000000> <StaticData: Exception:
Exception in ResultSQL: java.lang.ArrayIndexOutOfBoundsException>
####<Sep 19, 2003 9:15:36 AM PDT> <Error> <T3Services> <ExecuteThread: '4' for
queue: 'weblogic.kernel.System'> <<anonymous>> <> <000000> <StaticDataImpl: Error
connecting to DB java.lang.ArrayIndexOutOfBoundsException, server did not register
cache with DB>

Joseph Weinstein

unread,

Sep 19, 2003, 1:11:20 PM9/19/03

to Jen

Jen wrote:

Hi. These are odd! Would you please turn on JDBC logging, and show me the SQLExceptions
that reach the jdbc.log file? Also, I suspect that the driver may be trying to make multiple
DBMS connections in too fast a loop for the DBMS to handle. If you will set the login-delay
property on the pool to be 1 second, it might help.
Joe

Joseph Weinstein

unread,

Sep 26, 2003, 11:22:43 AM9/26/03

to Jen

Hi.
Have you been able to duplicate this with jdbc logging on?
thanks,
joe

Joseph Weinstein

unread,

Sep 26, 2003, 2:46:45 PM9/26/03

to Jen

Jen wrote:

> Thank you very much. Today I got one. Here is the log.

Ok, As the log shows, it seems there's significant problems
with JDBC code in the class com.officialpayments.cache.CacheManagerImpl.
I would be happy to examine that code, but you should also have it looked
at there, regarding the commit() call and the statement.close() call. I am concerned
that the subsequent failures may have to do with applicaiton code using ResultSets
after the Statements that created them have been closed.
Joe

> ----------------------------------------------------------------------------------------------------
> Name: jdbc.log00001.log
> jdbc.log00001.log Type: Text Document (application/x-unknown-content-type-txtfile)
> Encoding: base64