Bug 152494 Support deployment of ODA Bundles in Web Application
When deploying a WAR package embedded with the ODA runtime plugins on a web application, e.g. WebLogic 9, the Stop( Shutdown Platform ) and restart service fails to restart platform correctly. This is due to instances not being released when WebLogic is shutdown. So in subsequent startup, those classes and their static variables are not re-initialized. Any objects referenced by singleton instances, such as plugin extensions objects, are thus from the previous platform instance, and are no longer valid.
data/org.eclipse.birt.data/src/org/eclipse/birt/data/engine/odaconsumer/ConnectionManager.java
IConnection connection = driverHelper.getConnection( dataSourceId );
			connection.open( connectionProperties );
			
			Connection ret = ( new Connection( connection, dataSourceElementId ) );
			
			sm_logger.exiting( sm_className, methodName, ret );	
			return ret;
		}
		catch( OdaException ex )
		{
			sm_logger.logp( Level.SEVERE, sm_className, methodName, 
							"Cannot open connection.", ex );
			
			throw new DataException( ResourceConstants.CANNOT_OPEN_CONNECTION, ex, 
			                         new Object[] { dataSourceElementId } );
		}
		catch( UnsupportedOperationException ex )
		{
			sm_logger.logp( Level.SEVERE, sm_className, methodName, 
							"Cannot open connection.", ex );
			
			throw new DataException( ResourceConstants.CANNOT_OPEN_CONNECTION, ex, 
			                         new Object[] { dataSourceElementId } );
		}
	}
	/**
	 * Returns the maximum number of active connections that the driver can support.
	 * @return	the maximum number of connections that can be opened concurrently, 
	 * 			or 0 if there is no limit or the limit is unknown.