MDB TCKs that use topics are failing with 0.14 client. They were working with 0.10.

Take for example com/sun/ts/tests/jms/ee/mdb/mdb_msgPropsT

The TCK integration layer creates on the fly topic to which an MDB is bound. The code for this purpose is

topic = session.createTopic(name + ";{create:always, link:{x-bindings:[{exchange: 'amq.topic', key : '" + name + "'}]}}");
final MessageProducer producer = session.createProducer(topic);
producer.close();

And follows the proposal at #734059.

Regardless of it it seems that the messages are delivered multiple times to MDB which causes havoc in the test.

If I modify JBoss EJB DD to this form
    <message-driven>
      <ejb-name>MDB_TOPIC</ejb-name>
      <destination-jndi-name>jms_ee_mdb_mdb_msgPropsT_MDB_TOPIC</destination-jndi-name>
      <mdb-user>j2ee</mdb-user>
      <mdb-passwd>j2ee</mdb-passwd>
      <resource-adapter-name>qpid-ra.rar</resource-adapter-name>
      <activation-config>
        <activation-config-property>
          <activation-config-property-name>ConnectionURL</activation-config-property-name>
          <activation-config-property-value>amqp://guest:guest@/test?brokerlist='tcp://mrg01.mw.lab.eng.bos.redhat.com:5672'&amp;sync_ack='true'&amp;maxprefetch='0'</activation-config-property-value>
        </activation-config-property>
        <activation-config-property>
          <activation-config-property-name>maxSession</activation-config-property-name>
          <activation-config-property-value>1</activation-config-property-value>
        </activation-config-property>
      </activation-config>

Then the test is passing again. So it seems that the culprit is defaul maxSession set to 15