Neha, > - I deploy one service on another machine with a Queue name say Q1 which > connect to the broker on machine 1. > ./deployAsyncService.sh > $UIMA_HOME/uimas_test/examples/deploy/as/Deploy_tokenSentenceaggregate.xml
As you say, this deploys a service on machine 1, presumably with Q1 as the queue name in the deployment descriptor. > - I start another service on third machine with Queue name say Q2. > ./deployAsyncService.sh > $UIMA_HOME/uimas_test/examples/deploy/as/Deploy_tokenSentenceaggregate.xml and another on machine 2. Did you change the queue name in Deploy_tokenSentenceaggreate.xml to be Q2 for this service instance? > - Now on the client machine I run this command: > ./runRemoteAsyncAE.sh tcp://IPBrokerMachine:61616 Q1 -d > /hdd-1/AStest/uimas_test/examples/deploy/as/Deploy_tokenSentenceaggregate.xml The last argument, "-d /hdd....", is deploying another instance of the service on machine 1. According to your scenario, this is not needed as the service was already deployed. > - Now on client2 I run the same command.: > ./runRemoteAsyncAE.sh tcp://IPBrokerMachine:61616 Q2 -d > /hdd-1/AStest/uimas_test/examples/deploy/as/Deploy_tokenSentenceaggregate.xml ditto. > So my problem stands there itself, that how do I process different Document > ID's from different client machines on different instances of the same > service. > please suggest me what should I do. Double check that the deployment descriptor on machine 2 is specifying Q2. Eddie
