[SERVER-13895] 17133 SSL Handshake Requested Created: 09/May/14  Updated: 10/Dec/14  Resolved: 12/May/14

Status: Closed
Project: Core Server
Component/s: Stability
Affects Version/s: 2.6.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Edgar Hipp Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

Install mongodb on windows 64bit (with the installer from the website from 5/9/2014).

Use the latest mongodb driver for node.

Write a query inside the nodejs that uses selection, condition, sort and limit, and call toArray.

Participants:

 Description   

I'm using mongodb 2.6.1 on Windows 64bit.

I use the mongodb native node driver.

The connection works, however, with some of the queries, I get the following exception:


C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connection\base.js:245
throw message;
^
Error: failed to connect to [127.0.0.1:27017]
at null.<anonymous> (C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connecti
on\server.js:536:74)
at EventEmitter.emit (events.js:106:17)
at null.<anonymous> (C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connecti
on\connection_pool.js:150:15)
at EventEmitter.emit (events.js:98:17)
at Socket.<anonymous> (C:\wamp\www\poker-tell\server\node_modules\mongodb\lib\mongodb\connec
tion\connection.js:516:10)
at Socket.EventEmitter.emit (events.js:95:17)
at onwriteError (_stream_writable.js:233:10)
at onwrite (_stream_writable.js:251:5)
at WritableState.onwrite (_stream_writable.js:97:5)
at fireErrorCallbacks (net.js:438:13)
npm ERR! weird error 8
npm ERR! not ok code 0

When I look into the mongod.exe output, I have the following:


2014-05-09T21:29:07.315+0200 [conn10] AssertionException handling request, closing client connec
tion: 17133 SSL handshake requested, SSL feature not available in this build

I'm not initializing a ssl connection in node.



 Comments   
Comment by Edgar Hipp [ 09/May/14 ]

Somehow I found out that the problem was something completely unrelated to SSL. I used a syntax for selections that apparently did work before but now doesn't, eg I wrote:

selection=

{'name',id'}

but you should write:

selection=

{'name':true,id':true}
Generated at Thu Feb 08 03:33:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.