[erlang-questions] Mystery exit message in ejabberd_odbc

Dmitry Kolesnikov dmkolesnikov@REDACTED
Fri Aug 22 07:08:16 CEST 2014

If port exit signal is delivered to you process then it is an port owner. Should you be able to trace the place where it is created at given code?

Best Regards,
Dmitry >-|-|-(*>

> On 22.8.2014, at 0.53, Devdutt Sheth <dsheth@REDACTED> wrote:
> I seem to be getting a ton of - {'EXIT',#Port<0.1079543>,normal}
>  ( the pid of course varies) messages in my ejabberd_odbc message queue. 
> I
>  understand that since we have process_flags(trap_exit, true) EXIT signals from linked processes are turned into messages and placed
> In
>  ejabberd_odbc’s message queue. 
> My question is –
> How do we determine what exactly is
> #Port<0.1079543>
>  - doing/executing? 
> I
>  obviously cannot do a port_info on this PID since it has already exited, nor am I able to see when it is spawned. I have tried to print out all the ports in the vm
> via a call to erlang:ports() every second,
>  but I do not see the port that I am receiving the exit message from. This leads me to believe that the port exists for a very brief period ( maybe atomically).
> Any clues on how I can track down the
>  source of this exit message?
> Thanks.
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140822/a9825288/attachment.htm>

More information about the erlang-questions mailing list