Problem with LOBs in JDBC Provider

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1-rc1
  • Fix Version/s: 1.3-rc2
  • Component/s: Transport: JDBC
  • Labels:
    None
  • Similar Issues:
    None

Description

I'm trying to use Mule to retrieve database data from Oracle BLOB.
There is a problem with no connection to database while getting blob content from a stream.
(I use a transaction in my Mule endpoint config.)

Polling method (JdbcMessageReceiver.getMessages) cause problem, because transaction doesn't include this method.
Message construction by polling method is realized by hash map containing row set columns.
One of this columns can be a blob.
When message is transofrmed by transformer, connection is lost, so you can't open blob stream.

Issue Links

relates to

Patch submission - User code to be reviewed and incorporated into the product. MULE-751 JdbcUtils.getParams returns null when root is a Map, even if there is a property with the correct name on endpoint

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ross Mason added a comment -

Hi,

thanks for reporting. I'll have to see if I have an Oracle instance anywhere to try and fix it. Do you have a testcase for this issue I can use?

Cheers,

Ross

Show
Ross Mason added a comment - Hi, thanks for reporting. I'll have to see if I have an Oracle instance anywhere to try and fix it. Do you have a testcase for this issue I can use? Cheers, Ross
Hide
Permalink
David Oram added a comment -

Hi,

First things first - this is my first post to the Mule Jira - thanks to all the Mule development team. I am using Mule 1.1 as the backbone for a large governmental application integration project, and it has served us extreemly well.

I have developed a patch that might help this particular issue. It addresses the following problems that I encountered when using Mule:

1) Allows the end user to override the default ResultSetHandler for a given endpoint. We have used this to read CLOB's from Oracle.

2) Allows the user to override the default QueryRunner. This solved a problem when interfacing with our Ingres database where the default QueryRunner didn't read null values correctly.

3) The systems we are integrating via Mule, have null values in the database tables. In our situation nulls are valid, so I patched JdbcUtils class so that when a null value for a given property is encountered it is accepted rather than rejected.

I have attached the patch files (created via Eclipse - using the 'context' diff output format- is that best?), created against the latest version of the code

Risks: The patch has been developed against the latest code, and I you will note that the patch does not include a Unit test for the changes. [Ross/Travis - If you can point me in the right direction I would gladly undertake this task].

Cheers,

Dave Oram

Show
David Oram added a comment - Hi, First things first - this is my first post to the Mule Jira - thanks to all the Mule development team. I am using Mule 1.1 as the backbone for a large governmental application integration project, and it has served us extreemly well. I have developed a patch that might help this particular issue. It addresses the following problems that I encountered when using Mule: 1) Allows the end user to override the default ResultSetHandler for a given endpoint. We have used this to read CLOB's from Oracle. 2) Allows the user to override the default QueryRunner. This solved a problem when interfacing with our Ingres database where the default QueryRunner didn't read null values correctly. 3) The systems we are integrating via Mule, have null values in the database tables. In our situation nulls are valid, so I patched JdbcUtils class so that when a null value for a given property is encountered it is accepted rather than rejected. I have attached the patch files (created via Eclipse - using the 'context' diff output format- is that best?), created against the latest version of the code Risks: The patch has been developed against the latest code, and I you will note that the patch does not include a Unit test for the changes. [Ross/Travis - If you can point me in the right direction I would gladly undertake this task]. Cheers, Dave Oram
Hide
Permalink
Ross Mason added a comment -

I've jst applied these patches. Thanks Sebastian. Sorry for the delay

Show
Ross Mason added a comment - I've jst applied these patches. Thanks Sebastian. Sorry for the delay

People

Vote (0)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: