Bug 777733 (SOA-249) - bpm_orchestration1 needs to be updated
Summary: bpm_orchestration1 needs to be updated
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-249
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.2 Beta 1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.2 CP01
Assignee: Kurt Stam
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On: SOA-344
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-20 13:47 UTC by Jiri Pechanec
Modified: 2013-01-11 02:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-02 07:23:33 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777817 0 high CLOSED Debug situation where process image is not available in jBPM console 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 777818 0 high CLOSED bpm_orchestration1 quickstart does not deploy in beta2 build 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 777819 0 high CLOSED org.jbpm.JbpmException: setRollbackOnly was invoked while configuration specifies user managed transactions 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-249 0 None None None Never

Internal Links: 777817 777818 777819

Description Jiri Pechanec 2007-12-20 13:47:44 UTC
Date of First Response: 2008-01-02 09:39:40
project_key: SOA

See JBESB-1417

Comment 1 Jiri Pechanec 2007-12-20 13:47:56 UTC
Link: Added: This issue depends JBESB-1417


Comment 2 Kurt Stam 2008-01-02 14:39:40 UTC
Fixed on the CP branch. SHould be fixed with the next merge.

Comment 3 ryan.campbell 2008-01-02 15:32:48 UTC
Kurt, I'm confused as to why you assigned this to me?

Comment 4 Len DiMaggio 2008-01-18 17:49:07 UTC
Link: Added: This issue related SOA-343


Comment 5 Len DiMaggio 2008-01-18 18:36:38 UTC
Link: Added: This issue related SOA-344


Comment 6 Len DiMaggio 2008-01-18 20:37:29 UTC
Link: Added: This issue related SOA-345


Comment 7 Jiri Pechanec 2008-01-21 09:16:39 UTC
Cennot be verified due to SOA-344

Comment 8 Jiri Pechanec 2008-01-21 09:17:38 UTC
Prevents issue testing

Comment 9 Jiri Pechanec 2008-01-21 09:17:38 UTC
Link: Added: This issue depends SOA-344


Comment 10 Mark Little 2008-01-21 10:19:09 UTC
Since the dependent issue is resolved in CR1, resolving this accordingly.

Comment 11 Jiri Pechanec 2008-01-23 09:11:36 UTC
Verified in CR1

Comment 12 Len DiMaggio 2008-02-11 14:08:01 UTC
Seeing this line in SOA-P CR3:

19:52:36,403 INFO  [EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead.




19:52:35,786 WARN  [ProxyWarnLog] Narrowing proxy to class org.jbpm.graph.node.StartState - this operation breaks ==
19:52:35,802 INFO  [STDOUT] Executed by the process, not by the ESB
19:52:36,010 INFO  [STDOUT] 1********** Begin Service 1 ***********
19:52:36,012 INFO  [STDOUT] In: Start It Up
19:52:36,013 INFO  [STDOUT] Out: Service 1 Start It Up
19:52:36,013 INFO  [STDOUT] ************ End Service 1 ************
19:52:36,403 INFO  [EsbActionHandler] millisToWaitForResponse is no longer a valid element, please use a jBPM timer for this node instead.
19:52:36,581 INFO  [STDOUT] 2********** Begin Service 2 ***********
19:52:36,582 INFO  [STDOUT] In: Service 1 Start It Up
19:52:36,582 INFO  [STDOUT] Out: Service 2 Service 1 Start It Up
19:52:36,582 INFO  [STDOUT] ************ End Service 2 ************
19:52:36,975 INFO  [STDOUT] 3********** Begin Service 3 ***********
19:52:36,976 INFO  [STDOUT] In: Service 2 Service 1 Start It Up
19:52:36,976 INFO  [STDOUT] Out: Service 3 Service 2 Service 1 Start It Up
19:52:36,976 INFO  [STDOUT] ************ End Service 3 ************
19:52:37,177 INFO  [STDOUT] Executed by the process, not by the ESB
19:52:37,362 INFO  [MessageSpy] Body: Service 3 Service 2 Service 1 Start It Up

Comment 13 Kurt Stam 2008-02-11 15:21:13 UTC
removed  millisToWaitForResponse statement

Comment 14 Jiri Pechanec 2008-04-02 07:23:33 UTC
Verified in CP01


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