"kennardconsulting" wrote : Tim,
| What you say is very interesting. Could you please elaborate on what you mean when you say:
| > The local queue will first attempt to send messages to the local queue
| > until it determines it is busy
| Do you mean the 'local queue will send messages to the prefetch buffer'?
anonymous wrote :
| > If the processing time for each of your messages is significant
| What kind of time is considered significant?
You can try experimenting with different prefetch size values but if you're processing time is more than a few milliseconds then prefetching is probably not much use to you.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240965#4240965
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240965
1) jBPM4 is not in the QA run of JBoss, but the jBPM core libraries have no specifc dependencies in that it should not run on WLS 10. You basic packaging issues with dependent jars might occur though, but that should not be to difficult to find out
2) jBPM 4 GPD uses the *symbols* of BPMN for designing processis in the jPDL language. Do not expect all BPMN notations to be available. But for most things it will be sufficient.
ProcessInspector: Yes, the web console has functionality for this.
Nested processes: Yes, that is supported
Debugging for runnning (production) processes is not something that is supported in a sense that you can visually set breakpoints. But by using Test Driven Development of your process with unittests, you can do a lot design time.
Java: yes, JCA: no (but SQL, ESB, Mail are there), Webservice: no since it was most of the time to specific and with webservices frameworks you can generate javacode easily.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240961#4240961
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240961
Actually JBM 1.x does both. (BTW there is a FAQ on this, but I didn't right it so can't vouch for it's accuracy).
When using a clustered connection factory, subsequent *connections* will normally be created to different nodes of the cluster, by default in a round robin fashion.
So connection 1 might be to node B, connection 2 might be to node A, and connection 3 might be to node C. So that determines where you're messages get initially sent.
Now, when the messages reach a node, if they're non persistent and you're using a topic, then they will be instantly sent off to all the nodes where you have consumers using JGroups.
If they're persistent and/or you're using queues then they'll initially go into the local queue.
Each message consumer by default has an internal buffer of messages that it "prefetches" from the queue (this is faster than it fetching a message each time).
The local queue will first attempt to send messages to the local queue until it determines it is "busy" - busy means its buffer is full. If all local consumers are determined to be busy, then messages are eligible to be redistributed to other nodes where consumers might be idle.
If the processing time for each of your messages is significant then it might make sense for you to reduce your prefetch size (see docs) since there is little or no advantage in consumers buffering messages. You should then see a smoother distribution of messages across different nodes in the cluster.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240959#4240959
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240959
"gaohoward" wrote :
| Using /ClusteredConnectionFactory, each time you gets a connection, you connects to a different node (round robin load balancing by default).
| By enable Message Suckers in the cluster, messages will be pulled off from nodes that have no local consumers to the nodes that have local consumers but no messages in queue.
Actually that is not correct. In JBM 1.x messages will be redistributed from one node to another if JBM determines that consumers on one node are sitting idle, whilst there are messages and busy consumers on other nodes.
If you're seeing some consumers sitting idle while one node consumes all the messages your system is probably misconfigured.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240952#4240952
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4240952