Comment on Event Driven Business Process Management in jBPM5 by Lillian A

Lillian A — Fri, 20 Apr 2012 16:21:31 +0000

Excellent article! I created my own listener and logged the run of one of my working processes. I was shocked by the output. It appears that the listener runs on the SAME thread (as seen in the log) and yet the logging is out of order, even the "afterProcessCompleted" event. Am I doing something wrong? I use jBPM5.2 with Drools 5.3 on Jboss App Server 7.1 final. Thank you for any insight you can offer.


Line 278: 11:53:01,726 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeProcessStarted
	Line 280: 11:53:01,742 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 281: 11:53:01,742 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 282: 11:53:01,757 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 291: 11:53:01,757 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 292: 11:53:01,757 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 295: 11:53:01,773 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 296: 11:53:01,773 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 297: 11:53:01,773 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 298: 11:53:01,773 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 299: 11:53:01,773 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 300: 11:53:01,773 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 301: 11:53:01,788 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 302: 11:53:01,788 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 303: 11:53:01,788 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 304: 11:53:01,788 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterProcessStarted
	Line 306: 11:53:01,804 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 307: 11:53:01,804 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 312: 11:53:01,804 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 313: 11:53:01,804 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 3976: 11:53:10,806 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 3977: 11:53:10,806 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 3978: 11:53:10,806 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 3979: 11:53:10,806 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 4079: 11:53:10,946 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 4080: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeTriggered
	Line 4081: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeNodeLeft
	Line 4082: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) beforeProcessCompleted
	Line 4083: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterProcessCompleted
	Line 4084: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 4085: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 4086: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 4087: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 4088: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 4089: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 4090: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 4091: 11:53:10,962 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 4092: 11:53:10,977 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft
	Line 4093: 11:53:10,977 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeTriggered
	Line 4094: 11:53:10,977 INFO  [FrameworkEventMonitor] (http--0.0.0.0-8080-2) afterNodeLeft

The BPMN is as follows.


 


  
  
  
  
  
  
  
  
  

  

    
     
     
     
     
     
     
     
     
    
    
    
    
    
    
    
    
    
    
    

    
    
        
    
    
    
    
    
      try
{
MonitorUtil.monitor(kcontext) ;

// prepare the feed for the decision table
AnIMSFile projectFile  =null ; 

try {
         projectFile =  imsFileNoun.find(projectName) ;
} catch (Exception e) { System.out.println ("noun!!!!!!!!!!!") ; e.printStackTrace(); }

Boolean foundIt = (projectFile != null) ;

//global String projectUID
projectUID = "" ;
if (foundIt) {  projectUID= projectFile.getFileUID(); }

kcontext.setVariable ("projectUID",projectUID);
kcontext.setVariable ("found", foundIt) ;

//System.out.println (projectName + projectUID  + "     " + foundIt) ;
//System.out.println ("------------------------------------------------------FOUND-----------------    " + foundIt) ;

 }catch (Exception e)  { e.printStackTrace(); }
    
    
      
        
        
        
        
        
        
        
        
          _20_userNameInput
          _20_projectNameInput
          _20_DueDateInput
          _20_ListNameInput
          _20_AssignedToInput
          _20_TitleInput
        
        
          _20_serviceResultsOutput
        
      
      
        userName
        _20_userNameInput
      
      
        projectName
        _20_projectNameInput
      
      
        _20_DueDateInput
        
          TODO
          _20_DueDateInput
        
      
      
        _20_ListNameInput
        
          Tasks for IBE Developers
          _20_ListNameInput
        
      
      
        _20_AssignedToInput
        
          Lillian Andres
          _20_AssignedToInput
        
      
      
        _20_TitleInput
        
          check project - may need to add to the database
          _20_TitleInput
        
      
      
        _20_serviceResultsOutput
        serviceResults
      
    
    
        
    
    
      try
{
//System.out.println("Gather Work Packages from Active Detail Tasks");

MonitorUtil.monitor(kcontext) ;

filteredOutputTasks.getWorkPkgsFromActiveTasks();	// sets workPkds

//System.out.println("DONE Gather Work Packages from Active Detail Tasks");
 } catch (Exception e)  { e.printStackTrace(); }
    
    
      try
{
MonitorUtil.monitor(kcontext) ;

String forLog = filteredOutputTasks.myScriptDisplayTask(rangeInDays, statusDate, "\n");

System.out.println("=======================================");
System.out.println (forLog) ;
System.out.println("=======================================");
    	
MonitorUtil.stopMonitorProcess(kcontext) ;
} catch (Exception e)  { e.printStackTrace(); }
    
    
      
System.out.println("user name is " + userName ) ;
System.out.println("statusDate is " + statusDate) ;
System.out.println("range in days " + rangeInDays) ;
System.out.println("project name  is " + projectName) ;

MonitorUtil.monitor(kcontext) ;


	
      
    
    
      try
{
MonitorUtil.monitor(kcontext) ;


//System.out.println (projectName + " = " + projectUID) ;
//System.out.println ("filteredOutputTasks = " + filteredOutputTasks) ;
try {	
       filteredOutputTasks.fillRulePassedTasks (projectUID) ;
       } catch (Exception e) { e.printStackTrace(); }
       
filteredOutputTasks.myScriptGetActiveAndActiveNearTermTasks(rangeInDays, statusDate);
} catch (Exception e)  { e.printStackTrace(); }
    
    

    
    
    
    
    
      Boolean foundIt = (Boolean)  kcontext.getVariable("found") ;
System.out.println ("in XOR with found having value "  + foundIt) ;
return !foundIt  ;
    
    
    
    
    
    
      Boolean foundIt = (Boolean)  kcontext.getVariable("found") ;
System.out.println ("in XOR with found having value "  + foundIt) ;
return foundIt  ;

Comment on Event Driven Business Process Management in jBPM5 by Saigo

Saigo — Wed, 18 Apr 2012 08:33:14 +0000

Hi!

First: thanks for good example.
But I found a bug in the rule:

over window:size(1h),

window:size doesn’t work. I fixed it to:

over window:time(1h),

Comment on Plugtree jBPM5 Tutorial #1 : Modeling your basic processes by Jigar

Jigar — Fri, 23 Mar 2012 07:38:07 +0000

Considering a broad aspect,

Any best practices on how to fit this piece of process in big architecture

Comment on Plugtree jBPM5 Tutorial #1 : Modeling your basic processes by Jigar

Jigar — Fri, 23 Mar 2012 07:36:38 +0000

Fixed above error by selecting code in conditions

Comment on Plugtree jBPM5 Tutorial #1 : Modeling your basic processes by Jigar

Jigar — Wed, 21 Mar 2012 06:44:09 +0000

I added diverge gateway in to the .bpmn file and started facing

org.drools.RuntimeDroolsException: invalid package name at org.jbpm.compiler.ProcessBuilderImpl.buildProcess(ProcessBuilderImpl.java:173) at org.jbpm.compiler.ProcessBuilderImpl.addProcessFromXml(ProcessBuilderImpl.java:252) at org.drools.compiler.PackageBuilder.addProcessFromXml(PackageBuilder.java:564) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:608) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:37) at com.sample.ProcessMain.readKnowledgeBase(ProcessMain.java:25) at com.sample.ProcessMain.main(ProcessMain.java:17) [12,13]: [ERR 102] Line 12:13 mismatched input 'false' in rule "RuleFlow-Split-com.sample.bpmn.hello-5-6-DROOLS_DEFAULT" [0,0]: Parser returned a null Package ProcessLoadError: unable to parse xml : Exception class org.drools.RuntimeDroolsException : invalid package name Exception in thread "main" java.lang.IllegalArgumentException: Could not parse knowledge. at org.drools.builder.impl.KnowledgeBuilderImpl.newKnowledgeBase(KnowledgeBuilderImpl.java:67) at com.sample.ProcessMain.readKnowledgeBase(ProcessMain.java:27) at com.sample.ProcessMain.main(ProcessMain.java:17)

Comments for PlugTree

Comment on Event Driven Business Process Management in jBPM5 by Lillian A

Comment on Event Driven Business Process Management in jBPM5 by Saigo

Comment on Plugtree jBPM5 Tutorial #1 : Modeling your basic processes by Jigar

Comment on Plugtree jBPM5 Tutorial #1 : Modeling your basic processes by Jigar

Comment on Plugtree jBPM5 Tutorial #1 : Modeling your basic processes by Jigar