Author |
Message
|
rajasri |
Posted: Tue Jan 25, 2011 5:45 am Post subject: What is underlying code for MQ and MB - java or c or ??? |
|
|
 Centurion
Joined: 11 Jun 2006 Posts: 114
|
Hi People,
I was asked a question by one of my teammate and i couldn't ans him. What is underlying code for MQ and MB - java or c or ???. Does anybody have info or link for the same.
Thanks
Pradeep. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jan 25, 2011 6:03 am Post subject: Re: What is underlying code for MQ and MB - java or c or ??? |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rajasri wrote: |
What is underlying code for MQ and MB - java or c or ???. |
AFAIK both are mostly C with a hint of Java (hence the different binary distributions for different platforms).
I'm not aware of exact details of what bits of what product are in what language being posted anywhere. A passing IBMer may wish to correct me. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jan 25, 2011 7:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It provides no end user value to know this information.
MQ has absolutely no core functionality written in Java, as far as I know. I have heard statements from the product strategist that he is more than happy to see that continue to be true.
Broker is a mix of Java and C. There's no documentation on how it is mixed, but every ExecutionGroup is both a JVM and a C/C++ runtime.
It does you no good to know this.
Read the documentation on the interfaces exposed and allowed by the products for developing applications and managing and administering the products and troubleshooting them. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jan 25, 2011 7:17 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
It provides no end user value to know this information. |
mqjeff wrote: |
It does you no good to know this. |
And yet people have been asking me that for years. Sometimes because techies are curious by nature, sometimes becuase they want to fix a problem by "increasing the queue manager's heap size" (!) and sometimes because some manager somewhere wants a "pure Java" site.
No, I've never really known what that is either. Smile & nod, smile & nod, then push the invoice over the table to be signed... _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jan 25, 2011 7:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Vitor wrote: |
Sometimes because techies are curious by nature, |
Yes, there's naught wrong that.
Vitor wrote: |
sometimes becuase they want to fix a problem by "increasing the queue manager's heap size" (!) |
Well, but which one of the several standalone processes that make up the qmgr?
Also, again, there is no JVM anywhere "inside" a queue manager. Unlike in Broker. |
|
Back to top |
|
 |
Vitor |
Posted: Tue Jan 25, 2011 8:03 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Vitor wrote: |
sometimes becuase they want to fix a problem by "increasing the queue manager's heap size" (!) |
Well, but which one of the several standalone processes that make up the qmgr? |
In these situations I've always seen the plan to "increase the heap size" as much as the same as "increase the flow of pixie dust". Vague on detail, uncertain in execution and more technical sounding than "do stuff until it starts working".
How doing anything to the queue manager would stop their badly written application throwing null pointer exceptions has always been beyond me. Especially as we (obviously) never increase the heap size of the queue manager and yet their code starts to work. After they fix it.
 _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
exerk |
Posted: Tue Jan 25, 2011 8:10 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
Vitor wrote: |
...How doing anything to the queue manager would stop their badly written application throwing null pointer exceptions has always been beyond me. Especially as we (obviously) never increase the heap size of the queue manager and yet their code starts to work... |
But they (management) think that something has been done to the queue manager because you've probably had to restart it - as with most things, it's the perception rather than the reality  _________________ It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
Back to top |
|
 |
bruce2359 |
Posted: Tue Jan 25, 2011 10:35 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
There was a time when IBM developers wrote in a proprietary source programming language called PLX. The PLX code would be passed through a translator that produced platform-specific source code. This allowed an application to be ported to whatever target platform was needed. _________________ 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 |
|
 |
mvic |
Posted: Tue Jan 25, 2011 1:59 pm Post subject: Re: What is underlying code for MQ and MB - java or c or ??? |
|
|
 Jedi
Joined: 09 Mar 2004 Posts: 2080
|
rajasri wrote: |
I was asked a question by one of my teammate |
Is there a problem to be solved? Or is it just for "information" ? |
|
Back to top |
|
 |
rajasri |
Posted: Tue Jan 25, 2011 7:05 pm Post subject: What is underlying code for MQ and MB - java or c or ??? |
|
|
 Centurion
Joined: 11 Jun 2006 Posts: 114
|
Hi all, thank you all for the replies. It was very helpful. This is just for information. |
|
Back to top |
|
 |
|