[jboss-jira] [JBoss JIRA] Updated: (JBAS-6221) Default JmsActivationSpec ignore configuration in standardjboss.xml

[Adrian Brock (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-6221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrian Brock updated JBAS-6221:
-------------------------------

     Issue Type: Feature Request  (was: Bug)
    Component/s:     (was: JMS (JBossMQ))
                     (was: Deployers)
                     (was: JMS (JBoss Messaging))


This "bug report" contains at least two misunderstandings.

1) JMSXDeliveryCount is set by the jms provider. The DLQHandler just references it.
(Also, if your jms provider already has DLQ handling on the server - unlike JBossMQ -
then you don't need any DLQ handling within JBoss).

2) EJB3 has never referenced standardjboss.xml or had invoker/container-configurations
It uses aop and annotations to override/control configurations.

For (1) you should talk to your jms provider.

For  (2) I've discussed this before with the EJB3 team (I won't go into details here).
So I'm making this a feature request for them.

Discussions around this feature request belong in the forums  (which is where
also this post should have originated).

JIRA is for tracking what gets done, it is the release notes.
It should not be used for confusing other users with misguided speculation.

> Default JmsActivationSpec ignore configuration in standardjboss.xml
> -------------------------------------------------------------------
>
>                 Key: JBAS-6221
>                 URL: https://jira.jboss.org/jira/browse/JBAS-6221
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB3
>    Affects Versions: JBossAS-4.2.2.GA, JBossAS-4.2.3.GA
>            Reporter: mark.lowe
>            Assignee: Ales Justin
>
> Configuring an external MQ provider as DefaultJMSProvider works until there's an error and hence the genericdql handler is called into action. The GenericDQLHandler is broken is doesn't increment the JMSXDeliveryCount header, so being able to change the DLQHander implementation would be handy.. However, changing the values in standardjboss.xml has no effect. So you're forced into defining the DLQHander property in the ejb-jar.xml or worse still annotations for MDBs. 
> This also creates problems when attempting to change the confguration of any invokers used in these cases.. Mapping the invokers /containers in jboss.xml also has no effect.. The defaukt values of JmsActivationSpec is all you have.. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira