On Sun, May 8, 2011 at 10:13 AM, Hiranya Jayathilaka <hira...@wso2.com>wrote:
> > > On Sun, May 8, 2011 at 7:43 AM, Amila Suriarachchi <am...@wso2.com> wrote: > >> >> >> On Sun, May 8, 2011 at 12:08 AM, Afkham Azeez <az...@wso2.com> wrote: >> >>> >>> >>> On Sun, May 8, 2011 at 12:02 AM, Hiranya Jayathilaka >>> <hira...@wso2.com>wrote: >>> >>>> >>>> >>>> On Sat, May 7, 2011 at 10:59 PM, Amila Suriarachchi <am...@wso2.com>wrote: >>>> >>>>> >>>>> >>>>> On Sat, May 7, 2011 at 8:11 PM, Hiranya Jayathilaka >>>>> <hira...@wso2.com>wrote: >>>>> >>>>>> Hi Folks, >>>>>> >>>>>> Can somebody please explain what QueueService and MessageQueue are? >>>>>> These services shout whenever I enable some transport in the ESB: >>>>>> >>>>>> [2011-05-07 20:08:39,148] WARN - VFSTransportListener Unable to >>>>>> configure the service QueueService for the VFS transport: Service doesn't >>>>>> have configuration information for transport vfs. This service is being >>>>>> marked as faulty and will not be available over the VFS transport. >>>>>> [2011-05-07 20:08:39,162] WARN - VFSTransportListener Disabling the >>>>>> vfs transport for the service QueueService, because it is not configured >>>>>> properly for the service >>>>>> [2011-05-07 20:08:39,163] WARN - VFSTransportListener Unable to >>>>>> configure the service MessageQueue for the VFS transport: Service doesn't >>>>>> have configuration information for transport vfs. This service is being >>>>>> marked as faulty and will not be available over the VFS transport. >>>>>> [2011-05-07 20:08:39,163] WARN - VFSTransportListener Disabling the >>>>>> vfs transport for the service MessageQueue, because it is not configured >>>>>> properly for the service >>>>>> >>>>> >>>>> The reason is we have not limited the transport to https unlike in >>>>> other admin services. >>>>> >>>> >>>> So then I guess it's a bug, isn't it? We have fixed all other services >>>> (Version, HelloWorld etc) by exposing them over HTTP/S only. >>>> >>> >>> >>> No! What if users deploy their own services? Their services will >>> automatically be marked as faulty, and none of their services will work >>> OOTB. Why don't we make VFSTransport optional? >>> >> >> +1. >> >> We want SQS services expose what ever available transport since it is not >> just a service used for Admin Console. >> >> Yes, it won't work with transports like SMTP, JMS, VFS without having >> explicit parameters set. In that sense one can argue every one suppose to >> specify all the transports that service can actually work with. >> >> But as Azeez pointed out normally Axis2 service authers don't specify >> those and hence all those services are marked as faulty. So making >> VFSTransport optional would be better solution. >> > > And how do we do that? By default Axis2 exposes services over all available > transports. If a particular transport is not configured for a service, above > warnings are shown. I think service also gets marked as faulty in this case, > but other active transport bindings continue to work (they don't malfunction > as Azeez has mentioned). You will see this behavior in all the releases we > have done so far and I don't think this can be fixed without some serious > changes to Axis2. > I think making services as faulty happens at the base transport module. So we may be able to check a parameter to make a service faulty. > > Also please note that problem is not just about VFS. It is in fact about > all the transports you have mentioned above. So clearly these 2 services are > not working with any transport other than HTTP/S. Since the services are not > shown in the UI, user cannot really change this behavior for these services > either. So IMO better to restrict these services to HTTP/S. > yes we can make this service only for http/https. But that is not the problem. Is it correct make services, which have not configured to these transport faulty? thanks, Amila. > > Thanks, > Hiranya > > >> >> thanks, >> Amila. >> >> thanks, >> Amila. >> >>> >>> >>>> Thanks, >>>> Hiranya >>>> >>>> >>>>> If you remove that you should get this error with other Admin services >>>>> as well. >>>>> >>>> >>>>> thanks, >>>>> Amila. >>>>> >>>>> >>>>>> >>>>>> Thanks >>>>>> -- >>>>>> Hiranya Jayathilaka >>>>>> Senior Software Engineer; >>>>>> WSO2 Inc.; http://wso2.org >>>>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>>>>> Blog: http://techfeast-hiranya.blogspot.com >>>>>> >>>>>> _______________________________________________ >>>>>> Carbon-dev mailing list >>>>>> Carbon-dev@wso2.org >>>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> Carbon-dev@wso2.org >>>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Senior Software Engineer; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> Carbon-dev@wso2.org >>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>>> >>> >>> >>> -- >>> *Afkham Azeez* >>> Director of Architecture; WSO2, Inc.; http://wso2.com >>> Member; Apache Software Foundation; http://www.apache.org/ >>> * <http://www.apache.org/>** >>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>> * >>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>> * >>> * >>> *Lean . Enterprise . Middleware* >>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Hiranya Jayathilaka > Senior Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
