Versions Compared

Old Version 1

changes.mady.by.user Rukshani Weerasinha (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
languagehtml/xml
<messageStore class="org.wso2.carbon.message.store.persistence.jms.JMSMessageStore"
		name="wso2MessageStore">
   	<parameter name="vender.class.loader.enabled">false</parameter>
   	<parameter name="java.naming.factory.initial">weblogic.jndi.WLInitialContextFactory</parameter>
   	<parameter name="store.jms.cache.connection">false</parameter>
   	<parameter name="store.jms.password">admin123</parameter>
   	<parameter name="java.naming.provider.url">t3://localhost:7001</parameter>
   	<parameter name="store.jms.ConsumerReceiveTimeOut">300</parameter>
   	<parameter name="store.jms.connection.factory">jms/myConnectionFactory</parameter>
   	<parameter name="store.jms.username">weblogic</parameter>
   	<parameter name="store.jms.JMSSpecVersion">1.1</parameter>
   	<parameter name="store.jms.destination">jms/wso2MessageQueue</parameter>
</messageStore>
Info

The vender.class.loader.enabled parameter in the above configuration should be added only when you use IBM Websphere MQ as the JMS broker.

WSO2 uses some external class loader mechanisms for some external products such as QPID and AMQP due to the limitation of serializing the JMSObject message. However, it is not required to use this mechanism for IBM Websphere MQ. Therefore, the vender.class.loader.enabled parameter can be used to skip the external class loader for IBM Websphere MQ.

 

Start the ESB.