cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1523
Views
0
Helpful
4
Replies

Application Gateway Unsuccessful.

prashs
Level 1
Level 1

Customer is using the Application Gateway to send the Variable to the external application and receive the updated variable through the same.

We are observing that Application gateway is unsuccessful for more than 50 % . Can we know the reson for the unsuccessful.

whether the application gateway node is not receiving the required variable or is there any timeout.

Can the router logs show me the information .

1 Accepted Solution

Accepted Solutions

Hi,

not because of the timeout. ICM sent Query_Req and the Application Gateway host responded correctly, with a Query_Resp message, but with the Reject flag enabled and the reject code set to 1. Remember, there are four bytes, or, an Integer for the Reject value in the Query_Resp message, if set to a nonzero value, ICM assumes the host rejected the request.

So it's time to turn to the person who controls the Application gateway, there might be several reasons:

- application gateway rejects, because... for a specific reason, for instance, insufficient resources, etc;

- the application sets this flag because of a programming error.

G.

View solution in original post

4 Replies 4

Gergely Szabo
VIP Alumni
VIP Alumni

Hi,

it's either the external application sending information ICM cannot understand or the reply timed out.

You may want to try adjusting the timeout parameters for your application gateway instance in Config Manager.

Yes, the agi Router subprocess would show you what's going on.

G.

I did checkec the agi router process but not able to get required information . Can i know is there any trace setting which i need to enable.

Hi All,

I did enabled the trace and was able to see the agi process . And  I am come up with some rejections  and i see delay is more than 50 is rejected.

16:01:23:230 ra-agi Trace: Received Query Confirm message from application gateway host.

16:01:23:230 ra-agi Trace:     ApplicationGatewayID = 5000

16:01:23:230 ra-agi Trace:     InvokeID =             115057

16:01:23:230 ra-agi Trace:     Reject code =             1

16:01:23:230 ra-agi Trace:  Error count =     1

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable1, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable2, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable3, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable4, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable5, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable6, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable7, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable8, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable9, Tag Value = A300FDC9AD1811E2900344D3CA1C8100

16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable10, Tag Value = 

16:01:23:230 ra-agi Trace:     Tag type = CustomerProvidedDigits, Tag Value = 

16:01:23:230 ra-agi Trace: Current Time is: 16:01:23.230

16:01:23:230 ra-agi Trace: Sending AppGWLookupReply: 

16:01:23:230 ra-agi Trace:     transaction ID is 1113906

16:01:23:230 ra-agi Trace:     result is         Host Rejected Request

16:01:23:230 ra-agi Trace:     delay is          200 16:01:23:230 ra-agi Trace: Received Query Confirm message from application gateway host.
16:01:23:230 ra-agi Trace:     ApplicationGatewayID = 5000
16:01:23:230 ra-agi Trace:     InvokeID =             115057
16:01:23:230 ra-agi Trace:     Reject code =             1
16:01:23:230 ra-agi Trace:  Error count =     1
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable1, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable2, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable3, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable4, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable5, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable6, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable7, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable8, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable9, Tag Value = A300FDC9AD1811E2900344D3CA1C8100
16:01:23:230 ra-agi Trace:     Tag type = PeripheralVariable10, Tag Value = 
16:01:23:230 ra-agi Trace:     Tag type = CustomerProvidedDigits, Tag Value = 
16:01:23:230 ra-agi Trace: Current Time is: 16:01:23.230
16:01:23:230 ra-agi Trace: Sending AppGWLookupReply: 
16:01:23:230 ra-agi Trace:     transaction ID is 1113906
16:01:23:230 ra-agi Trace:     result is         Host Rejected Request
16:01:23:230 ra-agi Trace:     delay is          200

I am just curious to know is this because of the timeout or external host which ICM is connected that is rejecting.

Hi,

not because of the timeout. ICM sent Query_Req and the Application Gateway host responded correctly, with a Query_Resp message, but with the Reject flag enabled and the reject code set to 1. Remember, there are four bytes, or, an Integer for the Reject value in the Query_Resp message, if set to a nonzero value, ICM assumes the host rejected the request.

So it's time to turn to the person who controls the Application gateway, there might be several reasons:

- application gateway rejects, because... for a specific reason, for instance, insufficient resources, etc;

- the application sets this flag because of a programming error.

G.