[#AMQ-705] ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable - Apache ActiveMQ, Apache ServiceMix, Apache Camel

ActiveMQ

ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable

Created: 04/May/06 07:40 AM Updated: 04/May/06 01:42 PM

Return to search

Issue 1717 of 2405 issue(s)

<< Previous | AMQ-705 | Next >>

Component/s:

JCA Container

Affects Version/s:

3.2.1, 3.2.2, 3.2.3, 4.0 M4, 4.0 RC2, 4.0 RC3

Fix Version/s:

3.2.4, 4.0

Time Tracking:

Not Specified

File Attachments:

File Name	Date Attached	Attached By	Size
AMQ-705-activemq-3.patch	2006-05-04 10:06 AM	John Sisson	3 kB
AMQ-705-incubator-trunk.patch	2006-05-04 10:06 AM	John Sisson	3 kB

Description

« Hide

Found problem when using Geronimo with an incorrectly configured EJB 2.0 MDB that has:

<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>Durable</subscription-durability>
</message-driven-destination>

The above config doesn't make sense since subscription-durability is only applicable for Topics.

This resulted in a message that didn't directly point to the problem:

C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear myplan.xml
Error: Unable to distribute my.ear: JMS settings for
message-driven bean FooMDBean are not valid:
Invalid settings: clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested.

With the patch applied, the error will now be:

C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear wmyplan.xml
Error: Unable to distribute my.ear: JMS settings for
message-driven bean FooMDBean are not valid:
Invalid settings: subscriptionDurability cannot be set to: Durable when destinationType is set to javax.jms.Queue as it is only valid when destinationType is set to javax.jms.Topic. clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested.

All

Comments

Work Log

Change History

Subversion Commits

FishEye

Crucible

Sort Order:

John Sisson made changes - 04/May/06 07:43 AM

Field	Original Value	New Value
Attachment		AMQ-705-activemq-3.patch [ 14915 ]

John Sisson made changes - 04/May/06 07:44 AM

Attachment

AMQ-705-incubator-trunk.patch [ 14916 ]

John Sisson made changes - 04/May/06 07:46 AM

Assignee	John Sisson [ johnrsisson ]	Hiram Chirino [ chirino ]
Description	Found problem when using Geronimo with an incorrectly configured EJB 2.0 MDB that has: <message-driven-destination> <destination-type>javax.jms.Queue</destination-type> <subscription-durability>Durable</subscription-durability> </message-driven-destination> The above config doesn't make sense since subscription-durability is only applicable for Topics. This resulted in a message that didn't directly point to the problem: C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear myplan.xml Error: Unable to distribute my.ear: JMS settings for message-driven bean FooMDBean are not valid: Invalid settings: clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested. Invalid settings: clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested.	Found problem when using Geronimo with an incorrectly configured EJB 2.0 MDB that has: <message-driven-destination> <destination-type>javax.jms.Queue</destination-type> <subscription-durability>Durable</subscription-durability> </message-driven-destination> The above config doesn't make sense since subscription-durability is only applicable for Topics. This resulted in a message that didn't directly point to the problem: C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear myplan.xml Error: Unable to distribute my.ear: JMS settings for message-driven bean FooMDBean are not valid: Invalid settings: clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested. Invalid settings: clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested. With the patch applied, the error will now be: C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear wmyplan.xml Error: Unable to distribute my.ear: JMS settings for message-driven bean FooMDBean are not valid: Invalid settings: subscriptionDurability must be set to: Durable when destinationType is set to javax.jms.Queue. clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested. Invalid settings: subscriptionDurability must be set to: Durable when destinationType is set to javax.jms.Queue. clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested.

John Sisson made changes - 04/May/06 07:49 AM

Assignee

Hiram Chirino [ chirino ]

John Sisson [ johnrsisson ]

John Sisson made changes - 04/May/06 07:50 AM

Attachment

~~AMQ-705~~-activemq-3.patch [ 14915 ]

John Sisson made changes - 04/May/06 07:50 AM

Attachment

~~AMQ-705~~-incubator-trunk.patch [ 14916 ]

John Sisson made changes - 04/May/06 07:53 AM

Status

Open [ 1 ]

In Progress [ 3 ]

John Sisson made changes - 04/May/06 08:08 AM

Description

Found problem when using Geronimo with an incorrectly configured EJB 2.0 MDB that has:

         <message-driven-destination>
            <destination-type>javax.jms.Queue</destination-type>
            <subscription-durability>Durable</subscription-durability>
         </message-driven-destination>

The above config doesn't make sense since subscription-durability is only applicable for Topics.

This resulted in a message that didn't directly point to the problem:

C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear myplan.xml
    Error: Unable to distribute my.ear: JMS settings for
    message-driven bean FooMDBean are not valid:
    Invalid settings: clientId must be set since durable subscription
    was requested. subscriptionName must be set since durable
    subscription was requested.

        Invalid settings: clientId must be set since durable subscription
    was requested. subscriptionName must be set since durable
    subscription was requested.

With the patch applied, the error will now be:

C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear wmyplan.xml
    Error: Unable to distribute my.ear: JMS settings for
    message-driven bean FooMDBean are not valid:
    Invalid settings: subscriptionDurability must be set to: Durable
    when destinationType is set to javax.jms.Queue. clientId must be set
    since durable subscription was requested. subscriptionName must be
    set since durable subscription was requested.

        Invalid settings: subscriptionDurability must be set to: Durable
    when destinationType is set to javax.jms.Queue. clientId must be set
    since durable subscription was requested. subscriptionName must be
    set since durable subscription was requested.

Found problem when using Geronimo with an incorrectly configured EJB 2.0 MDB that has:

         <message-driven-destination>
            <destination-type>javax.jms.Queue</destination-type>
            <subscription-durability>Durable</subscription-durability>
         </message-driven-destination>

The above config doesn't make sense since subscription-durability is only applicable for Topics.

This resulted in a message that didn't directly point to the problem:

C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear myplan.xml
    Error: Unable to distribute my.ear: JMS settings for
    message-driven bean FooMDBean are not valid:
    Invalid settings: clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested.

With the patch applied, the error will now be:

C:\test>java -jar geronimo-1.1-SNAPSHOT\bin\deployer.jar --user system --password manager deploy my.ear wmyplan.xml
    Error: Unable to distribute my.ear: JMS settings for
    message-driven bean FooMDBean are not valid:
    Invalid settings: subscriptionDurability cannot be set to: Durable when destinationType is set to javax.jms.Queue as it is only valid when destinationType is set to javax.jms.Topic. clientId must be set since durable subscription was requested. subscriptionName must be set since durable subscription was requested.

John Sisson made changes - 04/May/06 10:06 AM

Attachment

AMQ-705-activemq-3.patch [ 14917 ]

John Sisson made changes - 04/May/06 10:06 AM

Attachment

AMQ-705-incubator-trunk.patch [ 14918 ]

John Sisson made changes - 04/May/06 10:08 AM

Assignee

John Sisson [ johnrsisson ]

Hiram Chirino [ chirino ]

Hiram Chirino made changes - 04/May/06 01:42 PM

Resolution		Fixed [ 1 ]
Status	In Progress [ 3 ]	Resolved [ 5 ]
Fix Version/s	4.1 [ 11691 ]
Fix Version/s		4.0 [ 11660 ]