If I remove the two jars from dropins and submit a payload I am hit with an error as below. I did the configurations as per [1] I added the below 3 lines to axis2.xml but no luck
- In the parameters section: <parameter name="defaultContentType" locked="false">empty/content</parameter> - In the message builders section: <messageBuilder contentType="empty/content" class="org.wso2.carbon.relay.BinaryRelayBuilder"/> - In the message formatters section: <messageFormatter contentType="empty/content" class="org.wso2.carbon.relay.ExpandingMessageFormatter"/> [1] https://docs.wso2.com/display/ESB490/Working+with+Message+Builders+and+Formatters#WorkingwithMessageBuildersandFormatters-Handlingmessageswithnocontenttype [2018-08-15 19:47:06,881] WARN - JMSUtils Can't determine size of JMS message; unsupported message type : com.ibm.jms.JMSObjectMessage [2018-08-15 19:47:06,883] ERROR - JMSMessageReceiver Axis fault processing message org.apache.axis2.AxisFault: Unable to determine content type for message ID:414d5120455342514d616e61676572204662725b16d18624 at org.apache.axis2.transport.jms.JMSMessageReceiver.processThoughEngine(JMSMessageReceiver.java:172) at org.apache.axis2.transport.jms.JMSMessageReceiver.onMessage(JMSMessageReceiver.java:122) at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.handleMessage(ServiceTaskManager.java:575) at org.apache.axis2.transport.jms.ServiceTaskManager$MessageListenerTask.run(ServiceTaskManager.java:468) at org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Shavantha Weerasinghe Senior Engineering Process Coordinator WSO2, Inc. lean.enterprise.middleware. http://wso2.com http://wso2.org *Mobile : +94 <+94%2071%20593%203168>714800048* Tel : 94 11 214 5345 Fax :94 11 2145300 On Wed, Aug 15, 2018 at 6:04 PM, Shavantha Weerasinghe <shavan...@wso2.com> wrote: > Hi All > > When I attempt to connect to IBMMQ I get the below error thrown. This was > after I added the below two jars to the drop ins folder. I am currently > using IBM MQ Version: 9.0.0.0 > > The jar versions added to drop ins are(com.ibm.mq_2.0.0.jar/ > fscontext_1.0.0.jar) > > Am I to use a different version of the 2 jars with BM MQ Version: 9.0.0.0 > > > The full set of jars I have in dropins is > > com.ibm.mq_2.0.0.jar > fscontext_1.0.0.jar > jms_1.0.0.jar > jta_1.0.0.jar > org.wso2.carbon.logging.propfile_1.0.0.jar > wmq-client-9.0.0.0.jar > > > Exception > [2018-08-15 17:46:41,167] ERROR - ServiceTaskManager Error reciving the > message. > MQJE001: Completion Code '2', Reason '6114'. > [2018-08-15 17:46:41,180] ERROR - ServiceTaskManager Error creating JMS > consumer for service : MyJMSProxy2. JMSWMQ2008: Failed to open MQ queue > 'Queue1'. > [2018-08-15 17:46:41,181] ERROR - ServiceTaskManager Error reciving the > message. > MQJE001: Completion Code '2', Reason '6114'. > [2018-08-15 17:46:41,196] ERROR - ServiceTaskManager Error creating JMS > consumer for service : MyJMSProxy2. JMSWMQ2008: Failed to open MQ queue > 'Queue1'. > [2018-08-15 17:46:41,197] ERROR - ServiceTaskManager Error reciving the > message. > MQJE001: Completion Code '2', Reason '6114'. > [2018-08-15 17:46:41,212] ERROR - ServiceTaskManager Error creating JMS > consumer for service : MyJMSProxy2. JMSWMQ2008: Failed to open MQ queue > 'Queue1'. > [2018-08-15 17:46:41,213] ERROR - ServiceTaskManager Error reciving the > message. > MQJE001: Completion Code '2', Reason '6114'. > [2018-08-15 17:46:41,228] ERROR - ServiceTaskManager Error creating JMS > consumer for service : MyJMSProxy2. JMSWMQ2008: Failed to open MQ queue > 'Queue1'. > [2018-08-15 17:46:41,228] ERROR - ServiceTaskManager Error reciving the > message. > MQJE001: Completion Code '2', Reason '6114'. > ^C[2018-08-15 17:46:41,243] INFO - CarbonServerManager Shutdown hook > triggered.... > [2018-08-15 17:46:41,243] INFO - CarbonServerManager Gracefully shutting > down WSO2 Enterprise Service Bus... > [2018-08-15 17:46:41,245] INFO - ServerManagement Starting to switch to > maintenance mode... > [2018-08-15 17:46:41,245] INFO - PassThroughHttpSSLListener Stopping > Pass-through HTTPS Listener.. > [2018-08-15 17:46:41,246] INFO - PassThroughListeningIOReactorManager > Shutting down IO Reactor bind for port 8243 > [2018-08-15 17:46:41,246] ERROR - ServiceTaskManager Error creating JMS > consumer for service : MyJMSProxy2. JMSWMQ2008: Failed to open MQ queue > 'Queue1'. > [2018-08-15 17:46:41,246] ERROR - ServiceTaskManager Error reciving the > message. > [2018-08-15 17:46:41,247] INFO - PassThroughListeningIOReactorManager > HTTPS-Listener I/O dispatcher Listener shutdown. > [2018-08-15 17:46:41,247] INFO - PassThroughHttpListener Stopping > Pass-through HTTP Listener.. > [2018-08-15 17:46:41,247] INFO - PassThroughListeningIOReactorManager > Shutting down IO Reactor bind for port 8280 > [2018-08-15 17:46:41,248] INFO - PassThroughListeningIOReactorManager > HTTP-Listener I/O dispatcher Listener shutdown. > [2018-08-15 17:46:41,248] INFO - JMSListener JMS Listener Shutdown > MQJE001: Completion Code '2', Reason '6114'. > [2018-08-15 17:46:41,265] ERROR - ServiceTaskManager Error creating JMS > consumer for service : MyJMSProxy2. JMSWMQ2008: Failed to open MQ queue > 'Queue1'. > [2018-08-15 17:46:41,266] ERROR - ServiceTaskManager Error reciving the > message. > ^C^C^C^C^C^C^C^C^CMQJE001: Completion Code '2', Reason '6114'. > [2018-08-15 17:46:42,252] INFO - ServiceTaskManager Task manager for > service : MyJMSProxy2 shutdown > [2018-08-15 17:46:42,253] INFO - JMSListener Stopped listening for JMS > messages to service : MyJMSProxy2 > [2018-08-15 17:46:42,254] INFO - ServerManagement Stopped all transport > listeners > [2018-08-15 17:46:42,254] INFO - ServerManagement Waiting for request > service completion... > [2018-08-15 17:46:42,259] INFO - ServerManagement All requests have been > served. > [2018-08-15 17:46:42,259] INFO - ServerManagement Waiting for deployment > completion... > [2018-08-15 17:46:42,264] INFO - ServerManagement All deployment tasks > have been completed. > [2018-08-15 17:46:42,265] INFO - ServerManagement Waiting for server task > completion... > [2018-08-15 17:46:42,307] INFO - ServerManagement All server tasks have > been completed. > [2018-08-15 17:46:42,307] INFO - CarbonServerManager Shutting down WSO2 > Enterprise Service Bus... > [2018-08-15 17:46:42,308] INFO - CarbonServerManager Shutting down OSGi > framework... > [2018-08-15 17:46:42,384] INFO - SynapseTaskManager Shutting down the > task manager > [2018-08-15 17:46:42,471] INFO - CarbonServerManager Stopping > CarbonServerManager... > [2018-08-15 17:46:42,472] INFO - PassThroughHttpSSLSender HTTPS Sender > shutdown > [2018-08-15 17:46:42,473] INFO - PassThroughHttpSender HTTP Sender > shutdown > [2018-08-15 17:46:42,474] INFO - JMSSender JMS Sender Shutdown > [2018-08-15 17:46:42,474] INFO - PassThroughHttpSSLListener Destroying > PassThroughHttpListener > [2018-08-15 17:46:42,475] INFO - PassThroughHttpListener Destroying > PassThroughHttpListener > MQJE001: Completion Code '2', Reason '6114'. > MQJE001: Completion Code '2', Reason '6114'. > > > Shavantha Weerasinghe > Senior Engineering Process Coordinator > WSO2, Inc. > lean.enterprise.middleware. > http://wso2.com > http://wso2.org > *Mobile : +94 <+94%2071%20593%203168>714800048* > Tel : 94 11 214 5345 > Fax :94 11 2145300 > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
