On Tue, Jun 21, 2011 at 9:45 AM, Simon Nash <[email protected]> wrote: > Monosij Dutta-Roy wrote: >> >> hi Simon - >> Attached are the composite files. The qmAppSCA01 is the webapp that calls >> the qmController which then uses domainBCA objects to return results. >> >> It gives the errors in duplicate components for QueryOrchestrator, >> QueryComposer, QueryExecutor which are in qmController composite. As you >> will see in the qmController composite each has been defined only once. >> >> Again this is only happening on the AIX box and not on Ubuntu. >> >> Please let me know anything else you need or may want me to try. I have >> been out for a while so took me some to get back with proper details. >> >> Thanks for your help. >> >> monosij >> .... >> >> SEVERE: [ASM50001] Duplicate component name: Composite = >> {http://docs.oasis-open.org/ns/opencsa/sca/200912} Component = >> QueryOrchestratorComponent >> May 22, 2011 10:56:49 PM >> org.apache.tuscany.sca.builder.impl.CompositeComponentTypeBuilderImpl >> [Composite: {http://docs.oasisopen. >> org/ns/opencsa/sca/200912}] (DuplicateComponentName) >> SEVERE: [ASM50001] Duplicate component name: Composite = >> {http://docs.oasis-open.org/ns/opencsa/sca/200912} Component = >> QueryComposerComponent >> May 22, 2011 10:56:49 PM >> org.apache.tuscany.sca.builder.impl.CompositeComponentTypeBuilderImpl >> [Composite: {http://docs.oasisopen. >> org/ns/opencsa/sca/200912}] (DuplicateComponentName) >> SEVERE: [ASM50001] Duplicate component name: Composite = >> {http://docs.oasis-open.org/ns/opencsa/sca/200912} Component = >> >> >> >> On Fri, May 27, 2011 at 8:18 AM, Simon Laws <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi >> >> It's difficult to tell what going on without seeing the composite >> files. If this error is being validly reported it means that more than >> one component with the same name have been added to the domain level >> composite. Could this be the case? >> >> Regards >> >> Simon >> >> -- >> Apache Tuscany committer: tuscany.apache.org >> <http://tuscany.apache.org> >> Co-author of a book about Tuscany and SCA: tuscanyinaction.com >> <http://tuscanyinaction.com> >> >> > Hi Monosij, > As this is now happening on another system (as described in your private > email to me), I can only suggest that you have accidentally changed > something in your application and this is causing the qmController composite > to be deployed twice. You might be able to work around it by removing the > qmController composite and putting the components from that composite > into one of your other composites that isn't reporting the duplicate > component problem. > > Simon > >
I had a quick look back in the logs you had in one of the earlier emails about this and can see this: May 22, 2011 10:56:46 PM org.apache.tuscany.sca.node.impl.NodeFactoryImpl loadContributions INFO: Loading contribution: file:/home/imracif/qm.01/qmAppSCA01/src/main/webapp/ May 22, 2011 10:56:48 PM org.apache.tuscany.sca.node.impl.NodeFactoryImpl loadContributions INFO: Loading contribution: file:/home/imracif/qm.01/qmAppSCA01/src/main/webapp/WEB-INF/sca-contributions/domainBCA-1.0-SNAPSHOT.jar May 22, 2011 10:56:48 PM org.apache.tuscany.sca.node.impl.NodeFactoryImpl loadContributions INFO: Loading contribution: file:/home/imracif/qm.01/qmAppSCA01/src/main/webapp/WEB-INF/sca-contributions/domainBCA.jar May 22, 2011 10:56:48 PM org.apache.tuscany.sca.node.impl.NodeFactoryImpl loadContributions INFO: Loading contribution: file:/home/imracif/qm.01/qmAppSCA01/src/main/webapp/WEB-INF/sca-contributions/qmController-1.0-SNAPSHOT.jar May 22, 2011 10:56:48 PM org.apache.tuscany.sca.node.impl.NodeFactoryImpl loadContributions INFO: Loading contribution: file:/home/imracif/qm.01/qmAppSCA01/src/main/webapp/WEB-INF/sca-contributions/qmController.jar See in there its loading the contributions domainBCA-1.0-SNAPSHOT.jar and domainBCA.jar, as well as qmController-1.0-SNAPSHOT.jar and qmController.jar. Those look like duplicates or each other don't they as its including jars with and without the version 1.0-SNAPSHOT? Could the problem be something in the build script with they way its assembling the .war and including the contributions? ...ant
