Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358473 - Exception logged when service.pid contains characters restricted by JMX
Summary: Exception logged when service.pid contains characters restricted by JMX
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows Server 2003
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Chris Frost CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 14:21 EDT by szetheli+eclipse CLA
Modified: 2011-09-29 10:03 EDT (History)
1 user (show)

See Also:


Attachments
Exception when srevice.pid contains : (1.93 KB, text/plain)
2011-09-21 14:22 EDT, szetheli+eclipse CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description szetheli+eclipse CLA 2011-09-21 14:21:57 EDT
Build Identifier: Virgo 2.1.0.RELEASE

Virgo exposes the configuration service.pid via JMX for each registered configuration.  It uses the service.pid as part of the ObjectName, however, it apparently fails to sanitize the service.pid before passing it to JMX.  If that service.pid contains characters that are restricted in JMX, an exception is thrown

Reproducible: Always

Steps to Reproduce:
1. Create a service.pid with configuration, in the exception example: "urn:expedia:cc:samples:sampleservice:v2:contract"
2. Start virgo
3. Look at the logs
Comment 1 szetheli+eclipse CLA 2011-09-21 14:22:34 EDT
Created attachment 203798 [details]
Exception when srevice.pid contains :
Comment 2 Chris Frost CLA 2011-09-29 10:03:18 EDT
Fixed on master. Any property values that contain ':' or ',' or '"' or '=' will now be automatically quoted.