Hi all,
I just wanna mention some couple of facts that can cause $subject since this is a error which occurs quite frequently for users. The reason behind this issue is bit tricky because even though the exception tells something, but actually what could happen is something else.
1. If you have missed any configuration related to WSO2 ESB and MB integration i.e adding queue info in jndi properties files and etc ESB will give this error since ESB is the JMS client. Pleas refer [1]
2. If you are sure that all the configurations are done but still getting this error, there is one other reason for this. When you enable axis2 JMS transports in ESB for the MB ESB integration scenario as per docs, by default the JMS transport will be enabled to all the services you have hosted there.For instance you might have axis2 services/data services inside. So for those it expect those to inherit the JMS transport also. But your already deployed such axis2 services might not need JMS transport.
The solution that comes to mind at first is to add JMS transport to all other services deployed which is also a solution. But it is not practical to change existing service due to MB integratoin.
So the possible best solution is as follows.
So in such case what you need to do is for each such service create a axis2 services xml file such that it specifically
mention that it needs only HTTP/HTTPs like transports.
i.e
https http
[1] - http://docs.wso2.org/wiki/display/MB201/Integrating+WSO2+ESB
