[jBPM Users] - Re: Violation of unique constraint with two splits (JBPM-255
by Alkero
With the following process definition the problem still occurs, I don't think the nesting is the source of the problem:
<?xml version="1.0" encoding="UTF-8"?>
|
| <process name="test" xmlns="http://jbpm.org/4.0/jpdl">
| <start g="143,8,31,30" name="start1">
| <transition to="fork1"/>
| </start>
| <fork g="143,72,65,29" name="fork1">
| <transition g="-44,-18" name="left" to="task1"/>
| <transition g="9,-24" name="right" to="task2"/>
| </fork>
| <task assignee="test" g="73,134,66,56" name="task1">
| <transition to="join1"/>
| </task>
| <task assignee="test" g="192,135,64,55" name="task2">
| <transition to="join1"/>
| </task>
| <join g="142,201,34,36" name="join1">
| <transition to="fork2"/>
| </join>
| <fork g="138,269,57,32" name="fork2">
| <transition g="-44,-18" name="left" to="task3"/>
| <transition g="-44,-18" name="right" to="task4"/>
| </fork>
| <task g="66,329,56,51" name="task3">
| <transition to="join2"/>
| </task>
| <task g="191,332,65,43" name="task4">
| <transition to="join2"/>
| </task>
| <join g="133,385,39,35" name="join2">
| <transition to="end1"/>
| </join>
| <end g="136,455,44,56" name="end1"/>
| </process>
Code:
String deploymentId = repositoryService.createDeployment()
| .addResourceFromClasspath(processDefinitionFilename)
| .deploy();
|
| Execution execution = executionService.startProcessInstanceByKey("test");
|
| List<Task> tasks = processEngine.getTaskService().findPersonalTasks("test");
| for(int i = 0;i<tasks.size();i++){
| System.out.println(i);
| processEngine.getTaskService().completeTask(tasks.get(i).getId());
| }
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257640#4257640
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257640
16 years, 6 months
[JNDI and Naming] - HA JNDI , failed to connect from stand alone
by roman.mandeleil＠gmail.com
Hi,
I am trying to connect from a stand alone program to a 2 nodes cluster started on binding set ports-02 and ports-03, all the start and node discovery seams to be ok, but the JNDI lookup fails.
here is the client code:
| Connection connection = null;
| InitialContext initialContext = null;
|
|
| Hashtable<String, String> jndiParameters = new Hashtable<String, String>();
| jndiParameters.put("java.naming.provider.url", "127.0.0.1:1102,127.0.0.1:1103");
| jndiParameters.put("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
| jndiParameters.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces");
|
|
| initialContext = new InitialContext(jndiParameters);
|
|
| ConnectionFactory cf = (ConnectionFactory)initialContext.lookup("/ConnectionFactory");
I get the following:
| Exception in thread "Main Thread" javax.naming.CommunicationException: Could not obtain connection to any of these urls: 127.0.0.1:1102,127.0.0.1:1103 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server /127.0.0.1:1103 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server /127.0.0.1:1103 [Root exception is java.net.ConnectException: Connection refused: connect]]]
| at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1763)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:693)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686)
| at javax.naming.InitialContext.lookup(InitialContext.java:392)
| at HAJNDISample.main(HAJNDISample.java:32)
|
Very strange, I have checked the MBean configurations in JMX and it seams to be correct.
Thanks in advance
Roman
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257635#4257635
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257635
16 years, 6 months