| Author |
Message
|
| KeeferG |
 Posted: Fri Aug 07, 2009 2:50 am Post subject: |
 |
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
I would remove the entry from your inted.conf that is causing the creation of the amqcrsta process.
Then I would define a listener using the same port specified in the inetd.conf.
Ideally you shouldn't be using the SYSTEM.DEF.SVRCONN channel either but creating a new channel for them to connect to.
As PeterPotkay states each amqrmppa process can run up to 64 threads before it spawns a new process which can be up to 64 channels or 32 channels if running with pipelinelength greater than 1.
This should help somewhat with performance but I would try and get more memory as well.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Fri Aug 07, 2009 4:12 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7716
|
| exerk wrote: |
| Ko wrote: |
JosephGramig said,
The inetd configuration is only supported for backwards compatibility.
We use 6.0.2.5., on the other side they use 5.2, do you mean that this combination is not possible to run a listener? If no, do you need to define the listener on two sides (remote QM and local QM)? |
No. For your queue manager, which is at V6.0.2.5, you should configure a Listener object, and place it under control of the queue manager. The other end must use the method appropriate to V5.2 on their platform - very brave people to still be on that version  |
Or very scared....
"OK, It's finally working. Nobody breathe, nobody...touch...anything."
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Ko |
| Posted: Fri Aug 07, 2009 6:59 am Post subject: |
|
|
Newbie
Joined: 05 Aug 2009
Posts: 9
|
| Peter, we are reasearching the possibilties you gaved me, thnx. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Aug 07, 2009 7:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Ko wrote: |
| We use 6.0.2.5., on the other side they use 5.2, do you mean that this combination is not possible to run a listener? |
To clarify my post, when I said inetd became obsolete years ago I meant when v5.3 was released.
If the other side are still using v5.2 then they have to accept there will be problems, both in performance & reliability. Even v5.3 is out of support now so they're 2 versions out of date.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Ko |
| Posted: Thu Aug 13, 2009 1:27 am Post subject: |
|
|
Newbie
Joined: 05 Aug 2009
Posts: 9
|
Hi,
We are trying to use the listener you specified. We would like to shutdown the inetd service (specified in the inetd.conf). So I have do a
| Code: |
| # svcadm refresh inetd |
When I send a message trough MQ it still send to the other party. Does it use anyway the inetd.conf? I haven't started the mq listener. So why it is sended anyway?
Thanks. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 13, 2009 1:35 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Ko wrote: |
| ...When I send a message trough MQ it still send to the other party. Does it use anyway the inetd.conf? I haven't started the mq listener. So why it is sended anyway?... |
Because your Listener is only involved with inbound messages, not outbound.
_________________
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 |
|
|
| Ko |
| Posted: Thu Aug 13, 2009 1:38 am Post subject: |
|
|
Newbie
Joined: 05 Aug 2009
Posts: 9
|
| you're right, only I can still receive messages from another queuemanager (on the same server). |
|
| Back to top |
|
|
|
|
