RE: Not receiving ISO response during high volume transactions

The default for the MUX key are fields 11 and 41.  If you're defaulting, and
those keys - when taken together - are not unique, you're going to have a
problem.

While ostensibly not about the MUX key, this piece from my blog talks about
the <key> definition in the MUX:

http://tinyurl.com/285lcu  

Additionally, my on-boarding Guide mentions the <key> definition as a
required step:

http://tinyurl.com/2wjlyq  

Andy Orrock

> -----Original Message-----
> From: jpos-dev@...
[mailto:jpos-dev@...] On Behalf
> Of Alejandro Revilla
> Sent: Monday, December 17, 2007 7:40 AM
> To: jpos-dev@...
> Subject: Re: [jpos-dev] Not receiving ISO response during high volume
> transactions
> 
> >
> > I've seen this before with high traffic and key collisions...
> >
> You can mitigate key collisions by adding additional echo-back fields to
> the MUX key (i.e. pan, amount, currency).
> 
> But we could also detect a key collision before we attempt to send a
> message and either raise an exception or wait until the collision is
> gone... I believe that could be a nice and easy to implement addition to
> QMUX. Messages with the same key would be serialized which is not a
> perfect solution but far better than ignoring the response...
> 
> 
> 
> 
> Yahoo! Groups Links
> 
> 
>