Symfony-IT » webdev http://www.symfony.it Just another Symfony Framework weblog Mon, 30 Jan 2012 13:53:22 +0000 en hourly 1 http://wordpress.org/?v=3.3.1
eAccelerator e routing dei metodi http://www.symfony.it/articoli/17/eaccelerator-e-routing-dei-metodi/ http://www.symfony.it/articoli/17/eaccelerator-e-routing-dei-metodi/#comments Tue, 04 Sep 2007 10:19:19 +0000 fullo http://www.symfony.it/articoli/17/eaccelerator-e-routing-dei-metodi/ forward('default', 'module') #1 /usr/share/pear/symfony/action/sfActions.class.php(53): connectActions->executeIndex() #2 /usr/share/pear/symfony/filter/sfExecutionFilter.class.php(115): sfActions->execute() #3 /usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfExecutionFilter->execute(Object(sfFilterChain)) #4 /usr/share/pear/symfony/filter/sfFlashFilter.class.php(50): sfFilterChain->execute() #5 /usr/share/pear/symfony/filter/sfFilterChain.class.php(43): [...]]]> Se utilizzate eAccelerator sul vostro server di produzione e con le ultime due versioni di symfony ottenete strani messaggi di errore relativi al routing dei metodi simili a 

Fatal error:
Uncaught exception 'sfStopException' in /usr/share/pear/symfony/action/sfAction.class.php:136 Stack trace:
#0 /var/www/html/progetto/apps/applicazione/modules/modulo/actions\actions.class.php(19): sfAction->forward('default', 'module')
#1 /usr/share/pear/symfony/action/sfActions.class.php(53): connectActions->executeIndex()
#2 /usr/share/pear/symfony/filter/sfExecutionFilter.class.php(115): sfActions->execute()
#3 /usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfExecutionFilter->execute(Object(sfFilterChain))
#4 /usr/share/pear/symfony/filter/sfFlashFilter.class.php(50): sfFilterChain->execute()
#5 /usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfFlashFilter->execute(Object(sfFilterChain))
#6 /usr/share/pear/symfony/filter/sfCommonFilter.class.php(29): sfFilterChain->execute()
#7 /usr/share/pear/symfony/filter/sfFilterChain.class.php(43): sfCommonFilter->execute(Object(sfFilterChain))
#8 /usr/share/pear/symfony/filter/sfWebDeb in  /usr/share/pear/symfony/action/sfAction.class.php on line 136

significa che siete incappati in questo scomodo bug.

La soluzione è molto semplice, basta infatti disabilitare il modulo eAccellerator per php o alternativamente limitarsi a bloccarne l’ottimizzazione modificando nel php.ini la direttiva eaccelerator.optimizer = "0" finchè non sarà rilasciata la nuova versione dell’optimizer.

via sfForum

]]> http://www.symfony.it/articoli/17/eaccelerator-e-routing-dei-metodi/feed/ 0