Bug 535363 (RHQ-2067)

Summary: Double slash in event source path causes source field to be truncated
Product: [Other] RHQ Project Reporter: Jeff Weiss <jweiss>
Component: EventsAssignee: Charles Crouch <ccrouch>
Status: CLOSED CURRENTRELEASE QA Contact: Jeff Weiss <jweiss>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.2CC: cwelton, dajohnso, hbrock, mazz, skondkar
Target Milestone: ---Keywords: SubBug
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-2067
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
2.2.0 GA, linux
Last Closed: 2013-09-02 07:26:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 565628, 585306    
Attachments:
Description Flags
eventpath.png
none
Screenshot none

Description Jeff Weiss 2009-05-08 14:14:00 UTC 
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.
Comment 1 Jeff Weiss 2009-05-08 20:39:12 UTC 
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.
Comment 2 Red Hat Bugzilla 2009-11-10 20:57:06 UTC 
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2067
Imported an attachment (id=368743)
Comment 3 wes hayutin 2010-02-16 16:58:47 UTC 
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug
Comment 4 wes hayutin 2010-02-16 17:03:31 UTC 
making sure we're not missing any bugs in rhq_triage
Comment 8 John Mazzitelli 2011-02-17 16:51:25 UTC 
this page has been reimplemented in gwt
Comment 9 Sunil Kondkar 2011-07-05 10:57:27 UTC 
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.
Comment 10 Sunil Kondkar 2011-08-05 11:33:04 UTC 
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.
Comment 11 Sunil Kondkar 2011-08-05 11:34:14 UTC 
Created attachment 516874 [details]
Screenshot
Comment 12 Heiko W. Rupp 2013-09-02 07:26:21 UTC 
Bulk closing of issues that were VERIFIED, had no target release and where the status changed more than a year ago.