[jBPM] - Unable to Autowire in AssignmentHandler
by kh4m khurram
kh4m khurram [https://community.jboss.org/people/kh4m] created the discussion
"Unable to Autowire in AssignmentHandler"
To view the discussion, visit: https://community.jboss.org/message/734450#734450
--------------------------------------------------------------
Hi good noon,
I am facing problem in my CustomAssignmentHandler class that implements AssignmentHandler
> package com.tabs.bcrs.bpm.handler;
>
> import org.jbpm.api.model.OpenExecution;
> import org.jbpm.api.task.Assignable;
> import org.jbpm.api.task.AssignmentHandler;
> import org.springframework.beans.factory.annotation.Autowired;
> import org.springframework.stereotype.Component;
>
> import com.tabs.bcrs.custombpm.service.BPMCustomService;
>
> @Component
> public class CustomAssignmentHandler implements AssignmentHandler {
>
>
> @Autowired
> BPMCustomService bpmCustomService;
>
>
> String assignee;
>
> /**
> *
> */
> private static final long serialVersionUID = 7980992364382900445L;
>
> public void assign(Assignable assignable, OpenExecution openExecution)
> throws Exception {
> System.out.println("Assignee: " + assignee);
> //assignable.addCandidateUser("userId");
> assignable.addCandidateGroup(assignee);
> openExecution.createVariable("node", openExecution.getProcessInstance().getActivity().getName());
>
>
>
> bpmCustomService.getTaskListOfSpecificGrp("ChecklistWindowGroup");
>
>
> }
>
>
The problem is my object bpmCustomService generates NullPointer Exception as it seems it is not properly autowired using @Autowired. Can anybody help me out please??
Your help is appreciated.
Khurram
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/734450#734450]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 4 months
[JBoss Messaging] - Doubts while configuring JMS in JBOSS 7.1.1 Final.
by Sabarinath Selvaraj
Sabarinath Selvaraj [https://community.jboss.org/people/sabarinathsss] created the discussion
"Doubts while configuring JMS in JBOSS 7.1.1 Final."
To view the discussion, visit: https://community.jboss.org/message/734423#734423
--------------------------------------------------------------
Hi I have some doubts while configuring JMS in JBOSS 7.1.1 Final.
In jboss-4.0.5.GA under this path "jboss-4.0.5.GA\server\default\deploy\jms" in mysql-jdbc2-service.xml we specify 'datasource' name like
<mbean code="org.jboss.mq.pm.jdbc2.PersistenceManager" name="jboss.mq:service=PersistenceManager">
<depends optional-attribute-name="ConnectionManager">jboss.jca:service=DataSourceBinding,name=jdbc/sampleDS</depends>
<attribute name="SqlProperties">
CREATE_TABLES_ON_STARTUP = TRUE
</attribute>
<!-- Uncomment to override the transaction timeout for recovery per queue/subscription, in seconds -->
<!--attribute name="RecoveryTimeout">0</attribute-->
<!-- The number of blobs to load at once during message recovery -->
<attribute name="RecoverMessagesChunk">1</attribute>
</mbean>
</server>
In JBOSS 7.1.1 Final where we need to specify this configuration?
ThanksAdvance
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/734423#734423]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 4 months
[jBPM] - Questions about session management and memory resource issues
by pmukundan
pmukundan [https://community.jboss.org/people/pmukundan] created the discussion
"Questions about session management and memory resource issues"
To view the discussion, visit: https://community.jboss.org/message/734408#734408
--------------------------------------------------------------
Hi All,
Let me first describe the way I am trying to use JBPM.
*Usage Scenario*
I have a UI running on an application server. JBPM is deployed on top of a Tomcat in a separate JVM. At the startup of the tomcat knowledge base is loaded, knowledge session is created and kept ready for the UI to call. The UI responds to user inputs and decides to launch a process in JBPM. The UI calls the JBPM through a web service and process instance gets started. The processes contain human tasks and may run for days( those lazy humans !!). The number of process instances could become high( may be thousands).
*Perceived Problem:*
As the number of launched process instances go on increasing, the JBPM JVM shall run out of memory. The solution does not scale.
*Approaches for problem resolution*
There are two ways of handling this
a. Create only one session within the JBPM instance and let all process instance launches happen within this session. If JVM starts running out of memory, add more memory, more CPU firepower.
b. For each process start request, create a new sesson and load/unload the session as and when required. Live within whatever memory/CPU you have.
I am evaluating the two appraoches.
*Questions*
1. Does JBPM keep all process instance information in memory at all times ?
2. Does JBPM keep all the knowledge base in memory at all times ?
3. For approach b to work, the internal handling of JBPM should enable me to load/unload session at will. Does that work well? any firsthand experience ?
4. For approach b, if session dispose is called, do all process instances associated with that session go dormant ? In other words, if a session dispose is executed, are the process instances started by that session still in memory ?
If these have been answered anywhere else, please do point me to that location.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/734408#734408]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 4 months
[jBPM] - GetTasksOwned API is not returning the claimed tasks as Task.createdBy_Id column is not updated
by S Jegan
S Jegan [https://community.jboss.org/people/jegan] created the discussion
"GetTasksOwned API is not returning the claimed tasks as Task.createdBy_Id column is not updated"
To view the discussion, visit: https://community.jboss.org/message/716523#716523
--------------------------------------------------------------
Hi All,
Request you all to please help me on this. I am using jbpm 5.2. I use getTasksOwned API to get the tasks assigned to an user. It works fine in all scenarios except for the tasks that are claimed.
What happens is, as part of the claim operation the "createdBy_id" column of Task is not getting updated. Because of this the query "TaskOwned" which is defined in TaskOrm.xml does not return the results. The "actualOwner_id" column is updated, but for some reason "createdBy_id" column is not.
I tried going through the code and found that in commands method of TaskServiceSession.class, only actual owner is set. Is this an issue? If I manually update this column in db, it works.
Is this an issue? If yes, is there any work-around for this? I am right now thinking of using the query API to get the tasks assigned. Will there be any other issue if I do that?
Please provide your suggestions. Let me know if I need to provide any more information. Thanks for your time.
Regards.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/716523#716523]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 4 months
[JBoss Messaging] - Multiple Post Office Configuration
by Caleb Powell
Caleb Powell [https://community.jboss.org/people/caleb.powell] created the discussion
"Multiple Post Office Configuration"
To view the discussion, visit: https://community.jboss.org/message/734315#734315
--------------------------------------------------------------
Hi,
we are currently dealing with Messaging problems in the JBoss 4.3 CP08 container. We realize these issues are well known and that the best move is to upgrade. However, our client (a very large corporation) is reluctant to do so at this time. As a result, we are trying to mitigate the problems as best we can.
Basically, our application uses Queues for lots asynchronous processing, and it uses Topics to send notifications to subscribed clients. The server is a single instance running in a retail location and there are anywhere from 4-12 subscribed clients (on the same network, in the same retail location). It is a very simple setup and there is no clustering of any kind.
In November of last year, the stores started to experience network disruptions. We don't know what the root cause of the network disruptions are (and being the vendor, we may never know) but they are seriously impacting the JBoss Messaging component. The main problem we see is that the Post Office blocks indefinitely when it tries to write a message to a subscribed client workstation. This ends up deadlocking the entire Post Office, which in turn blocks all of the other Threads that are trying to write to the Queues. The entire server comes to a halt and all of the workstations eventually freeze up:
https://community.jboss.org/servlet/JiveServlet/showImage/2-734315-18548/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-734315-18...
We have been dealing with Red Hat support on this and we have a very solid grasp on the problems with the Messaging implementation in 4.3. As I mentioned, we are looking for workarounds to the problem. One workaround we have come up with is to configure 2 separate Post Office implementations in the same JBoss instance. We assign the Queues to one instance, and we assign the Topics to another instance. The purpose of this change is to reduce the impact of a failure when writing a Topic message to a subscriber. If the Topic Post Office freezes up, the Queue Post Office is unnaffected and can continue processing requests from other Threads on the server.
https://community.jboss.org/servlet/JiveServlet/showImage/2-734315-18549/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-734315-18...
Red Hat support has indicated that this configuration has never been through their QA process and therefore is not supported. I respect their position.
What I am interested in knowing is whether anyone else in the community has ever tried this type of configuration, and/or whether anyone knows of why this is a bad idea? We have run this configuration through our automated regression and performance tests and have not seen any problems. And it does reduce the impact of a failure in the Messaging system. Any thoughts?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/734315#734315]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 4 months
