[SERVER-6100] C + + driver error or mongodb error Created: 15/Jun/12  Updated: 08/Mar/13  Resolved: 08/Jan/13

Status: Closed
Project: Core Server
Component/s: Internal Client
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: jackliu Assignee: Unassigned
Resolution: Done Votes: 0
Labels: C++
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

SUSE 10.0 SP2 64bit


Operating System: Linux
Participants:

 Description   

Prompt the following error when I have a large number of users access the server, C + + driver

Fri Jun 15 18:03:52 recv(): message len 1489639793 is too large1489639793
Fri Jun 15 18:03:52 DBClientCursor::init call() failed

Fri Jun 15 18:05:12 recv(): message len 1489643966 is too large1489643966
Fri Jun 15 18:05:12 DBClientCursor::init call() failed
Fri Jun 15 18:05:12 ERROR: MessagingPort::call() wrong id got:1 expect:a2c
toSend op: 2004
response msgid:2604
response len: 67356
response op: 8
remote: 192.168.1.13:27017
Fri Jun 15 18:05:12 Assertion failure false mongo/util/net/message_port.cpp 245
0x5b0c84 0x5a65bc 0x5b3ec2 0x5b4504 0x544d94 0x56c1af 0x550e0d 0x5584d1 0x551174 0x494524 0x494b20 0x447060 0x4c9a1a 0x4cc8d9 0x4ccd5e 0x4cce0e 0x4cce4e 0x4cce6c 0x5dc784 0x2b04a37aa143
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x5b0c84]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x5a65bc]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x5b3ec2]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x5b4504]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x544d94]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x56c1af]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x550e0d]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x5584d1]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x551174]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x494524]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x494b20]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x447060]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x4c9a1a]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x4cc8d9]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x4ccd5e]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x4cce0e]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x4cce4e]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x4cce6c]
/home/koangel/sportmeeting/GameServer/dist/Debug/GNU-Linux-x86/gameserver [0x5dc784]
/lib64/libpthread.so.0 [0x2b04a37aa143]

How do I solve it?



 Comments   
Comment by Gary Murakami [ 21/Dec/12 ]

Jack:
Can you answer Eliot's surmise - is your client app multi-threaded and using a single DBClientConnection?

Comment by Eliot Horowitz (Inactive) [ 15/Jun/12 ]

Your probably not using the driver in a thread safe way.
A single DBClientConnection is not thread safe.
You should use ScopedDbConnection

Comment by jackliu [ 15/Jun/12 ]

my email : jackliu100@gmail.com

Generated at Thu Feb 08 03:10:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.