I’m getting this error in my Prisma 1.19 server lo...
# orm-helpf
Fran Dios
10/26/2018, 5:27 AMI’m getting this error in my Prisma 1.19 server log:
[SubscriptionSessionActor] Received unknown message: com.prisma.subscriptions.protocol.SubscriptionProtocolV07$Requests$GqlConnectionTerminate$@7313ce90n
nilan
10/26/2018, 8:18 AMwhat messages are you sending via WS?
f
Fran Dios
10/26/2018, 9:17 AMThe only WS I use is Prisma subscriptions for some entities. However, I wasn’t even using the service when I got 4 of these errors during 1 hour. Weird 🤷♂️
n
nilan
10/26/2018, 9:20 AMWhat is "Prisma subscriptions"?
n
nilan
10/26/2018, 9:37 AMWell, yea 🙂
nilan
10/26/2018, 9:37 AMWhat subscription client do you use?
f
Fran Dios
10/26/2018, 9:39 AMI’m using apollo-server v2 and graphql-subscriptions package. A typical resolver looks like this:
Copy code
packageCreated: {
subscribe: (parent, args, { db }, info) =>
db.subscription.package(
{
where: {
mutation_in: [CREATED],
},
},
info
),
},Fran Dios
10/26/2018, 9:39 AM(with prisma-binding)
n
nilan
10/26/2018, 9:40 AMok. for context:
1) my first guess when seeing your original error message is that you are using a subscription client that sends an unexpected message.
2) my second guess for this is that there is a bug in Prisma - however I'd like to investigate this possibility only once we erradicated possibility 1).
nilan
10/26/2018, 9:40 AMthe situation becomes difficult to inspect due to the three layers - client, server (the code you shared), Prisma.
Can you try to reproduce the error by making subscriptions against Prisma directly, without a server?
f
Fran Dios
10/26/2018, 9:43 AMI see, I’ll try to do it during the weekend. In any case, it’s the first time I see that error and looks like it doesn’t show again 🤔
Thanks for the answers!
🙌 1
n
nilan
10/26/2018, 9:44 AMI also never saw this error before! Might be a one-off weirdness 🙂