PM
Subject: Re: [JBoss-user] JMS persistence manager for Oracle8
On Monday, February 17, 2003, at 02:51 PM, Rod Macpherson wrote:
I still hold there is no
4K limit using JDBC calls.
I have tested this in the past using straight java(x).sql.* calls and
was unable to get it to work unless
I believe the direct support is through Oracle specific API's.
FALSE.
The JDBC API works fine with the underlying driver which is obviously
oracle-specific. There is no problem using LOBs except when using jboss. The
same method that works in a stand-alone executable and under weblogic fails
in
Sorry, I really should not respond to questions at 2:00AM!
:-)
If you have just hacked, er, modified the standard jbossmq-service.xml
file, then the CREATE_MESSAGE_TABLE string will be wrong for Oracle,
and this will yield the invalid column type exception that you are
seeing below.
On Sunday, February 16, 2003, at 06:51 PM, Rod Macpherson wrote:
I believe the direct support is through Oracle specific API's.
FALSE.
The JDBC API works fine with the underlying driver which is obviously
oracle-specific. There is no problem using LOBs except when using
jboss. The
same
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, February 16, 2003 5:22 AM
Subject: Re: [JBoss-user] JMS persistence manager for Oracle8
On Sunday, February 16, 2003, at 06:51 PM, Rod Macpherson wrote:
I believe the direct support is through Oracle specific API's.
FALSE.
The JDBC API
On Monday, February 17, 2003, at 12:47 PM, Rod Macpherson wrote:
The standard JDBC result set returns the blob without any
vendor-specific
magic aside from using the correct driver. The actual column type is an
oracle blob and we use that to update the column by writing a stream
supplied by
Doesn't this [code] just confirm my remark:
That you need oracle-specific code to exceed the 4K limit? It does not
confirm that because it fails under jboss and works everywhere else. The
oracle-specific code is just a convenience after using vanilla JDBC to get
the blob, but that's not very
On Monday, February 17, 2003, at 02:51 PM, Rod Macpherson wrote:
I still hold there is no
4K limit using JDBC calls.
I have tested this in the past using straight java(x).sql.* calls and
was unable to get it to work unless the oci driver was used. I suspect
that weblogic is using the Oracle
Enough already
As of 9.2.0:
Oracle do not support the standard JDBC stream APIs for BLOBs with the
thin driver. This includes setObject()
Oracle support the standard API with the OCI driver.
Oracle support their own API with the thin driver.
Oracle do not support the JDBC3.0 Blob write API
JBoss
Hi,
I just can't get the JBossMQ persistence manager to work with an Oracle8
data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are
successfully created (using BLOB_TYPE=BLOB and the sql statement
CREATE_MESSAGE_TABLE = CREATE TABLE JMS_MESSAGES ( MESSAGEID INTEGER NOT
NULL, \
Is this JBoss 2.4?
Anyway, it smells like a problem with your JDBC driver - get the latest
Oracle 9.2 JDBC drivers, even if you're backend is Oracle 8.
For more information, see the Oracle BLOB FAQ in the JBoss FAQ forum.
Steve Coy
On Saturday, February 15, 2003, at 10:20 PM, Marek Lange
Is this JBoss 2.4?
This is JBoss 3.2RC1.
Anyway, it smells like a problem with your JDBC driver - get the latest
Oracle 9.2 JDBC drivers, even if you're backend is Oracle 8.
For more information, see the Oracle BLOB FAQ in the JBoss FAQ forum.
Thanks for your tip, Stephen, I tried the 9.2
PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, February 15, 2003 6:20 AM
Subject: [JBoss-user] JMS persistence manager for Oracle8
Hi,
I just can't get the JBossMQ persistence manager to work with an
Oracle8
data source. The tables JMS_TRANSACTIONS and JMS_MESSAGES are
successfully created
This is JBoss 3.2RC1.
Anyway, it smells like a problem with your JDBC driver - get the
latest Oracle 9.2 JDBC drivers, even if you're backend is Oracle 8.
For more information, see the Oracle BLOB FAQ in the JBoss FAQ forum.
Thanks for your tip, Stephen, I tried the 9.2 driver and read your
How is your datasource configured to connect to Oracle: oci or thin?
I've never stored BLOBs in Oracle - don't believe in it. But I've read
on this list repeatedly that using the thin driver to store blobs won't
work, you need the oci driver.
It's a 9i thin driver. From the Oracle JDBC Drivers
: Re: [JBoss-user] JMS persistence manager for Oracle8
How is your datasource configured to connect to Oracle: oci or thin?
I've never stored BLOBs in Oracle - don't believe in it. But I've read
on this list repeatedly that using the thin driver to store blobs won't
work, you need the oci
On Sunday, February 16, 2003, at 05:14 AM, Marek Lange wrote:
It's a 9i thin driver. From the Oracle JDBC Drivers release 9.2.0
README:
Direct support for LOBs in the Thin driver.
The Thin driver now provides direct support for BFILEs, BLOBs, and
CLOBs.
But you have to read between the
Sorry, I really should not respond to questions at 2:00AM!
If you have just hacked, er, modified the standard jbossmq-service.xml
file, then the CREATE_MESSAGE_TABLE string will be wrong for Oracle,
and this will yield the invalid column type exception that you are
seeing below. There's an
18 matches
Mail list logo
