Page 1 of 1

Error deploying to tomcat

Posted: Mon Aug 13, 2012 2:03 pm
by csrinivasrao
After deploying the Admin.war and site.war, I got the following error.

Code: Select all

[ERROR] 19:50:27 Ejb3Configuration - Container is providing a null PersistenceUn
itRootUrl: discovery impossible


The site.war on its own works fine.

Thanks for the help,

Srinivas

Re: Error deploying to tomcat

Posted: Mon Aug 13, 2012 4:09 pm
by phillipuniverse
You should be able to safely ignore this error message. This is currently being tracked at http://jira.broadleafcommerce.org/browse/BLC-73 but is relatively low priority for us. I assume that other than this everything starts up ok?

Re: Error deploying to tomcat

Posted: Thu Aug 16, 2012 1:26 pm
by csrinivasrao
The site works fine but the problem with admin console. When I accessed http://host:port/admin/admin.html, it is keep redirecting to http://localhost:7001/admin/admin/admin ... admin.html and the web page has resulted in too many redirects.

context.xml

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<Context useNaming="true" antiJARLocking="true">
    <!-- This is a sample datasource configuration for Tomcat
         THIS IS NOT A PRODUCTION READY CONFIGURATION!!
         Production ready configurations include additional settings,
         such as validationQuery, maxActive and maxIdle -->
                 
    <ResourceLink name="jdbc/web" type="javax.sql.DataSource" global="jdbc/web"/>
    <ResourceLink name="jdbc/storage" type="javax.sql.DataSource" global="jdbc/storage"/>
    <ResourceLink name="jdbc/secure" type="javax.sql.DataSource" global="jdbc/secure"/>
    <WatchedResource>WEB-INF/web.xml</WatchedResource>
</Context>

Re: Error deploying to tomcat

Posted: Thu Aug 16, 2012 3:01 pm
by aazzolini
In applicationContext-admin-security.xml, add the applicable port mapping for 7001 to your HTTPS port. Alternatively, turn off HTTPS for the admin by setting the requires-channel attribute to "http" or "any".

You will need to do some HTTPS configuration on site as well.

For Jetty, we generate self-signed keys via a Maven plugin during server startup -- however, for Tomcat, you will need to provide your own keys or disable HTTPS.

Re: Error deploying to tomcat

Posted: Fri Aug 17, 2012 3:21 pm
by csrinivasrao
Thanks it works now.