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

Thanks again. I understand whats happening. Each of these engines runs its
own control server. I thought each servers were registered and if you just
went to http://localhost:6580 you will see all the engines there. Obviously
this is not the case.

Thanks a bunch for that. Now onto Error Handling... :-)

Kind regards...
Arup

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

On 12.07.2005, at 14:31, Arup Vidyerthy wrote:

> 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

because it launches the http control server on port 6580, you may connect to
it with your browser and see for yourself. Add -hcport
6581 to run it on port 6581, or -hcport -1 to not run the http control
server at all.

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 03:15:48 2005