Larry Leeth
New Member
Our application generates 'dynamic queries' based on Client input parameters which are passed to a 'state-aware' Web Agent.
An initial set on 'n' records are passed back to the Client in a Reply. When the Client requests additional data, a 2nd request is passed to the Web Agent (the same Web Agent since it is 'state-aware'). The initial 'results-list' is then used to do a 'get next' block on the query to get the next 'n' records.
The application worked without a problem under WebSpeed 2.1. However, after moving to version WebSpeed 3.1, any 2nd request from the Client to a 'state-aware' Web Agent results in a 'Bus Error'.
The procedure which receives Client requests (process-web-requests) never receives the 2nd request when running 'state-aware'. The Bus Error terminates the process before CGI can complete the message back to the Server.
Has anyone experienced this problem when migrating from WebSpeed 2.1 to 3.1?
Any thoughts on possible causes?
Larry Leeth
An initial set on 'n' records are passed back to the Client in a Reply. When the Client requests additional data, a 2nd request is passed to the Web Agent (the same Web Agent since it is 'state-aware'). The initial 'results-list' is then used to do a 'get next' block on the query to get the next 'n' records.
The application worked without a problem under WebSpeed 2.1. However, after moving to version WebSpeed 3.1, any 2nd request from the Client to a 'state-aware' Web Agent results in a 'Bus Error'.
The procedure which receives Client requests (process-web-requests) never receives the 2nd request when running 'state-aware'. The Bus Error terminates the process before CGI can complete the message back to the Server.
Has anyone experienced this problem when migrating from WebSpeed 2.1 to 3.1?
Any thoughts on possible causes?
Larry Leeth