On Wed, May 8, 2013 at 6:12 PM, Afkham Azeez <[email protected]> wrote: > > > On Wed, May 8, 2013 at 6:03 PM, Amila Maha Arachchi <[email protected]>wrote: > >> Hi Azeez, >> >> A major concern we have in Stratos is, we haven't enabled any transport >> other than http and https. >> > > We have never tested non-HTTP transports for tenants since we haven't > figured out how to retrieve the tenant from the incoming request for > non-HTTP transports. For HTTP, it was easy, the URL contained the tenant > domain. We will have to review each & every transport (listener) & figure > out how to derive the tenant from those transports. For transport sender, > it is a different story. There shouldn't be any major issue in tenant code > making a call using HTTP as well as non-HTTP transports. >
Yes. I didnt mention about the listeners due to above mentioned same reasons. With this effort we felt that we will be able to at least enable the senders in the cloud. > > >> No one had tried this and thought this would simply work when we enable >> the transport sender and receiver. Therefore, we tried a jms sender >> scenario to see whether it works for tenants. Above mail from SumedhaS >> describes the issues he faced and how he is able to get the jms sending >> working for tenants. >> >> We have some questions: >> >> Is it correct to use the org.wso2.carbon.context.RequestBaseContext=true >> parameter? >> What it does? >> Does it have any security threats? >> > > Sorry, I have no idea about that parameter or its security implications. > It is possible that this exposes a vulnerability, so the usage of this > parameter needs to be thoroughly reviewed before adding it in. > Yes. We'll try to understand the behaviour of this. > > >> >> Regards, >> AmilaM. >> >> >> On Wed, May 8, 2013 at 5:40 PM, Sumedha Kodithuwakku >> <[email protected]>wrote: >> >>> Hi all, >>> >>> While I was trying ESB as a JMS Producer use case [1] with a Stratos >>> local setup, the following error was encountered. This was tested against a >>> standalone ESB, and same issue was encountered. >>> >>> ERROR - ClientUtils The system cannot infer the transport information >>> from the >>> jms:/SimpleStockQuoteService?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616 >>> URL. >>> >>> >>> After debugging the code it was found that the required Transport >>> sender (JMS) is not added in TenantAxisUtils class (in >>> *createTenantConfigurationContext >>> *method). Although this was added (see carbon.patch), the sample was >>> not working (The patched jar is attached). The following error >>> was encountered. >>> >>> ERROR - Axis2Sender Unexpected error during sending message out >>> java.lang.RuntimeException: An error occurred while creating the initial >>> context for tenant: 1 >>> >>> >>> After debugging the code and having a discussion with >>> Amila, following property was added to the JMS Connection URI in the proxy >>> service. >>> >>> >>> org.wso2.carbon.context.RequestBaseContext=true >>> >>> Adding this property solved the issue. >>> >>> Is this the correct approach of solving this issue. Are there any >>> security concerns over adding this property..? >>> >>> Suggestions are welcome. >>> >>> [1] http://docs.wso2.org/wiki/display/ESB460/ESB+as+a+JMS+Producer >>> >>> >>> Thanks >>> SumedhaS >>> >>> -- >>> *Sumedha Kodithuwakku* >>> >>> Software Engineer >>> >>> WSO2 Inc. : wso2.com >>> lean . enterprise . middleware >>> >>> Mobile : +94718081124 >>> >>> >> >> >> -- >> *Amila Maharachchi* >> Technical Lead >> Member, Management Committee - Cloud & Platform TG >> WSO2, Inc.; http://wso2.com >> >> Blog: http://maharachchi.blogspot.com >> Mobile: +94719371446 >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* 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* > -- *Amila Maharachchi* Technical Lead Member, Management Committee - Cloud & Platform TG WSO2, Inc.; http://wso2.com Blog: http://maharachchi.blogspot.com Mobile: +94719371446
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
