[jboss-jira] [JBoss JIRA] (WFWIP-148) Artemis logging codes/IDs have changed for CORE protocol

[Dimitris Andreadis (Jira)]

    [ https://issues.jboss.org/browse/WFWIP-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664163#comment-13664163 ] 

Dimitris Andreadis commented on WFWIP-148:
------------------------------------------

[~bilge], we know this will impact EAP customers if they depend on detecting the AMQ119007 error code, so what would be the impact if we keep the same codes for CORE and change them for AMQP instead? [~martyn-taylor] [~jbertram]

Then if we cannot decide which impact is worse, we could seek someone higher up (MarkL?) to make a decision.

Or, revert the https://issues.apache.org/jira/browse/ARTEMIS-1018 fix altogether, which seems to be only a minor issue, causing nevertheless some trouble

Or find some middle ground solution, like revert the change but add some CORE / AMQP string in the text message to allow distinguishing which protocol the failure refers to.

> Artemis logging codes/IDs have changed for CORE protocol
> --------------------------------------------------------
>
>                 Key: WFWIP-148
>                 URL: https://issues.jboss.org/browse/WFWIP-148
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: Artemis
>            Reporter: Miroslav Novak
>            Assignee: Justin Bertram
>            Priority: Blocker
>
> Artemis logging codes for CORE protocol has changed in scope of jira: https://issues.apache.org/jira/browse/ARTEMIS-1018
> For example in WF14 if standalone JMS client failed to connect then it was logged with code AMQ119007:
> {code}
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
> {code}
> but newly it would have code AMQ219007:
> {code}
> Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]
> {code}
> This is problem for any user/customer who had monitoring based on those codes as this will require to change it.
> The reason for change was because those codes were duplicated between AMQP and CORE protocol. As CORE protocol is default and AMQP is not supported for EAP ti would makes sense to change AMQP codes instead and keep codes for CORE protocol without any change. 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)