Regarding performance, I think you'd get a flood of responses if this
were posted on the tomcat list. Current incarnations of tomcat are so
close to the same speed as native httpd that the extra network latency
of mod_jk makes tomcat -> ajp -> httpd slower than if tomcat were
serving content directly. I run the combination because I have an
authentication module with no tomcat equivalent. Otherwise I'd drop it
and go with a tomcat stand-alone in a heartbeat.
The point of PHP is well taken though. When mixing technologies, tomcat
behind httpd is probably the best arrangement.
--David
Antonio Malcolm wrote:
On Jan 17, 2008, at 5:24 AM, Grégory Joseph wrote:
On Jan 17, 2008, at 09:44 , Antonio Malcolm wrote:
Well, okay, this is odd...
My current site, which is a plain-jane JSP site, runs just fine
with the address set at http://localhost/antoniomalcolm/index.jsp
(thanks to my settings with Apache and mod_jk, however, I found, on
a whim, Magnolia still requires localhost:8080. With that, it still
takes me to an update page, but that page leads to where it's
supposed to.
Your first message said you had "Apache configured to handle html
and php files", which really sounds suspicious, as it should
delegate everything to jk. Did you have a look at this page on the
wiki?
http://wiki.magnolia.info/display/WIKI/RunningMagnoliaWithApache
Well, the point to using mod_jk is make things more efficient by
having Apache http handle html. Tomcat will do the job, just not as
quickly. Also, Tomcat doesn't do PHP.
However, I'm using the jkMount directive to determine which server
handles what, if that's what you're referring to.
One down, database connectivity to go. And just maybe I'll take a
deeper look at my connector settings. There's nothing wrong with
them, per say, there are no more errors in the logs (maybe a good
reason for this happenstance), but maybe I can tweak them to give
my server setup greater dexterity.
If you're starting from scratch, just edit WEB-INF/config/default/
magnolia.properties, and change the
"magnolia.repositories.jackrabbit.config" property from "WEB-INF/
config/repo-conf/jackrabbit-derby-search.xml" to "WEB-INF/config/
repo-conf/jackrabbit-mysql-search.xml", before the first start of
Magnolia. If not and you don't care about your current content, just
drop the repositories directory, change the property and restart.
All my content is currently in my JSP-based site, so I don't have any
content yet in the Magnolia install (the goal was to find a Java-
based CMS which would allow me to use my JSP files as a template with
just a little configuring, and I think I've now found just that). I
figured I had to edit the properties file for the mysql dependency
after looking around the file structure and examining individual
files, but had no clue about the repositories directory, so a
definite thanks for that.
Cheers,
g
Cheers,
~Antonio
~Antonio
On Jan 16, 2008, at 6:01 PM, David Smith wrote:
And what is in your logs? This works for me repeatedly out of the
box using MySQL. Unlike 3.0 and earlier you don't have to start
tomcat and then wait blindly for several minutes for the bootstrap
to finish. The install/update does all the bootstrapping. About
all that happens on initial tomcat start is the repository is
initialized and left empty until the install/ update process.
--David
Antonio Malcolm wrote:
Hey all, I Just installed v3.5 on Tomcat v6.0.13 with Apache
v2.2.6 and mod_jk. I have Apache configured to handle html and
php files.
When first loading after installing, I get "Magnolia install/
update ...Magnolia needs to be updated." instead of the
AdminCentral page. And the update link, of course, does not work.
Also, I've tried getting it to work with the MySQL repository as
per Gregory Joseph's instructions, but that lands me with a 403
Access Forbidden error.
I have the database set up for the site, and correctly entered
the username, password, and database names in the xml file, as
well as followed the rest of the instructions (which I felt left
a lot out, to be honest), so what gives? Am I missing something
here? Is there a means for database connectivity which is more
out-of-the box than the JNDIPooledDatabasePersistenceManager? I
noticed Derby is installed, and that there are some other MySQL
related files in WEB-INF.
Well, first I suppose I should worry about making the generic
install work. I have no idea why it doesn't. Set Tomcat to a
minimum of 512m, drop the WAR package into WEBAPPS, start Tomcat,
give it time to expand and bootstrap, stop Tomcat, remove the
WAR, restart Tomcat.
Seems simple enough, but then again, I think too simple.
Thanks in advance for any advice,
~Antonio
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
