[esb-issues] [JBoss JIRA] Commented: (JBESB-1833) SQLCourier BLOB/CLOB support does not work on Oracle

[Kevin Conner (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12421674#action_12421674 ] 

Kevin Conner commented on JBESB-1833:
-------------------------------------

Trunk updated in revision 21085.

> SQLCourier BLOB/CLOB support does not work on Oracle
> ----------------------------------------------------
>
>                 Key: JBESB-1833
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1833
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.3, 4.2.1 CP3
>            Reporter: Jiri Pechanec
>            Assignee: Kevin Conner
>             Fix For: 4.2.1 CP4, 4.4
>
>
> The BLOB and CLOB support, added as part of JBESB-1690, is not sufficient for oracle
> When the table contains BLOB or CLOB which does not contain value - has null value the following exceptions are thrown
> java.lang.NullPointerException
>         at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.pollForCandidates(SqlTableGatewayListener.java:490)
>         at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:177)
>         at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
>         at java.lang.Thread.run(Thread.java:595)
> java.lang.NullPointerException
>         at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.pollForCandidates(SqlTableGatewayListener.java:493)
>         at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:177)
>         at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
>         at java.lang.Thread.run(Thread.java:595)
> When the SQL courier tries to write message to the table the following exception is thrown
> java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
>         at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
>         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
>         at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
>         at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
>         at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
>         at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
>         at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
>         at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316)
>         at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3400)
>         at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:278)
>         at org.jboss.internal.soa.esb.couriers.SqlTableCourier.deliver(SqlTableCourier.java:158)
>         at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:188)
>         at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.attemptDelivery(ServiceInvoker.java:525)
>         at org.jboss.soa.esb.client.ServiceInvoker$EPRInvoker.access$200(ServiceInvoker.java:447)
>         at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:316)
>         at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:225)
>         at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:202)
>         at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
>         at java.lang.Thread.run(Thread.java:595)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira