Page 1 of 1

404 error when deployed in Tomcat, Built with no errors

Posted: Tue Oct 01, 2013 12:43 am
by karun
Hi,

I migrated broadleaf demo to mysql and tomcat in Eclipse. I deployed application in Tomcat (embedded in Eclipse). Maven build was successful and tomcat throws following error and starts application fine. However http://localhost:8080/mycompany/ (Also tried with http://localhost:8080/ ) results in 404 error. I followed documentation before posting, please advise if any changes are needed in configuring tomcat

Sep 30, 2013 10:13:37 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
[ WARN] 22:13:49 RuntimeEnvironmentPropertiesConfigurer - Unable to determine runtime environment, using default environment 'development'
[ERROR] 22:13:54 Ejb3Configuration - HHH000050: Container is providing a null PersistenceUnitRootUrl: discovery impossible
[ WARN] 22:13:55 Ejb3Configuration - HHH000144: hibernate.connection.autocommit = false breaks the EJB3 specification
[ WARN] 22:13:57 AbstractEhcacheRegionFactory - HHH020003: Could not find a specific ehcache configuration for cache named [org.hibernate.cache.spi.UpdateTimestampsCache]; using defaults.
[ WARN] 22:13:57 AbstractEhcacheRegionFactory - HHH020003: Could not find a specific ehcache configuration for cache named [org.hibernate.cache.internal.StandardQueryCache]; using defaults.
[ WARN] 22:13:58 AbstractEhcacheRegionFactory - HHH020003: Could not find a specific ehcache configuration for cache named [blSandBoxElements]; using defaults.
[ERROR] 22:14:02 Ejb3Configuration - HHH000050: Container is providing a null PersistenceUnitRootUrl: discovery impossible
[ WARN] 22:14:02 Ejb3Configuration - HHH000144: hibernate.connection.autocommit = false breaks the EJB3 specification
[ERROR] 22:14:02 Ejb3Configuration - HHH000050: Container is providing a null PersistenceUnitRootUrl: discovery impossible
[ WARN] 22:14:02 Ejb3Configuration - HHH000144: hibernate.connection.autocommit = false breaks the EJB3 specification
[ WARN] 22:14:06 CoreContainer - Log watching is not yet implemented for log4j
[ WARN] 22:14:07 SolrCore - New index directory detected: old=null new=C:\Users\kk\AppData\Local\Temp\kk\solrhome\core0dir\data\index/
[ WARN] 22:14:08 SolrCore - New index directory detected: old=null new=C:\Users\kk\AppData\Local\Temp\kk\solrhome\core1dir\data\index/
Sep 30, 2013 10:14:11 PM org.apache.coyote.http11.Http11Protocol start

Re: 404 error when deployed in Tomcat, Built with no errors

Posted: Tue Oct 01, 2013 8:36 am
by phillipuniverse
What happens if you leave off the trailing slash? And did you deploy the war to any context besides ROOT in Tomcat?

Re: 404 error when deployed in Tomcat, Built with no errors

Posted: Mon Nov 04, 2013 1:56 pm
by frederik@fdemoor.be
I have got the same problem. In my case the problem was that the application didn't run at the tomcat root context(/) . So I removed the tomcat manager app and let this application run on the root context.