[hunchentoot-devel] hunchentoot-1.2.2 throw a Recursive lock attempt error in sbcl 1.0.55

Jingtao Xu jingtaozf at gmail.com
Sat Mar 3 13:16:09 UTC 2012


Hi Hans,

This is some output of my sbcl 1.0.55 on debian 6.0(i686):
===========================================
error error in FORMAT: unknown format directive (character: Return)
  This sequence can't be decoded ~
using ~A as it is too short.  ~A octet~:P missing at then end.
                                  ^
while processing indirect format string:
  [~A~@[ [~A]~]] ~?~%
                  ^ while writing to error log, error not logged
error error in FORMAT: unknown format directive (character: Return)
  This sequence can't be decoded ~
using ~A as it is too short.  ~A octet~:P missing at then end.
                                  ^
while processing indirect format string:
  [~A~@[ [~A]~]] ~?~%
                  ^ while writing to error log, error not logged
===========================================

With best regards,jingtao.


2012/3/1 Xu Jingtao <jingtaozf at gmail.com>

> Hi Hans,
>
> I have update your patch to my web server(its hunchentoot version is
> 1.1.1).
> If I found some error output,I'll send them to this mail list.
>
> My site use a flexi-stream with cp936 patched (
> https://github.com/jingtaozf/flexi-streams).
> And the site use utf-8 as default encoding but some browser send us cp936
> characters sometimes.
>
> With Best Regards.
> jingtao.
>
> >
> https://github.com/edicl/hunchentoot/commit/f4a3bbd5a915f83c42ff2351978f2e342a478b8a
> > fixes your problem?  If so, you should see a message on the console
> > when logging an error failed.  Please share that message.  My
> > suspicion is that the problem is related to character encoding
> > problems (i.e. Hunchentoot tries to write characters that cannot be
> > encoded in the external format of the error log stream), but at this
> > point, this is just a guess.  The error message will help.
> >
> > Thanks,
> > Hans
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/tbnl-devel/attachments/20120303/48d877d8/attachment.html>


More information about the Tbnl-devel mailing list