Re: [Php-java-bridge-users] tmp file explosion?

[<php...@li...>]

> r SERVLET:9676

SERVLET does set promiscuous mode. For local communication please use
SERVLET_LOCAL.

However, Java.inc should delete the fifo if the back end doesn't want to use
it, of course.

On Sep 14, 2009 12:00 AM, <php...@li...>
wrote:

Hi Jost-

Glad to report the bug! Sadly I seem to be good at finding them ;)

This is the *only* setup I use for getting the bridge going. If this
either of these settings turns on promiscuous mode, I didn't do it on
purpose.

// PHP side (duh)
define ("JAVA_HOSTS", "127.0.0.1:9676");
define ("JAVA_PREFER_VALUES", true);    # required for BC with the way
we wrote our php-java-bridge code. Could try to debug and fix but no
downside to this.
require_once('/Users/alanpinstein/dev/sandbox/showcase2/showcase2/
classes/dieselpoint/Java.inc');

// bridge side
java -server -Xmx1200m -Dphp.java.bridge.default_log_level=5 -jar /
path/to/JavaBridge.jar SERVLET:9676 2>$LOGFILE 1>$LOGFILE &

I read the docs just now on promiscuous mode and I am not certain I
understand what it does. I sort of see what it's used for, but it's
not really clear exactly what it does, and consequently, what
technically doesn't happen if it's not on.

In fact I have a nice wrapper script for starting/stopping a
standalone bridge (which frankly I think is really convenient for
people that aren't already running an app server). I will post the
script in a separate email if you want to use it in the project.

Alan

On Sep 13, 2009, at 5:45 PM, php-java-bridge-

us...@li... wrote: > Hi, > > Yes, if your back end rejects
the local fifo (in promi...