[SERVER-13734] Remove catch (...) from handleIncomingMsg Created: 25/Apr/14  Updated: 11/Jul/16  Resolved: 16/Jun/14

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: 2.6.4, 2.7.0

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

Issue Links:
Depends
Related
related to SERVER-14257 "remove" command can cause process te... Closed
Tested
Operating System: ALL
Backport Completed:
Participants:
Linked BF Score: 0

 Description   

This will help us get stack dumps on all unhandled exceptions on Windows,
not just those, which occur on non-query threads.

Original description:

jsCore/where4.js fails occasionally on Windows, when run with small oplog.

The cause of the failure is emergency server shutdown due to unhandled exception, which is neither of assertion, MongoDB exception or STL exception.

Steps to Reproduce: Happens randomly, no specific steps to reproduce other than running the jsCore suite with small oplog.



 Comments   
Comment by Githook User [ 17/Jul/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-13734 Remove catch (...) from handleIncomingMsg

This will help us get stack dumps on all unhandled exceptions on Windows,
not just those, which occur on non-query threads.
(cherry picked from commit ece2f2e2b997eb5c21328966ce2ccff9bdfe4db2)
Branch: v2.6
https://github.com/mongodb/mongo/commit/e764b354c2e4a9cfbb3c7d27116b45014fee0592

Comment by J Rassi [ 16/Jun/14 ]

Updating title / description to focus on catch (...) block, so it can be reviewed for backport. Open a new ticket for new commits intending to fix a where4.js failure.

Comment by Kaloian Manassiev [ 30/Apr/14 ]

We have checked-in change, which will help us get stack dumps on all unhandled exceptions. This issue has not been seen on the recent runs, so I am resolving the ticket until it gets hit again, when we should have more diagnostic information.

Comment by Githook User [ 25/Apr/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-13734 Remove catch (...) from handleIncomingMsg

This will help us get stack dumps on all unhandled exceptions on Windows,
not just those, which occur on non-query threads.
Branch: master
https://github.com/mongodb/mongo/commit/ece2f2e2b997eb5c21328966ce2ccff9bdfe4db2

Comment by Kaloian Manassiev [ 25/Apr/14 ]

First step is to remove the catch (...) block from handleIncomingMsg, so we can get stack dumps. Code review pending.

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