Aaron-
The reason I think it is not working is because, as far as I can tell, a
table is NOT successfully being created in the SQL Server database I
requested (despite the fact that the JBoss log says the table IS being
created).
I enabled the SQL trace capabilities on the ODBC DSN and can see JBoss
"submitting" the SQL to CREATE the table (an excerpt from the "sql.log"
generated by the ODBC-layer tracing is included below). However, when I go
into the SQL Server Enterprise Manager to see the newly-created table, SQL
Enterprise Manager "hangs" until I shutdown JBoss. After JBoss is shutdown,
SQL Enterprise Manager operates normally, but does NOT show the table being
present in the SQL Server database.
Will JBoss retain a table it has created if that table does not have any
entity bean info (rows) persisted into it?
In my case, I am deploying an entity bean, but have not created instances of
the entity bean (rows in the table) yet. If I shutdown JBoss, should the
table be persisted with no rows in it? I am assuming the answer is "Yes",
but it appears in practice the answer is "No." It appears that the CREATE
TABLE statement is successfully executed, but is perhaps being "rolled back"
when JBoss is shutdown.
Thanks again, Aaron, for looking into this.
-Mark
conf" -Dtomcat. 310-394 ENTER SQLExecDirect
HSTMT 09582350
UCHAR * 0x08AFA9C8 [ -3] "SELECT COUNT(*)
FROM joelull WHERE 0=1\ 0"
SDWORD -3
conf" -Dtomcat. 310-394 EXIT SQLExecDirect with return code -1 (SQL_ERROR)
HSTMT 09582350
UCHAR * 0x08AFA9C8 [ -3] "SELECT COUNT(*)
FROM joelull WHERE 0=1\ 0"
SDWORD -3
DIAG [S0002] [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'joelull'. (208)
conf" -Dtomcat. 310-394 ENTER SQLErrorW
HENV 00000000
HDBC 00000000
HSTMT 09582350
WCHAR * 0x0006ECFC (NYI)
SDWORD * 0x0006ED40
WCHAR * 0x0006E8FC
SWORD 300
SWORD * 0x0006ED3C
conf" -Dtomcat. 310-394 EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 00000000
HDBC 00000000
HSTMT 09582350
WCHAR * 0x0006ECFC (NYI)
SDWORD * 0x0006ED40 (208)
WCHAR * 0x0006E8FC [ 77] "[Microsoft][ODBC
SQL Server Driver][SQ"
SWORD 300
SWORD * 0x0006ED3C (77)
conf" -Dtomcat. 310-394 ENTER SQLErrorW
HENV 00000000
HDBC 00000000
HSTMT 09582350
WCHAR * 0x0006ECFC (NYI)
SDWORD * 0x0006ED40
WCHAR * 0x0006E8FC
SWORD 300
SWORD * 0x0006ED3C
conf" -Dtomcat. 310-394 EXIT SQLErrorW with return code 100
(SQL_NO_DATA_FOUND)
HENV 00000000
HDBC 00000000
HSTMT 09582350
WCHAR * 0x0006ECFC (NYI)
SDWORD * 0x0006ED40
WCHAR * 0x0006E8FC
SWORD 300
SWORD * 0x0006ED3C
conf" -Dtomcat. 310-394 ENTER SQLFreeStmt
HSTMT 09582350
UWORD 1 <SQL_DROP>
conf" -Dtomcat. 310-394 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 09582350
UWORD 1 <SQL_DROP>
conf" -Dtomcat. 310-394 ENTER SQLAllocStmt
HDBC 09581598
HSTMT * 0006EDD4
conf" -Dtomcat. 310-394 EXIT SQLAllocStmt with return code 0 (SQL_SUCCESS)
HDBC 09581598
HSTMT * 0x0006EDD4 ( 0x09582350)
conf" -Dtomcat. 310-394 ENTER SQLSetStmtOption
HSTMT 09582350
UWORD 6 <SQL_CURSOR_TYPE>
SQLLEN 0
conf" -Dtomcat. 310-394 EXIT SQLSetStmtOption with return code 0
(SQL_SUCCESS)
HSTMT 09582350
UWORD 6 <SQL_CURSOR_TYPE>
SQLLEN 0
conf" -Dtomcat. 310-394 ENTER SQLSetStmtOption
HSTMT 09582350
UWORD 7 <SQL_CONCURRENCY>
SQLLEN 1
conf" -Dtomcat. 310-394 EXIT SQLSetStmtOption with return code 0
(SQL_SUCCESS)
HSTMT 09582350
UWORD 7 <SQL_CONCURRENCY>
SQLLEN 1
conf" -Dtomcat. 310-394 ENTER SQLPrepare
HSTMT 09582350
UCHAR * 0x08B06D28 [ -3] "CREATE TABLE
joelull (description VARCHAR(256),value INTEGER,id INTEGER)\ 0"
SDWORD -3
conf" -Dtomcat. 310-394 EXIT SQLPrepare with return code 0 (SQL_SUCCESS)
HSTMT 09582350
UCHAR * 0x08B06D28 [ -3] "CREATE TABLE
joelull (description VARCHAR(256),value INTEGER,id INTEGER)\ 0"
SDWORD -3
conf" -Dtomcat. 310-394 ENTER SQLNumParams
HSTMT 09582350
SWORD * 0x0006EDA8
conf" -Dtomcat. 310-394 EXIT SQLNumParams with return code 0 (SQL_SUCCESS)
HSTMT 09582350
SWORD * 0x0006EDA8 (0)
conf" -Dtomcat. 310-394 ENTER SQLFreeStmt
HSTMT 09582350
UWORD 0 <SQL_CLOSE>
conf" -Dtomcat. 310-394 EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 09582350
UWORD 0 <SQL_CLOSE>
conf" -Dtomcat. 310-394 ENTER SQLExecute
HSTMT 09582350
conf" -Dtomcat. 310-394 EXIT SQLExecute with return code 0 (SQL_SUCCESS)
HSTMT 09582350
conf" -Dtomcat. 310-394 ENTER SQLNumResultCols
HSTMT 09582350
SWORD * 0x0006ED78
conf" -Dtomcat. 310-394 EXIT SQLNumResultCols with return code 0
(SQL_SUCCESS)
HSTMT 09582350
SWORD * 0x0006ED78 (0)
conf" -Dtomcat. 310-394 ENTER SQLNumResultCols
HSTMT 09582350
SWORD * 0x0006ED94
conf" -Dtomcat. 310-394 EXIT SQLNumResultCols with return code 0
(SQL_SUCCESS)
HSTMT 09582350
SWORD * 0x0006ED94 (0)
conf" -Dtomcat. 310-394 ENTER SQLRowCount
HSTMT 09582350
SQLLEN * 0x0006ED94
conf" -Dtomcat. 310-394 EXIT SQLRowCount with return code 0 (SQL_SUCCESS)
HSTMT 09582350
SQLLEN * 0x0006ED94 (-1)
conf" -Dtomcat. 310-4dc ENTER SQLFreeStmt
HSTMT 09582350
UWORD 1 <SQL_DROP>
conf" -Dtomcat. 310-4dc EXIT SQLFreeStmt with return code 0 (SQL_SUCCESS)
HSTMT 09582350
UWORD 1 <SQL_DROP>
conf" -Dtomcat. 310-4dc ENTER SQLDisconnect
HDBC 09581598
conf" -Dtomcat. 310-4dc EXIT SQLDisconnect with return code -1 (SQL_ERROR)
HDBC 09581598
DIAG [25000] [Microsoft][ODBC SQL Server Driver]Invalid
transaction state (0)
conf" -Dtomcat. 310-4dc ENTER SQLErrorW
HENV 00000000
HDBC 09581598
HSTMT 00000000
WCHAR * 0x0988F718 (NYI)
SDWORD * 0x0988F75C
WCHAR * 0x0988F318
SWORD 300
SWORD * 0x0988F758
conf" -Dtomcat. 310-4dc EXIT SQLErrorW with return code 0 (SQL_SUCCESS)
HENV 00000000
HDBC 09581598
HSTMT 00000000
WCHAR * 0x0988F718 (NYI)
SDWORD * 0x0988F75C (0)
WCHAR * 0x0988F318 [ 60] "[Microsoft][ODBC
SQL Server Dr"
SWORD 300
SWORD * 0x0988F758 (60)
conf" -Dtomcat. 310-4dc ENTER SQLErrorW
HENV 00000000
HDBC 09581598
HSTMT 00000000
WCHAR * 0x0988F718 (NYI)
SDWORD * 0x0988F75C
WCHAR * 0x0988F318
SWORD 300
SWORD * 0x0988F758
conf" -Dtomcat. 310-4dc EXIT SQLErrorW with return code 100
(SQL_NO_DATA_FOUND)
HENV 00000000
HDBC 09581598
HSTMT 00000000
WCHAR * 0x0988F718 (NYI)
SDWORD * 0x0988F75C
WCHAR * 0x0988F318
SWORD 300
SWORD * 0x0988F758
-----Original Message-----
From: Aaron Mulder [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 12, 2000 4:05 PM
To: jBoss
Cc: Van Bruggen, Pete
Subject: Re: [jBoss-User] CMP entity bean deployment inoperable using
JDBC -ODBC bridge to Microsoft SQL Server 7
It doesn't look like there's any problem to me! The pool is
initialized, it successfully opens a connection, JAWS creates a
table... Why do you think it's not working?
Also, the DataSourceImpl is no longer supported so your
configuration is correct.
Aaron
On Thu, 12 Oct 2000, McLain, Mark wrote:
> Aaron-
>
> Here is the information you requested. Thanks for taking a look.
>
> While I have your attention, one other question comes to mind: The
approach
> I am taking (detailed in the files below) is different from the jdbc-odbc
> approach posted to jboss-user by Steve Kwee on June 27, 2000 at 8:20pm.
In
> his approach, the MLET is defined to use "org.jboss.jdbc.DataSourceImpl".
> My MLET is using "org.jboss.jdbc.XADataSourceLoader". Is his approach
still
> valid, or does the XADataSourceLoader supersede the DataSourceImpl? (My
> implementation is derived from following the "Advanced Configuration"
> section of the "JBoss 2.0 Manual" in the "Getting Started" section of the
> JBoss website. I am not sure how Steve came up with his approach.)
>
> -Mark
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
