[jBPM] New message: "Re: How to get sub process instance id"
by Santanu Saraswati
User development,
A new message was posted in the thread "How to get sub process instance id":
http://community.jboss.org/message/519951#519951
Author : Santanu Saraswati
Profile : http://community.jboss.org/people/saraswati.santanu
Message:
--------------------------------------------------------------
Two questions here:
Question 1:
How to get sub process instance id:
Here is a possible solution
*+//Assuming processINstance to be your main process instance+*
+* Collection<? extends Execution> executions = processInstance.getExecutions();
for (Execution execution:executions) {
//cast it to open execution..we will need it
OpenExecution openExecution = (OpenExecution)execution;
//check if this is a sub-process or just a fork
if (openExecution.getSubProcessInstance() != null) {
OpenExecution subProcessInstance = openExecution.getSubProcessInstance();*+
+* //you should be able to do whatever you want to*++*
}
}*+
Question 2:
Can we signal without the sub process id:
Yes. Here is a code snippet which is achieving that:
*+ //again..process instance is the main process instance+*
*+ //stateName is the name of the state node you want to signal
+*
*+ Execution execution = processInstance.findActiveExecutionIn(stateName);
+*
*+ //signal name is the transition you need to take on signalling
+*
*+ executionService.signalExecutionById(execution.getId(), signalName);+*
You need to be cautious here that you do not have two states active at the same time with the same name. Then you might get either of them and may get unexpected result.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519951#519951
16 years, 3 months
[EJB 3.0 Development] New message: "Re: EJB3 Version Targets for AS 6.0 M3"
by jaikiran pai
User development,
A new message was posted in the thread "EJB3 Version Targets for AS 6.0 M3":
http://community.jboss.org/message/519940#519940
Author : jaikiran pai
Profile : http://community.jboss.org/people/jaikiran
Message:
--------------------------------------------------------------
For AS trunk, the module which integrates with the AS is the ejb3_1 (available at EJB3_Trunk/ejb3_1). This week we'll be releasing 1.0.1 version of that module into AS for 6.0.0.M2. (most of the) other sub-modules are EJB3 are pulled in as transitive dependencies from this module. So the appropriate versions of the other sub-modules are listed in the EJB3_trunk/ejb3_1/pom.xml.
Which sub-modules have changed in EJB3, for VFS? If for example, it's the "core" module which has changed, then usually it would mean bumping the version of core appropriately and then updating the ejb3_1/pom.xml dependency to pull in this new version.
Once M2 is out, we plan to continue our regular release cycles (twice a month). So the latest released EJB3 version, at that point in time, will be integrated in M3.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519940#519940
16 years, 3 months
[JBoss Remoting] New message: "Re: Client hangs when get JMS connection factory"
by mingjun jiang
User development,
A new message was posted in the thread "Client hangs when get JMS connection factory":
http://community.jboss.org/message/519933#519933
Author : mingjun jiang
Profile : http://community.jboss.org/people/mjjiangbhr
Message:
--------------------------------------------------------------
Ron, thanks for your explaination. I know the meaning of "validatorPingTimeout" and "timeout". In Li Lin's original post, he said he solved this problem by changing the value of "timeout", actually, the changing of timeout value doesn't solve our problem, the changing of timeout value incurred another issue: you know, if there is no message in topic/queue in server side, then the remote client (message listener) won't receive any message, that mean the connection is idle, if the idle duration exceeds the "timeout" value, then the JBM will forcibly close the connection, so the remoting client won't receive any subsequent messages any more, it's a serious problem!
Once more, as what I mentioned in this thread or https://jira.jboss.org/jira/browse/JBREM-1169, if we pull the physical ethernet connection, the connection Validator won't detect the failure and close the failure connection correspondingly. But if we killed the client (i.e. kill the process of message listener in "Task Manager" of Windows OS), the value of "currentClientPoolSize" will decrease to 0 immediately, that meants the Connectionvalidator could detect and close the failure connection under such situation.
Ron, do you mean your test result show the ConnectionValidator could detect and close the failure connection when pulling out the physical ethernet connection? Are you using the same version of JBM and remoting jar mentioned in Li Lin's post?
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/519933#519933
16 years, 3 months