Using php-java-bridge v 4.1.1 built from source on a 64-bit SUSE 9 Linux
box. Running PHP 4.3.4, Apache 2.0.52. JRE is 1.4.2_11, from SuSE (which
I'm pretty sure is Sun Java).
Just started using php-java-bridge, and so far have had mostly success,
except for one annoying problem that could be a deal-breaker.
Occassionally, when I load a page that actually uses php-java-bridge on
Firefox, I get a blank page. I can reload, and it comes up fine. When I
get the blank page, I can view source and see all of the source for the page
I requested is there. I don't have this problem on IE6.
First thought is that this is a Firefox problem, what does php-java-bridge
have to do with it? Well, I never saw the problem before, and I can load
pages using php that do not actually use any of the php-java-bridge
functionality, and they NEVER fail. My thought is that the process does not
exit cleanly during some of the clean-up, and that Firefox chooses to not
display the information it has so far whereas IE does. I've heard some
reports of crashes/segfaults during the clean-up process, but always PHP 5,
and we're using PHP 4.
Looked in the logs and found some segfaults in the apache logs, but often I
see the failure behavior without a segfault. The only thing I see happening
regularly when there is a failure are some Samba warnings (have no idea why
this would be using Samba at all-it doesn't access any files off of the
local fs). However, those warnings also occur when it does NOT fail (though
not when I load a page that does not use php-java-bridge), and we have been
seeing those warnings come up in various contexts for years without any
manifest problem.
So, I think the segfault and the samba warnings may be red herrings.
Any ideas?
Michael.
|
