Ws02 jms transport for websphere MQ

After searching a couple of days, I had a problem with the IBM MQ message form. I followed the documentation, but still could not work calmly. I am using 4.8.0 and MQ 7.5.0.2

Error

[2014-02-06 01:06:14,341] ERROR - JMSListener Unable to continue server startup as it seems the JMS Provider is not yet started. Please start the JMS provider now.
[2014-02-06 01:06:14,342] ERROR - JMSListener Connection attempt : 1 for JMS Provider failed. Next retry in 20 seconds
[2014-02-06 01:06:34,364] ERROR - JMSListener Unable to continue server startup as it seems the JMS Provider is not yet started. Please start the JMS provider now.
 [2014-02-06 01:06:34,365] ERROR - JMSListener Connection attempt : 2 for JMS Provider failed. Next retry in 40 seconds

root@sandbox:/opt/wso2esb-4.8.0/FFDC# more JMSCC0001.FDC
----------------------------------START FFST------------------------------------
/opt/wso2esb-4.8.0/FFDC/JMSCC0001.FDC PID:5897

                                JMS Common Client First Failure Symptom Report


Product          :- IBM WebSphere MQ classes for JMS
Date/Time        :- Thu Feb 06 00:54:07 CET 2014
System time      :- 1391644447539
Operating System :- SunOS
UserID           :- root
Java Vendor      :- Oracle Corporation
Java Version     :- 23.3-b01

Source Class     :- com.ibm.mq.jms.MQQueueConnectionFactory
Source Method    :- readObject()
ProbeID          :- XF001003
Thread           :- name=localhost-startStop-1 priority=5 group=main ccl=org.eclipse.core.runtime.internal.adaptor.ContextFinder@1da36ad

axis2 config

<transportReceiver name="jms" class="org.apache.axis2.transport.jms.JMSListener">
        <parameter name="default" locked="false">
                <parameter name="java.naming.factory.initial" locked="false">com.sun.jndi.fscontext.RefFSContextFactory</parameter>
                <parameter name="java.naming.provider.url" locked="false">file:///var/tmp/jndi</parameter>
                <parameter name="transport.jms.ConnectionFactoryJNDIName" locked="false">ivtQCF</parameter>
                <parameter name="transport.jms.ConnectionFactoryType" locked="false">queue</parameter>
                <parameter name="transport.jms.Destination" locked="false">ivtQ</parameter>
        </parameter>
</transportReceiver>

test jndi works

java JmsJndiConsumer -i file:///var/tmp/jndi -c ivtQCF -d ivtQ
Initial context found!
Received message:

  JMSMessage class: jms_text
  JMSType:          null
  JMSDeliveryMode:  2
  JMSExpiration:    0
  JMSPriority:      4
  JMSMessageID:     ID:414d5120514d412020202020202020204424ee5203db0020
  JMSTimestamp:     1391646438379
  JMSCorrelationID: null
  JMSDestination:   queue://QMA/QUEUE1
  JMSReplyTo:       null
  JMSRedelivered:   false
    JMSXAppID: JmsJndiProducer
    JMSXDeliveryCount: 1
    JMSXUserID: webservd
    JMS_IBM_Character_Set: UTF-8
    JMS_IBM_Encoding: 273
    JMS_IBM_Format: MQSTR
    JMS_IBM_MsgType: 8
    JMS_IBM_PutApplType: 28
    JMS_IBM_PutDate: 20140206
    JMS_IBM_PutTime: 00271840
JmsJndiProducer: Your lucky number today is 324

proxies

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns="http://ws.apache.org/ns/synapse"
       name="StockQuoteProxy2"
       transports="jms"
       startOnLoad="true"
       trace="disable">
   <description/>
   <target>
      <endpoint>
         <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
      </endpoint>
     <inSequence>
         <property name="OUT_ONLY" value="true"/>
     </inSequence>
     <outSequence>
         <send/>
     </outSequence>
   </target>
   <publishWSDL uri="file:repository/samples/resources/proxy/sample_proxy_1.wsdl"/>
   <parameter name="transport.jms.ContentType">
      <rules>
         <jmsProperty>contentType</jmsProperty>
         <default>application/xml</default>
      </rules>
   </parameter>
</proxy>

I checked the network and I do not see any form of esb connecting to the mq server.

Any idea?

Update

I configured the axis server in the sample ($ WSO2_HOME / samples / axis2Server / repository / conf / axis2.xml) with exactly the same jms transport (by default).

Atfer compiles "SimpleStockQuoteService" and starting the server, I see that it is working fine.

cd wso2esb-4.8.1/samples/axis2Server/src/SimpleStockQuoteService/ && ant
cd wso2esb-4.8.1/samples/axis2Server/ && ./axis2server.sh

14/02/10 21:20:29 INFO jms.JMSListener: JMS listener started
14/02/10 21:20:30 INFO jms.JMSListener: Connection attempt: 1 for JMS Provider for
service: SimpleStockQuoteService was successful!
14/02/10 21:20:30 INFO jms.ServiceTaskManager: Task manager for service : 
SimpleStockQuoteService [re-]initialized
14/02/10 21:20:31 INFO jms.JMSListener: Started to listen on destination : ivtQ of 
type queue for service SimpleStockQuoteService
14/02/10 21:20:31 INFO util.SampleAxis2ServerManager: [SimpleAxisServer] Started

I still do not understand why carbon does not work inside.

+3
source share
1 answer

, , script (ws02server.sh), java- MQ

CARBON_CLASSPATH =/Opt//Java/Library/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar: "$ CARBON_CLASSPATH"

MQ BIND (ws02 , MQ), jni (-Djava.library.path =/opt/mqm/java/lib)

Java MQ //lib, , .

MQ 7.5.0.2 ws02 4.8.1 Solaris RHEL7

+2

All Articles