Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exception during tcpConnection.write() and connection pool. #75

Open
pinver opened this issue Jan 31, 2018 · 1 comment
Open

exception during tcpConnection.write() and connection pool. #75

pinver opened this issue Jan 31, 2018 · 1 comment

Comments

@pinver
Copy link
Contributor

pinver commented Jan 31, 2018

This is a following of #71.

Unfortunately I'm still having exceptions during the write, as PostgreSQL is disconnecting after some inactivity time:

object.Exception@../../../../root/.dub/packages/vibe-core-1.3.0/vibe-core/source/vibe/core/net.d(639): Error writing data to socket.
[main(eDjH) ERR] ----------------
[main(eDjH) ERR] ??:? [0x7e7c0e]
[main(eDjH) ERR] ??:? [0x7d9922]
[main(eDjH) ERR] net.d:639 [0x761753]
[main(eDjH) ERR] net.d:647 [0x76185a]
[main(eDjH) ERR] postgres.d:2367 [0x5fb5a4]
[main(eDjH) ERR] postgres.d:237 [0x5fb4fe]
[main(eDjH) ERR] postgres.d:250 [0x5fb640]
[main(eDjH) ERR] postgres.d:1102 [0x5fdabf]
[main(eDjH) ERR] postgres.d:1315 [0x600c0b]
[main(eDjH) ERR] postgres.d:2123 [0x605317]
[main(eDjH) ERR] postgres.d:2167 [0x5c8169]
[main(eDjH) ERR] postgres.d:1795 [0x5c7480]

If the exception is not trapped, the connection become unusable, but there's no way to remove it from the pool, as #71.

As a last resort, I would like to add a try / catch for exception around the write in line 2367: @jacob-carlborg, suggestions?

I've posted the issue in the vibe forum, but right now there's no reply.

@jacob-carlborg
Copy link
Collaborator

As a last resort, I would like to add a try / catch for exception around the write in line 2367: jacob-carlborg, suggestions?

Currently I have no suggestions. I'm also wondering why the connected check doesn't work. Have you looked at the source code for the connected, could there be a bug in vibe.d? Have you tried if a try-catch works?

I've posted the issue in the vibe forum, but right now there's no reply.

I would like to get a reply there before taking any decisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants