[hibernate-issues] [Hibernate-JIRA] Commented: (METAGEN-51) C3P0 connection pool tester is not called if buildSessionFactory failed due to wrong password

Andrey Dryahlov (JIRA) noreply at atlassian.com
Tue Jan 18 10:55:05 EST 2011


    [ http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=39686#action_39686 ] 

Andrey Dryahlov commented on METAGEN-51:
----------------------------------------

Sorry, probably the project is really wrong.

There is no exception in my code. What I am trying to say is that it for some reason MySQL DB is down then buildSessionFactory() is not failed. As I read on forum this is correct scenario. But I created a C3P0 connection tester which should run every timeout to check the connection status and let me know if the connection to DB is established or not. But in this case tester is not called for some reason. I want to understand why it happens. Documentation says nothiing about this situation. If this is a bug and the tester should be started then the issue should be fixed.

This is what I am talking about.

> C3P0 connection pool tester is not called if buildSessionFactory failed due to wrong password
> ---------------------------------------------------------------------------------------------
>
>                 Key: METAGEN-51
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-51
>             Project: Hibernate Metamodel Generator
>          Issue Type: Bug
>         Environment: I used Hibernate+C3P0. 
> Here is a my config:
>         setProperty("hibernate.connection.driver_class",
>                 "com.mysql.jdbc.Driver");
>         setProperty("hibernate.dialect", "org.hibernate.dialect.MySQLDialect");
>         setProperty("hibernate.connection.url", "jdbc:mysql://localhost:"
>                 + getDBPort() + "/emplatcore");
>         setProperty("hibernate.connection.username", Network.getInstance()
>                 .getMASDBAccountCred().getUserName());
>         setProperty("hibernate.connection.password", Network.getInstance()
>                 .getMASDBAccountCred().getPassword());
>         setProperty("hibernate.show_sql", "false");
>         setProperty("hibernate.c3p0.aquire_increment",
>                 Integer.toString(getConnectionAcquireIncrement()));
>         setProperty("hibernate.c3p0.idle_test_period",
>                 Integer.toString(getIdleTestPeriod()));
>         setProperty("hibernate.c3p0.timeout",
>                 Integer.toString(getIdleTimeout()));
>         setProperty("hibernate.c3p0.max_size",
>                 Integer.toString(getMaxConnections()));
>         setProperty("hibernate.c3p0.max_statements",
>                 Integer.toString(getStatementCache()));
>         setProperty("hibernate.c3p0.min_size",
>                 Integer.toString(getInitialPoolSize()));
>         setProperty(
>                 "c3p0.connectionTesterClassName",
>                 "com.nortelnetworks.mcp.ne.mediaserver.db.dao.hibernate.c3p0.MCPHibernateConnectionTester");
>         setProperty("c3p0.acquireRetryAttempts",
>                 Integer.toString(getAcquireRetryAttempts()));
>         setProperty("c3p0.acquireRetryDelay",
>                 Long.toString(getAcquireRetryDelay()));
>            Reporter: Andrey Dryahlov
>            Assignee: Hardy Ferentschik
>            Priority: Critical
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> I tried to check if connect is up or down to MySQL using C3P0 connection pool tester. It works if password is correct. But password can be changed and I need to let user know that there is no connection to MySQL. 
> I want to understand why buildSessionFactory() does not start connection tester.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list