[jBPM] - No current status match exception.
by Dsire krish
Dsire krish [https://community.jboss.org/people/arselv] created the discussion
"No current status match exception."
To view the discussion, visit: https://community.jboss.org/message/755934#755934
--------------------------------------------------------------
I need to get the tasks by status and then start them.
But at some times while retrieveing the tasks im getting the started process id as well and thats in where im getting this exception.
org.jbpm.task.service.PermissionDeniedException: Server-side Exception: User '[User:'admin']' was unable to execution operation 'Start' on task id 287271 due to a no 'current status' match
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
My mina task handler is running in jboss and the application uses its client to the task operations.
Retrieveing tasks by status:
BlockingTaskSummaryResponseHandler resHandler = new BlockingTaskSummaryResponseHandler();
List<Status>statusls=new ArrayList<Status>();
statusls.add(Status.Reserved);
client.getTasksAssignedAsPotentialOwnerByStatus("admin",statusls, "en-UK", resHandler);
Starting the task:
BlockingTaskOperationResponseHandler responseHandler = new BlockingTaskOperationResponseHandler();
client.start(taskId, userId, responseHandler);
*Is there any thing to do with hibernate or what should i take care to eliminate this replication.?*
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/755934#755934]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[Beginner's Corner] - Error initializing endpoint
by Govind Raju
Govind Raju [https://community.jboss.org/people/govindtis] created the discussion
"Error initializing endpoint"
To view the discussion, visit: https://community.jboss.org/message/754158#754158
--------------------------------------------------------------
Hi ,
This error on ubuntu 12.04 while starting JBOSS AS .
I stoped apache service on my mechine.
ERROR [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Error initializing endpoint: java.net.BindException: Address already in use /127.0.0.1:8080
at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:983) [jbossweb-7.0.13.Final.jar:]
at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
11:00:09,862 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Caused by: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use /127.0.0.1:8080
at org.apache.catalina.connector.Connector.init(Connector.java:985)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
... 5 more
11:00:10,065 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss-as-7.1.1.Final/standalone/deployments
11:00:10,078 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on /127.0.0.1:9999
11:00:10,078 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:4447
11:00:10,248 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/754158#754158]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[jBPM] - Re: Jbpm 5.3 JPA2 Jboss 7.1.1 table "dbo.OrganizationalEntity", column 'id'.
by Ted Pan
Ted Pan [https://community.jboss.org/people/ted.pan] created the discussion
"Re: Jbpm 5.3 JPA2 Jboss 7.1.1 table "dbo.OrganizationalEntity", column 'id'."
To view the discussion, visit: https://community.jboss.org/message/774673#774673
--------------------------------------------------------------
you need to add the user to takservice by using the following code
|
|
|
| Properties userGroups = new Properties(); |
|
|
|
| userGroups.setProperty("john", "user"); |
|
|
|
| UserGroupCallbackManager manager = UserGroupCallbackManager.getInstance(); |
|
|
|
| manager.setCallback(new DefaultUserGroupCallbackImpl(userGroups)); |
*or* implement a an UserGroupCallback. Then
UserGroupCallbackManager manager = UserGroupCallbackManager
.getInstance();
if (!manager.existsCallback()) {
UserGroupCallback userGroupCallback = new JBPMUserGroupCallback();
manager.setCallback(userGroupCallback);
}
this is the callback implementation:
public class JBPMUserGroupCallback implements UserGroupCallback {
@Override
public boolean existsGroup(String groupId) {
return true;
}
@Override
public boolean existsUser(String userId) {
return true;
}
@Override
public List<String> getGroupsForUser(String userId, List<String> groupIds,
List<String> allExistingGroupIds) {
if(groupIds != null) {
List<String> retList = new ArrayList<String>(groupIds);
// merge all groups
if(allExistingGroupIds != null) {
for(String grp : allExistingGroupIds) {
if(!retList.contains(grp)) {
retList.add(grp);
}
}
}
return retList;
} else {
//
// return empty list by default
//please note: there are different return value for different version of jPBM
//List<String> retList = new ArrayList<String>();
//retList.add("user");
//return retList;
//return new ArrayList<String>(); //for jBPM5.3.0.Final
return null; //for jBPM5.4.0.CR1
}
}
}
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/774673#774673]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 7 months
[jBPM] - jBPM5 - Can't Scale, Won't Scale
by M Arnold
M Arnold [https://community.jboss.org/people/m_arnold123] created the discussion
"jBPM5 - Can't Scale, Won't Scale"
To view the discussion, visit: https://community.jboss.org/message/771731#771731
--------------------------------------------------------------
Hi,
I'm having great trouble designing an application which uses jBPM5 in a scalable way. It seems to be impossible on a practical level. I hope that this is just due to my misunderstandings of the way the jBPM5 works.
I have listed each of my assumptions, and the ramifications of each below. I hope that someone from the community will be able to point out where these assumptions are incorrect.
I would particularly appreciate it if anyone has managed to scale jBPM5, and could described how they achieved it.
1. Everytime jBPM5 executes a process the database transaction updates the process instance info AND the session info, therefore:
1a. it's not scalable to use a single session to execute all processes, or you would suffer contention on the session info.
1b, it's not scalable to use a single session to execute all processes in a cluster, or the updated session info would have to be continually synchronised across the cluster.
2. When using BPMN2 events, jBPM5 only allows you to send events to the process instances within a single session at a time. You need to maintain a list of all the sessions which have incompleted process instances(*), and loop through them all to send events. Therefore:
2a. you should execute all processes in as few sessions as possible, to lessen the number of iterations through this loop.
3. jBPM5 persists BPMN2 timer info in the session info, but the session must be active (ie. loaded from persistence) in order for the timers to activate. Therefore:
3a. when your application starts, you must load all sessions that have active process instances that have timers(**).
3b. you must not have the same session active in two different nodes of a cluster, or the same timers will expire around the same time
3c. when a node crashes, your application must detect this and reload the sessions that were active in the crashed node
4. If you start a process instance in a session, that process instance must always be executed in that session.
4a. when a node wishes to resume a process instance that was persisted, it must first (due to 3b) ask all other nodes if they have the session active, and if so instruct them to dispose it. It can then load the session, load and resume the process. All while preventing race conditions.
4b. when a node receives an event it must (due to 2) carry out all the processing in 4a for each session with active process instances.
(*) I don't think it's possible to know if a session has incompleted process instances..?
(**) I don't think it's possible to know if a session and timers..?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/771731#771731]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years, 8 months