Tag Archives: apache

Fronting Tomcat with Apache HTTPD to Remove Ports and Context Paths

Posted on by
17

In this How-To guide, I show a combination of software and configuration to clean up URLs by removing the port numbers of the Java servlet engine (Tomcat) and the context path of the application. The goal is to create “cool URLs” that are are short (removing the unnecessary context path) and follow conventions (using the default port “80″ rather than “8080″). OhioLINK also uses a custom access control module — built for Apache HTTPD — which makes the fronting of Apache HTTPD for Tomcat even more desirable.

This is a preview of Fronting Tomcat with Apache HTTPD to Remove Ports and Context Paths. Read the full post (562 words, 2:15 minutes estimated reading time)

Solr-ized MARC Record Catalog

Posted on by
1

Rob Casson of Miami University announced this weekend the beta availability of their video catalog. In a subsequent posting, Rob describes the user interface elements. Rob and the crew at Miami are seeking feedback on the interface, so if you have some be sure to offer it to them.

A couple of notes on the mechanisms Rob is using. Apache Solr is an open source enterprise search server based on the Lucene Java search library (also an Apache project). You can think of Lucene as the raw indexing and search engine with Solr layered on top to provide a non-Java interface to a rich feature set. What Miami has done is extract all of the bibliographic and related item records out of their Innovative Interface system, written programs to transform that data into XML, indexed it with Solr/Lucene and created a search interface.

This is a preview of Solr-ized MARC Record Catalog. Read the full post (471 words, 2 images, 1:53 minutes estimated reading time)

Killing Off Runaway Apache Processes

Posted on by
4

Well, something is still going wrong on dltj.org — despite previous performance tuning efforts, I’m still running into cases where machine performance grinds to a halt. In debugging it a bit further, I’ve found that the root cause is an apache httpd process which wants to consume nearly all of real memory which then causes the rest of the machine to thrash horribly. The problem is that I haven’t figured out what is causing that one thread to want to consume so much RAM — nothing unusual appears in either the access or the error logs and I haven’t figured out a way to debug a running apache thread. (Suggestions anyone?)

This is a preview of Killing Off Runaway Apache Processes. Read the full post (397 words, 1:35 minutes estimated reading time)