mongrel2 crashes on multiple handlers

[javierguerragiraldez]

I'm trying to start more than one handler on the same 0MQ port; but as soon as the second one is connected, mongrel2 crashes with

Assertion failed: !engine (session.cpp:288)

session.cpp is a 0MQ file where the assertion seems to protect against attaching two 'engine' objects to the same session. I don't know enough about 0MQ internals to interpret the cause :-(

I don't know if it's related; but in your library, the sender_id is used only on the PULL socket, but reading the Python, Lua, and PHP Mongrel2 libraries, it seems they all use it on the SUB socket. I tried to change your code to do the same; but then it never received Mongrel messages.

[derdewey]

Very interesting. I will look in to it sometime this week. Thanks for the report!

Also: could you possibly attach your code?

[derdewey]

Follow up -- did you start mongrel2_init with threads enabled? mongrel2_init(0) vs mongrel2_init(1).

[javierguerragiraldez]

Hi, i'm using mongrel2_init(1).

I haven't been doing more tests, mostly waiting until the new tnetstring based protocol settles down...