Bug 1213316 - [GSS](6.4.z) logging statement to trace remoting heartbeat
Summary: [GSS](6.4.z) logging statement to trace remoting heartbeat
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.3.3
Hardware: All
OS: All
unspecified
low
Target Milestone: CR1
: EAP 6.4.14
Assignee: Peter Palaga
QA Contact: Jiří Bílek
URL:
Whiteboard:
Depends On:
Blocks: eap6414-payload 1419495
TreeView+ depends on / blocked
 
Reported: 2015-04-20 10:25 UTC by Carsten Lichy-Bittendorf
Modified: 2019-05-20 11:44 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 08:21:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-8306 0 'Minor' 'Verified' '[GSS] (7.1.0) logging statement to trace remoting heartbeat' 2019-12-02 10:10:51 UTC
Red Hat Issue Tracker JBEAP-8307 0 'Minor' 'Pull Request Sent' '[GSS] (7.0.z) logging statement to trace remoting heartbeat' 2019-12-02 10:10:51 UTC
Red Hat Issue Tracker REM3-255 0 'Minor' 'Resolved' 'logging statement to trace remoting heartbeat' 2019-12-02 10:10:51 UTC
Red Hat Issue Tracker WFLY-4539 0 'Minor' 'Closed' 'logging statement to trace remoting heartbeat' 2019-12-02 10:10:51 UTC

Description Carsten Lichy-Bittendorf 2015-04-20 10:25:00 UTC 
Description of problem:

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.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. set remote.connection.default.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL
2. enable org.jboss.remoting3 logging on DEBUG
3. create remoting connection and check log statements

Actual results:
- debug messages on heartbeat not available

Expected results:
- debug messages on heartbeat every beat available

Additional info:
- https://issues.jboss.org/browse/WFLY-4539
Comment 7 Jiří Bílek 2017-03-03 07:57:27 UTC 
For clear:

Steps to Reproduce:
1. set remote.connection.default.connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL
2. enable org.jboss.remoting logging on TRACE
3. create remoting connection and check log statements

Expected results:
2017-03-02 16:26:49,575 3274  TRACE [org.jboss.remoting.remote.connection] (Remoting "config-based-ejb-client-endpoint" write-1:) Sending connection alive


Verified with EAP 6.4.14.CP.CR1
Comment 8 Petr Penicka 2017-03-23 08:21:15 UTC 
Released with EAP 6.4.14 on March 14 (ZIPs) and March 22 (RPMs).
Note You need to log in before you can comment on or make changes to this bug.