A couple of times in testing, we have experienced the busy.jsp.

Can someone explain or point me to some resource on the web that will help
me understand the "busy" jsp - when it comes up, and mainly, how to prevent
it...

Thanks,
Mike

[ Post a follow-up to this message ]

Michael,

I believe a busy condition occurs if-and-only-if the transformation, whether
it is default of customized, is submitted twice.
When I say 'twice' I mean,

1) You click a button or press the enter key
2) The host is busy processing the request
3) You click the button or press the enter key again

Result: You get a busy response from the HATS runtime

If you are using an HTML input tag to pass keys to the host, whether it is
type=image or type=button or type=submit watch out for the following!!!!

<input type='button' name='[enter]' class='HostButton' accesskey="HATSFo
rm"
value='ENTER ' onclick="ms('[enter]','HATSForm')" />



If you click the above button, it MAY issue the web page to host TWICE. Try
ms('[enter]','HATSForm');return false;
inside the onclick event instead. I.E. the HATS form MAY get submitted after
onclick is issued via javascript.

Note: the same thing may or may not apply to macro buttons


Hope this helps,

Greg Peters
Beaver Creek Web Solutions, Inc.


"Michael Connors" <connomi@dwd.state.wi.us> wrote in message
news:crjtvt$7c08$1@news.boulder.ibm.com...
>
> A couple of times in testing, we have experienced the busy.jsp.
>
> Can someone explain or point me to some resource on the web that will help
> me understand the "busy" jsp - when it comes up, and mainly, how to
> prevent
> it...
>
> Thanks,
> Mike
>
>

[ Post a follow-up to this message ]