[JBoss Messaging] - Re: Messaging 1.3 Clustering question
by timfox
"nbakizada" wrote :
|
| I'm having trouble understanding if the 2 nodes in a cluster act as some sort of primary/secondary, or if they're both equal primaries. In the event of a basic failover (one of the 2 appservers goes down), things failover to the other just fine. But what happens if, say, both servers are running, but are somehow unable to connect to each over the network (so each thinks the other is unavailable). What happens to the messages stored in the shared database?
|
You're referring to network partitioning commonly known as "split brain".
In this case both nodes would fail over for each other. This can result in duplicate delivery of messages.
Note that exact same issue would arise with JBoss MQ / A.N. other product so is not specific to JBM. It's a general network condition.
To mitigate against this you can use IP bonding to add redundancy on the IP level (see JGroups wiki), and code your consumers to be resilient to duplicate messages.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120747#4120747
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120747
18 years, 5 months
[JBossWS] - Re: Adding application specific properties to the MessageCon
by yhrn
anonymous wrote : The docs say you can get the RequestContext from the BindingProvider, add properties all on the client, and then that is accessible via the MessageContext on the server.
In what document have you read that? The properties you set on a BindingProvider request context is used to initialize the client side message context which is available to all client side handlers and the client side JAX-WS runtime.
If you want the properties set on BindingProvider request context to be transferred to the server you can implement a custom handler on the client side that puts it in the SOAP header and a server side handler that retrieves the properties from the header and puts it in the message context on the server side. The following is quoted from the JAX-WS 2.1 spec:
anonymous wrote : Handlers may manipulate the values and scope of properties within the message context as desired. E.g.,
| a handler in a client-side SOAP binding might introduce a header into a SOAP request message to carry
| metadata from a property that originated in a BindingProvider request context; a handler in a server-side
| SOAP binding might add application scoped properties to the message context from the contents of a header
| in a request SOAP message that is then made available in the context available (via injection) to a service
| endpoint implementation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4120743#4120743
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4120743
18 years, 5 months