downloads | documentation | faq | getting help | mailing lists | licenses | wiki | reporting bugs | php.net sites | links | conferences | my php.net

search for in the

MongoConnectionException> <MongoException
Last updated: Fri, 13 Nov 2009

view this page in

The MongoCursorException class

Introduction

Caused by accessing a cursor incorrectly or a error receiving a reply.

If there is an error receiving a reply, there will be a more specific error message to help diagnose the problem:

  • could not establish db connection

    A database reply could not be recieved because a connection with the database could not be established.

  • no db response

    This may not even be an error, for example, the database command "shutdown" returns no response. However, if you were expecting a response, this means the database didn't give one.

  • bad response length: %d, max: %d, did the db assert?

    This means that the database said that its response was greater than 4Mb or less than 0. Generally, a number greater than 5Mb should be reported to the developers as a potential database bug (max response length is 4Mb). A response of less than 0 often means a database assertion occured.

  • incomplete response

    Occurs if the database response is malformed.

  • [WSA ]error getting database response: errstr

    "errstr" is an io error reported directly from the C socket subsystem. On Windows, is prefixed with "WSA".

Class synopsis

MongoCursorException
extends MongoException {
}


add a note add a note User Contributed Notes
MongoCursorException
There are no user contributed notes for this page.

MongoConnectionException> <MongoException
Last updated: Fri, 13 Nov 2009
 
 
show source | credits | stats | sitemap | contact | advertising | mirror sites