You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2015/11/20 18:44:11 UTC

[jira] [Assigned] (ARTEMIS-246) Warn if the destination lookup for the MDB activation fails

     [ https://issues.apache.org/jira/browse/ARTEMIS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Bertram reassigned ARTEMIS-246:
--------------------------------------

    Assignee: Justin Bertram

> Warn if the destination lookup for the MDB activation fails
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-246
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-246
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Jeff Mesnil
>            Assignee: Justin Bertram
>
> in Artemis RA, the destination is by default looked up by JNDI using the destinationLookup (or destination) activation config properties.
> If the lookup fails, it will automatically create a JMS destination based on the destination name.
> There is a debug log in that case: "Unable to retrieve... etc." but I think this should be upgraded to a WARN log as it is a configuration issue that the user must be aware of.
> I'm not sure whether this is even a good idea to have this fallback when the JNDI lookup fails.
> Creating a client-side JMS destination can also be achieved by setting the destination activation config property *and* setting the useJNDI prop to false.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)