[jBPM] - obsolete id
by Darryl Youngblood
Darryl Youngblood [http://community.jboss.org/people/d.y.] created the discussion
"obsolete id"
To view the discussion, visit: http://community.jboss.org/message/625248#625248
--------------------------------------------------------------
Greetings,
i get a Nullpointer exception due to an obsolete workitem id. I created a process with the eclipse bpmn2 process editor so the ids of the tasks are automatically incremented. then i deleted some tasks and replaced them. so in my case the task with id 10 got deleted and replaced with a task with the id 34. but when i start my process and it comes to my custom task and custom task handler i get 10 as the id instead of 34
public void executeWorkItem(WorkItem wi, WorkItemManager wim) {
this.workItemId = wi.getId(); // ==10 instead of 34
this.wi = wi; // wi.name is also wrong
this.workItemManager = wim;
I could run my process when i used ((RuleFlowProcess) process).getNode(*34*).getOutgoingConnections().values() instead of
((RuleFlowProcess) process).getNode(*workItemId*).getOutgoingConnections().values()
but that is not a satisfying solution ;-) Is this bug known or do you have any advices how to solve this issue?
I'm using jbpm 5.1
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/625248#625248]
Start a new discussion in jBPM at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 7 months
[JBoss Messaging] - Re: Configure MDB PoolSize
by Harry P.
Harry P. [http://community.jboss.org/people/harishpandya] created the discussion
"Re: Configure MDB PoolSize"
To view the discussion, visit: http://community.jboss.org/message/625437#625437
--------------------------------------------------------------
Hi jaikiran,
i want to use concurrency using JMS so i used topic implementation of JMS.
My standardjboss.xml is
<proxy-factory-config>
<JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
<ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
<CreateJBossMQDestination>true</CreateJBossMQDestination>
<!-- WARN: Don't set this to zero until a bug in the pooled executor is fixed -->
<MinimumSize>2</MinimumSize>
<MaximumSize>2</MaximumSize><!--how many parellel need for FPM -->
<KeepAliveMillis>150000</KeepAliveMillis>
<MaxMessages>15</MaxMessages>
<MDBConfig>
<ReconnectIntervalSec>10</ReconnectIntervalSec>
<DLQConfig>
<DestinationQueue>queue/DLQ</DestinationQueue>
<MaxTimesRedelivered>10</MaxTimesRedelivered>
<TimeToLive>0</TimeToLive>
</DLQConfig>
</MDBConfig>
</proxy-factory-config>
Concurrency is achieved. But the problem is that concurrency is applied to a fixed no of messages after that remaining messages are taken sequentially.
Ex.
No. of messages on topic(range) Connecurrency performed for message Sequential
11-15 4 (2 parellel) 7-11
21-24 10(5 parellel) 11-15
25-29 18(9 parellel) 7-11
35-40 34(17 perellel- best perf.) 1-6
do you know why such pattern is followed & can we restrict it.
Thanks in Advance.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/625437#625437]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 7 months