Bug 777984 (SOA-513) - helloworld_tx_sql_action quickstart - transaction processing error
Summary: helloworld_tx_sql_action quickstart - transaction processing error
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-513
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.2 CP01
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-10 13:29 UTC by Jehudi Castro Sierra
Modified: 2013-01-11 02:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-15 17:21:35 UTC
Type: Bug


Attachments (Terms of Use)
CP01_server.log (4.74 MB, text/x-log)
2008-04-10 19:45 UTC, Len DiMaggio
no flags Details
GA_server.log (4.94 MB, text/x-log)
2008-04-10 19:45 UTC, Len DiMaggio
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777985 0 high CLOSED helloworld_tx_sql_action quickstart - intermittent timing error - quickstart sometimes fails to start - infinite loop 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBQA-1570 0 None Closed SOA-P - 4.2.0 GA - Tier 1 - need a new automated test for helloworld_tx_sql_action - JBESB-1648 2012-04-19 14:36:36 UTC
Red Hat Issue Tracker SOA-513 0 None Closed helloworld_tx_sql_action quickstart - transaction processing error 2012-04-19 14:36:36 UTC

Internal Links: 777985

Description Jehudi Castro Sierra 2008-04-10 13:29:38 UTC
Date of First Response: 2008-04-10 09:42:47
project_key: SOA

see  JBESB-1648

Comment 1 Jiri Pechanec 2008-04-10 13:42:12 UTC
Link: Added: This issue depends JBESB-1648


Comment 2 Jiri Pechanec 2008-04-10 13:42:47 UTC
Increasing severity level to spur investigation - the issue can be not in quickstart but in TX processing

Comment 3 Mark Little 2008-04-10 18:26:18 UTC
No, the issue could well be with the quickstart.

Comment 4 Jiri Pechanec 2008-04-10 18:33:40 UTC
That is what I meant, just to clarify
Increasing severity level to spur investigation - the issue can be not only in quickstart but also in TX processing

Comment 5 Len DiMaggio 2008-04-10 18:51:38 UTC
Link: Added: This issue related SOA-514


Comment 6 Len DiMaggio 2008-04-10 19:45:05 UTC
Attaching sever logs  from GA and CP01.

The test runs successfully in GA - not in CP01.



Comment 7 Len DiMaggio 2008-04-10 19:45:06 UTC
Attachment: Added: CP01_server.log
Attachment: Added: GA_server.log


Comment 8 Kevin Conner 2008-04-14 09:21:24 UTC
The issue is in the TX processing and there are two parts to it.

- add the correct TX code to message aware listener (after the rewrite)
- fix the SQL resource handling

The first is my fault and I am about to commit the changes into our CP branch and trunk.  The second was raised by Tom Fennelly shortly before the CP release and he has been working on fixing this.

The fact that this QS worked in the GA release appears to have been a fluke.

Comment 9 Kevin Conner 2008-04-14 09:25:15 UTC
I'll follow this up.

Comment 10 Len DiMaggio 2008-04-15 14:38:39 UTC
Link: Added: This issue related JBQA-1570


Comment 11 Len DiMaggio 2008-04-15 17:21:35 UTC
Closing - fix verified in April 15 2008 CP01 build.

This message - in the server.log -  may be alarming at first glance:

12:24:28,140 INFO  [STDOUT] BAD READ ON DATA!

But - it is correct:

                  // Set message properties and message body so that SystemPrintln will display message 
                  message.getProperties().setProperty("jbesbfilename", "helloworldTxSQlAction.log");
                  message.getBody().add(results.toString());

                  if (problem)
                          System.out.println("Will rollback transaction. Expect to see record again!");
                  else
                          System.out.println("Will commit transaction. Will not see record again!");

                  if (!problem)
                          return message;
                  else
                  {
                          System.out.println("BAD READ ON DATA!");

                          throw new RuntimeException();
                  }


&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
12:24:28,139 INFO  [STDOUT] DATA READ: data 22
12:24:28,140 INFO  [STDOUT] column DATA_COLUMN = <data 22>column TIMESTAMP_COL = <null>column UNIQUE_ID = <2>
12:24:28,140 INFO  [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
12:24:28,140 INFO  [STDOUT] Will rollback transaction. Expect to see record again!
12:24:28,140 INFO  [STDOUT] BAD READ ON DATA!
12:24:28,142 WARN  [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JDBCEpr [ PortReference < <wsa:Address jdbc:hsqldb:hsql://localhost:1703/>, <wsa:ReferenceProperties jbossesb:postDelete : true/>, <wsa:ReferenceProperties jbossesb:errorDelete : true/>, <wsa:ReferenceProperties jbossesb:datasource : java:/QuickstartDB/>, <wsa:ReferenceProperties jbossesb:tablename : TX_ESB_MESSAGES/>, <wsa:ReferenceProperties jbossesb:message_id_column : MESSAGE_ID/>, <wsa:ReferenceProperties jbossesb:status_column : STATUS_COL/>, <wsa:ReferenceProperties jbossesb:message_column : DATA_COLUMN/>, <wsa:ReferenceProperties jbossesb:insert_timestamp_column : TIMESTAMP_COL/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jdbc/> > ] MessageID: 18fe7384-e01b-42e0-a10b-28337f1e252f ]
java.lang.RuntimeException
        at org.jboss.soa.esb.samples.quickstart.helloworldtxsqlaction.MyAction.displayMessage(MyAction.java:74)
        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)
12:24:28,181 ERROR [STDERR] Exception in thread "pool-9-thread-1" 
12:24:28,182 ERROR [STDERR] java.lang.RuntimeException
12:24:28,182 ERROR [STDERR]     at org.jboss.soa.esb.samples.quickstart.helloworldtxsqlaction.MyAction.displayMessage(MyAction.java:74)
12:24:28,182 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
12:24:28,182 ERROR [STDERR]     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
12:24:28,182 ERROR [STDERR]     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
12:24:28,182 ERROR [STDERR]     at java.lang.reflect.Method.invoke(Method.java:585)
12:24:28,182 ERROR [STDERR]     at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102)
12:24:28,182 ERROR [STDERR]     at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74)
12:24:28,182 ERROR [STDERR]     at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
12:24:28,183 ERROR [STDERR]     at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530)
12:24:28,183 ERROR [STDERR]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
12:24:28,183 ERROR [STDERR]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
12:24:28,183 ERROR [STDERR]     at java.lang.Thread.run(Thread.java:595)
12:24:28,184 INFO  [STDOUT] 
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
12:24:28,184 INFO  [STDOUT] DATA READ: data 22
12:24:28,185 INFO  [STDOUT] column DATA_COLUMN = <data 22>column TIMESTAMP_COL = <null>column UNIQUE_ID = <2>
12:24:28,185 INFO  [STDOUT] &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
12:24:28,185 INFO  [STDOUT] Will commit transaction. Will not see record again!
12:24:28,186 INFO  [STDOUT] Message structure: 
12:24:28,186 INFO  [STDOUT] [column DATA_COLUMN = <data 22>column TIMESTAMP_COL = <null>column UNIQUE_ID = <2>].
12:24:28,262 INFO  [STDOUT] 



Note You need to log in before you can comment on or make changes to this bug.