You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "John Sisson (JIRA)" <ji...@apache.org> on 2006/05/04 09:41:37 UTC
[jira] Created: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
---------------------------------------------------------------------------------------------------------------------------
Key: AMQ-705
URL: https://issues.apache.org/activemq/browse/AMQ-705
Project: ActiveMQ
Type: Bug
Components: JCA Container
Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
Reporter: John Sisson
Assigned to: John Sisson
Priority: Minor
Fix For: 4.1, 3.2.4
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
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.
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.
was:
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.
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
Attachment: AMQ-705-activemq-3.patch
Attached patch for review for activemq-3 branch.
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
> Attachments: AMQ-705-activemq-3.patch, AMQ-705-incubator-trunk.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
Attachment: (was: AMQ-705-incubator-trunk.patch)
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
Hiram Chirino resolved AMQ-705:
-------------------------------
Fix Version: 4.0
(was: 4.1)
Resolution: Fixed
Great patch! Applied!
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: Hiram Chirino
> Priority: Minor
> Fix For: 4.0, 3.2.4
> Attachments: AMQ-705-activemq-3.patch, AMQ-705-incubator-trunk.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
Attachment: (was: AMQ-705-activemq-3.patch)
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
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.
was:
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.
Assign To: Hiram Chirino (was: John Sisson)
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: Hiram Chirino
> Priority: Minor
> Fix For: 4.1, 3.2.4
> Attachments: AMQ-705-activemq-3.patch, AMQ-705-incubator-trunk.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
Attachment: AMQ-705-incubator-trunk.patch
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
> Attachments: AMQ-705-activemq-3.patch, AMQ-705-incubator-trunk.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Work started: (AMQ-705) ActiveMQActivationSpec does not
validate that DestinationType is set to Topic when SubscriptionDurability
is set to Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
Work on AMQ-705 started by John Sisson
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
Attachment: AMQ-705-activemq-3.patch
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
> Attachments: AMQ-705-activemq-3.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson updated AMQ-705:
----------------------------
Attachment: AMQ-705-incubator-trunk.patch
Attached patch for review for incubator trunk.
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
> Attachments: AMQ-705-activemq-3.patch, AMQ-705-incubator-trunk.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson reassigned AMQ-705:
-------------------------------
Assign To: John Sisson (was: Hiram Chirino)
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: John Sisson
> Priority: Minor
> Fix For: 4.1, 3.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-705) ActiveMQActivationSpec does not validate
that DestinationType is set to Topic when SubscriptionDurability is set to
Durable
Posted by "John Sisson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-705?page=all ]
John Sisson reassigned AMQ-705:
-------------------------------
Assign To: Hiram Chirino (was: John Sisson)
> ActiveMQActivationSpec does not validate that DestinationType is set to Topic when SubscriptionDurability is set to Durable
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-705
> URL: https://issues.apache.org/activemq/browse/AMQ-705
> Project: ActiveMQ
> Type: Bug
> Components: JCA Container
> Versions: 3.2.1, 3.2.2, 4.0 M4, 3.2.3, 4.0 RC2, 4.0 RC3
> Reporter: John Sisson
> Assignee: Hiram Chirino
> Priority: Minor
> Fix For: 4.1, 3.2.4
> Attachments: AMQ-705-activemq-3.patch, AMQ-705-incubator-trunk.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira