在Debian上运行的Tomcat上部署Hibernate Web应用程序

时间:2016-06-25 04:48:31

标签: java linux spring hibernate tomcat

参考我的older question,我在Linux上运行企业级Web应用程序时遇到了一些问题。在投资真正的升级机之前,我认为我应该尝试一下Raspbery Pi,但现在,我们正在真正的 Debian计算机上运行该应用程序。

问题与我之前的问题相同。

  

起初,我认为这更像是一个tomcat问题,但现在,我是   认为这是 Raspberry Pi Linux 问题。

     

这个完全相同的配置适用于我们的Windows服务器,但我不能   找出为什么它不适用于 Pi Staging Macine


问题:

tomcat没有注册我在应用程序上下文中定义的JNDI名称,即使提供了正确的数据库URL,Hibernate也无法连接到数据库。

在我的$ CATALINA_HOME / conf / Catalina / localhost / $ appname.xml;

<?xml version="1.0" encoding="UTF-8"?>
<Context antiResourceLocking="false" privileged="true" cookies="true">
    <Resource name="stagingDS" auth="Container" type="javax.sql.DataSource"
                driverClassName="com.mysql.jdbc.Driver" url="jdbc:mysql://localhost:3306/preview"
                username="root" password="root" />
</Context>

我已将Spring bean定义为;

    <bean id="velocityConfig"
        class="org.springframework.web.servlet.view.velocity.VelocityConfigurer">

        <property name="velocityProperties">

            <map>

                <entry key="resource.loader" value="ds" />
                <entry key="ds.resource.loader.class"
                    value="com.simplestack.velocity.config.SimpleStackDataSourceResourceLoader" />
                <entry key="ds.resource.loader.resource.table" value="Catalog" />
                <entry key="ds.resource.loader.resource.keycolumn" value="name" />
                <entry key="ds.resource.loader.resource.templatecolumn" value="html" />
                <entry key="ds.resource.loader.resource.defaultVendorId"
                    value="1" />
                <entry key="ds.resource.loader.resource.defaultSiteId" value="20160109144" />
                <entry key="ds.resource.loader.resource.datasource" value="java:comp/env/stagingDS" />
                <entry key="ds.resource.loader.resource.timestampcolumn"
                    value="lastmod" />

            </map>

        </property>
    </bean>

它让我NamingConventionExceptionstagingDS未定义。

这也可能是一个Tomcat问题,所以我也发布了version.sh的输出。

Screenshot of PuTTY

休眠;

我正在调用此方法来创建会话工厂

protected static SessionFactory buildSessionFactory(File cfgfile, File[] hbmfiles, String dburl, String dbuser, String dbpassword, String dbdriver, String treecacheConfigFile) 
            throws Exception{
        logger.info("Hibernate Configuration File Path:"+cfgfile.getPath());
        for (int i=0; i<hbmfiles.length; i++)
            logger.info("Hibernate Mapping File Path:"+hbmfiles[i].getPath());
        logger.info("Hibernate Using JDBC, dburl:"+dburl+" dbuser:"+dbuser+" dbdriver:"+dbdriver);

        Configuration hibernateConfig = new Configuration();
        for (int i=0; i<hbmfiles.length; i++)
            hibernateConfig = addHbmFile(hibernateConfig, hbmfiles[i]);

//      TODO: Add the audit interceptors
//      AuditInterceptor auditInterceptor = new AuditInterceptor();
//      addDefaultInterceptor(hibernateConfig, auditInterceptor);
//      addEventListeners(hibernateConfig);

        hibernateConfig.configure(cfgfile);
        logger.info("Configfile:"+cfgfile);

        if (treecacheConfigFile != null){
            hibernateConfig.setProperty("hibernate.cache.configuration_file", treecacheConfigFile);
            logger.info("hibernate.cache.configuration_file:"+treecacheConfigFile);
        }

        hibernateConfig.setProperty("hibernate.connection.url", dburl);
        hibernateConfig.setProperty("hibernate.connection.username", dbuser);
        hibernateConfig.setProperty("hibernate.connection.password", dbpassword);
        hibernateConfig.setProperty("hibernate.connection.driver_class", dbdriver);


        SessionFactory sessionFactory = hibernateConfig.buildSessionFactory();
        //TODO:set a separate session factory
//      auditInterceptor.setSessionFactory(sessionFactory);

        return sessionFactory;

    }

会话工厂创建成功,但在我的日志文件中,我看到: -

2016-06-15 08:04:54,504 INFO  [com.simplestack.SessionFactoryPool] Building Hibernate STAGING Session Factory...
2016-06-15 08:04:54,504 INFO  [com.simplestack.SessionFactoryPool] Hibernate Configuration File Path:/SimpleStack/tomcat/webapps/staging/WEB-INF/hibernatecfg/hibernate_mysql.cfg.xml
2016-06-15 08:04:54,505 INFO  [com.simplestack.SessionFactoryPool] Hibernate Mapping File Path:/SimpleStack/tomcat/webapps/staging/WEB-INF/hibernate
2016-06-15 08:04:54,505 INFO  [com.simplestack.SessionFactoryPool] Hibernate Using JDBC, dburl:jdbc:mysql://localhost:3306/preview dbuser:root dbdriver:com.mysql.jdbc.Driver
2016-06-15 08:04:55,173 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,284 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,327 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,380 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,408 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,434 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,459 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,483 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,505 WARN  [org.hibernate.internal.util.xml.DTDEntityResolver] HHH000223: Recognized obsolete hibernate namespace http://hibernate.sourceforge.net/. Use namespace http://www.hibernate.org/dtd/ instead. Refer to Hibernate 3.6 Migration Guide!
2016-06-15 08:04:55,514 INFO  [com.simplestack.SessionFactoryPool] Configfile:/SimpleStack/tomcat/webapps/staging/WEB-INF/hibernatecfg/hibernate_mysql.cfg.xml
2016-06-15 08:04:55,882 WARN  [org.hibernate.mapping.RootClass] HHH000038: Composite-id class does not override equals(): com.simplestack.hibernate.domainmodel.Siteproperty
2016-06-15 08:04:55,883 WARN  [org.hibernate.mapping.RootClass] HHH000039: Composite-id class does not override hashCode(): com.simplestack.hibernate.domainmodel.Siteproperty
2016-06-15 08:04:55,928 WARN  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] HHH000022: c3p0 properties were encountered, but the org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider provider class was not found on the classpath; these properties are going to be ignored.
2016-06-15 08:04:56,466 WARN  [org.hibernate.engine.jdbc.internal.JdbcServicesImpl] HHH000342: Could not obtain connection to query metadata : Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

我尝试将JNDI名称放在

  1. $ CATALINA_HOME / CONF /卡塔利娜/本地主机/ $ appname.xml
  2. $ CATALINA_HOME / web应用/ $应用程序的名字/ META-INF / context.xml中
  3. $ CATALINA_HOME / CONF / context.xml中
  4. $ CATALINA_HOME / CONF / server.xml中
  5. 但问题仍然存在。

    我们仍然对这是什么感到困惑......我做错了什么?

1 个答案:

答案 0 :(得分:1)

这不是数据库连接问题。

Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

通常表示您的数据库服务器已关闭或位于localhost以外的IP /主机名中。