Christoph Willing wrote: > > On 14/01/2007, at 1:01 AM, Ismail Bhana wrote: > >> I've been developing a set of node services called JMast >> (JMastConsumer and JMastProducer services) which basically provide a >> form of application sharing using streaming technologies. However, >> whilst I can get the software to boot from AG 3.0.2 with parameters >> passed correctly I'm having a problem where I'm being passed the same >> multicast address/port as the vic tool which causes vic to crash. If >> I change the Capabilities type (say, from "JMAST" to "jmast1") a >> different address to vic is assigned in the first instance of >> execution but the next time I run the software its back to giving me >> the same address/port as vic and I can't really work out why. > > > Ismail, > > I've seen this too in another service we've been developing and would > be interested in knowing the cause. > > One thing I found which has lessened the problem somewhat, but not > cured it completely, is to make (in your case) a JMastService i.e. not > exclusively a Producer or Consumer service. Do that by adding > Capability.CONSUMER etc. to the self.capabilities already in your > Producer service. This is a bit like the normal VideoService, compared > with VideoProducerService and VideoConsumerService. Then use the new > JMastService as the producer service while still using your original > JMastConsumerService as the consumer service. > > > chris > > > Christoph Willing +61 7 3365 8350 > QCIF Access Grid Manager > University of Queensland > > > Ok, I've tried the above and it seems that JMast is getting its own address and port now :)
Thanks Again, Ismail
