On 05/12/2007, Anton anton.list@gmail.com wrote:
On 05/12/2007, Tom Holmes Jr. tom@tomholmes.net wrote:
As I think I clearly stated ... I installed Drupal in two different environments: one where both resin/drupal/mysql are all on my laptop ... and the other environment where resin/drupal and mysql are separate servers. The former works ok, the latter does not ... that makes me think there is something else wrong and it's not resin.
Maybe. If the problem still cropped up on mod_php to a remote MySQL server, then I'd agree Resin has been eliminated as a variable. The reason I'm harping on about eliminating Resin is because it is a VASTLY different environment to everything else. It isn't the fact that the web server is written in Java (that is the minor bit) - it is the fact that PHP itself is reimplemented in Java, and there are huge differences between the way a JVM compiles/optimises/runs something and natively compiled code runs.
There could be a subtle session problem with the php-mysql libraries in Resin when using a remote mysql server - is that not plausible?
Sounds even more plausible now...
After stumbling across Resins bug tracker, it looks like Resin 3.1.4 fixed a bug with connecting to remote mysql servers. eg:
http://bugs.caucho.com/view.php?id=2103 http://bugs.caucho.com/view.php?id=2074
Hopefully an upgrade to Resin 3.1.4 will fix all your problems, and Drupal will instantly become enterprise ready again.
It looks like Caucho use Drupal for their forums (I'm learning stuff all the time). I'd say at least someone in high places has a stake in making Drupal run well on Resin.
As part of Resins maturing process, they seem to be fixing lots of bugs that are found by running Drupal.