Broadleaf Commerce Discussion Forums

I have a demo and Admin application on a external server running and every morning the Admin site needs to be restarted to be able to log-in. This would happen on the local version to overcome you would just have to start the site first and then the admin but now I was wondering how this is done in a production installation.

Thanks for the assistance.....in advance

I was wondering if anybody as see this or if is a known problem.
With my Admin site in external server needs restarted daily to sign in.

Please make sure that your demo on the external server is not configured for "create" or "create-drop" (see http://docs.broadleafcommerce.org/curre ... ation.html). Otherwise, if the demo ever goes down or is recycled, the database is wiped.

I have the update statement added but it still requires a restart. What else do you think would require the admin application to be re started. This is the same reason you can not start the admin first in a local environment I know I am missing a setting I just can figure it out.

Any Ideas?

the same reason you can not start the admin first in a local environment

The admin application will actually start up locally no problem without 'site' running. The difference is that you cannot login or do anything until the site has been started up. This is because the hibernate ddl is set to 'create-drop' in site (see development.properties in the site project) and is also where all the import SQL files necessary to run the site and admin are referenced (while the files themselves are contained in core/src/main/resources/sql). This is what development.properties looks like in site:



The admin does not have this and so no tables are created and no import files are run.

There should be no reason that you have to restart the admin in order to log in unless for some reason the site and admin are pointing at separate databases. I regularly run on Tomcat deploying both applications at the same time (the admin as 'admin.war' and the site as 'ROOT.war'). Because I have it configured in this way, the admin.war file is deployed first and starts up without a problem, then the ROOT.war file is deployed and also starts up no problem, the Tomcat restart is completed and now I can do whatever I want with both site and admin. I would check your database configuration and also that you don't have anything wonky in your properties files.