activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Co (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1071) Activemq connection factory silently ignores the erroneous arguments in broker url
Date Mon, 18 Jun 2007 08:58:34 GMT

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

Adrian Co resolved AMQ-1071.
----------------------------

       Resolution: Fixed
    Fix Version/s: 5.0.0

Fix added here: http://svn.apache.org/viewvc?view=rev&rev=548260

Test case here: http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/transport/failover/FailoverUriTest.java?view=auto&rev=548260

Though it should be noted that errors within the transport list is ignored. i.e. failover:(tcp://localhost:61616?cheese=abc)
will not be flagged as erroneous because the tcp part is configured during actual connection
only. Any exceptions during connection in failover will result in the transport trying to
reconnect. In this case unless the failover transport is configured to fail after n retries
it will hang. I'm not sure if this is a serious bug or an expected side effect.

Let me know if it works for you Dileepan. Thanks! :)

> Activemq connection factory silently ignores the erroneous arguments in broker url
> ----------------------------------------------------------------------------------
>
>                 Key: AMQ-1071
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1071
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>         Environment: Linux
>            Reporter: Dileepan K
>            Assignee: Adrian Co
>            Priority: Minor
>             Fix For: 5.0.0
>
>
> When an erroneous argument is passed to the broker url with failover, activemq connection
factory ignores the error. However if failover is removed, it does throw exception. 
> Here is the example
> 1. failover:(tcp://localhost:62012)?jms.prefetchPolicy.all=10&amp;wireFormat.maxInactivityDuration=0&amp;jms.optimizeAcknowledge=false
> 2. tcp://localhost:62012?jms.prefetchPolicy.all=10&amp;wireFormat.maxInactivityDuration=0&amp;jms.optimizeAcknowledge=false
> Only the # 2 throws exception as jms.prefetchPolicy.all is an invalid argument here

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