Ticket #180 ( Closed )

Short Description Javascript placement/Waiting for pop term message
Entered By: Michael - Charleston When: 1998-10-13 14:58:31 Build: 1.03.19d
Categories Type: Question   Department: Product   Category: DevCenter Compiling
Part I: When I use the <TEMACRO TERMFORM> tag to generate a form the compiler replaces it with *both* the JavaScript for SurferSubmit() and the <Form> tag (w/hidden variables). Is there a way to get the Javascript between the <HEAD> tags where it belongs and not within the <BODY> tag?

Part II: A couple times now we have clicked on the "Recompile templates" link in the DevCenter and gotten the message "waiting for a pop term ..." (repeating down the screen every 30 seconds or so indefinately). The only recourse for escaping this infintite loop was to re-boot the server. Why is this happening and how can it be avoided?


Append By: Michael - Charleston  When: 1998-10-14 09:03:52  New Status: Pending IE
Comment PS - when we looked in the NT Event Log, it stated "WSAECONRESET - the virtual circuit was reset by the remote site executing a 'Hard or Abortive' close for upd sockets. The remote host was unable to deliver a previously sent UDP datagram and responded with a 'Port unreacheable ICMP packet'. The application should close the socket as it is no longer usable." It filled up the application log hundreds of times with this message (over the course of 8 hours) until the server was re-booted.
Append By: WindSurfer  When: 1998-10-14 09:48:58  New Status: Pending Customer
Comment In our experience it is okay to define JavaScript functions outside of the <HEAD> block, as long as these functions aren't called "inline" during the display of the document. Since SurferSubmit will only be called following completion of the document, we generate it at the same time as the TEFORM. We associated the generation of the SurferSubmit with the TEFORM because it is only relevant when a TEFORM is used, and we don't have any way knowing whether-or-not a TEFORM will be used...
Append By: WindSurfer  When: 1998-10-14 09:51:33  New Status: Pending Customer
Comment Sorry that the above append appeared out of synch-- it was authored yesterday, but wasn't posted until after your follow-up regarding item B.

Thanks for the extra information-- this should help in identifying the problem. We are in the process of creating a new build and are using a high-volume test script (hundreds of concurrent sessions) to wring it out, with the compile problem being one of our highest priorities.

Append By: Michael - Charleston  When: 1998-10-14 10:21:00  New Status: Pending IE
Comment I anxiously await as we have two folks actively developing and are re-booting the server about 5 times a day ... BTW, I stated the first message incorrectly - it should have read "waiting for term port stop ..."
Append By: WindSurfer  When: 1998-10-14 10:57:39  New Status: Pending Customer
Comment You don't need to reboot-- just bring-up task manager and whack ielua.exe (terminate process). This is perfectly safe; ielua leaves nothing open and whacking it has never caused us a problem in all of our testing.

Also, please try our latest build at ftp://ftp.ieinc2.com/pub/surfer/t1_3_26d.zip (unzip into \screensurfer\bin to replace ielua.exe when the service is stopped)...unless you are already using this version (ielua timestamp of 10/7/98).