Why event published by composite publisher is not delivered to subscriber

Question

Hello.
Why event published by composite publisher is not delivered to subscriber but same event published by test Business event is delivered?
Which points are necessary to deliver published event to subscriber. I use same EDL/XSD files for publisher and subscriber to assure using same event.
Here is example content of message published by composite and used to publish by test Business event:
<message>
<properties>
<property name="tracking.compositeInstanceId" value="220056"/>
<property name="tracking.ecid" value="531982e54d355120:-5544feab:1320045804b:-7ffe-0000000000182444"/>
<property name="tracking.conversationId" value="52%401315226747"/>
</properties>
<parts>
<part name="payload">
<BasketInvoiceCollection>
<BasketInvoice>
<basketInvoiceId>52</basketInvoiceId>
<loggedUserId>1</loggedUserId>
<statusId>1</statusId>
</BasketInvoice>
</BasketInvoiceCollection>
</part>
</parts>
</message>
I found problem in server diagnostic log about XA transaction. For information I running against MySQL database.
Edited by: Peter551059 on Sep 6, 2011 2:40 PM

Answer 1

Problem solved. Many configuration changes are made in DBAdapter configuration and Connection pool configuration.
Home >Summary of Deployments >DbAdapter >Summary of JDBC Data Sources >MyOutboundConnectionPool
Driver Class Name: com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
for XA transaction
Home >Summary of JDBC Data Sources >webjet >Summary of Deployments >DbAdapter >Summary of JDBC Data Sources >MyOutboundConnectionPool: Outbound Connection Properties
platformClassName     org.eclipse.persistence.platform.database.MySQLPlatform
for MySQL
Transaction Support: XA Transaction