Call a mongoose model inside the socket.on method?

Question

Question, I'm just wondering if I can call a mongoose schema inside the socket.on function? Like

socket.on('sendMessage', ({ senderId, receiverId, message }) => {
    const user = getUser(receiverId);
  const accountId = await accountModel.findById(senderId);
    if (user) {
      socket.to(user.socketId).emit('getMessage', {
        accountId,
        message,
      });
    }
  });

Thanks!

score 0 · Answer 1 · answered Oct 06 '21 at 14:39

0

You probably can have it, just make sure the .on callback receives an async function on it. Something like:

socket.on('sendMessage', async ({ senderId, receiverId, message }) => {
    const user = getUser(receiverId);
    const accountId = await accountModel.findById(senderId);
    if (user) {
      socket.to(user.socketId).emit('getMessage', {
        accountId,
        message,
      });
    }
  });

answered Oct 06 '21 at 14:39

Luiz Fernando da Silva

1,409
14
21

I tried that one but I'm having buffering issue – rSeeker Oct 06 '21 at 14:52
what buffering issue? – Luiz Fernando da Silva Oct 06 '21 at 14:59
Operation `accountmodels.findOne()` buffering timed out after 10000 – rSeeker Oct 06 '21 at 15:41
does this query works outside the socket.io method? Does the db connection working properlu? – Luiz Fernando da Silva Oct 06 '21 at 15:48
Yeah, i'm using it in my api when fetching a account by id – rSeeker Oct 06 '21 at 15:50
I'm using two connection in the backend. First is the connection on my db to mongodb then this socket io – rSeeker Oct 06 '21 at 15:53
I had a similiar issue and the solution was to check if the database connection is really working properly. Maybe you can check this issue here and check other alternatives: https://stackoverflow.com/questions/65408618/mongooseerror-operation-users-findone-buffering-timed-out-after-10000ms – Luiz Fernando da Silva Oct 06 '21 at 15:58
Thanks for the help i saw this thread. my db connection is working file in my api folder. i'm using different port on socket.io folder. – rSeeker Oct 06 '21 at 16:07
Sure, but the point is I don't think it is a socket.io issue itself, but some kind of network issue. You can, for example, test with raw tcp socket (as the synthax is similar) and check if the issue persists (to actually make sure is a network issue). – Luiz Fernando da Silva Oct 06 '21 at 17:19

Call a mongoose model inside the socket.on method?

1 Answers1