activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-1253) AMQ Should Print a Warning (Or Throw an Exception) If Messages Are Received to a Non-Started Connection
Date Thu, 24 May 2007 10:36:35 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39147
] 

James Strachan commented on AMQ-1253:
-------------------------------------

For details, see the use of the warnAboutUnstartedConnectionTimeout property [on this page|http://cwiki.apache.org/ACTIVEMQ/connection-configuration-uri.html]

> AMQ Should Print a Warning (Or Throw an Exception) If Messages Are Received to a Non-Started
Connection
> -------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-1253
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1253
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: JMS client
>            Reporter: ocean
>             Fix For: 4.2.0
>
>
> The following scenario can occur:
> (1) Create a javax.jms.Connection but don't start it
> (2) Create a MessageConsumer on the Connection and subscribe to a Queue
> (3) Send messages to the Queue
> In this case (turning on trace logging) the messages will be received by the Connection
and they will silently be discarded. To the poor bloke who forgot to call Connection.start()
it looks like the messages have simply disappeared and the universe is torturing him. He then
must endure the horror of tracing through his code trying to find out why some cruel god is
consuming his messages only to discover six hours later that he forgot to call Connection.start()
and thus the punchline of the cruel joke that is his life is delivered and he's prompted to
thoughts of self destruction and spilling the blood innocents.
> To prevent this scenario it would be nice if AMQ printed a warning (or better yet threw
an exception) indicating that activity is occurring on a Connection that has not been started.
In this case the programmer could clearly see that he forgot to call Connection.start(), happily
add the line and continue on into the brave future!

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message