Problems using iMQ 2.0SP1 with iAS 6.5 MDBs.

My client is using iMQ 2.0 SP1 with a standalong java client and has set up a durable subscription within the java code. The durable subscription is listed using the iMQ admin tool. However, on iAS 6.5 client has deployed a message-driven bean that is using durable subsription. This time the durable subscription is NOT listed using the iMQ admin tool. Is this a known problem?

[400 byte] By [christenscreen] at [2007-11-25 8:07:27]
# 1

Given that they have configured the deployment descriptors according to the details in the dtd file they will have run into a problem because

one of the dtd comments is wrong. In the subscription-durability comments it says specify Durable or NonDurable, in fact this should be set

to true or false where true means durable.

This is the incorrect description:

<!--

The subscription-durability element specifies whether a JMS topic

subscription is intended to be durable or nondurable.

The subscription-durability element must be one of the two following:

<subscription-durability>Durable</subscription-durability>

<subscription-durability>NonDurable</subscription-durability>

Used in: message-driven-destination

-->

So what they should have should look something like this:

<durable-name>TopicEJBClientID</durable-name>

<message-driven-destination>

<destination-type>javax.jms.Topic</destination-type>

<subscription-durability>true</subscription-durability>

</message-driven-destination>

christenscreen at 2007-7-1 13:58:26 > top of Java-index,Application & Integration Servers,Sun Java System Message Queue...