There are some typos in previous mail and please find correct configuration as follows. Sorry for the inconvenience made.
*ESB Configuration in axis2.xml should be as follows:* <transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener"> <parameter name="*myTopicConnectionFactory*" locked="false"> <parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">TopicConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false"> *queue*</parameter> </parameter> <parameter name="*myQueueConnectionFactory*" locked="false"> <parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">*topic* </parameter> </parameter> <parameter name="*default*" locked="false"> <parameter name="java.naming.factory.initial" locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter> <parameter name="java.naming.provider.url" locked="false">repository/conf/jndi.properties</parameter> <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">QueueConnectionFactory</parameter> <parameter name="transport.jms.ConnectionFactoryType" locked="false">*topic* </parameter> </parameter> </transportReceiver> *Warning coming from ESB console not from MB* On Thu, May 12, 2016 at 3:04 PM, Dilshani Subasinghe <dilsh...@wso2.com> wrote: > Hi Devs, > > I am testing JMS transport parameters in ESB and using MB as the broker. I > am little bit confused about the parameter > "transport.jms.ConnectionFactoryType" with its' behavior. > > I used the JMS use case of "ESB as both JMS producer and consumer" > > - In ESB, I configured receiver with incorrect value for > "transport.jms.ConnectionFactoryType=topic" as follows: > > <transportReceiver name="jms" > class="org.apache.axis2.transport.jms.JMSListener"> > <parameter name="*myTopicConnectionFactory*" locked="false"> > <parameter name="java.naming.factory.initial" > locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter> > <parameter name="java.naming.provider.url" > locked="false">repository/conf/jndi.properties</parameter> > <parameter name="transport.jms.ConnectionFactoryJNDIName" > locked="false">TopicConnectionFactory</parameter> > <parameter name="transport.jms.ConnectionFactoryType" locked="false"> > *queue*</parameter> > </parameter> > > <parameter name="*myQueueConnectionFactory*" locked="false"> > <parameter name="java.naming.factory.initial" > locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter> > <parameter name="java.naming.provider.url" > locked="false">repository/conf/jndi.properties</parameter> > <parameter name="transport.jms.ConnectionFactoryJNDIName" > locked="false">TopicConnectionFactory</parameter> > <parameter name="transport.jms.ConnectionFactoryType" locked="false"> > *topic*</parameter> > </parameter> > > <parameter name="*default*" locked="false"> > <parameter name="java.naming.factory.initial" > locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory</parameter> > <parameter name="java.naming.provider.url" > locked="false">repository/conf/jndi.properties</parameter> > <parameter name="transport.jms.ConnectionFactoryJNDIName" > locked="false">TopicConnectionFactory</parameter> > <parameter name="transport.jms.ConnectionFactoryType" locked="false"> > *topic*</parameter> > </parameter> > </transportReceiver> > > > - And created a proxy as follows: > > <proxy xmlns="http://ws.apache.org/ns/synapse" > name="JMSProxy" > transports="jms" > statistics="disable" > trace="disable" > startOnLoad="true"> > <target> > <inSequence> > <property name="OUT_ONLY" value="true"/> > <send> > <endpoint> > <address > uri="jms:/JMSMS?transport.jms.ConnectionFactoryJNDIName= > *QueueConnectionFactory* > &java.naming.factory.initial=org.wso2.andes.jndi.PropertiesFileInitialContextFactory&java.naming.provider.url=repository/conf/jndi.properties&transport.jms.ConnectionFactoryType= > *topic*"/> > </endpoint> > </send> > </inSequence> > </target> > <description/> > </proxy> > > Within JMS sender (JMS endpoint) also given incorrect value for > "transport.jms.ConnectionFactoryType". But still it may create queue in MB > without considering *Connection Factory Type*. (Both JMSProxy and JMSMS > are queues) > > When publishing messages, there is a warning from MB side as follows > (Warning is printing per message): > > *WARN - AMQConnectionDelegate_8_0 Loading keystore and truststore from > system properties* > > Can someone help to understand this behavior ? Is it correct, not to > identify connection factory type ? > > Thank you. > > > -- > Best Regards, > > Dilshani Subasinghe > Software Engineer - QA > WSO2, Inc.;http://wso2.com/ > <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ> > lean.enterprise.middleware > Mobile: +94773375185 > Blog: dilshanilive.blogspot.com > -- Best Regards, Dilshani Subasinghe Software Engineer - QA WSO2, Inc.;http://wso2.com/ <http://www.google.com/url?q=http%3A%2F%2Fwso2.com%2F&sa=D&sntz=1&usg=AFQjCNGJuLRux6KkJwXKVUCYOtEsNCmIAQ> lean.enterprise.middleware Mobile: +94773375185 Blog: dilshanilive.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev