| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TCP Input in diff EG |
« View previous topic :: View next topic » |
| Author |
Message
|
| ardi |
 Posted: Wed Oct 30, 2013 7:31 am Post subject: TCP Input in diff EG |
 |
|
Newbie
Joined: 30 Oct 2013
Posts: 7
|
Hi, I have cases like these :
EG1 = TCP Input -> Calculate Header Length -> TCP Receiver -> MQ Out
EG2 = TCP Input -> Calculate Header Length -> TCP Receiver -> MQ Out
EG3 = TCP Input -> Calculate Header Length -> TCP Receiver -> MQ Out
Message : ISO with header length
Problem :
Why my TCP Input node in a EG2 & EG3 does not receive any message from backend ? it just only want to recieve message from EG1.
Reason for this design :
Multi instance TCP Input purpose. Since our existing TCP Input flow throws exception if we set the additional instance more than 0.
Need your advise  |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Wed Oct 30, 2013 7:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Are all TCPInput Nodes configured to listen on the same port?
I'd expect this to throw some errors. You can only have one thing listening on an individual port.
If your existing flow throws errors when using additional instances then I'd be inclined to raise a PMR with IBM over this.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| ardi |
| Posted: Wed Oct 30, 2013 7:22 pm Post subject: |
|
|
Newbie
Joined: 30 Oct 2013
Posts: 7
|
| smdavies99 wrote: |
Are all TCPInput Nodes configured to listen on the same port?
I'd expect this to throw some errors. You can only have one thing listening on an individual port.
If your existing flow throws errors when using additional instances then I'd be inclined to raise a PMR with IBM over this. |
Thanks smdavies for the reply, yep our node listen to same port. The exception occurs because we have the "Cut The Length based on ISO header", so the next instance will get the wrong value header.
So we decide to using single EG with no additional instances. Is there any option ? since i guess is the bottleneck for the entire flow.
Need your help 
_________________
Indonesian WMQ & WMB User |
|
| Back to top |
|
|
| NealM |
| Posted: Thu Nov 07, 2013 2:40 pm Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
Interesting. I assume you are talking about the TCPServerInput node. Which can only be deployed to one EG in the Broker for a particular port. Two things:
1. I have no idea why data from one instance would effect a second instance (unless you are using shared variables), but if that is your entire flow, with no need to send a TCPIP response back, are you closing your connection each time?
2. Although the TCPIPServer node can only be deployed to one EG per port, the InfoCenter says it is OK to have multiple flows on the same port in the same EG, so you could try that, just make pretty much your entire current flow into a subflow, and have 3 different named flow shells for it.
That said, and I admittedly don't know what is special about ISO, in our Prod we run a TCPIPServer asynchronous request/reply flow pair each with 2 additional instances (at the input node level) and variable length data (also going to/from MQ) and have absolutely no interference between instances issues. And in our case of course we leave the connection open until the reply. So multiple TCPIPServer node instances do work. |
|
| 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
|
|
|
|
