Questions on GDC interaction with GAS
"Steve Underwood" <[email protected]> Tue, 5 Dec 2006 17:12:32 -0500
| Newsgroups | gmane.comp.lang.4gl.fourjs.user |
|---|---|
| Organization | Versaterm Inc. |
| Message-ID | <000201c718ba$75c42140$4ed849c6@Montero2K> |
This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C71890.8CEF9FE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi: We've been trying to use a non-ActiveX Windows version of the Genero Desktop Client (i.e. not GDCAX but just GDC - version 1.33.1b), to interact with the Genero Application Server (GAS - version 1.32.1c for RedHat Linux) and have encountered a few issues where some clarification would be appreciated. ===> Issue #1 First, when we configure the GDC for a HTTP type connection through a web-server (as opposed to GAS-direct connection), the connection fails with an information dialog displaying the message "Invalid application identifier". The entries recorded in the Apache web-server's "access_log" file as a result of the connection attempt are as follows: 198.73.216.78 - - [05/Dec/2006:10:56:18 -0500] "GET /cgi-bin/fglccgi/ja/r/rms-login?Arg=records63&Arg=e HTTP/1.1" 200 222 198.73.216.78 - - [05/Dec/2006:10:56:19 -0500] "GET /cgi-bin/fglccgi/ja/sua/230387047/0/2?Arg=records63&Arg=e HTTP/1.1" 200 78 198.73.216.78 - - [05/Dec/2006:10:56:19 -0500] "POST /cgi-bin/fglccgi/ja/sua/230387047/0/1?Arg=records63&Arg=e HTTP/1.1" 200 78 198.73.216.78 - - [05/Dec/2006:11:01:18 -0500] "POST /cgi-bin/fglccgi/ja/sua/230387047/0/2?Arg=records63&Arg=e HTTP/1.1" 200 78 At the same times, what was recorded in the GAS log (i.e. GAS was started using the "-l" option) is as follows: 2006/12/05 10:56:18 gasd info Process created with parameters : pid='1801', program='/usr1/fgl2p-1.31.2d.rt/bin/fglrun rms_login.42r records63 e' 2006/12/05 11:01:18 gasd info JavaFE: rms-login - USER_AGENT timeout expired. We are reasonably confident that both the "connector.xcf" file and the "as.xcf" files have been properly configured as we see the application (rms_login.42r) running on the back-end server until the "USER_AGENT timeout expired" message is recorded in the GAS log file. However, no connection between the application and the GDC is established. Of concern are the GET and POST entries in the Apache log that show the "/cgi-bin/fglccgi/ja/." values. It would appear to us neophytes that the program is being launched for interaction with a Genero Java client (GJC) instead of the GDC. Given that it is the GDC that is attempting to invoke the application, we would have anticipated something more akin to "/cgi-bin/fglccgi/wa/..." to be found in the Apache logs. Are the Apache web-server log entries indicative of a problem with the GDC/Apache/GAS combination or, as is more likely the case, are we missing something else? ===> Issue #2 The second issue we are encountering appears to be a timeout issue when a "frontcall" to the GDC is issued from a back-end process when that back-end process has been spawned via GAS. Unlike above, in this case we've configured the GDC for a HTTP type connection directly to GAS. When so configured, the back-end process is launched and the connection between it and the GDC (via GAS) is successfully established. But we then issue a "frontcall" to a function built into a custom DLL. That custom DLL's function then issues a user-dialog that will wait on user-input for an indefinite length of time. If this DLL issued user-dialog is actioned within about 10 seconds or less of having been displayed (i.e. the user performs the requested action, control is returned to the GDC and the GDC passes the results back to the back-end process) everything works as expected. If, however, the user dilly-dallies and doesn't action the user-dialog within 10 or so seconds, it appears that the connection between the GDC and the back-end is lost with GDC-rendered window for the back-end application disappearing and, in the event GDC logging was enabled, we see the following message written to the GDC log: 1:COMMENT:19087:end of connection The back-end process that was up until that point connected to the GDC via GAS remains running for another 5 minutes (exactly - presumably a USER_AGENT timeout) until it terminates with the following message being logged in its application error log: Date: 12/04/2006 Time: 11:49:19 Program error at 'vtm_ds_proc.4gl', line number 1685. FORMS statement error number -6327. Internal error in the run time library file Interface.c(365): *ev. After some digging, we can across the DVM_AVAILABLE parameter in the GAS configuration file (e.g. "as.xcf") but manipulating its value, from 10 to 60 for example, and restarting the GAS daemon had no affect. Is there another timer that we need to be aware of in this case? Is this timeout expected behavior or is this a known problem with GAS to be addressed in a future release? We don't experience this issue if we attempt the same test when the application is invoked via a GDC SSH connection. Of course, the underlying connection mechanisms when GDC GAS connections are used are completely different than when GDC SSH connections are used. Any insight that you may be able to provide into these two issues would be appreciated. Thanks for your time. Steve Underwood, Versaterm Inc. ------=_NextPart_000_0003_01C71890.8CEF9FE0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 10"> <meta name=3DOriginator content=3D"Microsoft Word 10"> <link rel=3DFile-List href=3D"cid:[email protected]"> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"time"/> <o:SmartTagType = namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags" name=3D"date"/> <!--[if gte mso 9]><xml> <o:OfficeDocumentSettings> <o:DoNotRelyOnCSS/> </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:DocumentKind>DocumentEmail</w:DocumentKind> <w:EnvelopeVis/> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--><!--[if !mso]> <style> st1\:*{behavior:url(#default#ieooui) } </style> <![endif]--> <style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0in; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} span.EmailStyle17 {mso-style-type:personal-compose; mso-style-noshow:yes; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-font-family:Arial; color:windowtext;} span.SpellE {mso-style-name:""; mso-spl-e:yes;} span.GramE {mso-style-name:""; mso-gram-e:yes;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 10]> <style> /* Style Definitions */=20 table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";} </style> <![endif]--> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple = style=3D'tab-interval:.5in'> <div class=3DSection1> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Hi:<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>We’ve been trying to use a non-ActiveX Windows = version of the <span class=3DSpellE>Genero</span> Desktop Client (i.e. not GDCAX = but just GDC – version 1.33.1b), to interact with the <span = class=3DSpellE>Genero</span> Application Server (GAS – version 1.32.1c for <span = class=3DSpellE>RedHat</span> Linux) and have encountered a few issues where some clarification would = be appreciated.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>=3D=3D=3D> Issue #1<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>First, when we configure the GDC for a HTTP type = connection through a web-server (as opposed to GAS-direct connection), the = connection fails with an information dialog displaying the message “Invalid application identifier”.<span style=3D'mso-spacerun:yes'> = </span>The entries recorded in the Apache web-server’s “<span = class=3DSpellE>access_log</span>” file as a result of the connection attempt are as = follows:<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>198.73.216.78 - - [</span></font><st1:date = Month=3D"12" Day=3D"5" Year=3D"2006"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>05/Dec/2006</span></font></st1:date><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>:</span></font><st1:time = Hour=3D"10" Minute=3D"56"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>10:56:18</span></font></st1:time><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> -0500] "GET /<span class=3DSpellE>cgi-bin/fglccgi/ja/r/rms-login<span = class=3DGramE>?Arg</span></span>=3Drecords63&Arg=3De HTTP/1.1" 200 222<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>198.73.216.78 - - [</span></font><st1:date = Month=3D"12" Day=3D"5" Year=3D"2006"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>05/Dec/2006</span></font></st1:date><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>:</span></font><st1:time = Hour=3D"10" Minute=3D"56"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>10:56:19</span></font></st1:time><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> -0500] "GET /cgi-bin/fglccgi/ja/sua/230387047/0/2<span = class=3DGramE>?Arg</span>=3Drecords63&Arg=3De HTTP/1.1" 200 78<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>198.73.216.78 - - [</span></font><st1:date = Month=3D"12" Day=3D"5" Year=3D"2006"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>05/Dec/2006</span></font></st1:date><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>:</span></font><st1:time = Hour=3D"10" Minute=3D"56"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>10:56:19</span></font></st1:time><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> -0500] "POST /cgi-bin/fglccgi/ja/sua/230387047/0/1<span = class=3DGramE>?Arg</span>=3Drecords63&Arg=3De HTTP/1.1" 200 78<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>198.73.216.78 - - [</span></font><st1:date = Month=3D"12" Day=3D"5" Year=3D"2006"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>05/Dec/2006</span></font></st1:date><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>:</span></font><st1:time = Hour=3D"11" Minute=3D"1"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family: Arial'>11:01:18</span></font></st1:time><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'> -0500] "POST /cgi-bin/fglccgi/ja/sua/230387047/0/2<span = class=3DGramE>?Arg</span>=3Drecords63&Arg=3De HTTP/1.1" 200 78<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>At the same times, what was recorded in the GAS log = (i.e. GAS was started using the “-l” option) is as = follows:<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>2006/12/05 </span></font><st1:time Hour=3D"10" = Minute=3D"56"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'>10:56:18</span></font></st1:= time><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'> <span class=3DSpellE>gasd</span> info Process created with <span = class=3DGramE>parameters :</span> <span class=3DSpellE>pid</span>=3D'1801', program=3D'/usr1/fgl2p-1.31.2d.rt/bin/fglrun rms_login.42r records63 = e'<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>2006/12/05 </span></font><st1:time Hour=3D"11" = Minute=3D"1"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'>11:01:18</span></font></st1:= time><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'> <span class=3DSpellE>gasd</span> info <span class=3DSpellE>JavaFE</span>: = <span class=3DSpellE>rms</span>-login - USER_AGENT timeout = expired.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>We are reasonably confident that both the = “<span class=3DSpellE>connector.xcf</span>” file and the “<span class=3DSpellE>as.xcf</span>” files have been properly configured = as we see the application (rms_login.42r) running on the back-end server until the “USER_AGENT timeout expired” message is recorded in the GAS = log file.<span style=3D'mso-spacerun:yes'> </span>However, no = connection between the application and the GDC is established.<span style=3D'mso-spacerun:yes'> </span>Of concern are the GET and POST = entries in the Apache log that show the “/<span = class=3DSpellE>cgi-bin/fglccgi/ja</span>/…” values.<span style=3D'mso-spacerun:yes'> </span>It would appear to = us neophytes that the program is being launched for interaction with a = <span class=3DSpellE>Genero</span> Java client (GJC) instead of the GDC.<span style=3D'mso-spacerun:yes'> </span>Given that it is the GDC = that is attempting to invoke the application, we would have anticipated = something more akin to “/<span = class=3DSpellE>cgi-bin/fglccgi/wa</span>/...” to be found in the Apache logs.<span style=3D'mso-spacerun:yes'> = </span>Are the Apache web-server log entries indicative of a problem with the = GDC/Apache/GAS combination or, as is more likely the case, are we missing something = else? <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>=3D=3D=3D> Issue #2<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>The second issue we are encountering appears to be a = timeout issue when a “<span class=3DSpellE>frontcall</span>” to the = GDC is issued from a back-end process when that back-end process has been = spawned via GAS.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Unlike above, in this case we’ve configured the = GDC for a HTTP type connection directly to GAS.<span style=3D'mso-spacerun:yes'> </span>When so configured, the = back-end process is launched and the connection between it and the GDC (via GAS) is = successfully established.<span style=3D'mso-spacerun:yes'> </span>But we then = issue a “<span class=3DSpellE>frontcall</span>” to a function built = into a custom DLL.<span style=3D'mso-spacerun:yes'> </span>That custom = DLL’s function then issues a user-dialog that will wait on user-input for an indefinite length of time.<span style=3D'mso-spacerun:yes'> = </span>If this DLL issued user-dialog is <span class=3DSpellE>actioned</span> within = about 10 seconds or less of having been displayed (i.e. the user performs the = requested action, control is returned to the GDC and the GDC passes the results = back to the back-end process) everything works as = expected.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>If, however, the user dilly-dallies and doesn’t = action the user-dialog within 10 or so seconds, it appears that the connection = between the GDC and the back-end is lost with GDC-rendered window for the = back-end <span class=3DGramE>application disappearing</span> and, in the event GDC = logging was enabled, we see the following message written to the GDC = log:<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>1<span class=3DGramE>:COMMENT:19087:end</span> of = connection<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>The back-end process that was up until that point = connected to the GDC via GAS remains running for another 5 minutes (exactly = – presumably a USER_AGENT timeout) until it terminates with the following message = being logged in its application error log:<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Date: </span></font><st1:date Month=3D"12" Day=3D"4" = Year=3D"2006"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'>12/04/2006</span></font></st= 1:date><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'><span style=3D'mso-spacerun:yes'> </span>Time: = </span></font><st1:time Hour=3D"11" Minute=3D"49"><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>11:49:19</span></font></st1:time><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p= > <p class=3DMsoNormal><span class=3DGramE><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>Program error at = 'vtm_ds_proc.4gl', line number 1685.</span></font></span><font size=3D2 face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p= > <p class=3DMsoNormal><span class=3DGramE><font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'>FORMS statement error = number -6327.</span></font></span><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p= > <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Internal error in the run time library file <span class=3DSpellE><span class=3DGramE>Interface.c</span></span><span = class=3DGramE>(</span>365):<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>*<span class=3DSpellE><span = class=3DGramE>ev</span></span>.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>After some digging, we can across the DVM_AVAILABLE parameter in the GAS configuration file (e.g. “<span = class=3DSpellE>as.xcf</span>”) but manipulating its value, from 10 to 60 for example, and restarting = the GAS daemon had no affect.<span style=3D'mso-spacerun:yes'> </span>Is = there another timer that we need to be aware of in this case?<span style=3D'mso-spacerun:yes'> </span>Is this timeout expected = behavior or is this a known problem with GAS to be addressed in a future release?<span style=3D'mso-spacerun:yes'> </span>We don’t experience this = issue if we attempt the same test when the application is invoked via a GDC SSH connection.<span style=3D'mso-spacerun:yes'> </span>Of course, the underlying connection mechanisms when GDC GAS connections are used are completely different than when GDC SSH connections are = used.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Any insight that you may be able to provide into = these two issues would be appreciated.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Thanks for your time.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Steve Underwood,<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Versaterm Inc.</span></font> <font size=3D2 = face=3DArial><span style=3D'font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p= > </div> </body> </html> ------=_NextPart_000_0003_01C71890.8CEF9FE0--