[hunchentoot-devel] Recursive lock when logging
Hi, On svn-latest Hunchentoot I get this error when running on Allegro CL: #1=#<MULTIPROCESSING:PROCESS Hunchentoot worker (client: 192.168.0.136:48688)(10) @ #x72086c32> seizing #<MULTIPROCESSING:PROCESS-LOCK global-message-log-lock locked by #1# @ #x71e1393a> recursively [Condition of type SIMPLE-ERROR] Following knobs have been turned: (setq *log-lisp-errors-p* t) (setq *log-lisp-warnings-p* t) (setq *message-log-pathname* "log/message.log") (setq *access-log-pathname* "log/access.log") Thanks, /S
Slawek, I think that noone currently supports or tests Hunchentoot on Allegro CL. Its primary platforms are Lispworks, SBCL and Clozure CL. There are ports to other free CL implementations (ECL, CLISP), but I don't know how well they work. If you are looking for a CL web server and want to use Allegro CL, consider using Allegroserve. It is included with Allegro CL and fully supported by Franz Inc. If you still want to use Hunchentoot, you'll have to do some debugging work yourself. The locking problem that you described should be relatively simple to solve (but looking at the stack backtrace would be illuminating, use :zoom to see the backtrace). The segmentation fault that you've seen will be harder to debug. One you got it running, please send patches after having read http://weitz.de/patches.html Cheers, Hans
I used to use it on Allegro; I don't think it should be too hard to get going. As to the segfaults, Allegro does that from time to time but it almost always turns out to be the result of some fairly stupid error involving passing an object of the wrong type into some thing that somehow dodges the normal type checks. (I realize that's pretty vague but I've had segfaults and then eventually realized I was doing something stupid and they went away.) You should certainly be able to bug Franz support about the segfault. My guess, in this case, is it has something to do with the streams, what SLIME is doing vs. what Allegro is expecting. -Peter On Sun, Nov 22, 2009 at 12:32 PM, Hans Hübner <hans.huebner@gmail.com> wrote:
Slawek,
I think that noone currently supports or tests Hunchentoot on Allegro CL. Its primary platforms are Lispworks, SBCL and Clozure CL. There are ports to other free CL implementations (ECL, CLISP), but I don't know how well they work.
If you are looking for a CL web server and want to use Allegro CL, consider using Allegroserve. It is included with Allegro CL and fully supported by Franz Inc.
If you still want to use Hunchentoot, you'll have to do some debugging work yourself. The locking problem that you described should be relatively simple to solve (but looking at the stack backtrace would be illuminating, use :zoom to see the backtrace). The segmentation fault that you've seen will be harder to debug. One you got it running, please send patches after having read http://weitz.de/patches.html
Cheers, Hans
_______________________________________________ tbnl-devel site list tbnl-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/tbnl-devel
-- Peter Seibel http://www.codersatwork.com/ http://www.gigamonkeys.com/blog/
Hey Peter, On Sun, Nov 22, 2009 at 9:41 PM, Peter Seibel <peter@gigamonkeys.com> wrote:
I used to use it on Allegro; I don't think it should be too hard to get going. As to the segfaults, Allegro does that from time to time but it almost always turns out to be the result of some fairly stupid error involving passing an object of the wrong type into some thing that somehow dodges the normal type checks. (I realize that's pretty vague but I've had segfaults and then eventually realized I was doing something stupid and they went away.) You should certainly be able to bug Franz support about the segfault. My guess, in this case, is it has something to do with the streams, what SLIME is doing vs. what Allegro is expecting.
I think you've nailed it. I've been toying for some time w/ stream redirection in swank. After removing the hooks ACL doesn't segfault anymore. Will look into it further. Thanks!. /S
On Sun, Nov 22, 2009 at 9:32 PM, Hans Hübner <hans.huebner@gmail.com> wrote:
Slawek,
I think that noone currently supports or tests Hunchentoot on Allegro CL. Its primary platforms are Lispworks, SBCL and Clozure CL. There are ports to other free CL implementations (ECL, CLISP), but I don't know how well they work.
Yeah, but I use ACL for AllegroCache goodness too, so can't switch my lisp that easily. As a second thought - isn't Lisp beautiful? Noone tests on ACL but for the most part Hunchentoot works just fine on it despite large code base and all the dependencies :)
If you are looking for a CL web server and want to use Allegro CL, consider using Allegroserve. It is included with Allegro CL and fully supported by Franz Inc.
I've been a long-time user of Allegroserve, but still find Hunchentoot code clearer and more compelling.
If you still want to use Hunchentoot, you'll have to do some debugging work yourself. The locking problem that you described should be relatively simple to solve (but looking at the stack backtrace would be illuminating, use :zoom to see the backtrace). The segmentation fault that you've seen will be harder to debug. One you got it running, please send patches after having read http://weitz.de/patches.html
I sure will do that. There is another issue w/ handle-static-file that I've found today. Will tackle it as well. Thanks Hans!, /S
participants (3)
-
Hans Hübner -
Peter Seibel -
Slawek Zak