| Author |
Message
|
| ydsk |
 Posted: Mon Jul 18, 2005 8:02 am Post subject: IA91...Broker Domain scope |
 |
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
Did anyone successfully implement IA91 with scope as 'Broker Domain' ?
I am able to do it successfully with scope as the 'execution group'. Somehow it doesn't seem to work when the scope is 'Broker Domain'.
I have a msgflow1 that PUTs a msg into the cache. It is deployed onto Broker1. A different msgflow2 that GETs msgs from the Cache is deployed onto Broker2 in the same broker domain.
I have all the jar files, classpath, etc correct on both the brokers. I also deployed "Realtime-optimizedflow" successfully on each broker. I also have all the MQ jar files in the classpath.
But it's not working at the broker domain level.
It's working at the execution group level though.
If any one implemented it successfully at broker domain level can pls send me the code I would be grateful.
Thanks. |
|
| Back to top |
|
 |
| JT |
| Posted: Mon Jul 18, 2005 9:15 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Did you ensure that the port number specified in the Real-timeOptimzedFlow node does not conflict with any other listener service?
What OS platform ?
Are there any messages in the system log/eventlog ? |
|
| Back to top |
|
|
| ydsk |
| Posted: Mon Jul 18, 2005 9:25 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
JT,
I already mentioned that it is working fine at the execution group level on each of the brokers boxes separately. If port number is clashing with other services it won't work even at execution group level.
One broker is on AIX and the other is on Win XP.
Did you use this support pack or are you just trying to investigate the problem with your ideas ?
Thanks. |
|
| Back to top |
|
|
| ydsk |
| Posted: Mon Jul 18, 2005 9:28 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
I tried by deploying the msgflow1 that PUTs msgs to cache to ExecGroup1 and the flow that GETs msgs to ExecGroup2 on the same broker and it works fine. This is at the broker domain scope / level.
It is working fine on AIX and Win XP as well.
So, there are no issues with the port number of realtime-optimized flow.
Thanks. |
|
| Back to top |
|
|
| JT |
| Posted: Mon Jul 18, 2005 9:37 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| If port number is clashing with other services it won't work even at execution group level. |
Are you sure?
It's been some time since I configured the IA91 supportpac, but I thought the real-time port wasn't used at the EG-scope level, just the broker-domain-scope level, in which case you didn't exercise the port. |
|
| Back to top |
|
|
| JT |
| Posted: Mon Jul 18, 2005 9:40 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
From the IA91 documentation:
| Quote: |
There are additional facilities that this SupportPac brings around this caching mechanism. Following is a list of these functions:
- The ability to store data in both a local and domain cache via an execution group and/or a broker domain. (WebSphere MQ Real-time transport is used to communicate between the brokers).
|
|
|
| Back to top |
|
|
| ydsk |
| Posted: Mon Jul 18, 2005 11:51 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
The realtime optimized flow and port are needed only for broker domain scope.
And as I already mentioned it works with the broker domain scope only when the PUT flow is in one execution group and the GET flow is in another exec group BUT both on the same broker.
I could go only that far. I am unable to get successful results when I deploy the PUT and GET flows to different brokers.
Did anybody get this piece working at the broker domain scope by deploying to multiple brokers in the same domain ?
Thanks. |
|
| Back to top |
|
|
| martc |
| Posted: Mon Jul 18, 2005 6:24 pm Post subject: |
|
|
Apprentice
Joined: 23 Mar 2005
Posts: 39
|
We have tested using the broker domain scope with our msg. flows running on 4 execution groups. On low load this is no problem BUT this configuration fails under heavy load. I even tested it using different ports and bumping up the read & write threads. Did not work.
As I understand it, a broker domain does not mean you can share cache with separate brokers. It simply gives you the ability to share cache with separate execution groups? |
|
| Back to top |
|
|
| ydsk |
| Posted: Tue Jul 19, 2005 7:36 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
Can you pls specify what the high load for you was ? So, you are saying it doesn't work with more than one broker.
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 19, 2005 7:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| ydsk wrote: |
| So, you are saying it doesn't work with more than one broker. |
I don't see anything that would indicate that it knows how to find and communicate with other brokers.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| ydsk |
| Posted: Tue Jul 19, 2005 8:00 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
Well, the broker domain scope was meant for that. As per the documentation for the support pack it should work with more than 1 broker but in the same domain.
It wasn't the case with the previous release of the support pack, which was limited to a scope of 'execution group'.
Thanks. |
|
| Back to top |
|
|
| ydsk |
| Posted: Wed Jul 20, 2005 6:40 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
Hi Martc,
You said it fails under heavy load. Can you pls tell me what the heavy load is ? Even we are trying to use it with heavy loads.
Appreciate your response.
Thanks. |
|
| Back to top |
|
|
| martc |
| Posted: Wed Jul 20, 2005 2:11 pm Post subject: |
|
|
Apprentice
Joined: 23 Mar 2005
Posts: 39
|
You said it fails under heavy load. Can you pls tell me what the heavy load is ? Even we are trying to use it with heavy loads.
3tps should do it. I tried this with 2 very simple flows, the put flow with 3 nodes MQIN-CachePut-MQOut, the get flow MQIN-CacheGet-MQOut. Please try this. I'm still hoping I'm wrong.
Regarding other brokers to share the cache, I tend to agree with jeff... The RealtimeOptimization flow does not provide for another ip, just a port. This assumes that you are communicating within the same TCP stack.
Am I missing something? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Jul 23, 2005 3:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| martc wrote: |
Regarding other brokers to share the cache, I tend to agree with jeff... The RealtimeOptimization flow does not provide for another ip, just a port. This assumes that you are communicating within the same TCP stack.
Am I missing something? |
Well, maybe eventually the author of this support pack will chime in.
Something that occurred to me just now, though, is that this support pack could be relying on broker collectives to find and communication with other brokers.
If so, it should be documented that that's the case... Likewise it should be documented if it can only share scope with brokers on the same machine/IP address...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
