geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-4625) JMS statistics does not work correctly while the server url is of vm protocol
Date Wed, 01 Jul 2009 08:42:47 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725971#action_12725971
] 

Ivan commented on GERONIMO-4625:
--------------------------------

The question is that in the connector plan, we usually use tcp://****:61613 or vm://localhost:61613.
Currently, I need  to compare those urls to the listening addresses of existed brokers to
detect the right broker name. Due to various style of those urls, for example, the listening
address maybe tcp://0.0.0.0:61613, the url in the plan maybe something like tcp://localhost:61613.
I just feel it is hard to do the match,
Not sure there is a better way to do this, :-(

> JMS statistics does not work correctly while the server url is of vm protocol
> -----------------------------------------------------------------------------
>
>                 Key: GERONIMO-4625
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4625
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.2
>         Environment: WIndows XP
> JDK 1.5.0
>            Reporter: Ivan
>            Priority: Minor
>
> While doing the statistics for queue, we need the name of the broker, so that we could
query the status in the MBeanServer by the borker name, current codes could not handle the
server url like vm://.

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