[JBoss jBPM] - Re: BPEL 2.0 examples
by alex.guizar＠jboss.com
The query in your process is wrong. The Eclipse BPEL designer has the annoying costume of prepending '/' to queries which should be relative.
Try one of the following options:
<bpws:query><![CDATA[tns:result]]></bpws:query>
| or
| <bpws:query><![CDATA[/tns:HelloProcessResponse/tns:result]]></bpws:query>
Notice the following features:
* the context node for both queries is the value of the payload part, namely a tns:HelloProcessResponse
* the first query is relative to the context node; look at the absence of a heading '/'
* the second query is an absolute traversal from the context node's owner document (also referred as root node); look at the heading '/' and an explicit reference to the element tns:HelloProcessResponse
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152172#4152172
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152172
18 years
[JBoss Messaging] - Re: Limiting the consumers & producers of a queue
by simba_mb
Maybe it's a little bit late to join the conversation, but better late than never. :)
The thing is that the message group idea only solves the problem if we want to limit the consumers to only one (1). If we want to have, let's say, max 3 consumers, then the message group idea is no longer useful.
For example: Let say that some operation or process needs (or occupies) 1 core in the processor to complete. Let say that we have a quad core processor (4 cores) in our server. We want to save one core for other operations. That leaves us to 3 cores to run 3 simultaneous processes. In this scenario it would be great to limit the consumers to 3. Maybe through an attribute in the settings-file for the specific queue and/or even set the limitation programatically.
Of course, we could create a singleton pool with mutex- or semafore-technology in each consumer to control the number of simultaneous processes. But this would (could) lead to transaction timeouts if the wait is too long between the first and last loaded consumer, which could fail the whole idea with QoS.
timfox: In your blog, you have described nicely the consumer flow control between the queue and the consumer:
http://jbossfox.blogspot.com/2008/03/mysteries-of-flow-control-explained....
Is there a way, in the configuration or JMX bean, to control the number of tokens in the consumer flow control? If there are, I would really like to know how to manipulate them. That would really solve my problem. If not, is there a plan to make them visible in future versions of JBoss Messaging?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152170#4152170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152170
18 years
[Clustering/JBoss] - HAJNDI failover exception
by davidchen
Hi, there:
As new to jboss cluster. I have problem to invoke hajndi. I'm running jboss4.2.0.GA on 2 nodes(Windows 2000). I have several stateless ejbs deployed on both nodes. Load balance works fine, however, I have problem to get fail over work properly:
when I stopped jboss on one node (usually the first node 10.0.2.63 ex), hajndi keeps raising connection exception for about 30 secs, then switch to the other node. Which means each jndi invoke will at least take about 30 seconds before it can find the bean on the other node.
And, if I stopped the other node( the second node), it seems switch to the first node immediately without those connection creation attempts. I listed those exceptions I got from client side.
So, is that some configuration I did wrong? I just followed the clustering document and used default configuration on both nodes.
Thank you very much in advance. Highly appreciated if any hint.
| [2008-05-20 15:23:00,175 UnifiedInvokerHAProxy] Making invocation on InvokerLocator [socket://10.0.2.63:4446/?dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketTimeout=60000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
| [2008-05-20 15:23:00,191 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got SocketException java.net.SocketException: Connection reset by peer: socket write error
| [2008-05-20 15:23:00,191 SocketWrapper] unable to close output stream
| [2008-05-20 15:23:00,191 SocketWrapper] ClientSocketWrapper[Socket[addr=/10.0.2.63,port=4446,localport=2964].19ea173] closing
| [2008-05-20 15:23:01,269 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:02,363 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1079 ms
| [2008-05-20 15:23:03,456 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:04,566 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1094 ms
| [2008-05-20 15:23:05,659 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:06,737 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1062 ms
| [2008-05-20 15:23:07,847 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1094 ms
| [2008-05-20 15:23:08,940 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:10,034 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:11,112 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1062 ms
| [2008-05-20 15:23:12,206 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:13,315 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1093 ms
| [2008-05-20 15:23:14,393 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1062 ms
| [2008-05-20 15:23:15,487 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:16,596 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1093 ms
| [2008-05-20 15:23:17,690 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:18,768 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1062 ms
| [2008-05-20 15:23:19,893 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1109 ms
| [2008-05-20 15:23:20,987 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:22,081 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:23,174 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:24,268 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:25,362 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:26,456 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1079 ms
| [2008-05-20 15:23:27,549 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:28,643 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:29,737 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:30,830 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:31,924 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:33,018 MicroSocketClientInvoker] SocketClientInvoker[1b64e6a, socket://10.0.2.63:4446] got Exception java.net.ConnectException: Connection refused: connect, creation attempt took 1078 ms
| [2008-05-20 15:23:33,018 UnifiedInvokerHAProxy] Invocation failed: CannotConnectException - org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://10.0.2.63:4446/?dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketTimeout=60000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
| org.jboss.remoting.CannotConnectException: Can not get connection to server. Problem establishing socket connection for InvokerLocator [socket://10.0.2.63:4446/?dataType=invocation&enableTcpNoDelay=true&marshaller=org.jboss.invocation.unified.marshall.InvocationMarshaller&socketTimeout=60000&unmarshaller=org.jboss.invocation.unified.marshall.InvocationUnMarshaller]
| at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:530)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152159#4152159
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152159
18 years, 1 month
[Clustering/JBoss] - Re: HA-JNDI server side problem
by bstansberry＠jboss.com
Your English is fine; if you hadn't apologized for it I'd have figured you were a native speaker. :)
"wecucho" wrote :
| and i am calling this method from the action of the button this way:
|
| anonymous wrote :
| |
| | JMQueuesUtils.getMasterNodeFromCluster(10, "192.168.5.63:1100");
| |
| |
|
Where does this "192.168.5.63" value come from? Does your app somehow know the IP addresses of the cluster members?
If so, change it to use regular JNDI (1099) not HA-JNDI:
| JMQueuesUtils.getMasterNodeFromCluster(10, "192.168.5.63:1099");
|
It sounds like what you want is a regular JNDI lookup of a particular node. You don't want HA; i.e. if that node isn't able to respond you don't want to connect to some other node. If you use HA, you can't control what node it's going to do the lookup on; it will either try to optimize locally or will load balance, neither of which gives you the guaranteed answer I *think* you want.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4152158#4152158
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4152158
18 years, 1 month