[JBoss Microcontainer Users] - Confused about POJO service
by karypid
Hello,
The new mc is probably the most feature-rich container out there. You can roll with anything from POJOs to MBeans. However, I am a little confused due to the multitude of options. My predicament is this:
I want to create a service to be deployed in JBoss. Until recently, I'd create a SAR and launch my thread in start(), then kill it in stop() of my MBean. I do this at deployment/undeployment time, so I do not really need the JMX features to control the service. Therefore I want to turn it into a POJO service and remove dependencies on MBean classes. How would you go about packaging such a POJO service so that:
1) it may be included in an EAR (The SAR approach requires that an MBean be defined in jboss-service.xml so it is no longer an option)
2) it executes on application startup / shutdown
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259323#4259323
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259323
16 years, 7 months
[jBPM Users] - Re: How to stop a process instance
by fdegrigny
Last I found how to do this.
In fact the ProcessIntance.end() method really terminate the process but not all the running process tasks in it (this has confused me).
The process tasks have to be terminated separately.
At last, I have made all my ActionHandlers extends a custom base one :
public abstract class BaseActionHandler implements ActionHandler {
|
| public void execute(ExecutionContext executionContext) throws Exception {
| try {
| doAction(executionContext);
| } catch (Throwable t) {
| handleException(t, executionContext);
| }
| }
|
| public abstract void doAction(ExecutionContext executionContext) throws Exception;
|
| protected void handleException(Throwable t, ExecutionContext executionContext) throws Exception {
| log.fatal("Error in " + this.getClass().getName() + ": " + t.getMessage(), t);
|
| //try to stop process instance and associated tasks
| ProcessInstance processInstance = executionContext.getProcessInstance();
| stopProcess(processInstance);
|
| throw new JbpmException(t.getMessage(), t);
| }
|
| protected void stopProcess(ProcessInstance processInstance) {
| JbpmContext jbpmContext = JbpmConfiguration.getInstance().getCurrentJbpmContext();
| Collection<TaskInstance> taskInstances = unchekedCast(processInstance.getTaskMgmtInstance().getTaskInstances());
| for(TaskInstance task : taskInstances) {
| if( ! task.hasEnded() ) {
| task.setSignalling(false);
| task.cancel();
| jbpmContext.save(task);
| }
| }
| processInstance.end();
| }
| }
What I have found over-complicated is the JBPM API itself. I'm working with for few month now and there is many things I still cannot understand. For example, the various variables scopes are very confusing and the semantic of many operations are not very clear.
My customers have very basics needs for their workflows but I have discover that they cannot be done simply with the JBPM API.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259303#4259303
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259303
16 years, 7 months
[JBoss Messaging Users] - Re: User: null is NOT authenticated
by gbansal80
We are currently using JBoss v4.2.3.ga and have upgraded JBoss messaging to v 1.4.4 and JBoss remoting to v2.2.3.
JMS messages are sent & received without any exceptions for initial 3-4 days. After that we are observing exception messagesjavax.jms.JMSSecurityException: User null is NOT authenticated, whenever we are trying to create the connection.
We have seen that there is no deadlock on JBoss AS and other DB operations are working normally.
We are using the following security domain for JMS
<application-policy name="messaging">
<login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
flag = "required">
<module-option name = "unauthenticatedIdentity">guest</module-option>
<module-option name = "dsJndiName">java:/DefaultDS</module-option>
<module-option name = "principalsQuery">SELECT PASSWD FROM JBM_USER WHERE USER_ID=?</module-option>
<module-option name = "rolesQuery">SELECT ROLE_ID, 'Roles' FROM JBM_ROLE WHERE USER_ID=?</module-option>
</login-module>
</application-policy>
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259299#4259299
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4259299
16 years, 7 months