Bug 1147506 - [GSS](6.3.z) Excessive logging when a JMS message is received
Summary: [GSS](6.3.z) Excessive logging when a JMS message is received
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Remoting
Version: 6.3.2
Hardware: Unspecified
OS: Windows
high
high
Target Milestone: CR1
: EAP 6.3.3
Assignee: baranowb
QA Contact: Jitka Kozana
URL: https://access.redhat.com/support/cas...
Whiteboard:
Depends On: 1153281
Blocks: eap633-payload
TreeView+ depends on / blocked
 
Reported: 2014-09-29 12:38 UTC by Shaun Appleton
Modified: 2019-08-19 12:40 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
: 1153281 (view as bug list)
Environment:
Last Closed: 2019-08-19 12:40:42 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3974 0 Major Coding In Progress Move 'Channel end notification received, closing channel' to DEBUG 2014-10-13 21:03:50 UTC

Description Shaun Appleton 2014-09-29 12:38:01 UTC 
When a remote jms queue is located the following is seen:

2014-09-25 16:48:29,327 INFO  [org.jboss.as.naming] (Remoting "jeev6dev01_200" task-1) JBAS011806: Notification de fin de canal reçue, fermeture du canal Channel ID 0cb79bd5 (inbound) of Remoting connection 53a1933a to /10.23.132.245:57733


This is due to org.jboss.as.naming.NamingLogger where the following is used:

  @LogMessage(level=Logger.Level.INFO)
  @Message(id=11806, value="Channel end notification received, closing channel %s")
  public abstract void closingChannelOnChannelEnd(Channel paramChannel);


Changin this to 

  @LogMessage(level=Logger.Level.DEBUG)

Would ensure that an INFO log event is not seen every time a jms message is sent to the server.
Comment 1 JBoss JIRA Server 2014-10-13 21:03:51 UTC 
Brad Maxwell <bmaxwell> updated the status of jira WFLY-3974 to Coding In Progress
Comment 10 Ladislav Thon 2015-01-20 11:01:05 UTC 
Verified with EAP 6.3.3.CP.CR1.
Note You need to log in before you can comment on or make changes to this bug.