[
https://issues.apache.org/jira/browse/ARTEMIS-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clebert Suconic updated ARTEMIS-5206:
-------------------------------------
Description:
Certain exception types, for example ActiveMQRemoteDisconnectException are
showing the following exception trace when thrown:
{code:java}
org.apache.activemq.artemis.api.core.ActiveMQRemoteDisconnectException: null
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.connectionDestroyed(RemotingServiceImpl.java:600)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMAcceptor$Listener.connectionDestroyed(InVMAcceptor.java:296)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.internalClose(InVMConnection.java:157)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.disconnect(InVMConnection.java:166)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMAcceptor.disconnect(InVMAcceptor.java:246)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnector$Listener.connectionDestroyed(InVMConnector.java:274)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.internalClose(InVMConnection.java:157)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.close(InVMConnection.java:145)
~[classes/:?]
{code}
It would be more aesthetically if they were providing "" as a description
instead of "null"
This caught my attention on logs as I thought it was a NullPointerException.
This is just a trivial change.
was:
Certain exception types, for example ActiveMQRemoteDisconnectException are
showing the following exception trace when thrown:
org.apache.activemq.artemis.api.core.ActiveMQRemoteDisconnectException: null
at
org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.connectionDestroyed(RemotingServiceImpl.java:600)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMAcceptor$Listener.connectionDestroyed(InVMAcceptor.java:296)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.internalClose(InVMConnection.java:157)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.disconnect(InVMConnection.java:166)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMAcceptor.disconnect(InVMAcceptor.java:246)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnector$Listener.connectionDestroyed(InVMConnector.java:274)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.internalClose(InVMConnection.java:157)
~[classes/:?]
at
org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.close(InVMConnection.java:145)
~[classes/:?]
It would be more aesthetically if they were providing "" as a description
instead of "null"
This caught my attention on logs as I thought it was a NullPointerException.
This is just a trivial change.
> Provide description = "" instead of null in certain exception instances
> -----------------------------------------------------------------------
>
> Key: ARTEMIS-5206
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5206
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.38.0
> Reporter: Clebert Suconic
> Assignee: Clebert Suconic
> Priority: Trivial
> Fix For: 2.39.0
>
>
> Certain exception types, for example ActiveMQRemoteDisconnectException are
> showing the following exception trace when thrown:
> {code:java}
> org.apache.activemq.artemis.api.core.ActiveMQRemoteDisconnectException: null
> at
> org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl.connectionDestroyed(RemotingServiceImpl.java:600)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMAcceptor$Listener.connectionDestroyed(InVMAcceptor.java:296)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.internalClose(InVMConnection.java:157)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.disconnect(InVMConnection.java:166)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMAcceptor.disconnect(InVMAcceptor.java:246)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnector$Listener.connectionDestroyed(InVMConnector.java:274)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.internalClose(InVMConnection.java:157)
> ~[classes/:?]
> at
> org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection.close(InVMConnection.java:145)
> ~[classes/:?]
> {code}
> It would be more aesthetically if they were providing "" as a description
> instead of "null"
> This caught my attention on logs as I thought it was a NullPointerException.
> This is just a trivial change.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
