[
https://issues.apache.org/jira/browse/ARTEMIS-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661561#comment-16661561
]
ASF GitHub Bot commented on ARTEMIS-2130:
-----------------------------------------
Github user jbertram commented on the issue:
https://github.com/apache/activemq-artemis/pull/2376
I agree with @michaelandrepearce - JMS specifics should not be built into
the console (or any part of the core broker, for that matter). The session
contains generic meta-data which can be displayed on the console and then users
can interpret that meta-data as necessary for their applications. We've worked
hard to get JMS stuff out of the core broker to better support other protocols.
Let's not add it back in.
> Web console display blank ClientID for the core client.
> -------------------------------------------------------
>
> Key: ARTEMIS-2130
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2130
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.6.3
> Reporter: Shailendra Kumar singh
> Priority: Major
> Attachments: ConnectionView.png, ProducersView.png
>
>
> Web console display blank ClientID for the core client.
> connection.setClientID("Test2"); Web console display blank, attached
> screen-shot.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
