| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DataFlowEngine tcp port |
« View previous topic :: View next topic » |
| Author |
Message
|
| opmind |
 Posted: Wed May 11, 2016 3:47 am Post subject: DataFlowEngine tcp port |
 |
|
Acolyte
Joined: 04 Dec 2001
Posts: 68
|
Hello there,
I have a IIB V9 Broker which run under AIX and today I had a tcp port problem with another tool which tried to access the same port of one of my DataFlowEngine.
I'm not using any httplistener or tcp nodes, everything is under MQSeries but if I do a lsof, I have this result :
DataFlowE 8912968 eappro 394u IPv6 0xf1000e0002189bb8 0t0 TCP loopback:6542 (LISTEN)
DataFlowE 9240752 eappro 304u IPv6 0xf1000e00003083b8 0t0 TCP loopback:6527 (LISTEN)
DataFlowE 9240752 eappro 366u IPv6 0xf1000e00003233b8 0t0 TCP loopback:6529 (LISTEN)
DataFlowE 11206740 eappro 366u IPv6 0xf1000e000030f3b8 0t0 TCP loopback:6518 (LISTEN)
So, for my problem I have two choice :
-> changing the "other" tool configuration to access through another tcp port,
-> changing tcp port used by dataflowengines.
I'm curious, so here's my question :
It it possible to configure a tcp port range for DataFlowEngine ?
If any clue ... |
|
| Back to top |
|
 |
| mayheminMQ |
| Posted: Fri May 13, 2016 5:27 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
the lsof command will also list the ports assigned for the Integration Server aka execution group aka DataflowEngine's debugger. I can see the debug port listed when I run lsof.
I do not believe you can assign a range of ports and perform a restriction on the port range for an execution group.
_________________
A Colorblind man may appear disadvantaged but he always sees more than just colors... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 13, 2016 5:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can assign a range of port #s for the eg-level http listeners in a broker.
You can assign port #s to listen on for the TCP IP nodes...
You should, in theory, be able assign port #s to every TCP listening service in IIB.
You should probably review all the ports being listened to, and make sure you're setting them to a known range. And then set the other tool's ports to a different known range. i.e. set all the IIB ports to be in 2200-2300 and all the other tool's ports to 3200-3300. Or etc.
Watch out for well known ports in any ranges you use.
And I'd personally tend to use 'netstat -tnlp" for getting listening ports.
But that's me.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| mayheminMQ |
| Posted: Fri May 13, 2016 5:47 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
