Back to bug 1031448
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Osamu Nagano | 2013-11-18 02:07:39 UTC | Link ID | JBoss Issue Tracker WFLY-2524 | |
| Brian Stansberry | 2013-11-18 15:51:53 UTC | CC | brian.stansberry | |
| Osamu Nagano | 2013-12-06 04:19:59 UTC | Target Release | --- | EAP 6.2.CP0a |
| mark yarborough | 2013-12-17 00:28:21 UTC | Target Release | EAP 6.2.CP0a | EAP 6.3.0 |
| Osamu Nagano | 2013-12-17 07:53:28 UTC | Target Release | EAP 6.3.0 | EAP 6.2.1 |
| Blocks | 1027004 | |||
| Brad Maxwell | 2014-01-08 21:05:27 UTC | Target Release | EAP 6.2.1 | EAP 6.2.2 |
| CC | bmaxwell | |||
| Blocks | 1027004 | 1049365 | ||
| Radim Hatlapatka | 2014-01-10 08:31:06 UTC | CC | rhatlapa | |
| mark yarborough | 2014-01-14 09:14:22 UTC | CC | myarboro | |
| Summary | logging-profile works for a servlet, but doesn't for a JSP | [GSS] (6.2.x) logging-profile works for a servlet, but doesn't for a JSP | ||
| mark yarborough | 2014-01-14 09:15:49 UTC | Flags | needinfo?(bmaxwell) | |
| Kyle Lape | 2014-01-22 18:41:12 UTC | CC | klape | |
| Carlo de Wolf | 2014-02-11 08:05:58 UTC | Target Release | EAP 6.2.2 | EAP 6.3.0 |
| CC | cdewolf | |||
| Blocks | 1049365 | |||
| Brad Maxwell | 2014-02-19 17:50:58 UTC | Summary | [GSS] (6.2.x) logging-profile works for a servlet, but doesn't for a JSP | [GSS] (6.3.0) logging-profile works for a servlet, but doesn't for a JSP |
| Flags | needinfo?(bmaxwell) | |||
| Scott Mumford | 2014-07-04 03:57:04 UTC | CC | jperkins, smumford | |
| Doc Text | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. Workaround (if any): Result: | |||
| Doc Type | Bug Fix | Known Issue | ||
| Flags | needinfo?(jperkins) | |||
| Kyle Lape | 2014-07-04 16:08:10 UTC | Doc Text | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. Workaround (if any): Result: | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP -- all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. Workaround (if any): Result: |
| Scott Mumford | 2014-07-06 19:20:02 UTC | Flags | needinfo?(jperkins) | needinfo- |
| Scott Mumford | 2014-07-08 02:26:40 UTC | Doc Text | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP -- all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. Workaround (if any): Result: | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP -- all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. |
| Scott Mumford | 2014-07-15 02:10:39 UTC | Doc Text | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP -- all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP; all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. |
| Dominik Pospisil | 2014-08-04 09:46:22 UTC | Status | NEW | ASSIGNED |
| CC | dpospisi | |||
| Assignee | jperkins | dpospisi | ||
| Nikoleta Hlavickova | 2014-08-13 11:09:32 UTC | Target Release | EAP 6.3.0 | EAP 6.4.0 |
| Severity | unspecified | urgent | ||
| James Perkins | 2014-09-02 21:58:31 UTC | Link ID | JBoss Issue Tracker LOGMGR-111 | |
| Assignee | dpospisi | jperkins | ||
| James Perkins | 2014-09-11 18:07:25 UTC | Depends On | 1140417 | |
| James Perkins | 2014-09-11 20:18:35 UTC | Status | ASSIGNED | POST |
| Kabir Khan | 2014-09-17 19:37:55 UTC | Status | POST | MODIFIED |
| CC | kkhan | |||
| Target Milestone | --- | DR2 | ||
| Vladimir Dosoudil | 2014-09-23 12:44:21 UTC | Status | MODIFIED | ON_QA |
| Nikoleta Hlavickova | 2014-09-25 14:27:44 UTC | Status | ON_QA | VERIFIED |
| Lucas Costi | 2015-01-27 01:26:59 UTC | CC | lcosti | |
| Doc Text | In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP; all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. | ** Needs bug fix text In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP; all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. | ||
| Doc Type | Known Issue | Bug Fix | ||
| Scott Mumford | 2015-03-02 01:43:17 UTC | Doc Text | ** Needs bug fix text In this release of JBoss EAP 6, logging profiles will work as expected for a servlet, but will not work for a JSP; all log messages from a JSP will go to the system log context. This is becasue the class loader being checked is a `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue is expected to be resolved in a future release of the product. | In a previous release of JBoss EAP 6, logging profiles worked as expected for a servlet, but did not work for a JSP; all log messages from a JSP went to the system log context. This issue presented because the class loader that was checked was `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue has been resolved by .... |
| Flags | needinfo?(jperkins) | |||
| James Perkins | 2015-03-02 16:45:21 UTC | Flags | needinfo?(jperkins) | |
| Scott Mumford | 2015-03-02 22:57:01 UTC | Doc Text | In a previous release of JBoss EAP 6, logging profiles worked as expected for a servlet, but did not work for a JSP; all log messages from a JSP went to the system log context. This issue presented because the class loader that was checked was `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue has been resolved by .... | In a previous release of JBoss EAP 6, logging profiles worked as expected for a servlet, but did not work for a JSP; all log messages from a JSP went to the system log context. This issue presented because the class loader that was checked was `org.apache.jasper.servlet.JasperLoader` with a parent class loader of the class loader that was registered for the log context. This issue has been resolved by adding an option to the log manager to recursively check a class loader's parent for a LogContext. |
| Russell Dickenson | 2017-10-10 00:13:22 UTC | Docs Contact | rdickens | |
| PnT Account Manager | 2018-03-05 15:29:27 UTC | CC | rhatlapa | |
| PnT Account Manager | 2018-03-06 20:36:59 UTC | CC | smumford | |
| PnT Account Manager | 2018-12-07 22:33:10 UTC | CC | lcosti | |
| PnT Account Manager | 2019-01-01 03:42:05 UTC | CC | dpospisi | |
| Jan Kurik | 2019-08-19 12:38:30 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2019-08-19 12:38:30 UTC |
Back to bug 1031448