Actually we should fix this. We can fix this by exposing these default services only through HTTP/S.
Thanks, Supun.. On Fri, Jan 21, 2011 at 2:38 PM, Tharindu Mathew <[email protected]> wrote: > > > On Fri, Jan 21, 2011 at 1:26 PM, Kasun Indrasiri <[email protected]> wrote: >> >> Yes. We have observed these default services listed under faulty services >> when we have enabled transports like tcp, mailto etc. >> I think, this is something that we have to fix. > > Ah ok. If this is a known issue, sorry for the noise. >> >> On Fri, Jan 21, 2011 at 12:25 PM, Tharindu Mathew <[email protected]> >> wrote: >>> >>> Yes, that's the reason. But, just because the service does not support >>> mailto doesn't mean it's a faulty service right? >>> >>> On Fri, Jan 21, 2011 at 12:19 PM, Amila Maha Arachchi <[email protected]> >>> wrote: >>>> >>>> Hi Tharindu, >>>> >>>> The reason may be configuration errors in the mailto transport. Check >>>> the log when starting ESB. It may give some warnings saying mailto >>>> transport >>>> is not configured properly. Something like shown below. >>>> >>>> [2011-01-21 12:14:39,768] WARN - MailTransportListener Disabling the >>>> mailto transport for the service wso2carbon-sts, because it is not >>>> configured properly for the service >>>> [2011-01-21 12:14:39,769] WARN - MailTransportListener Unable to >>>> configure the service XKMS for the MAILTO transport: Service doesn't have >>>> configuration information for transport mailto. This service is being >>>> marked >>>> as faulty and will not be available over the MAILTO transport. >>>> [2011-01-21 12:14:39,769] WARN - MailTransportListener Disabling the >>>> mailto transport for the service XKMS, because it is not configured >>>> properly >>>> for the service >>>> [2011-01-21 12:14:39,769] WARN - MailTransportListener Unable to >>>> configure the service version for the MAILTO transport: Service doesn't >>>> have >>>> configuration information for transport mailto. This service is being >>>> marked >>>> as faulty and will not be available over the MAILTO transport. >>>> [2011-01-21 12:14:39,770] WARN - MailTransportListener Disabling the >>>> mailto transport for the service version, because it is not configured >>>> properly for the service >>>> [2011-01-21 12:14:39,770] WARN - MailTransportListener Unable to >>>> configure the service WSDLValidatorService for the MAILTO transport: >>>> Service >>>> doesn't have configuration information for transport mailto. This service >>>> is >>>> being marked as faulty and will not be available over the MAILTO transport. >>>> [2011-01-21 12:14:39,770] WARN - MailTransportListener Disabling the >>>> mailto transport for the service WSDLValidatorService, because it is not >>>> configured properly for the service >>>> [2011-01-21 12:14:39,770] WARN - MailTransportListener Unable to >>>> configure the service Java2WSDLService for the MAILTO transport: Service >>>> doesn't have configuration information for transport mailto. This service >>>> is >>>> being marked as faulty and will not be available over the MAILTO transport. >>>> [2011-01-21 12:14:39,770] WARN - MailTransportListener Disabling the >>>> mailto transport for the service Java2WSDLService, because it is not >>>> configured properly for the service >>>> [2011-01-21 12:14:39,771] WARN - MailTransportListener Unable to >>>> configure the service WSDL2CodeService for the MAILTO transport: Service >>>> doesn't have configuration information for transport mailto. This service >>>> is >>>> being marked as faulty and will not be available over the MAILTO transport. >>>> [2011-01-21 12:14:39,771] WARN - MailTransportListener Disabling the >>>> mailto transport for the service WSDL2CodeService, because it is not >>>> configured properly for the service >>>> >>>> >>>> Thanks, >>>> AmilaM. >>>> >>>> On Thu, Jan 20, 2011 at 11:53 PM, Tharindu Mathew <[email protected]> >>>> wrote: >>>>> >>>>> Hi, >>>>> Is $subject normal? Screen shot attached. >>>>> >>>>> -- >>>>> Regards, >>>>> >>>>> Tharindu >>>>> >>>>> >>>>> _______________________________________________ >>>>> Carbon-dev mailing list >>>>> [email protected] >>>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Carbon-dev mailing list >>>> [email protected] >>>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>>> >>> >>> >>> >>> -- >>> Regards, >>> >>> Tharindu Mathew >>> Software Engineer, >>> WSO2 Inc., >>> http://wso2.com >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >> >> >> >> -- >> Kasun Indrasiri >> Senior Software Engineer >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 71 536 4128 >> Blog : http://kasunpanorama.blogspot.com/ >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> > > > > -- > Regards, > > Tharindu Mathew > Software Engineer, > WSO2 Inc., > http://wso2.com > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Supun Kamburugamuva Technical Lead WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 431 3585 Blog: http://supunk.blogspot.com _______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
