-
Bug
-
Resolution: Done
-
Blocker
-
None
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:
Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ119007: Cannot connect to server(s). Tried with all available servers.]
but newly it would have code AMQ219007:
Caused by: ActiveMQNotConnectedException[errorType=NOT_CONNECTED message=AMQ219007: Cannot connect to server(s). Tried with all available servers.]
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.
- blocks
-
JBEAP-16563 Journal compacting doesn't work with JDK 11
- Closed
-
WFLY-11026 Journal compacting doesn't work with JDK 11
- Closed
- is cloned by
-
JBEAP-16621 Artemis logging codes/IDs have changed for CORE protocol
- Closed