| Author |
Message
|
| yalmasri |
 Posted: Fri Apr 30, 2010 4:42 am Post subject: |
 |
|
Centurion
Joined: 18 Jun 2008
Posts: 110
|
| liz72701 wrote: |
| Quote: |
| But I don't have this option when I'm using using a "Distination" object, do I? |
If you use the MQQueue class you can specify open options (binding) there.
Liz |
But that defeats the whole purpose of using JNDI |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Apr 30, 2010 4:58 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| the problem here is that most of the contributors are admins and have no programming hands on. |
I strongly disagree.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| liz72701 |
| Posted: Fri Apr 30, 2010 6:43 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2007
Posts: 8
|
| Quote: |
| But that defeats the whole purpose of using JNDI |
Yes, you're right. Sorry, I forgot you were using JNDI. 
Liz |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Apr 30, 2010 7:42 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| yalmasri wrote: |
| Is that because I don't respond to Vitor's provocations? |
What provocations? Because I said using remote queues in a cluster environment was "odd"? I stand by that; it's odd to use a remote queue (which requires you to specify a destination) in a clustered environment (where the software finds the destination for you).
| yalmasri wrote: |
Don't worry, if you are an Apprentice between Grand Poobah's then you have to act like one  . |
The titles on this forum are an attempt to lighten the mood in a friendly way. As a contributor once said, "Grand Poobah just means I post too much". There are many people on this forum with much more "junior" titles who know much more than me about the software (in many cases because they develop it).
I also don't know the poster in question except as another poster.
| yalmasri wrote: |
| But anyway, the problem here is that most of the contributors are admins and have no programming hands on. |
So much for my 20 years of COBOL, C & C++. Gone, just because I warn people my Java is weak and thus my advice could be flawed.
| yalmasri wrote: |
| I just want a person who practically went through this, and I'm sure we can close this long thread with one short statement. |
That would be me. I've been doing clusters since they were introduced, both writing applications and administering, and I like to think my comments are valid both in terms of the use of binding defaults & the interaction with the application.
If you don't like my writing style then I'm sorry.
_________________
Honesty is the best policy.
Insanity is the best defence.
Last edited by Vitor on Fri Apr 30, 2010 8:10 am; edited 1 time in total |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Apr 30, 2010 7:45 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
Does this mean that if I don't like a reply, I can't ridicule the person that posted it?? Where's the fun in that...
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 30, 2010 11:51 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| yalmasri wrote: |
| fjb_saper wrote: |
| yalmasri wrote: |
| But I don't have this option when I'm using a "Destination" object, do I? |
Sure you do. It's in the setup of the Destination in JNDI.
It may also specify as QDEF and take on the value set on the queue. But if you specified something else in your JNDI setup for the destination this (JNDI) takes precedence.
Have fun  |
Great, here are all administered properties, can you tell me which is for "default bind type"? |
Sorry you're right. I was thinking about specifying the Destination via URI. This would give you the capability to specify this info
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| yalmasri |
| Posted: Fri Apr 30, 2010 4:02 pm Post subject: |
|
|
Centurion
Joined: 18 Jun 2008
Posts: 110
|
| Vitor wrote: |
| What provocations? Because I said using remote queues in a cluster environment was "odd"? |
Of course no, this is a pure technical observation that's completely valid. I'll be ridiculous to consider this as a provocation. Here is the one I was talking about:
| Vitor wrote: |
| You seem to be bring the same skills you use reading the cluster weighting attribute documentation to reading our posts. |
I don't think charging people's capabilities is what professionals should be on. This is not to mention that you couldn't get me the attribute's name that would control weighting on queue level to backup your assumption. But don't mean to that now, I think you're a professional afterall.
| fjb_saper wrote: |
| Sorry you're right. I was thinking about specifying the Destination via URI. This would give you the capability to specify this info |
That's it, I think I'm winning guys, default binding type cannot be overridden when a Destination is looked up using JNDI |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Apr 30, 2010 4:34 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9472
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| This is not to mention that you couldn't get me the attribute's name that would control weighting on queue level to backup your assumption. |
If you are interested, I can get that information for you, for my usual consulting rate. I'd guess that you could find that kind of info in a manual...
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| yalmasri |
| Posted: Fri Apr 30, 2010 5:02 pm Post subject: |
|
|
Centurion
Joined: 18 Jun 2008
Posts: 110
|
| bruce2359 wrote: |
| Quote: |
| This is not to mention that you couldn't get me the attribute's name that would control weighting on queue level to backup your assumption. |
If you are interested, I can get that information for you, for my usual consulting rate. I'd guess that you could find that kind of info in a manual... |
Hey Bruce, I think it's more valuable to your professional career to withdraw now with least losses than coming later with different type of excuses for why you can't find that attribute |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 30, 2010 9:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| yalmasri wrote: |
| fjb_saper wrote: |
| Sorry you're right. I was thinking about specifying the Destination via URI. This would give you the capability to specify this info |
That's it, I think I'm winning guys, default binding type cannot be overridden when a Destination is looked up using JNDI |
Not quite sure you're right... It all depends how the queue was saved to JNDI.
If you use the URI form to create the Destination and then save it to JNDI....
But if you use JMSAdmin then no you will not be able to override the defbind attribute unless you write some code to do so.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| yalmasri |
| Posted: Sat May 01, 2010 1:18 am Post subject: |
|
|
Centurion
Joined: 18 Jun 2008
Posts: 110
|
| fjb_saper wrote: |
| If you use the URI form to create the Destination and then save it to JNDI.... |
URI form?! Do you have any document on that? |
|
| Back to top |
|
|
| mvic |
| Posted: Sat May 01, 2010 9:53 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Just wondering what MQ code level you are at. Found these APARs:
| Code: |
IZ13144 Cluster workload is affected due to change in NETPRTY
behavior
IZ34130 Workload balancing in a cluster leads to unexpected results.
IZ51783 Destination sequence factor (destseqfactor) is not getting
reset when a new destination is made available. |
I have no idea whether these are a cause of what you are seeing, though.
But anyway, if you have 6.0.2.8 or 7.0.1.1 you have fixes for all of these. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 01, 2010 10:22 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| yalmasri wrote: |
| fjb_saper wrote: |
| If you use the URI form to create the Destination and then save it to JNDI.... |
URI form?! Do you have any document on that? |
Cast to MQQueue, set your attributes, and Cast to Destination Queue. Inspect the Queue and you should find somewhere the URI form:
| Code: |
| "queue://qmgr/qname?attr1=value1&attrn=valuen" |
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| yalmasri |
| Posted: Sat May 01, 2010 11:42 am Post subject: |
|
|
Centurion
Joined: 18 Jun 2008
Posts: 110
|
| mvic wrote: |
Just wondering what MQ code level you are at. Found these APARs:
| Code: |
IZ13144 Cluster workload is affected due to change in NETPRTY
behavior
IZ34130 Workload balancing in a cluster leads to unexpected results.
IZ51783 Destination sequence factor (destseqfactor) is not getting
reset when a new destination is made available. |
I have no idea whether these are a cause of what you are seeing, though.
But anyway, if you have 6.0.2.8 or 7.0.1.1 you have fixes for all of these. |
IZ34130 sounds close, and I in fact have 6.0.2.6. I guess I'll ask our admin to arrange for an upgrade, I'm out of options.
Thanks chum |
|
| Back to top |
|
|
| mvic |
| Posted: Sat May 01, 2010 12:32 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| yalmasri wrote: |
| IZ34130 sounds close, and I in fact have 6.0.2.6. I guess I'll ask our admin to arrange for an upgrade, I'm out of options. |
http://www.ibm.com/support/docview.wss?uid=swg1IZ34130 says that 6.0.2.6 includes IZ34130, so it can't be that one, I guess.
Still worth being at the latest fix pack (6.0.2.9) to be protected against as much as possible.
Not sure if you need this information, but to get more certainty about the bind type being specified on your app's MQOPEN, get an MQ trace capturing the application activity:
| Code: |
strmqtrc -m QM1 -t api
# recreate problem
endmqtrc -m QM1
cd /var/mqm/trace
# following step not needed on Windows
dspmqtrc *.TRC |
If the app is server-bound, you'll see the MQOPEN in a trace file for your program. If it's client-bound, you'll need to find the amqrmppa thread that was serving your app, and look at the MQOPEN it does on behalf of the app.
You should look for the flags in the Options field, to see whether they contain either of these values.
| Code: |
#define MQOO_BIND_ON_OPEN 0x00004000
#define MQOO_BIND_NOT_FIXED 0x00008000 |
|
|
| Back to top |
|
|
|
|
