[esb-issues] [JBoss JIRA] Closed: (JBESB-1834) SQLCourier BLOB support does not work on mysql

Kevin Conner (JIRA) jira-events at lists.jboss.org
Tue Jul 15 14:13:54 EDT 2008


     [ http://jira.jboss.com/jira/browse/JBESB-1834?page=all ]

Kevin Conner closed JBESB-1834.
-------------------------------

    Resolution: Done

The changes for JBESB-1805 cover this case.

> SQLCourier BLOB support does not work on mysql
> ----------------------------------------------
>
>                 Key: JBESB-1834
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1834
>             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
>         Assigned To: Kevin Conner
>             Fix For: 4.2.1 CP4, 4.4
>
>         Attachments: jboss-esb.xml, mysql-tx.log.gz, mysql-xa-ds.xml
>
>
> The BLOB support, added as part of JBESB-1690, is not sufficient for mysql.
> When the BYTEA datatype is used the record is read from gw table and status changed to D but the record in ESB message table is not nevertheless created.
> When varchar and text datatype are used and the exception is thrown the transaction is correctly rolled back but the record in ESB message table has status set to D, so no retry is exexcuted
> 2008-06-19 15:46:10,081 WARN  [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JDBCEpr [ PortReference < <wsa:Address jdbc:mysql://localhost:3306/soaesb1/>, <wsa:ReferenceProperties jbossesb:errorDelete : true/>, <wsa:ReferenceProperties jbossesb:datasource : java:/DefaultXADS/>, <wsa:ReferenceProperties jbossesb:tablename : CLOB_ESB_MESSAGE_TABLE/>, <wsa:ReferenceProperties jbossesb:message_id_column : UNIQUE_ID/>, <wsa:ReferenceProperties jbossesb:status_column : STATUS_COL/>, <wsa:ReferenceProperties jbossesb:message_column : CLOB_DATA_COLUMN/>, <wsa:ReferenceProperties jbossesb:insert_timestamp_column : TIMESTAMP_COL/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jdbc/> > ] MessageID: f37d7f32-eef1-45e5-b1b9-8bf72ae782d9 ]
> java.lang.NullPointerException: Simulate exception
>         at org.jboss.soa.esb.samples.quickstart.tx_bpm.FailingAction.process(FailingAction.java:45)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
>         at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
>         at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
>         at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)
> 2008-06-19 15:46:10,082 TRACE [org.jboss.soa.esb.common.JBossESBPropertyService$JTATransactionStrategy] Rollback transaction on current thread
> 2008-06-19 15:46:10,092 ERROR [STDERR] Exception in thread "pool-63-thread-1"
> 2008-06-19 15:46:10,092 ERROR [STDERR] java.lang.NullPointerException: Simulate exception
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at org.jboss.soa.esb.samples.quickstart.tx_bpm.FailingAction.process(FailingAction.java:45)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at java.lang.reflect.Method.invoke(Method.java:585)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
> 2008-06-19 15:46:10,092 ERROR [STDERR]  at java.lang.Thread.run(Thread.java:595)
> Please see attached log file, jboss-esb.xml file and datasource config file.

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

        



More information about the esb-issues mailing list