Bug 1095361 - Log level for websocket activation failure is INFO
Summary: Log level for websocket activation failure is INFO
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: DR1
: EAP 6.4.0
Assignee: Rémy Maucherat
QA Contact: Michael Cada
URL:
Whiteboard:
Depends On: 1138672
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-07 14:27 UTC by Vineet Reynolds
Modified: 2019-08-19 12:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Enhancement
Embargoed:


Attachments (Terms of Use)

Description Vineet Reynolds 2014-05-07 14:27:33 UTC
Description of problem:

The websocket activation failure message on Java 6 is at level INFO. This can be missed within the log files. Websocket capabilties of the deployed app are broken, and thus the level should be WARN or higher.

Version-Release number of selected component (if applicable): EAP 6.3 ER3; jbossweb-7.4.2.Final-redhat-1


How reproducible:


Steps to Reproduce:
1. Start JBoss EAP 6.3 ER3 with a Java 6 VM
2. Deploy a websocket-enabled app onto it. For e.g.: https://github.com/jboss-developer/jboss-eap-quickstarts/pull/941
3. Note the messages in the log. The requirement for Java 6 requirement is logged with level INFO, like so:
"18:45:04,821 INFO  [org.apache.tomcat.websocket] (ServerService Thread Pool -- 64) JBWEB008813: WebSocket support is not available when running on Java 6"

Actual results:

The message should have level WARN or higher.

Expected results:

The message has INFO level and can be missed.

Additional info:

Comment 1 Radim Hatlapatka 2014-08-05 07:02:46 UTC
This issue is still valid in latest build EAP 6.3.0.ER10.

Comment 2 Rémy Maucherat 2014-09-04 15:20:56 UTC
r2502 in web.

Comment 3 Kabir Khan 2014-09-08 11:57:17 UTC
Fixed by component upgrade to JBoss Web 7.5.0.Beta1: https://bugzilla.redhat.com/show_bug.cgi?id=1138672

Comment 4 Radim Hatlapatka 2014-09-17 14:39:43 UTC
Verified with EAP 6.4.0.DR1.1 that the log level is now WARN.


Note You need to log in before you can comment on or make changes to this bug.