[JBoss jBPM] - Re: Problem getting out of a join
by GrimShieldsson
I figured out why I'm not getting out of Join 2, but I'm not sure what to do about it. I think it's a bug in the way JBPM is designed, but it's entirely possible I don't understand something. It's even likely :)
>From 4.3.2 Concurrent Executions I get:
anonymous wrote : The execution paths can be ordered hierarchically. Meaning that one root execution path is created when a new process execution is instantiated. When the root execution path is forked into multiple concurrent execution paths, the root is the parent and the newly created execution paths are all children of the root. This way, implementation of a join can become straightforward: the implementation of the join just has to verify if all sibling-execution-paths are already positioned in the join node. If that is the case, the parent execution path can resume execution leaving the join node.
The problem is that Join 2 is waiting for the sibling execution path from PM-1 to join it, and that is not what I want to happen. The two execution paths join later in the process (my example is a small part of the whole flow). Clearly in this case Joind 2 does not want to wait for the PM-1 branch to finish.
Is this a design bug? Or am I being dense?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978584#3978584
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978584
19 years, 8 months
[Installation, Configuration & Deployment] - problem with connecting to jboss through Internet
by martacv
Hi, if I connect to jboss through a LAN works perfectly, but I do it through Internet leaves the following error:
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 192.168.1.10; nested exception is:
java.net.ConnectException: Connection refused: connect]
Caused by: java.rmi.ConnectException: Connection refused to host: 192.168.1.10; nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
... 10 more
Caused by: java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.proxy.RMIMasterSocketFactory.checkConnector(RMIMasterSocketFactory.java:309)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:174)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
... 15 more
Why?
all the ports are open. My chain of connection is the following one:
InitialContext ctx = null;
Properties env = new Properties();
env.setProperty("java.naming.factory.initial","org.jnp.interfaces.NamingContextFactory");
env.setProperty("java.naming.provider.url", "xxx.xxx.xxx.xxx:1099");
env.setPropert("java.naming.factory.url.pkgs", "org.jboss.naming");
ctx = new InitialContext(env);
xxx.xxx.xxx.xxx = IP
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978579#3978579
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978579
19 years, 8 months
[JBoss jBPM] - Re: Best way to structure a business process with a delay.
by gygerl
Hi Brad,
Well. It was not :((
I am working on making it run but, beyond others, I got this error :
17:12:37,667 [JbpmScheduler] INFO ConnectionProviderFactory : Initializing connection provider: org.hibernate.connection.DatasourceConnectionProvider
| 17:12:37,682 [JbpmScheduler] INFO NamingHelper : JNDI InitialContext properties:{}
| 17:12:37,713 [JbpmScheduler] FATAL DatasourceConnectionProvider : Could not find datasource: java:/OracleDS
| javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
| at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
| at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
| at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:284)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.hibernate.connection.DatasourceConnectionProvider.configure(DatasourceConnectionProvider.java:52)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:124)
| at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(ConnectionProviderFactory.java:56)
| at org.hibernate.cfg.SettingsFactory.createConnectionProvider(SettingsFactory.java:366)
| at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:60)
| at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:1859)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1152)
| at org.jbpm.persistence.db.DbPersistenceServiceFactory.getSessionFactory(DbPersistenceServiceFactory.java:90)
| at org.jbpm.persistence.db.DbPersistenceService.getSessionFactory(DbPersistenceService.java:74)
| at org.jbpm.persistence.db.DbPersistenceService.getSession(DbPersistenceService.java:78)
| at org.jbpm.persistence.db.DbPersistenceService.getSchedulerSession(DbPersistenceService.java:243)
| at org.jbpm.JbpmContext.getSchedulerSession(JbpmContext.java:425)
| at org.jbpm.scheduler.impl.SchedulerThread.executeTimers(SchedulerThread.java:103)
| at org.jbpm.scheduler.impl.SchedulerThread.run(SchedulerThread.java:70)
|
Do you know where it could come from ?
I do not get where the configuration needs to be done.
Cheers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978575#3978575
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978575
19 years, 8 months