RE: [xep-support] XEP Engines & Enamsse...

Hi David,

I issue the following command when I run engine

./engine
./engine -port 6571

Which should instantiate two engines - one on 6570 and the other on 6571.
Sadly for me, when the second attempt is made to instantiate a second
engine, it throws a java.net.BindException: Address already in use

So that would mean the port parameter I pass with the second command is
ignored and another attempt to instantiate a second engine on 6570 fails.

Is this how you ran two engines David?

Thanks...
Arup

-----Original Message-----
From: owner-xep-support@renderx.com [mailto:owner-xep-support@renderx.com]
On Behalf Of David Tolpin
Sent: 11 July 2005 17:57
To: xep-support@renderx.com
Subject: Re: [xep-support] XEP Engines & Enamsse...

> so far I have tried ./engine -port 6571 as well as actually modifying
> the following line inside 'engine' to include the extra port
> parameter.
> java -Dcom.renderx.xep.CONFIG=$XEP_HOME/xep.xml
> com.renderx.xepx.cliser.Engine -port 6571 $CLARGS
>

Yes, I've just done it, and it works exactly as advertised. It starts on
port 6571. On the other hand, an engine is multithreaded, so you can just
mention the same engine several times in EnMasse's configuration file.

The best results are when you run engines on separate machines, then the
throughput is scaled.

David
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address you are
subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/terms-of-service.html

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Tue Jul 12 02:54:56 2005