[postmodern-devel] the reason why i'd like an iolib network backend instead of usocket

[Attila Lendvai]

dear list,

after some uptime, all of a sudden i was getting these errors on our
server. this is probably something going awry inside sb-bsd-sockets.

as time permits, i'll experiment with an iolib based network backend
for cl-postgres.

- attila


*** At: 2008-06-14T03:47:32.266936+02:00
*** In thread: http worker 34 / serving request /
CALL-WITH-SERVER-ERROR-HANDLER / HANDLE-TOPLEVEL-CONDITION
*** Error:
Socket error in \"socket\": EPROTONOSUPPORT (Protocol not supported)
*** Backtrace is:
000: ((LAMBDA (SB-PCL::.PV. SB-PCL::.NEXT-METHOD-CALL. SB-PCL::.ARG0.
SB-PCL::.ARG1.)) #<unavailable argument> #<unavailable argument>
#<ESEHO-PRESENTATION::ESEHO-APPLICATION \"
/\" {911C645}> #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>)
001: ((HU.DWIM.WUI:HANDLE-TOPLEVEL-CONDITION :AROUND (T T))
#<ESEHO-PRESENTATION::ESEHO-APPLICATION \"/\" {911C645}>
#<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>)
002: ((FLET HU.DWIM.WUI::HANDLE-REQUEST-ERROR)
#<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>)
003: ((LAMBDA (ERROR)) #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>)
004: (SIGNAL #<SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR {EBE8041}>)
[:EXTERNAL]
005: (ERROR SB-BSD-SOCKETS:PROTOCOL-NOT-SUPPORTED-ERROR) [:EXTERNAL]
006: (SB-BSD-SOCKETS:SOCKET-ERROR \"socket\")
007: (SB-BSD-SOCKETS:SOCKET-ERROR \"socket\") [:EXTERNAL]
008: ((SHARED-INITIALIZE :AFTER (SB-BSD-SOCKETS:SOCKET T)) #<error
printing object: NIL>) [:EXTERNAL]
009: ((LAMBDA ()))
010: (USOCKET:SOCKET-CONNECT \"database\" 5432) [:EXTERNAL]
011: (CL-POSTGRES::INITIATE-CONNECTION
#<CL-POSTGRES:DATABASE-CONNECTION {107C3F11}>)
012: (CL-POSTGRES:OPEN-DATABASE \"eseho\" \"eseho\" \"szupertitok\"
\"database\" 5432 :NO)
013: ((CL-RDBMS.POSTGRESQL::CONNECTION-OF :AROUND
(CL-RDBMS.POSTGRESQL::POSTGRESQL-POSTMODERN-TRANSACTION))
#<DWIM-META-MODEL::TRANSACTION :begin-executed-p #t {107AB379}>)
0