Re: [Dev] [ESB][JMS] What is the usage and behavior of "transport.jms.ConnectionFactoryType" parameter ?

2016-05-12 Thread Dilshani Subasinghe 
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:*



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
   TopicConnectionFactory
   
*queue*



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 QueueConnectionFactory
*topic*




org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 QueueConnectionFactory
*topic*





*Warning coming from ESB console not from MB*




On Thu, May 12, 2016 at 3:04 PM, Dilshani Subasinghe 
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:
>
>   class="org.apache.axis2.transport.jms.JMSListener">
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">repository/conf/jndi.properties
> locked="false">TopicConnectionFactory
>
> *queue*
> 
>
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">repository/conf/jndi.properties
>   locked="false">TopicConnectionFactory
> 
> *topic*
> 
>
> 
>  locked="false">org.wso2.andes.jndi.PropertiesFileInitialContextFactory
>  locked="false">repository/conf/jndi.properties
>   locked="false">TopicConnectionFactory
> 
> *topic*
> 
> 
>
>
>- And created a proxy as follows:
>
> http://ws.apache.org/ns/synapse";
>name="JMSProxy"
>transports="jms"
>statistics="disable"
>trace="disable"
>startOnLoad="true">
>
>   
>  
>  
> 
> 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*"/>
> 
>  
>   
>
>
> 
>
> 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/
> 
> lean.enterprise.middleware
> Mobile: +94773375185
> Blog: dilshanilive.blogspot.com
>



-- 
Best Regards,

Dilshani Subasinghe
Software Engineer - QA
WSO2, Inc.;http://wso2.com/

lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] [ESB][JMS] What is the usage and behavior of "transport.jms.ConnectionFactoryType" parameter ?

2016-05-12 Thread Dilshani Subasinghe 
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:

 

org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
   TopicConnectionFactory
   
*queue*



org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 TopicConnectionFactory
*topic*




org.wso2.andes.jndi.PropertiesFileInitialContextFactory
repository/conf/jndi.properties
 TopicConnectionFactory
*topic*





   - And created a proxy as follows:

http://ws.apache.org/ns/synapse";
   name="JMSProxy"
   transports="jms"
   statistics="disable"
   trace="disable"
   startOnLoad="true">
   
  
 
 

   

 
  
   
   


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/

lean.enterprise.middleware
Mobile: +94773375185
Blog: dilshanilive.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev