|
Home > Archive > WebSphere HATS > October 2005 > Urgent: Connection Timeout doesn't work
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Urgent: Connection Timeout doesn't work
|
|
| Marta L 2005-10-10, 5:45 pm |
| Hi all,
We're involved in a project with HATS, using TN5250. We must connect to the iSeries specifying a fixed Workstation ID per user, so we decided to use a HTTP session variable to manage this.
The problem is when a Workstation ID is occupied, it is not until 2 minutes have lapsed that the user recieves a response saying that the connection hasn't been possible. During 2 minutes the browser appears as loading a page, so the user doesn't know what's happening and that amount of time is too much.
We want to become this time shorter but the parameter "Abandon attempt to connect after a specified number of seconds" doesn't work with a session variable as Workstation ID. However it does if we use a specified value.
In the meantime as terminal screen we can see is the one we attach (ErrorComm659.jpg) .
The communication message that appears (comm659) is clear:
The Telnet TCP connection to the session has not succeeded or has failed.
For 5250, the specified workstation ID is already in use, and the host closed the connection.
..
We experimented the same problem with TN3270 time ago and using this advanced parameters (after a pmr) we could set a reasonable connection timeout:
<parameter name="connectionTimeout" value="5"/> (seconds)
<parameter name="hostBackup1" value="dev.open.net"/> (the same host namespecified in the basic tab)
<parameter name="timeoutNoDataAtInitialization" value="true"/>
Is there a solution for TN5250 through HATS as well?
We need to implement the connection with a variable WorkstationID (obtained in a program).
| |
| George Baker 2005-10-13, 5:50 pm |
| In article <die8lb$1tfs$1@news.boulder.ibm.com>, mlorenzo@opennorte.com
says...
> Hi all,
> We're involved in a project with HATS, using TN5250. We must connect to the iSeries specifying a fixed Workstation ID per user, so we decided to use a HTTP session variable to manage this.
> The problem is when a Workstation ID is occupied, it is not until 2 minutes have lapsed that the user recieves a response saying that the connection hasn't been possible. During 2 minutes the browser appears as loading a page, so the user doesn't know w
hat's happening and that amount of time is too much.
> We want to become this time shorter but the parameter "Abandon attempt to connect after a specified number of seconds" doesn't work with a session variable as Workstation ID. However it does if we use a specified value.
>
> In the meantime as terminal screen we can see is the one we attach (ErrorComm659.jpg) .
> The communication message that appears (comm659) is clear:
> The Telnet TCP connection to the session has not succeeded or has failed.
> For 5250, the specified workstation ID is already in use, and the host closed the connection.
>
> .
> We experimented the same problem with TN3270 time ago and using this advanced parameters (after a pmr) we could set a reasonable connection timeout:
>
> <parameter name="connectionTimeout" value="5"/> (seconds)
> <parameter name="hostBackup1" value="dev.open.net"/> (the same host namespecified in the basic tab)
>
> <parameter name="timeoutNoDataAtInitialization" value="true"/>
>
>
>
> Is there a solution for TN5250 through HATS as well?
>
> We need to implement the connection with a variable WorkstationID (obtained in a program).
>
> [image/jpeg]
>
Sounds like a defect to me, so I would open a PMR, defect, with IBM
support.
|
|
|
|
|