[jboss-jira] [JBoss JIRA] (WFLY-4539) logging statement to trace remoting heartbeat
[
https://issues.jboss.org/browse/WFLY-4539?page=com.atlassian.jira.plugin....
]
Peter Palaga commented on WFLY-4539:
------------------------------------
[~dmlloyd] on one hand the downstream BZ asks for (1) "the option to log on the
client when the heartbeat message is *fired*", which we indeed do not provide, but on
the other hand we provide (2) an option on both server and client to log when a heartbeat
message is *received*.
From the downstream BZ steps to reproduce it is clear that they do not
know about (2), because they activate wrong log level (DEBUG instead of TRACE) for an
improper topic (org.jboss.remoting3 instead of org.jboss.remoting.remote,
org.jboss.remoting.remote.client, org.jboss.remoting.remote.connection and
org.jboss.remoting.remote.server).
regardless if (2) would serve their purpose, it is easy to add (1) and I am ready to send
a PR unless you want to veto it for some reason?
logging statement to trace remoting heartbeat
---------------------------------------------
Key: WFLY-4539
URL: https://issues.jboss.org/browse/WFLY-4539
Project: WildFly
Issue Type: Enhancement
Components: EJB
Affects Versions: JBoss AS7 7.2.0.Final
Reporter: Carsten Lichy-Bittendorf
Assignee: Peter Palaga
Priority: Minor
you can set the heartbeat on a remoting connection by setting:
remote.connection.default.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL
What is missing is the option to log on the client when the heartbeat message is fired.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)