headers
Junaid | 17 Dec 07:02
Picon
Favicon

Not receiving ISO response during high volume transactions

Hello all,

We are using Jpos 1.4.1 for connecting to Base24 station for balance
enquiry etc.  We have high volume of transaction happening all the
time. Once in a while during high volume transaction , JPOS is not
able to receive response from the server and it times out. But at the
server end they have sent us the response.

Following is the code we are using

ISORequest r = new ISORequest(msg);
mux.queue(r);
return r.getResponse(timeout);

We cannot upgrade the jpos for now also.

How can we fix this?

Junaid P K
Senior Software Engineer
enStage Software Private Limited.
Permalink | Reply |
headers
Alejandro Revilla | 17 Dec 10:22

Re: Not receiving ISO response during high volume transactions

> 
> ISORequest r = new ISORequest(msg);
> mux.queue(r);
> return r.getResponse(timeout);
> 
Is there a log attached to your channel? 
do you see the response in that log?
do you see any exception/channel disconnect after the message is transmitted?
is there a key collision (i.e. two messages at the same time with the same mux key?)
what's the value of your timeout?
Permalink | Reply |
headers
Victor Salaman | 17 Dec 16:24
Picon

Re: Not receiving ISO response during high volume transactions

I've seen this before with high traffic and key collisions...

-V

On Dec 17, 2007 5:22 AM, Alejandro Revilla <apr@...> wrote:
>
>
>
>
>
>
> >
>  > ISORequest r = new ISORequest(msg);
>  > mux.queue(r);
>  > return r.getResponse(timeout);
>  >
>  Is there a log attached to your channel?
>  do you see the response in that log?
>  do you see any exception/channel disconnect after the message is
> transmitted?
>  is there a key collision (i.e. two messages at the same time with the same
> mux key?)
>  what's the value of your timeout?
>
>
Permalink | Reply |
headers
Alejandro Revilla | 17 Dec 16:40

Re: 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...
Permalink | Reply |
headers
Andy Orrock | 17 Dec 17:04
Favicon

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).
(Continue reading)

Permalink | Reply |

Gmane