|
|
| Author |
Message |
< Advanced Erlang/OTP ~ Trapping exits in the yaws callback process? |
| anderst |
 Posted: Thu Sep 13, 2007 12:28 pm |
 |
|
|
User
Joined: 21 Nov 2006
Posts: 37
|
Hi,
what happens is one traps exits in the yaws callback process and the process it is linked to terminates? I am seeing strange behaviours in a live installation with message queues getting longer, and believe this might be the cause. Removing the trapexits (No pun intended  ) causes the process to crash, but ensures the error does not manifest itsself. Whatconfuses me is that there are many exit messages,as ifyaws was reusing the process. Has anyone ever debugged a similar problem?
Hilsen,
Anders |
|
|
| Back to top |
  
|
| francesco |
| Posted: Mon Sep 17, 2007 6:33 am |
|
|
|
User
Joined: 07 Jul 2006
Posts: 249
Location: London
|
Hi Anders,
I thought you were ejabberd:ing.. Why have you gone over to using YAWS?
In answer to your question, we came across a similar error a few weeks ago. We had connected the expat driver to parse some XML gunk and were trapping exits. The driver, upon exiting sent an exit signal. As the http client was using an http 1.1 connection, the process was handling all requests coming in from that port, queuing up the http requests. You do not mention if you are connecting to yaws using http 1.0 or 1.1. If it is the latter, this might be the behaviour you are seeing. Also follow http://forum.trapexit.org/mailinglists/viewtopic.php?t=9609
Hope this helps,
Francesco
--
http://www.erlang-consulting.com |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
