Also, I just wanted to show here the error message in LW when I browse to "http://localhost:8080/weblocks-demo"; in case it reveals something. The message says:
Error in process "WITH-TIMEOUT" The variable HUNCHENTOOT:*SESSION* is unbound. On Jul 8, 12:16 am, Harrison Maseko <[email protected]> wrote: > > Could you try setting the *request-timeout* to some large > > number, say 30 seconds, and waiting? > > I am a little lost here. Could you kindly specify where *request- > timeout* is? > > On Jul 6, 11:09 pm, "Leslie P. Polzer" <[email protected]> > wrote:> Harrison Maseko wrote: > > > I was trying to say that I've already asked a similar question and > > > haven't yet received an answer. I posted a similar question about > > > Weblocks timeout the previous day with the whole error message as it > > > appears in my browser. I have just re-posted it for your reference. > > > Ah, that one. I thought it was resolved. > > > Another user had a problem with ridiculously long request times > > on Windows due to ASDF, and we haven't put in the fix for that > > yet: > > >http://groups.google.com/group/weblocks/browse_thread/thread/b4851e36... > > > Could you try setting the *request-timeout* to some large > > > number, say 30 seconds, and waiting? > > If the request completes normally with that (results show up > > in the browser, tracing HANDLE-CLIENT-REQUEST shows it to > > return) we can solve your problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
