[JBoss jBPM] - Recursive process call
by Tar_Szator
Hi
I have following problem.
I build a webservice wich sends a JMS Message to ESB an then the ESB starts the Process. Now the Process gather information. In the end the process sends a JMS Message back to the Webservice with the result. Now the Webservice responce the result to the sender.
While gathering information the process is able to call webservices. Here I need to request my own webservice. Now the ESB starts want to start the process again.
But the process do not start. After a while the Node in the "Parent-Process" which is waiting for answer from the Webservice goes to "fail" node and is persistent. Now the "Child-Process" starts working.
What is the reason for that?
Is it because the is only one Process Executer. When one process instance is persistent he can switch to another? In that way more processes never really work parallel, right?
Is there any way to solve this Problem? Like starting more Process Executors in any way?
Thanks for help.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237992#4237992
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237992
17 years, 1 month
[JBoss Messaging] - Re: Problems while creating a bridge service
by PaulMe
I've downloaded a JMS Gui client ( Hermes ) and I could connect from my computer to the Tibco Server.
Could the problem originate because the server runs on 127.0.0.1 ???
These are the settings I've entered in my JBoss configuration
xyz-tibco-bridge-service.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Messaging Destinations deployment descriptor.
|
| $Id: destinations-service.xml 85945 2009-03-16 19:45:12Z dimitris(a)jboss.org $
| -->
|
| <server>
| <mbean code="org.jboss.jms.server.bridge.BridgeService" name="jboss.jms:service=Bridge,name=TestBridge" xmbean-dd="xmdesc/Bridge-xmbean.xml">
| <depends optional-attribute-name="SourceProviderLoader">jboss.messaging:service=JMSProviderLoader,name=JMSProvider</depends>
| <depends optional-attribute-name="TargetProviderLoader">jboss.jms:service=JMSProviderLoader,name=MyRemoteJMSProvider</depends>
| <attribute name="SourceDestinationLookup">/queue/local</attribute>
| <attribute name="TargetDestinationLookup">remote/queue/name</attribute>
| <attribute name="TargetUsername">*******</attribute>
| <attribute name="TargetPassword">*******</attribute>
| <attribute name="QualityOfServiceMode">0</attribute>
| <attribute name="MaxBatchSize">5</attribute>
| <attribute name="MaxBatchTime">-1</attribute>
| <attribute name="FailureRetryInterval">5000</attribute>
| <attribute name="MaxRetries">-1</attribute>
| <attribute name="AddMessageIDInHeader">false</attribute>
| </mbean>
| </server>
jms-ds.xml
<?xml version="1.0" encoding="UTF-8"?>
|
| <connection-factories>
|
| <!-- ==================================================================== -->
| <!-- JMS Stuff -->
| <!-- ==================================================================== -->
|
| <!--
| The JMS provider loader. Currently pointing to a non-clustered ConnectionFactory. Need to
| be replaced with a clustered non-load-balanced ConnectionFactory when it becomes available.
| See http://jira.jboss.org/jira/browse/JBMESSAGING-843.
| -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.messaging:service=JMSProviderLoader,name=JMSProvider">
| <attribute name="ProviderName">DefaultJMSProvider</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="FactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute>
| </mbean>
| <!-- Remote JMS Provider -->
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| name="jboss.jms:service=JMSProviderLoader,name=MyRemoteJMSProvider">
| <attribute name="ProviderName">RemoteConnectionFactory</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <attribute name="FactoryRef">QueueConnectionFactory</attribute>
| <attribute name="QueueFactoryRef">QueueConnectionFactory</attribute>
| <attribute name="TopicFactoryRef">TopicConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory
| java.naming.factory.url.pkgs=com.tibco.tibjms.naming
| java.naming.provider.url=tcp://serverip:7222
| </attribute>
| </mbean>
|
| <!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
| <tx-connection-factory>
| <jndi-name>JmsXA</jndi-name>
| <xa-transaction/>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
| <max-pool-size>20</max-pool-size>
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| <depends>jboss.messaging:service=ServerPeer</depends>
| </tx-connection-factory>
|
| </connection-factories>
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237977#4237977
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237977
17 years, 1 month