Rails 3.2.19 with Passenger 4.0.57

[Sivakumar G]

We have a rail 3.2.19 application running on ruby 1.9.3 and passenger 3.0.19. We upgraded ruby to 2.1.5 and passenger to 4.0.57 and ran into the following issues post deployment.

1) Some of the update queires generated had 0=0 instead of actual query's where clause

2) Some of the select queries the relation name in the where clause was missing.

We failed to notice RailsAppSpawnerIdleTime that we had set to 0 in Passenger 3.0.19. Looks like it has now been replaced by PassengerMaxPreloaderIdleTime. So I guess it is now using the default value of 300s(5 min). Could this be causing the issue I described?

[Hongli Lai]

I don't think so. Passenger doesn't change database behavior. I can't think of a reason why this issue would be caused by Passenger.

--
You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phusion-passen...@googlegroups.com.
To post to this group, send email to phusion-...@googlegroups.com.
Visit this group at http://groups.google.com/group/phusion-passenger.
To view this discussion on the web visit https://groups.google.com/d/msgid/phusion-passenger/b0eeb151-7ab1-4508-b419-c50108a1c5e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Phusion | Web Application deployment, scaling, and monitoring solutions

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)