Edson,
Thanks, enclosed with error with SQL Server from two driver:
***For Jdbc-Odbc bridge, error with jboss-2.4.x-tomcat-3.2.3 when using
MS Sql
Server:
can't load the entity, find works, just can't load, the error message
is:
java.rmi.ServerException: Load failed; nested exception is:
java.sql.SQLException: [Microsoft][ODBC SQL Server Driver]Invalid
Descriptor Index
***And for MS JDBC driver, error when connect use a samal test program:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error
establishing socket.
java.lang.Throwable(java.lang.String)
java.lang.Exception(java.lang.String)
java.sql.SQLException(java.lang.String, java.lang.String)
java.sql.SQLException
com.microsoft.jdbc.base.BaseExceptions.getException(java.sql.SQLExceptio
n, int, int, java.lang.String)
java.sql.SQLException
com.microsoft.jdbc.base.BaseExceptions.getException(java.sql.SQLExceptio
n, int, java.lang.String)
com.microsoft.jdbc.sqlserver.tds.TDSConnection(java.lang.String,
java.lang.String, boolean, com.microsoft.jdbc.base.BaseExceptions)
void com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open()
com.microsoft.jdbc.base.BaseImplConnection
com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(boolean,
int)
void
com.microsoft.jdbc.base.BaseConnection.open(com.microsoft.jdbc.base.Base
ConnectionProperties, com.microsoft.jdbc.base.BaseExceptions,
com.microsoft.util.UtilDebug)
java.sql.Connection
com.microsoft.jdbc.base.BaseDriver.connect(java.lang.String,
java.util.Properties)
java.sql.Connection
java.sql.DriverManager.getConnection(java.lang.String,
java.util.Properties, java.lang.ClassLoader)
java.sql.Connection
java.sql.DriverManager.getConnection(java.lang.String, java.lang.String,
java.lang.String)
java.sql.Connection com.ctbs.jdbc.test.DBAccess.connect()
java.sql.ResultSet
com.ctbs.jdbc.test.DBAccess.executeQuery(java.lang.String)
void com.ctbs.jdbc.test.DBAccess.main(java.lang.String [])
-----Original Message-----
From: Edson Carlos Ericksson Richter [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 14, 2001 10:58 AM
To: David Cao; JBOSS Mail List
Subject: Re: [JBoss-user] MS SQL JDBC Driver problem
Hummm. Trying to cut-off MSSQL is not a idea???
Well, JDBC Driver for SQL2K still beta...
And JDBC-ODBC bridge should not work because is not thread safe...
I'll try something here... But have you not any message error or
something???
Edson Richter
----- Original Message -----
From: "David Cao" <[EMAIL PROTECTED]>
To: "JBOSS Mail List" <[EMAIL PROTECTED]>
Sent: Wednesday, November 14, 2001 2:18 PM
Subject: [JBoss-user] MS SQL JDBC Driver problem
> Hi,
>
> Did any one successful make Jboss works with MS JDBC Driver for SQL
> 2000? the Jdbc-Odbc bridge won't work with Jboss 2.4 (but it work well
> for Jboss 2.2.2), but MS JDBC look not work with Jboss 2.4 also. does
> any body have a success solution?
>
> Thanks a lot.
>
> david
>
> -----Original Message-----
> From: Jose Ramon Diaz [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, November 06, 2001 8:24 AM
> To: danch
> Cc: JBOSS Mail List
> Subject: Re: [JBoss-user] Deadlock with Oracle and Jboss 2.2.1
>
>
> Hi Danch
>
> Sorry, but I don�t understand you, what do you mean with "more
> traditional
> deadlock scenario hunting"? What can I try?
>
> And a second question, although there was several instances of a
> bean,
> wouldn�t the container (JBoss 2.2.1) serialize all the database
access?
>
> Thanks a lot
>
> Jose R. D�az
>
>
> danch wrote:
>
> > If it's called ~5 times a second there's a good possibility
(depending
> > on how long the methods take to execute) that more than one instance
> of
> > the bean would be executing at the same time. Are these different
> > methods, and if so do they perform their accesses in different
orders?
> > that would deadlock pretty easily.
> >
> > You might try bean-managed transactions, but I'd perform more
> > traditional deadlock scenario hunting first.
> >
> > -danch
> >
> > Jose Ramon Diaz wrote:
> >
> > > Hi,
> > >
> > > We have a Stateless bean with JBoss 2.2.1. This EJB makes
> deletes
> > > and updates of several rows, inserts and selects in a table, and
> selects
> > > in other three tables.
> > > That table is only accessed from that EJB. This EJB is called
5
> or 6
> > > times/second. This table usually contains about 200 or 250 rows.
> > > Our problem is that Oracle is detecting deadlocks. If we
access
> that
> > > table only from that EJB, isn�t it supposed to be serialized every
> > > transaction? Why is Oracle detecting a deadlock?
> > > We have configured the EJB as a container managed transaction.
> Would
> > > it be better to be a Bean managed transaction and to make the
> commits
> > > and rollback on our own explicitly?
> > >
> > > Thanks
> > >
> > > Jose R. D�az
> > >
> > >
> > >
> > > _______________________________________________
> > > JBoss-user mailing list
> > > [EMAIL PROTECTED]
> > > https://lists.sourceforge.net/lists/listinfo/jboss-user
> > >
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
