Although I don't post often...mainly because I solve problems on my own...I am a power user. I am posting on this, because a lot of users are stuck, and only Adobe can fix the problem. We are no longer persuing CF10 at our organization, and like others have rolled back. Within my department we have over 250 servers...somewhere around 25 CF servers and over 20 tomcat servers using the jakarta connector. We see millions of page views a day. I have been using the jakarta connector for over 8 years. I am very familiar with how it works, tuning it, and troubleshooting it. Interestingly enough, we also tried to roll out version 1.2.32 of the connector for tomcat a while back(non CF server) and ran into a lot of errors and random crashes. Our solution was to upgrade to 1.2.35 and the connector stopped crashing.
What leads me very directly to the shared memory bug is the shared memory errors in the jakarta log every time to the connector crashes. I can say with confidence that the users on this thread will find this error in there log if they go looking. Below is the error line referring to the shared memory error. SHM=shared memory.
[Mon Mar 11 11:29:54.060 2013] [3960:4388] [error] init_jk::jk_isapi_plugin.c (2779): Initializing shm:(null) errno=-1. Load balancing workers will not function properly.
Oddly enough some articles refer to this being fixed in .31 while others say that it is not. You will notice that one of the posts in the second article refers to it being fixed in 1.2.33. I believe a lot of the discrepencies have to do with whether or not users had multiple application pools configured on their test servers. Due to the nature of what actually causes the crash some servers will see it and some won't. Also if no pages are accessed in other app pools you may not see the problem even if the server is configured exactly the same. I believe this to be the reason for descrepencies in the reporting of what fixes it. Think back to the posts where someone had it crashing every time it was indexed by google. Search engines are likely to cause the crash because they will hit every page on the server.