I have worked on web projects for many years and have noticed that project teams tend to get caught up doing performance testing at the last minute, just before going live. This always puts the project over time and sometimes causes technical problems post implementation. webFlange can be used as part of your continuous integration practice to provide performance testing on a regular basis while in the development phase.
[top] |
[top] |
Change the dataSource and hibernateProperties bean configurations in TOMCAT_HOME/webapps/webflange/WEB-INF/applicationContext.xml to the following
<bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource" destroy-method="close"> <property name="driverClass" value="com.mysql.jdbc.Driver" /> <property name="jdbcUrl" value="jdbc:mysql://localhost:3306/webflange?autoReconnect=true" /> <property name="user" value="webflange" /> <property name="password" value="webflange" /> </bean> <bean id="hibernateProperties" class="org.springframework.beans.factory.config.PropertiesFactoryBean"> <property name="properties"> <props> <prop key="hibernate.hbm2ddl.auto">update</prop> <prop key="hibernate.dialect"> org.hibernate.dialect.MySQLInnoDBDialect </prop> <prop key="hibernate.query.substitutions"> true 'T', false 'F' </prop> <prop key="hibernate.show_sql">false</prop> <prop key="hibernate.c3p0.minPoolSize">5</prop> <prop key="hibernate.c3p0.maxPoolSize">20</prop> <prop key="hibernate.c3p0.timeout">600</prop> <prop key="hibernate.c3p0.max_statement">50</prop> <prop key="hibernate.c3p0.testConnectionOnCheckout"> false </prop> <prop key="hibernate.c3p0.idle_test_period">3600</prop> </props> </property> </bean>
Run the following commands in mysql as user root
create database webflange; GRANT ALL PRIVILEGES ON webflange.* TO 'webflange'@'localhost' IDENTIFIED BY 'webflange' WITH GRANT OPTION;
Restart tomcat
[top] |