for patches always create jira and attach.

thanks,
Amila.


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 Suriarachchi*

Software Architect
WSO2 Inc. ; http://wso2.com
lean . enterprise . middleware

phone : +94 71 3082805
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to