[
https://issues.apache.org/jira/browse/GERONIMO-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved GERONIMO-2609.
------------------------------------
Resolution: Fixed
Completed: At revision: 528221 in trunk.
None of these messages are getting displayed in the latest 2.0 code, but
cleaning up for completeness.
Changed println() to not use "/r", which is the invalid char in the 1.1.1
output.
Switched shutdown word "begun" to "started" to match the "Server shutdown
completed" phrasing.
> On linux and maybe other platform, the geronimo.out log file contains invalid
> characters
> ----------------------------------------------------------------------------------------
>
> Key: GERONIMO-2609
> URL: https://issues.apache.org/jira/browse/GERONIMO-2609
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Logging
> Affects Versions: 1.1.1
> Environment: RedHat 4U3-32 (and maybe other plateforms), IBM JDK 1.5
> SR3
> Reporter: Stéphane Hoblingre
> Assigned To: Donald Woods
> Fix For: 2.0-M5
>
>
> Before each "Stopping server..." message, an invalid character is put in the
> log file ( ^M if you edit the file with VI). This makes failing the java
> BufferedReader readline() method : it reads 2 lines instead of 1. The problem
> is that any Log Analysis tool in Java will fail to assign a message to a line
> number (line number is shifted).
> To be clear, in VI this is what you can see :
> (...)
> Server started.
> ^M <---- This is the problem, the
> line is "^M ", a ^M followed
> by spaces
> Stopping server...
> (...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
