[Saravana Kumar.S]

All,
I am using HTTP TA as server in asynchronous dialog mode and it uses single connection for receiving and sending response. The timeout value for the response is 120. Two days back, i got a weird problem - I received a request say A and it got timed out before the processing is done and so timeout is returned back. And in meanwhile i received another say B and it was successfully processed but while responding it had sent back the response for request A.

I tried to find out what happened but the logger entry are not available for these requests.
More to this, this problem occurred for 2 minutes and after that every thing started working properly.

Any body faced this problem before? Any solutions or suggestions would be of great help!!!

Cheers,
Saravana

[basvandenberg]

Saravana,

Make sure the HTTP TA has it's own processing engine to prevent these problems and make sure you are on the latest patchlevel. In the past we have had some issues with the HTTP connector, but this should be fixed now.

Regards,

Bas

All,
I am using HTTP TA as server in asynchronous dialog mode and it uses single connection for receiving and sending response. The timeout value for the response is 120. Two days back, i got a weird problem - I received a request say A and it got timed out before the processing is done and so timeout is returned back. And in meanwhile i received another say B and it was successfully processed but while responding it had sent back the response for request A.

I tried to find out what happened but the logger entry are not available for these requests.
More to this, this problem occurred for 2 minutes and after that every thing started working properly.

Any body faced this problem before? Any solutions or suggestions would be of great help!!!

Cheers,
Saravana

[Saravana Kumar.S]

Hi Bas,

Thanks for the reply.
I found out the problem. Though the request A is timed out, the request message is still in the HME and it is processed by the HME. When the processing is done, integration invokes the HTTP TA to send the response and at this point, the response got changed i.e. response for request A is sent back to HTTP TA and HTTP TA assumes that it is response for request B and sends the response. I suspect that the message id comparison of the request and response messages is not correct in the HTTP TA.
We are running the HTTP TA in a separate PE but we are not in the latest patch level w.r.t HTTP TA.
Also i am thinking to delete the message from HME if the request is timed out in the custom MBC. But i am not able to get the asynchronous time out value in the custom MBC. I checked with the 'HTTP Server Receive Info' attribute but the time out value is not available in that. Any idea how to get that value?

Regards,
Saravana Kumar.S

Saravana,

Make sure the HTTP TA has it's own processing engine to prevent these problems and make sure you are on the latest patchlevel. In the past we have had some issues with the HTTP connector, but this should be fixed now.

Regards,

Bas

[basvandenberg]

Saravana,

We have several customers running a similar scenario, using the HTTP connector, without having the problem that the sessions get mixed up. It is important to use a separate TA and procengine for your "server" part and your client part of the integration. That will help solving this issue.

Regarding the other question (time-out): If you want to prevent that the response is parsed back to your TA after the time-out, you need to do some customization. Probably the easiest way to solve this, is that you create a "time-stamp" attribute and attach this attribute in your flow. Just before you send the result to the TA control activity, you match the attribute time-stamp with the current time stamp and do a quick calculation to see if you exceeded the time-out of 120 seconds.

Regards,

Bas

Hi Bas,

Thanks for the reply.
I found out the problem. Though the request A is timed out, the request message is still in the HME and it is processed by the HME. When the processing is done, integration invokes the HTTP TA to send the response and at this point, the response got changed i.e. response for request A is sent back to HTTP TA and HTTP TA assumes that it is response for request B and sends the response. I suspect that the message id comparison of the request and response messages is not correct in the HTTP TA.
We are running the HTTP TA in a separate PE but we are not in the latest patch level w.r.t HTTP TA.
Also i am thinking to delete the message from HME if the request is timed out in the custom MBC. But i am not able to get the asynchronous time out value in the custom MBC. I checked with the 'HTTP Server Receive Info' attribute but the time out value is not available in that. Any idea how to get that value?

Regards,
Saravana Kumar.S

[Saravana Kumar.S]

Bas,

Sorry i was busy these days, hence couldn't update the status.
I have raised this problem to the Axway support and they have confirmed that this is an issue in the HTTP TA .
For handling timeout, i also thought of same approach as already HTTP TA writes the received time as the time stamp in the message while passing it to the integration but only the problem is that i am not able to get the 'Time Out' value configured at the TA coz the 'Time Out' is not a fixed value. So i want to know how to read the time out value configured in the HTTP TA in the custom MBC.

Regards,
Saravana Kumar.S

[basvandenberg]

Saravana,

I think I do understand your problem not completely. Since the Time out is set on the TA level, you know what the time-out is, or not? I cannot imagine you change the TA time out every xx seconds or minutes, since that requires a change in the configuration (through composer) and a stop and start of the TA. Since you know the "fixed" time out value and you know the time stamp of the request, you can easily calculate whether the message has timed out or not.

Regards,

Bas

Bas,

Sorry i was busy these days, hence couldn't update the status.
I have raised this problem to the Axway support and they have confirmed that this is an issue in the HTTP TA .
For handling timeout, i also thought of same approach as already HTTP TA writes the received time as the time stamp in the message while passing it to the integration but only the problem is that i am not able to get the 'Time Out' value configured at the TA coz the 'Time Out' is not a fixed value. So i want to know how to read the time out value configured in the HTTP TA in the custom MBC.

Regards,
Saravana Kumar.S

[Saravana Kumar.S]

Bas,

As you mentioned, the time out value is not changed very often. But it is also not a fixed one i.e. i have different time out value in the test server and prod server. Yet i can configure same value at both the servers and perform check but don't want to. Also i am not in favor of solution with hard coded value. So only i am looking for a way to read the configured value in TA rather having a fixed value in the custom MBC.

Regards,
Saravana Kumar.S