You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-user@db.apache.org by "Jean T. Anderson" <jt...@bristowhill.com> on 2005/01/28 01:12:28 UTC
[WEB] Upgrade of Derby web site to forrest 0.6 tonight
I have an error-free build of the Derby site using forrest 0.6 and would
like to commit the changes tonight and make them visible to the web.
Access to the web site itself might experience a minor disruption while
the change takes effect. I apologize in advance for any inconvenience.
-jean
Re: [WEB] Upgrade of Derby web site to forrest 0.6 tonight
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Barnet Wagman wrote:
> ... Last night the mail archive server was working but its throwing a
> VelocityServlet error again (looks similar to the one it was throwing
> earlier yesterday).
> ...
Below is an explanation Noel posted to a jakarta list. I assume it's ok
to forward posts to public lists to other lists. If not, my apologies.
-jean
-------- Original Message --------
Subject: RE: Eyebrowse down?
Date: Sat, 29 Jan 2005 20:23:06 -0500
From: Noel J. Bergman <no...@devtech.com>
To: Jakarta General List <ge...@jakarta.apache.org>
Noel J. Bergman wrote:
> Some tables were marked as crashed in the eyebrowse database.
> I have taken mysql off-line and am running repairs.
This will take a bit longer. We ran out of space on the file system holding
the databases, and it is taking a while to purge the cache that caused the
problem so that we can repair the databases.
--- Noel
Re: [WEB] Upgrade of Derby web site to forrest 0.6 tonight
Posted by Barnet Wagman <b....@comcast.net>.
Jean T. Anderson wrote:
> I have an error-free build of the Derby site using forrest 0.6 and
> would like to commit the changes tonight and make them visible to the
> web.
>
> Access to the web site itself might experience a minor disruption
> while the change takes effect. I apologize in advance for any
> inconvenience.
>
> -jean
>
>
Last night the mail archive server was working but its throwing a
VelocityServlet error again (looks similar to the one it was throwing
earlier yesterday).
regards, bw
------------------------------------------------------------------------
VelocityServlet: Error processing the template
Unable to instantiate concrete database mapper org.tigris.eyebrowse.MySQLEyebrowseDb: Cannot connect to Database jdbc:mysql://localhost:3306/eyebrowse as eyebrowse
org.apache.velocity.exception.VelocityException: Unable to instantiate concrete database mapper org.tigris.eyebrowse.MySQLEyebrowseDb: Cannot connect to Database jdbc:mysql://localhost:3306/eyebrowse as eyebrowse
at org.tigris.eyebrowse.servlets.EyebrowseServlet.handleRequest(Unknown Source)
at org.apache.velocity.servlet.VelocityServlet.doRequest(VelocityServlet.java:396)
at org.tigris.eyebrowse.servlets.EyebrowseServlet.doRequest(Unknown Source)
at org.apache.velocity.servlet.VelocityServlet.doGet(VelocityServlet.java:355)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2416)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:601)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534)
Re: [WEB] Upgrade of Derby web site to forrest 0.6 tonight
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Jean T. Anderson wrote:
> I have an error-free build of the Derby site using forrest 0.6 and
> would like to commit the changes tonight and make them visible to the
> web.
The web site update is complete, but you may need to reload/refresh any
pages that your browser has cached.
The Derby site uses the default forrest setup/skin for 0.6. I enabled
one of the new features -- the font size change buttons. I can turn that
off if people don't like it.
Please post any problems you encounter.
One thing I notice with the Manuals tab is if you drop down into any
single page, the Manuals menu automatically collapses, which I find a
little startling. This is a side effect of how pages for the manuals are
entered in the site.xml site index. Here's a snippet of the explanation
from
http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=derby-dev@db.apache.org&msgNo=658
:
>... A file gets
>associated with the site by an entry in the site.xml file. If an entry
>for that file is not there, forrest generates a left-hand navigation tab
>with the entire site contents. It made me sea sick the first time I
>encountered it. If you want to see this effect, edit your local copy of
>the site.xml to remove all but the "table of contents" and "index"
>entries for the manuals, do 'forrest site', then 'forrest run', then
>click on a page in one of the manuals.
>
>So, the current site.xml has an entry for every page in every manual.
>With the exception of the "table of contents" and "index" pages,
>entries don't have a label so it doesn't explode that navigation bar.
>--Imagine 700 files listed in that navigation tab. One problem remains
>that I haven't been able to figure out. The pages without a label get
>correctly associated with the Manuals tab (and that tab gets built
>correctly), but you lose context for the specific manual to which the
>page belongs.
>
So the pages stay associated with the Manuals tab, but the contents of
the tab collapses.
If anyone has any suggestions for how to improve this, I'm all ears!
regards,
-jean
Re: [WEB] Upgrade of Derby web site to forrest 0.6 tonight
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Jean T. Anderson wrote:
> I have an error-free build of the Derby site using forrest 0.6 and
> would like to commit the changes tonight and make them visible to the
> web.
Built pages for the Derby site are checked into svn (see old history at
http://mail-archives.apache.org/eyebrowse/BrowseList?listName=derby-dev@db.apache.org&by=subject&from=634682&to=634682&first=1&count=6
).
At some point, we should discuss if that is the best way to proceed
moving forward. In the meantime, I'll check in built changes with
multiple commits to keep the size of commit records down.
Just an fyi for inquiring minds that might wonder about the mutiple
commit records.
-jean
Re: [WEB] Upgrade of Derby web site to forrest 0.6 tonight
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Jean T. Anderson wrote:
> I have an error-free build of the Derby site using forrest 0.6 and
> would like to commit the changes tonight and make them visible to the
> web.
The web site update is complete, but you may need to reload/refresh any
pages that your browser has cached.
The Derby site uses the default forrest setup/skin for 0.6. I enabled
one of the new features -- the font size change buttons. I can turn that
off if people don't like it.
Please post any problems you encounter.
One thing I notice with the Manuals tab is if you drop down into any
single page, the Manuals menu automatically collapses, which I find a
little startling. This is a side effect of how pages for the manuals are
entered in the site.xml site index. Here's a snippet of the explanation
from
http://mail-archives.apache.org/eyebrowse/ReadMsg?listName=derby-dev@db.apache.org&msgNo=658
:
>... A file gets
>associated with the site by an entry in the site.xml file. If an entry
>for that file is not there, forrest generates a left-hand navigation tab
>with the entire site contents. It made me sea sick the first time I
>encountered it. If you want to see this effect, edit your local copy of
>the site.xml to remove all but the "table of contents" and "index"
>entries for the manuals, do 'forrest site', then 'forrest run', then
>click on a page in one of the manuals.
>
>So, the current site.xml has an entry for every page in every manual.
>With the exception of the "table of contents" and "index" pages,
>entries don't have a label so it doesn't explode that navigation bar.
>--Imagine 700 files listed in that navigation tab. One problem remains
>that I haven't been able to figure out. The pages without a label get
>correctly associated with the Manuals tab (and that tab gets built
>correctly), but you lose context for the specific manual to which the
>page belongs.
>
So the pages stay associated with the Manuals tab, but the contents of
the tab collapses.
If anyone has any suggestions for how to improve this, I'm all ears!
regards,
-jean