Hello to @ll. I'm not sure if this is the correct list to post this question, but maybe i'm dealing with a bug.
I have develop an event logging mechanism where application processes connect to event loggers (using MPI_Lookup, MPI_open_port, MPI_Comm_Connect, MPI_Comm_Accept, etc) that are part of another MPI application. Well, i have develop my own vprotocol where once a process receive a message try to establish a connection with an event logger which is a thread that belongs to another mpi application. The event logger application consists in one mpi process per node with multiple threads waiting for connections of MPI processes from the main application. I'm suspecting that there is a problem with the critical regions when processes try to connect with the threads of the event logger. I'm attaching two short examples that i have written in order to show the problem. First, i launch the event-logger application: If i use mutex in order to serialized the access to MPI_Comm_Accept,
