Troubleshooting JMS and MQ JMS bindings

You can diagnose and fix problems with your JMS or MQ JMS bindings.

Why and when to perform this task

In response to various error conditions, the JMS and MQ JMS Import and Export implementation can return one of the two types of exceptions:

When an XML Schema has a type defined without a global element the JMS Bindings (JMSDataBindingImplXML and JMSDataBindingImplJava) cannot resolve the type to an element.

Schema:

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://www.ibm.com" xmlns:tns="http://www.ibm.com">
 <!-- global element required but missing -->

<complexType name="Quote">
		<sequence>
			<element name="symbol" type="string"></element>
		<element name="price" type="float"></element>
		</sequence>
	</complexType>
</schema>

If you receive an exception such as:

com.ibm.websphere.sca.ServiceRuntimeException: 
caused by: java.lang.IllegalArgumentException: 
{Quote}Quote is not corresponding to a global element.

Or

[8/25/06 10:20:40:938 PDT] 00000054 FFDC          Z 
com.ibm.ws.sca.databinding.impl.DataBindingImplXML 
com.ibm.ws.sca.databinding.impl.DataBindingImplXML#002 Exception:
                                
org.eclipse.emf.ecore.xmi.FeatureNotFoundException: 
Feature 'Quote' not found. (sca:/dataObject.xml, 2, 126)

This may mean you need to define a global element:

<?xml version="1.0" encoding="UTF-8"?>
<schema xmlns="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://www.ibm.com" xmlns:tns="http://www.ibm.com">

<element name="Quote" type="tns:Quote"></element> <!-- global element required -->
	
<complexType name="Quote">
		<sequence>
			<element name="symbol" type="string"></element>
			<element name="price" type="float"></element>
		</sequence>
	</complexType>
	
</schema>

JMS based SCA messages not appearing in the failed event manager

Why and when to perform this task

If SCA messages originated through a JMS interaction fail, you would expect to find these messages in the failed event manager. If such messages are not appearing in the failed event manager, ensure that the underlying SIB destination of the JMS Destination has a maximum failed deliveries value greater than 1. Setting this value to 2 or more enables interaction with the failed event manager during SCA invocations for the JMS bindings.

WebSphere MQ JMS based SCA Messages not appearing in the failed event manager

Why and when to perform this task

If SCA messages originated through a WebSphere MQ JMS interaction fail, you would expect to find these messages in the failed event manager. If such messages are not appearing in the failed event manager, ensure that the value of the maximum retries property on the underlying listener port is equal to or greater than 1. Setting this value to 1 or more enables interaction with the failed event manager during SCA invocations for the MQ JMS bindings.

Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)