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

["Justin Bertram (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018398#comment-15018398 ] 

Justin Bertram commented on ARTEMIS-246:
----------------------------------------

I agree that it might not be a good idea to have this silent fallback behavior when the JNDI look-up fails.  This was added way back in April 2009 (see 06d01a9c0f5b89994be900c73318dce95ce6daa2 in the HornetQ git repo).  Furthermore, this used to be logged at INFO level, but was change to DEBUG in 2012 (see 55f6e60bbcb7118b68653fe9e6d136393eefef1e in the HornetQ git repo).  

I don't mind changing the logging to WARN, but I wonder if we should just let the JNDI lookup fail without creating the destination.  In my opinion, a JNDI lookup failure indicates a bad configuration somewhere which we shouldn't try to work around.  Do you have any thoughts on this, [~clebertsuconic]?


> 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
>
> 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)