| Anonymous | Login | Signup for a new account | 04-23-2024 20:49 PDT |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0002640 | [Resin] | minor | always | 04-29-08 18:00 | 05-12-08 12:21 | ||||
| Reporter | remilon | View Status | public | ||||||
| Assigned To | ferg | ||||||||
| Priority | normal | Resolution | fixed | Platform | |||||
| Status | closed | OS | |||||||
| Projection | none | OS Version | |||||||
| ETA | none | Fixed in Version | 3.1.7 | Product Version | 3.1.5 | ||||
| Product Build | |||||||||
| Summary | 0002640: Change log level of response log in PingThread | ||||||||
| Description |
In PingThread, whenever a ping fails, the entire contents of the response are written to the log along with the normal log message. This is great when PingThread is used normally. However, we have extended and modified it a bit to fail the ping based on other criteria. This means that when the ping fails, it can get a full HTML page in the response. Seeing these in the logs is cumbersome. It would be great if the response char buffer could be logged at a lower level so it can be turned on and off. |
||||||||
| Steps To Reproduce | |||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
 Relationships |
|
| There are no notes attached to this issue. |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 04-29-08 18:00 | remilon | New Issue | |
| 04-30-08 11:53 | remilon | Issue Monitored: remilon | |
| 05-12-08 12:21 | ferg | Assigned To | => ferg |
| 05-12-08 12:21 | ferg | Status | new => closed |
| 05-12-08 12:21 | ferg | Resolution | open => fixed |
| 05-12-08 12:21 | ferg | Fixed in Version | => 3.1.7 |
| Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |  |
