Dear Lou,
These both problems are different but nodes are same. DUCC 1.0.0 is
running perfectly on same nodes.
When I was trying to configure DUCC 1.1.0 singly, I faced node down
problem. Due to this I thought why don't I try to run DUCC 1.0.0 and
DUCC 1.1.0 simultaneously on same node to compare their behaviour. But,
Now, I am facing problems in this too.
Reshu.
Signature On 11/17/2014 06:33 PM, Lou DeGenaro wrote:
Are these problems related? That is, are you having the node down problem
and the multiple DUCC's problem together on the same set of nodes?
Can you run the either configuration alone without issue?
Lou.
On Mon, Nov 17, 2014 at 7:41 AM, reshu.agarwal <[email protected]>
wrote:
Lou,
I have changed the broker port and ws port too but still faced a problem
in starting the ducc1.1.0 version simultaneously.
Reshu.
On 11/17/2014 05:34 PM, Lou DeGenaro wrote:
The broker port is specifiable in ducc.properties. The default is
ducc.broker.port = 61617.
Lou.
On Mon, Nov 17, 2014 at 5:29 AM, Simon Hafner <[email protected]>
wrote:
2014-11-17 0:00 GMT-06:00 reshu.agarwal <[email protected]>:
I want to run two DUCC version i.e. 1.0.0 and 1.1.0 on same machines
with
different user. Can this be possible?
Yes, that should be possible. You'll have to make sure there are no
port conflicts, I'd guess the ActiveMQ port is hardcoded, the rest
might be randomly assigned. Just set that port manually and watch out
for any errors during the start to see which other components have
hardcoded port numbers.
Personally, I'd just fire up a VM with qemu or VirtualBox.
