Hi Chamila, Is BAM run on the same virtualbox private network ?
On Tue, Oct 14, 2014 at 7:05 PM, Chamila De Alwis <chami...@wso2.com> wrote: > Update: > > This seems to be somehow caused by a network interface issue. The machine > I run CEP on has a virtualbox private network configured. I started another > CEP sever on a separate machine without the virtualbox network > configuration and the same code is able to connect and publish to the > latter server. > > The exact cause for this is unclear. > > > Regards, > Chamila de Alwis > Software Engineer | WSO2 | +94772207163 > Blog: code.chamiladealwis.com > > > > On Tue, Oct 14, 2014 at 5:42 PM, Chamila De Alwis <chami...@wso2.com> > wrote: > >> Hi, >> >> I'm trying to get a Python data publisher to publish data to WSO2CEP >> through the Thrift protocol. I can successfully publish data to BAM on its >> port 7711 using username and password. However the same code doesn't >> connect to the port 7711 on the CEP and gives the following error. >> >> >> thrift.transport.TTransport.TTransportException: Could not connect to >> 10.100.5.140:7711: [Errno 111] Connection refused >> >> >> The Python client I'm using is at [1]. The port 7711 is open, and I can >> telnet to it. >> >> Is there any difference when it comes to publishing to BAM vs CEP? >> >> >> [1] - https://github.com/dineshbandara/thrift-python-client >> >> >> Regards, >> Chamila de Alwis >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> > > _______________________________________________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Regards, Manula Chathurika Thantriwatte Software Engineer WSO2 Inc. : http://wso2.com lean . enterprise . middleware email : manu...@wso2.com / man...@apache.org phone : +94 772492511 blog : http://manulachathurika.blogspot.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
