Broadleaf Commerce Discussion Forums

Hello to the Broadleaf community,

I am attempting to build and deploy Broadleaf for evaluation. Building the project in IntelliJ IDEA seemed to go fine. The point where I run into difficulties is when configuring Broadleaf to use MySQL rather than HSQLDB. This is despite carefully following your documentation on the changeover (though I'm finding the directions rather unclear in places). I'm hoping that someone can help identify the cause/solution, based on the log output:

http://assets.optomus.com/documents/broadleaf.log

Happy to provide any configurations necessary to help solve.

Thanks & regards,

Chris.

The log link didn't work for me.

Strange. Here is the link again (works for me):

http://assets.optomus.com/documents/broadleaf.log

Below I've pasted a snippet from the logs containing the first signs of trouble.

What is in your web application context.xml, your Tomcat server context.xml and your Tomcat server server.xml? My hunch is that in META-INF/context.xml in your web application you have the same JNDI resources as your Tomcat server context.xml or server.xml. They should only exist in 1 place.

Also, it looks like you do not have a -javaagent:/path/to/spring-instrument.jar set in $CATALINA_OPTS (which is normally set in setenv.sh). This could impact future compatibility with Broadleaf 3rd-party module as this is assumed. There is a warning that references it at :

Thanks Phillip,

You are correct - I had configured the three JNDI data sources in Tomcat's context.xml, as I had previously been unsuccessful in getting Broadleaf to connect to MySQL via Broadleaf's own context.xml. So I am back to the original problem, which you might be able to assist with. Firstly, thank you for your assistance thus far.

I placed the JDBC driver in...

DemoSite/lib/mysql-connector-java-5.1.35-bin.jar Right place?

And updated pom.xml with the following dependency...



Yet, I get the following errors when attempting to run the application...



Incidentally, this same MySQL JDBC driver is also contained in Tomcat's own 'lib' folder. Seems to make no difference. Odd.

DemoSite/lib/mysql-connector-java-5.1.35-bin.jar Right place?

No.

And updated pom.xml with the following dependency...

This is fine if you are using the embedded Tomcat plugin that is kicked off via the ant tasks. For instance, if you are running nat tomcat or ant tomcat-jrebel then MySQL needs to be a dependency of the embedded Tomcat plugin (as the HSQL plugin is currently).

Yet, I get the following errors when attempting to run the application...

Instead of hardcoding the database username, password or URL directly in context.xml, we have these JNDI resource definitions set up to get this information from JVM arguments.

If you look in build.xml in the site and/or admin projects, you will see these JVM arguments being set up in the tomcat task prior to invoking tomcat7:run:

<target name="tomcat" depends="start-db">
<delete dir="war/WEB-INF/lib"/>
<artifact:mvn mavenHome="${maven.home}" fork="true">
<jvmarg value="-XX:MaxPermSize=256M" />
<jvmarg value="-Xmx512M" />
<jvmarg value="-Xdebug" />
<jvmarg value="-Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n" />
<jvmarg value="-javaagent:${spring.instrument.path}" />
<jvmarg value="-Druntime.environment=${runtime.environment}" />
<jvmarg value="-Ddatabase.user=${database.user}" />
<jvmarg value="-Ddatabase.password=${database.password}" />
<jvmarg value="-Ddatabase.driver=${database.driver}" />
<jvmarg value="-Ddatabase.url=${database.url}" />
<arg value="compile"/>
<arg value="war:exploded"/>
<arg value="tomcat7:run"/>
</artifact:mvn>
</target>

These jvmarg parameters:

<jvmarg value="-Ddatabase.user=${database.user}" />
<jvmarg value="-Ddatabase.password=${database.password}" />
<jvmarg value="-Ddatabase.driver=${database.driver}" />
<jvmarg value="-Ddatabase.url=${database.url}" />

popuplate those system properties from ant properties, in this order (look at the top of build.xml for this code):



If you're building a war and running on a standalone Tomcat instance (which is what I think that you're doing) then this is what you need to do:

1. Copy the mysql connector jar into the lib directory of Tomcat
2. Ensure that the CATALINA_OPTS environment variable sets database.user, database.driver, database.password and database.url. This is commonly set in setenv.sh (linux/osx) or setenv.bat (windows):

Thanks Philip.

I deployed mycompany.war and admin.war to a standalone instance of Tomcat, and finally got Broadleaf working.  The Broadleaf guide on switching to MySQL stipulated a number of changes to Broadleaf configuration files prior to compiling the program and building the WARs. Actually, how much of this is really necessary if the intention is to deploy the WARs to a standalone instance of Tomcat anyway?

Regarding the defining of database parameters in setenv.sh/bat, I'm wondering if this is the best strategy when there may be more than one instance of Broadleaf running on the same Tomcat instance, or server. In such a case would you personally rather define the database connection in the two context.xml files contained in Broadleaf itself? I guess a third option is to place these in Tomcat's context.xml, but that would require changing the JNDI names to avoid any conflict when installing additional instances of Broadleaf.

Thanks & regards,

Chris.

Yeah, if you're deploying different Broadleaf instances to the same Tomcat container then you would have to change JNDI resource names anyway if you wanted them to point to different databases. And then I would still use setenv.sh to pass in those credentials, you'll just need to mostly duplicate them.

Actually, how much of this is really necessary if the intention is to deploy the WARs to a standalone instance of Tomcat anyway?

Not sure I understand your question here.

I was trying to setup Broadleaf eCommerce in Apache Tomcat/MySQL/Win 10 environment, but I am not able to deploy the WAR. I had gone through the Broadleaf Blogs/Forums and also StackExchange for all possible solutions, but I am still not able to get the site/admin portal up and running.

Here are the steps which I had followed

Here is the Environment which I am working

Server version: Apache Tomcat/8.0.24
Server built: Jul 1 2015 20:19:55 UTC
Server number: 8.0.24.0
OS Name: Windows 8.1
OS Version: 6.3
Architecture: amd64
Java Home: C:\Program Files\Java\jdk1.8.0_51\jre
JVM Version: 1.8.0_51-b16
JVM Vendor: Oracle Corporation
CATALINA_BASE: E:\MyProject\apache-tomcat-8.0.24
CATALINA_HOME: E:\MyProject\apache-tomcat-8.0.24

As per the instructions in the forum, have updated the Apache Tomcat global server.xml and context.xml

server.xml



context.xml





I had downloaded the Demo site from Git and had modified the following properties(after running the ant build target to modify the site specific settings) and before running the Maven

build.properties



build.xml in both admin and site has been changed to reflect the MySQL URL and DB connection parameters

Have also updated core\src\main\resources\runtime-properties\common-shared.properties to change from HSQL to MySQl



Have updated the context.xml in both site and admin to be in line with Apache Tomcat context.xml

Changed the pom.xml commenting out the hsql DB and added entries for MySQL DB. Also, copied the MySQL JAR to the lib folder

Changed jetty-env.xml(although in forums it is pointed out that jetty is ignored and entries in context.xml would be picked up).

The problem that I see is that it is able to create certain tables while certain set of tables are not created. Also, both the site and admin WAR's are not deployed. Any idea on what other parameters I need to change? Here is the link to log fileshttp://1drv.ms/1P1Zycd.