Red Hat Bugzilla – Bug 535363
Double slash in event source path causes source field to be truncated
Last modified: 2015-02-01 18:25:20 EST
How to repeat:
Create an RHQ server event source with a path like /home/jonqa/jon/jon-server-2.2.0.GA//logs/autoTestEvent.log (contains double slash, which is legal in unix and java)
Create that file and insert some events into it (you can do something like :
tail -50 rhq-server-log4j.log >> autoTestEvent.log
wait a few minutes, and check the events tab for the RHQ server. see screenshot, the source field is truncated.
I was able to repeat the problem with a path of /home/jonqa/jon/jon-server-2.2.0.GA/logs/autoTestEvent1241812532990.log
(no double-slash). This may be a cosmetic issue, since the "Source" column is truncated, but if you click the event details, you can see that the source path is properly shown, and you can also filter correctly. ie, filtering on "logs" which was truncated.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2067
Imported an attachment (id=368743)
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.
new = Tracking + FutureFeature + SubBug
making sure we're not missing any bugs in rhq_triage
this page has been reimplemented in gwt
Tested in build#170 (Version: 4.1.0-SNAPSHOT Build Number: 67e6127)
Not able to create a Log Event Source. Trying to create an event source displays IndexOutOfBoundsException. A separate bug (Bug#717921) is already filed to address this issue.
Verified on Version: 4.1.0-SNAPSHOT Build Number: 601a57e
The event source path is displayed properly. Please refer the attached screenshot. Also verified on clicking the event details which displayed the source location properly.
Marking as verified.
Created attachment 516874 [details]
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.