From: <php...@li...> - 2006-05-31 18:22:34
|
Hi, > some 'real' work with it today. My first move was to > move the php classes > I've used so far into separate files - which didn't > work :| not sure what you mean with this, but if you want to split your files so that each php file exports one php class, this should work. > Fatal error: php_mod_java(88): Protocol violation at > pos 7, please check that > That goes for basically all java_ commands (e.g. > java_context() instead of > java_session()). Thank you very much for the bug report. Which version of the PHP/Java Bridge do you use? Version 3.1.0devel or the official 3.0.8? > Any idea how to solve that? This usually means that the php has received an HTML error message from tomcat instead of the expected XML from the back-end. Or it has received the HTML meta-information but didn't expect them, for example when the php.ini option "java.servlet" is not set but the bridge is actually using a servlet back-end. I think the bridge could somehow catch such an incorrect configuration (java.servlet not set while connected to a servlet or vice versa), but it is difficult to detect because our XML looks similar to the HTML header from the servlet back-end. Pos#7 could mean that a HTML error page was received (<HTML> instead of <Object ...> or <Exception ...>. > To give some further information: I'm running the > bridge inside tomcat on > ubuntu linux with php compiled as fastcgi. Bride Could you please open a ticket (please use http://sourceforge.net/tracker/?func=add&group_id=117793&atid=679233) and generate an append the error.log as at the end of the ticket? You can find the tomcat error message at the end of the error.log: strace -s1024 php test.php 2>error.log Regards, Jost Boekemeier ___________________________________________________________ Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de |