Hi Hasitha, If you have correctly updated the stream version that exception would not occur. If it happens there should be a problem. Can you go back to Service Stats configuration and see whether there the updated stream was correctly saved. Make sure you follow the [1].
[1] http://docs.wso2.org/wiki/display/BAM230/Setting+up+Service+Statistics+Data+Agent * Maninda Edirisooriya* Software Engineer *WSO2, Inc. *lean.enterprise.middleware. *Blog* : http://maninda.blogspot.com/ *Phone* : +94 777603226 On Sun, Jul 14, 2013 at 4:53 AM, Hasitha Hiranya <[email protected]> wrote: > I have setup WSO2 Application Server 5.1.0 with WSO2 BAM 2.1.0. > OOB WSO2 application server has “BAM Service Data Agent Aggregate” > feature, which we can use to publish data to BAM. > > I have done following in bam.xml file. > > <BamConfig> > <ServiceDataPublishing>enable</ServiceDataPublishing> > </BamConfig> > > and started the application server. > > Then tried to access Service Data publisher configuration UI. > > 1. It says > > *at > org.wso2.carbon.bam.service.data.publisher.ui.ServiceDataPublisherAdminClient.getBAMServerURL(ServiceDataPublisherAdminClient.java:81) > * > * > * > In order to get rid of the issue I had to define BAM server url in > carbon.xml. > > Isn't this a bug, because as Service Data publisher configuration UI has a > place to define BAM server url. It should wait until we configure it at the > first time and read the BAM server url from there. > > Then I defined a stream in configuration UI and tried out invoking a > service deployed in AS. > Then tried to add a new property. > > 2. The UI confirmed it was updated without issues. But after I publish I > could see following error at BAM console. > > [2013-07-14 01:30:31,710] ERROR > {org.wso2.carbon.databridge.agent.thrift.AsyncDataPublisher} - Stream > definition already exist > org.wso2.carbon.databridge.commons.exception.DifferentStreamDefinitionAlreadyDefinedException: > Same stream id with different definition already defined before sending > this event definitions to TCP,127.0.0.1:7619,TCP,127.0.0.1:7719 > at > ..... > > Then I updated the stream version from 1.0.0 to 2.0.0 and saved. Again UI > message was that the update was a success. > > But when I invoked the service, in BAM side same exception has occurred. > > Is it a bug, or am I missing something in AS+BAM configuration? > > Thanks. > > -- > *Hasitha Abeykoon* > Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * > * > * >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
