Re: [jboss-dev-forums] [JBoss Microcontainer Development] - Endless loop at AS server startup
by Thomas Diesler
Thomas Diesler [http://community.jboss.org/people/thomas.diesler%40jboss.com] replied to the discussion
"Endless loop at AS server startup"
To view the discussion, visit: http://community.jboss.org/message/548223#548223
--------------------------------------------------------------
I can't say that I understand the issue fully. When the AbstractDependencyInfo returns it's unresolved requirements - it is an unordered set. So the order of the requirements is not deterministic.
In AS we currently distribute these bundles
jboss-osgi-blueprint.jar
jboss-osgi-common-core.jar
jboss-osgi-common.jar
jboss-osgi-http.jar
jboss-osgi-husky.jar
jboss-osgi-jaxb.jar
jboss-osgi-jmx.jar
jboss-osgi-jndi.jar
jboss-osgi-reflect.jar
jboss-osgi-webapp.jar
jboss-osgi-webconsole.jar
jboss-osgi-xerces.jar
jboss-osgi-xml-binding.jar
org.apache.aries.jmx.jar
org.apache.aries.util.jar
org.apache.felix.eventadmin.jar
org.apache.felix.log.jar
org.osgi.compendium.jar
They come with mandatory/optional and of course dynamic requirements. One possibility could be to add a few "special" log messages that write an audit log to a dedicated appender. The test case could extract the module + caps + reqs topology from the log and build up the metadata from it.
I believe, it is a resolve time problem only - so there should be no actual class load needed.
The standalone Runtime BTW resolves these bundles in a timely manner even without the cache. One reason could be that the compendium and a few other key bundles are installed/resolved first before the others come in. Another reason is that we only deal with OSGi modules, which is unlike in AS where we have very many modules with an unknown set of caps/reqs.
I might also add, that I'm sure that the algorithm (without the cache) does not run into an endless loop after all. I'm fairly sure that the cache would prevent that.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548223#548223]
Start a new discussion in JBoss Microcontainer Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
Re: [jboss-dev-forums] [jBPM Development] - creating a sub process instance throw error: org.jbpm.JbpmException: couldn't signal without specifying a leaving transition : transition is null
by Mehul Verma
Mehul Verma [http://community.jboss.org/people/shashwat21] replied to the discussion
"creating a sub process instance throw error: org.jbpm.JbpmException: couldn't signal without specifying a leaving transition : transition is null"
To view the discussion, visit: http://community.jboss.org/message/548197#548197
--------------------------------------------------------------
I have three process say P1,P2,P3. P1 is my main process which in turn calls P2 and P2 calls P3. In my case P1 executes fine and calls P2. When P2 reaches its End node i get this error. Folliwing are the process def. files for the processes.
<?xml version="1.0" encoding="ISO-8859-1" ?>
# - <process-definition name="*P-1*">
# - <swimlane name="*TestSwimlane*">
<assignment pooled-actors="*TestSwimlane*" />
</swimlane>
# - <start-state name="*s1*">
<task name="*s1*" swimlane="*TestSwimlane*" />
<transition to="*t1*" name="*to t1*" />
</start-state>
# - <task-node name="*t1*">
# - <task name="*t1*" swimlane="*TestSwimlane*">
<controller allowAttachments="*false*" />
</task>
# - <transition to="*e1*" name="*to e1*">
# - <action class="*com.mypack.process.action.CallProcess*" config-type="*bean*">
<processName>A-2</processName>
</action>
</transition>
</task-node>
<end-state name="*e1*" />
</process-definition>
Second Process:
<?xml version="1.0" encoding="ISO-8859-1" ?>
# - <process-definition name="*P-2*">
# - <swimlane name="*TestSwimlane*">
<assignment pooled-actors="*TestSwimlane*" />
</swimlane>
# - <start-state name="*s2*">
<task name="*s2*" swimlane="*TestSwimlane*" />
<transition to="*t2*" name="*to t2*" />
</start-state>
# - <task-node name="*t2*">
# - <task name="*t2*" swimlane="*TestSwimlane*">
<controller allowAttachments="*false*" />
</task>
# - <transition to="*e2*" name="*to e2*">
# - <action class="*com.mypack.process.action.CallProcess*" config-type="*bean*">
<processName>A-3</processName>
</action>
</transition>
</task-node>
<end-state name="*e2*" />
</process-definition>
Third Process:
<?xml version="1.0" encoding="ISO-8859-1" ?>
# - <process-definition name="*P-3*">
# - <swimlane name="*TestSwimlane*">
<assignment pooled-actors="*TestSwimlane*" />
</swimlane>
# - <start-state name="*s3*">
<task name="*s3*" swimlane="*TestSwimlane*" />
<transition to="*t3*" name="*to t3*" />
</start-state>
# - <task-node name="*t3*">
# - <task name="*t3*" swimlane="*TestSwimlane*">
<controller allowAttachments="*false*" />
</task>
<transition to="*e3*" name="*to e3*" />
</task-node>
<end-state name="*e3*" />
</process-definition>
Code :
public void execute(ExecutionContext executionContext) throws Exception {
// debug("entering call process action handler");
String name = null;
try {
name = getProcessName();
ProcessInstance processInst = ProcessUtil.newProcessInstance(name);
Task task = Util.getStartTask(processInst.getProcessDefinition());
Token superProcessTOken = executionContext.getToken();
processInst.setSuperProcessToken(superProcessTOken); *// If i comment this line i don't get this error.*
........code to extract caller data......
TaskInstance ti = Util.initProcess(processInst, task, values,
false);
if (ti != null) {
// setup the swimlane instance
Swimlane swm = ti.getTask().getSwimlane();
if (s != null) {
String assignment = swm.getPooledActorsExpression();
if (!Strings.isEmpty(assignment)) {
ti.getSwimlaneInstance().setPooledActors(
assignment.split(","));
}
ti.end();
}
}
I hope now you can understand.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/548197#548197]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months