Browse Version - Rio JIRA

All Projects : Rio : 4.0 M3 (Fix For Version)

Release Date: 29/Jan/10
Description: Third milestone release for 4.0
4.0 M3 Third milestone release for 4.0 2010-01-29T00-00

Select:

Summary

Popular Issues

	RIO-179	FIXED	Concurrent threads are accessing the same Sigar object
	RIO-171	FIXED	DeploymentMap does not include correct utilization for forked/exec'd services
	RIO-174	FIXED	Multiple resources for interface declaration being parsed wrong
	RIO-196	FIXED	Declare forked service environment
	RIO-167	FIXED	Guard against circular includes dependency in opstring
	RIO-178	FIXED	OpStringManagerProxy should get ProvisionMonitors from ServiceRegistrar at startup
	RIO-128	FIXED	DSL Improvements
	RIO-203	FIXED	Rio UI should display services that are not registered as warning
	RIO-172	FIXED	Threshold Management notification
	RIO-160	FIXED	Adding a ServiceElement should check for null codebase
	RIO-162	FIXED	Adding a service element to a deployed opstring should allow a provision listener
	RIO-213	FIXED	Allow mulitple groovy config files to be declared for the configuration element in an opstring
	RIO-166	FIXED	Bean lifecycle notifications done in wrong classloader context
	RIO-197	FIXED	Create a RMIClientSocketFatory
	RIO-199	FIXED	Drag and drop (or copy) OAR behavior
	RIO-153	FIXED	Excessive logging during file removal
	RIO-182	FIXED	Externalize test configuration, allowing RIo infrastructure to be started by test framework
	RIO-210	FIXED	Forked service should unbind from registry before discarding
	RIO-165	FIXED	Forked/Exec'd log location
	RIO-164	FIXED	Generated shell script for monitoring forked/exec'd services does not work on OSX 10.4
	RIO-184	FIXED	GroovyDSLOpStringParser should set the parent classloader when calling GroovyShell.parse()
	RIO-215	FIXED	Illegal characters in service name cause illegal log and pid files
	RIO-200	FIXED	Improve Association collection ability to provide getNextServiceItem
	RIO-156	FIXED	Lifecycle annotation support
	RIO-154	FIXED	Memory capability reports MB instead of bytes
	RIO-209	FIXED	NPE when association injection strategy is eager
	RIO-198	FIXED	OAR file not deleted on WIndows
	RIO-161	FIXED	OpStringManagerProxy should get ProvisionMonitors from LookupCache at startup
	RIO-168	FIXED	Optimize service bean fork approach, reduce resources required to activate and monitor forked services
	RIO-152	FIXED	Overriding Thread deadlock SLA for forked services
	RIO-155	FIXED	ProcessMemoryMonitor does not use JMX if Sigar cannot be loaded
	RIO-192	FIXED	Provide a way to obtain logs from distributed services
	RIO-149	FIXED	Remove configuration support for components with the form $component_name_entry
	RIO-204	FIXED	Rio UI should provide support to update a deployed opstring
	RIO-208	FIXED	RioTestManager undeploy
	RIO-187	FIXED	RioTestRunner is extending a deprecated JUnit class JUnit4ClassRunner
	RIO-181	FIXED	Service configuration files should use the org.rioproject.groups system property, defaulting to rio group if not set
	RIO-183	FIXED	ServiceBeanContext.getInitParameterNames() needs to return an Iterable<String> instead of an Iterator<String>
	RIO-188	FIXED	ServiceBeanInstantiator should provide it's InetAddress
	RIO-207	FIXED	ServiceExec match on forked pid
	RIO-185	FIXED	Set LookupLocators if org.rioproject.locators system proeprty is set
	RIO-129	FIXED	Sigar support improvements
	RIO-150	FIXED	Simplify construction of the ComputeResource object
	RIO-83	FIXED	Support Groovy Configuration instead of the default Jini Configuration
	RIO-110	FIXED	Support extracting tar files
	RIO-148	FIXED	Symbolic directory names and OAR deployment
	RIO-170	FIXED	SystemMemory produces wrong MeasurableCapability class
	RIO-205	FIXED	Test infrastructure should provide declarative timeout
	RIO-163	FIXED	The OperationalString loaded from property is incorrect if the opstring is derived from a groovy file
	RIO-180	FIXED	UI does not support groovy config
Viewing 50 of 58 Issues.