If there is a newer one where can I download it?
Davin Czukoski wrote:
Hi. Sp12 is almost the most recent, and the only difference in the one
you can get from support has to do with the MS SQL2000sp3 security
patch. If you can connect to the DBMS with the driver you have, then
there's nothing new that will help you.
SHow us the whole stacktrace of the error you get. It usually just
means the network or DBMS hung up on the driver.
Joe
Here you go:
> ####<Mar 24, 2003 2:41:54 PM EST> <Error> <EJB> <zeppelin.ma.ovid.com>
<ovidServer> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <>
<010026> <Exception during commit of transaction 8:084fc1fcab0c34c2:
javax.transaction.HeuristicMixedException: (weblogic.jdbc.jts.Connection,
HeuristicHazard, (javax.transaction.xa.XAException: I/O exception while
talking to the server, java.io.EOFException))
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:258)
at
weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransaction
Impl.java:208)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:393)
at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:29
8)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2310)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2233)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
>
Davin Czukoski wrote:
Tunr on JDBC logging, and show me the whole actual exception. It would involve
actual sybase driver classes in the stack trace. Nevertheless, that does mean
the DBMS is cutting the connection. See if there's any DBMS error log to
record why the DBMS is doing that. If the problem is easy to duplicate, I would
simultaneosly log in to the DBMS and see what the DBMS thinks the connections
are doing. Then I'd cause the problem and look again.
Joe
I'll try that.
My problem is that your driver has this error and everyone elses driver
throws something similar to this (DataDirect, NetDirect)
javax.ejb.CreateException: Exception on Create:
javax.ejb.CreateException: SQLException on Create: com.jnetdirect.jsql.x:
Line 1: Incorrect syntax near 'M'. at
weblogic.knex.bean.WebProcessBean.ejbCreate(WebProcessBean.java:1032) at
weblogic.knex.bean.WebProcessBean_lrv41b_Impl.ejbCreate(WebProcessBean_lrv41
b_Impl.java:182) at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.
java:786) at
weblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityMa
nager.java:757) at
weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:244) at
weblogic.knex.bean.WebProcessBean_lrv41b_HomeImpl.create(WebProcessBean_lrv4
1b_HomeImpl.java:74) at
weblogic.knex.bean.WebDispatcherBean.invoke(WebDispatcherBean.java:69)
at
weblogic.knex.bean.InboundMessageBean$PrivilegedInvoke.run(InboundMessageBea
n.java:114) at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:780) at
weblogic.knex.bean.InboundMessageBean.onMessage(InboundMessageBean.java:185)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:364) at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:29
8) at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2310) at
weblogic.jms.client.JMSSession.execute(JMSSession.java:2233) at
weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213) at
weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
javax.ejb.CreateException: Exception on Create:
javax.ejb.CreateException: SQLException on Create: com.jnetdirect.jsql.x:
Line 1: Incorrect syntax near 'M'. at
weblogic.knex.bean.WebProcessBean.ejbCreate(WebProcessBean.java:1032) at
weblogic.knex.bean.WebProcessBean_lrv41b_Impl.ejbCreate(WebProcessBean_lrv41
b_Impl.java:182) at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.
java:786) at
weblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityMa
nager.java:757) at
weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:244) at
weblogic.knex.bean.WebProcessBean_lrv41b_HomeImpl.create(WebProcessBean_lrv4
1b_HomeImpl.java:74) at
weblogic.knex.bean.WebDispatcherBean.invoke(WebDispatcherBean.java:69)
at
weblogic.knex.bean.InboundMessageBean$PrivilegedInvoke.run(InboundMessageBea
n.java:114) at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:780) at
weblogic.knex.bean.InboundMessageBean.onMessage(InboundMessageBean.java:185)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:364) at
Here is what the BEA driver throws:
java.sql.SQLException: This JDBC 2.0 method is not implemented
at
weblogic.jdbc.mssqlserver4.TdsStatement.clearBatch(TdsStatement.java:2984)
at
weblogic.jdbc.common.internal.ConnectionEnv.cleanUpStatementForReUse(Connect
ionEnv.java:865)
at
weblogic.jdbc.common.internal.ConnectionEnv.dropStatement(ConnectionEnv.java
:849)
at weblogic.jdbc.jts.Statement.close(Statement.java:237)
at weblogic.jdbc.rmi.internal.StatementImpl.close(StatementImpl.java:112)
at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:127)
at weblogic.jdbc.rmi.SerialStatement.close(SerialStatement.java:117)
at weblogic.knex.bean.WebProcessBean.cleanup(WebProcessBean.java:1245)
at weblogic.knex.bean.WebProcessBean.doInsert(WebProcessBean.java:849)
at weblogic.knex.bean.WebProcessBean.ejbCreate(WebProcessBean.java:1024)
at
weblogic.knex.bean.WebProcessBean_lrv41b_Impl.ejbCreate(WebProcessBean_lrv41
b_Impl.java:182)
at java.lang.reflect.Method.invoke(Native Method)
at
weblogic.ejb20.manager.ExclusiveEntityManager.create(ExclusiveEntityManager.
java:786)
at
weblogic.ejb20.manager.ExclusiveEntityManager.remoteCreate(ExclusiveEntityMa
nager.java:757)
at weblogic.ejb20.internal.EntityEJBHome.create(EntityEJBHome.java:244)
at
weblogic.knex.bean.WebProcessBean_lrv41b_HomeImpl.create(WebProcessBean_lrv4
1b_HomeImpl.java:74)
at weblogic.knex.bean.WebDispatcherBean.invoke(WebDispatcherBean.java:69)
at
weblogic.knex.bean.InboundMessageBean$PrivilegedInvoke.run(InboundMessageBea
n.java:114)
at
weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:780)
at
weblogic.knex.bean.InboundMessageBean.onMessage(InboundMessageBean.java:185)
at weblogic.ejb20.internal.MDListener.execute(MDListener.java:364)
at
weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:29
8)
at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:273)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2310)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:2233)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
weblogic.jdbc.mssqlserver4.TdsException: I/O exception while talking to the
server, java.io.EOFException
at
weblogic.jdbc.mssqlserver4.TdsConnection.registerPipeline(TdsConnection.java
:362)
at weblogic.jdbc.mssqlserver4.TdsStatement.execute(TdsStatement.java:185)
at weblogic.jdbc.mssqlserver4.TdsStatement.execute(TdsStatement.java:1499)
at weblogic.jdbc.mssqlserver4.TdsConnection.commit(TdsConnection.java:228)
at weblogic.jdbc.mssqlserver4.BaseConnection.commit(BaseConnection.java:602)
at weblogic.jdbc.jts.Connection.internalCommit(Connection.java:810)
at weblogic.jdbc.jts.Connection.commit(Connection.java:491)
at
weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
ava:1326)
at
weblogic.transaction.internal.ServerResourceInfo.commit(ServerResourceInfo.j
ava:512)
at
weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:237
)
at
weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransa
ctionImpl.java:1490)
at
weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(Server
TransactionImpl.java:2058)
at
weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTrans
actionImpl.java:2005)
at
weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTra
nsactionImpl.java:242)
Will you send me the class files:
weblogic.knex.bean.WebProcessBean.class,
weblogic.knex.bean.WebProcessBean_lrv41b_Impl.ejbCreate.class
ignore the clearBatch() thing for now. It's harmless but we do have a fix.
Joe
"Joseph Weinstein" <j...@bea.com.remove.this> wrote in message
news:3E7F9C3F...@bea.com.remove.this...
Davin Czukoski wrote:
> Where are these located?
>
All are in the server's classpath. Use the weblogic commandline tool
java utils.WhichClass weblogic.knex.bean.WebProcessBean
java utils.WhichClass weblogic.knex.bean.WebProcessBean_lrv41b_Impl.ejbCreate
with your classpath the same as the servers. Extract them from the jar etc.
thanks,
Joe