[JBoss jBPM] - Fork only uses first transition
by swaroopreddy
I have the model as below:
| <urn:process-definition name="1" xmlns:urn="urn:jbpm.org:jpdl-3.2">
| <urn:start-state>
| <urn:transition to="1"/>
| </urn:start-state>
| <urn:node name="1">
| <urn:action
| class="com.sra.sraserver.workflow.api.driver.runtime.workflow.jbpm.EmbeddedActionHandler"/>
| <urn:transition to="2"/>
| </urn:node>
| <urn:node name="2">
| <urn:action
| class="com.sra.sraserver.workflow.api.driver.runtime.workflow.jbpm.EmbeddedActionHandler"/>
| <urn:transition to="2_fork"/>
| </urn:node>
| <urn:fork name="2_fork">
| <urn:transition to="3"/>
| <urn:transition to="4"/>
| </urn:fork>
| <urn:node name="3">
| <urn:action
| class="com.sra.sraserver.workflow.api.driver.runtime.workflow.jbpm.EmbeddedActionHandler"/>
| <urn:transition to="2_join"/>
| </urn:node>
| <urn:node name="4">
| <urn:action
| class="com.sra.sraserver.workflow.api.driver.runtime.workflow.jbpm.EmbeddedActionHandler"/>
| <urn:transition to="2_join"/>
| </urn:node>
| <urn:join name="2_join">
| <urn:transition to="5"/>
| </urn:join>
| <urn:node name="5">
| <urn:action
| class="com.sra.sraserver.workflow.api.driver.runtime.workflow.jbpm.EmbeddedActionHandler"/>
| <urn:transition to="6"/>
| </urn:node>
| <urn:node name="6">
| <urn:action
| class="com.sra.sraserver.workflow.api.driver.runtime.workflow.jbpm.EmbeddedActionHandler"/>
| <urn:transition to="end"/>
| </urn:node>
| <urn:end-state name="end"/>
| </urn:process-definition>
|
...The action handler simply calls executionContext.getToken().signal().
The problem here is that when I execute this model, the following nodes are hit (in order):
1, 2, 2_fork, 3, 2_join, 5, 6, end
for some reason, it completely skips the 2nd fork transition, node 4.
Can anyone tell why this would be happening? did I miss something in the process definition?
I am using an embedded jbpm solution with HSQL in memory.
Thanks in advance for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156091#4156091
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156091
17 years, 10 months
[JBoss Messaging] - classloader issue
by randiz
hi
I am trying to call a method in a session bean deployed on server (call it server1 ) that processes some data and then pushes the data on a queue existing on a external jboss server( call it server 2). tjhe session bean is unable to push the data on queue on server 2 ( the know the queue on server2 exists )
I get the following error :
ERROR javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.destination.JBossQueue (no security manager: RMI class loader disabled)]
the code for reference is simple refer below :
properties.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
properties.put(Context.URL_PKG_PREFIXES,
"org.jboss.naming:org.jnp.interfaces");
properties.put(Context.PROVIDER_URL, "jnp://127.0.0.1:1099");
context = new InitialContext(properties1);
queue = (Queue) context.lookup("queue/JMS_action_Request");
QueueConnectionFactory tcf = (QueueConnectionFactory)context.lookup("ConnectionFactory");
queueConnection = tcf.createQueueConnection();
queueSession = queueConnection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
QueueSender queueSender =queueSession.createSender(queue);
queueConnection.start();
queueSender.send(queueSession.createTextMessage(msg));
queueSession.commit();
queueConnection.close();
any clues to the problem and how to handle this problem
thanks
randiz
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156085#4156085
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156085
17 years, 10 months
JBOSS Cluster Network Floods
by M Wagad
Hi There
I have couple of questions with respect to Jboss Cluster
What happens when, in jboss cluster environment the Master and Slave can not sync?
In our case, the jboss nodes became disoriented and started to try to sync, so they have created lots and lots of UDP Broadcast messages flooding the Network.
Would it have been beneficial to use the UDP.ip_ttl and MCAST.ip_ttl?
Would this have occurred if we were using TCP instead of the default UDP?
Our current Application is written with default UDP protocol in mind, we have only couple of jboss nodes, how much of an effort does it need to change the protocol from UDP to TCP_IP?
Thanks in advance
M. Wagad
_________________________________________________________________
Find hidden words, unscramble celebrity names, or try the ultimate crossword puzzle with Live Search Games. Play now!
http://g.msn.ca/ca55/212
17 years, 10 months
[Management, JMX/JBoss] - Re: Spring JMX issues in JBoss
by krishh
repost: some of the bean definitions were lost when posted.
I have defined these beans in my appContext.
<bean id=mbeanServer class=org.springframework.jmx.support.MBeanServerFactoryBean>
<!-- indicate to first look for a server -->
<property name=locateExistingServerIfPossible value=true/>
<bean id=exporter class=org.springframework.jmx.export.MBeanExporter lazy-init=false>
<property name=server ref=mbeanServer/> <!-- refer to spring's factory comment out if using another jmx server agent-->
<property name=assembler ref=assembler/>
<property name=namingStrategy ref=namingStrategy/>
<property name=autodetect value=true/>
<property name=registrationBehaviorName value=REGISTRATION_IGNORE_EXISTING/>
<bean id=jmxAttributeSource
class=org.springframework.jmx.export.annotation.AnnotationJmxAttributeSource/>
<!-- will create management interface using annotation metadata -->
<bean id=assembler
class=org.springframework.jmx.export.assembler.MetadataMBeanInfoAssembler>
<property name=attributeSource ref=jmxAttributeSource/>
<!-- will pick up the ObjectName from the annotation -->
<bean id=namingStrategy
class=org.springframework.jmx.export.naming.MetadataNamingStrategy>
<property name=attributeSource ref=jmxAttributeSource/>
And in one of my spring beans, I have annotations
@ManagedResource(objectName = "spring.ua:service=TimePeriodServiceExecutione r", description = "A sample JMX-managed bean")
public class TimePeriodServiceImpl
implements TimePeriodService{
and a method
@ManagedAttribute
public List getAllResolutionsAsStrings()
{
When I build my ear, deploy it in Jboss, I am not able to see the auto detected managed bean in my JMXConsole. why?
It appears when JBoss start the mbeans are registered. What do I need to do to make the mbeans visible on the JMXConsole.
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156069#4156069
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156069
17 years, 10 months
