right now it's pretty ugly and annoying if you try to run railo_ctl as a non-root user.

Mappings to the windows uriworkermap.properties file need to be added so that default documents work "out of the box" for subfolders in addition to the main root folder.

For example, in the uriworkermap.properties file, add the following:

/*/=ajp13

The above would ensure that all URL calls that ended in a slash (like a subdirectory: mysite.com/add/another/subdir/) would be passed off to Tomcat.

When installing using the Windows installer on a 64-bit machine, a 32-bit JVM does not get properly installed with the user selects 32-bit as their installation type.

This is the result of a slight change in how the installer determines a 32-bit or 64-bit install. Most of the variables and files are configured using a custom variable called "bittype" which is originally set by auto-detection - but is changed when a user selects a 32-bit install.

Due to the way the JVM has been packaged in recent builds. The Installer extraction process only extracts one of the bundled JVM's - which is based entirely off the installer's auto-detection and CANNOT be based off the internal variable.

In order for this bug to be fixed, the structure of how the JVM's are packaged needs to be changed. Both JVM's need to be packaged and extracted, then which one becomes the "installed" version needs to be determined based on the internal "bittype" variable.

As reported by Allen Weng, selecting a non-default port for tomcat causes the Installer "set password" process to error with the following:

"Problem running post-install step. Installation may not complete
correctly. Error fetching URL http://localhost:8888/railo-context/admin/server.cfm"

Some idiot hard coded the port 8888 in there, and deserves a flogging.

Doing a port test will stop folks from getting an error message if nothing is listening to the port. It won't set the password, which is a bit insecure, but will appease some users and allow the rest of the install process to complete normally.

The fix is complex, but the problem is simple and frequent. Right now, information from Apache is not passed on to the servlet engine that tells the servlet engine how to resolve domain requests to their respective file locations on the file system. This means that in order to get a domain to resolve properly in the servlet engine, the domain has to be configured there in addition to being configured in Apache. This "double configuration" is confusing and at the very least, takes extra time.

It was suggested that we add the following mappings (commented) to the URI mappings in the Tomcat connector configs:

• /index.cfm/*
• /default.cfm/*
• /post.cfm/*
• /archive.cfm/*
• /blog.cfm/*
• /page.cfm/*
• /rewrite.cfm/*

Need to add the "headless" attributes to the JVM by default and (along the same vein), perform an check for the image processing libraries the JVM will need to process images in Linux builds.

The installer posts several screens to the user that are less then intuitive during the upgrade process. For example, the installer will ask for the Tomcat port, but basically the port is already an existing variable within the uninstaller, so it doesn't need to be there. Other examples are the Apache locations. Those were already asked to the user during the previous installation when performing an upgrade, and do not need to be asked during the upgrade process.

This can be particularly confusing to a user if they enter in a NEW value to one of these variables, then expect those new values to take effect in the "upgraded" install. In fact, most (if not all) of the variables are actually ignored in the actual system configuration. However, the values that the user enters are used primarily during the install process for processes that are not updated to use the pre-defined values in the uninstaller during an upgrade process.

Additional programming within the installer code is needed for two things:

1. Don't ask the user for values we already know or don't need.

2. Add code that will utilize previous values if those previous values are located in the uninstaller.

This should accomplish several things:

1. Simplify the upgrade process.

2. Make it higher quality and more intuitive.

Per Mark Drew:

When I loaded up the server administrator, I saw we have the following contexts (apart from my webroot context):ROOT, host-manage, docs, and manager . Are they all needed? docs is the tomcat one.

Subsequent conversations with the railo team led to the following context names in order to avoid confusion or accidental overriding of other potential contexts:

• tomcat-docs
• tomcat-manager
• host-manager

in order to avoid confusion, languages in language selection box should be ordered alphabetically.

Issue requested by Paul Klinkenberg.

Right now, the Railo Windows installers have been merged into 1 install file. This simplifies both the installer selection and usage but results in a slightly larger download file (from about 100MB to about 130MB).

This should be more acceptable when we add the option to torrent the file, so we should do this because it will also speed future development by making file trees simpler.

The main difference is just the JRE, and including the JRE for each bit type into the same installer.

A lot of users seem to like keeping their site files in this directory, so we will be adding a method in the upgrade process that will preserve the Tomcat "webapps" directory.

http://www.fusion-reactor.com/fr/whatsnew4.cfm

The Flex Gateway config is present in the Linux installs, but not in the Windows installs. Please add it to Windows installs as well.

The mod_cfml module should be optional during the install, that way users who do not need it are not forced to install it.

The Tomcat Password Screen needs to say that the password provided there is ALSO used for the Railo Administrators by default.

Requested by Mark Drew:
"The screen for the admin username and password should say that this is ALSO the Railo password, I guess this would be MUCH more important than saying it is the tomcat password (it should say it is also that)"

• UPDATE: to remove the tomcat apps entirely.

Even though the restriction is intended to be 6 characters OR more... the installer won't allow a 6 character password. This is a simple mistake of a GT being used instead of a GTE.

Some users have reported that default documents no longer work in IIS6. Need to review and see if I can duplicate.

At the request of Micha, update the railo servlet config in the installers to the following:

<servlet>
    <servlet-name>GlobalCFMLServlet</servlet-name>
    <description>CFML runtime Engine</description>
    <servlet-class>railo.loader.servlet.CFMLServlet</servlet-class>   
    <init-param>
        <param-name>railo-web-directory</param-name> 
        <param-value>{web-root-directory}/WEB-INF/railo/</param-value> 
        <description>Railo Web Directory directory</description> 
    </init-param>
    <!-- init-param>
        <param-name>railo-server-directory</param-name>
        <param-value>./</param-value>
        <description>directory where railo root directory is stored</description>
    </init-param -->
    <load-on-startup>1</load-on-startup>
</servlet>
<servlet>
    <servlet-name>GlobalAMFServlet</servlet-name>
    <description>AMF Servlet for flash remoting</description>
    <servlet-class>railo.loader.servlet.AMFServlet</servlet-class>
    <load-on-startup>2</load-on-startup>
</servlet>

The service_config.sh script needs to be updated (along with the change_user.sh script and associated railo_ctl files) to add railo_ctl to Run Level 2 as it seems Amazon Micro instances use Run Level 2 by default.

Reported by Juan (JEAguilar)
https://groups.google.com/forum/?fromgroups=#!topic/railo/30tXUunmqvg

Via Mark Drew and Neiland.net (http://neiland.dyndns.org/blog/article/set-session-cookies-as-httponly-in-coldfusion--railo/).

Need to update the context.xml file to include the following update to the context tag:

<Context useHttpOnly="true">

A technician at Vivio alerted me to a cause of a few problems with regards to how the uriworkermap.properties file is set up. Specifically, the entry for the simple "/":

/=ajp13

The purpose of this mapping was to assist with enabling the default document, but it has ended up causing more problems then it solved. In IIS6/7 this mapping would work great if your default document needed to be passed off to Tomcat, but if your default document doesn't need to be passed, then this mapping gets in the way because it bypasses the built-in default document features of IIS. The connector simply examines the request, sees that the request matches a URI pattern, and passes it off to Tomcat. Tomcat then processes the request based on it's own default document parameters. This is NOT useful for sites that need, for example, ASP support.

I've performed tests in the following OS's with this mapping removed:

Windows 7 Professional (IIS7)
Windows 2008 R2 (IIS7)
Windows 2003 64-bit (IIS6)

In all cases, IIS is able to process default documents like it should. If the default document is a CFM file, then the request is passed off to tomcat based on the CFML filter definition that the iis7connect.bat or iis6connect.bat add.

NOTE: The filter does NOT establish filters for .jsp and other potentially useful extensions. It simply covers .cfm. If other extensions need to be added, a filter similar to the CFML one need to be added.

So... in an effort to reduce problems with this installer, we will be removing this mapping from future releases.

-Jordan

For purposes of being secure by default, we need to set the password of the railo administrators at the time of installation. Preferably this should be done using a non-web-based method (like using the admin API) because it could potentially lead to problems in various install scenarios. Instead, a script or installer function should be used so that even if the installation fails to happen correctly, this independent piece could still occur and update the passwords.

A lot of folks seem to like storing their sites in the webapps directory, so performing a tomcat upgrade and wiping out the existing webapps directory is bad for those people.

Usually it's bad practice to customize a widely used installer to support a specific use case, but in this case enough people use the webapps directory that it would be better if we took some extra time to not wipe out the entire directory.

While I'm not entirely sure how it will work yet, there have been several requests for the installer to support Apache on Windows. We will need to check to see if Apache has a default install for Windows (I assume it does) and program the installer to assume the Apache defaults are used - but still prompt in case they weren't.

... even when start service automatically is checked.

This probably has to do with the new Tomcat service controls and the associated batch files. Need to find the right command call and call it correctly according to the new specifications for Tomcat 7.

After installation, the JRE folders are not currently cleaned up and cause confusion about which JRE folder is currently in use. These folders need to be removed as part of the install process.

performance and bugfix update

The Linux installers are experiencing a problem during a post-install step of setting the passwords on the Railo Administrators. in certain cases the Installers produce an "Error in Math Expression" error message which causes the post-install process to fail and for the install as a whole to LOOK like it has failed.

The reality is that the server is already installed and running, and the password setting process is one of the very last processes to be run.

The fix for this was to simply rewrite the password setting process to use a different method that didn't require a math expression. Once the process was rewritten, users who had reported the math expression error no longer had an issue with the install.

There has been a long-standing but benign error in Tomcat where during the boot process, Tomcat will error when reading the tomcat-users.xml file. Everything still works, but the error is confusing when folks see it and think something is wrong with their server.

for performance reasons. see:
http://blog.getrailo.com/post.cfm/railo-4-1-smarter-template-compilation

need to check for the presence of existing copies of mod_jk for the installer to check before installing the latest versions - unless doing an upgrade.

The current connector properties file does not contain exclusions for files in other languages besides CF and JSP. We need to add !/index.php=ajp13 (or similar) to the connector properties so that if those files are specified in the default documents before CF or JSP files, they can get processed first.

the SHM config is for shared memory, which is needed for load balancing. Currently it's just annoying because it throws errors in the logs. Not show-stopping, just annoying.

A bug has been discovered with the IIS5 connection process where the default site doesn't always get updated with the default documents correctly. Further inspection of this error has to do with how IIS6 (horribly) deals with site contexts.

WORKAROUND: Add the default document manually to the Default Site. Sites you create in IIS6 AFTER the install process will still contain index.cfm in the default document list.

In short, I will not be fixing this. IIS6 is a horrible web server, and I refuse to develop using it's awful nearly useless API any longer.

Like what's shown here:
https://github.com/igal-getrailo/railo-builder/blob/master/resources/web-servlet-definitions.xml

Maybe include additional comments about the {web-context-label} marker.

We need to add the ability for Windows users to select 64 or 32-bit installation modes even if their machine is a 64-bit machine. This will better allow support for control panels such as Plesk for Windows (which installs in 32-bit mode even on 64-bit machines) and other scenarios where different modes need to be forced.

the help statement gives the wrong script name - this is due to an improperly escaped variable in the change_user.sh script. Needs to be fixed.

Feature requested by Mark Drew (and hinted at by several others who also wanted to install multiple instances):
" It would be great to be able to say the name of the service, since then you could install multiple instances (which I did the other day) using the same installer."

Via Alex Skinner:

Just to make you aware there is currently an issue with the single instance Viviotech installer when you are consuming webservices.

This is not the known tools.jar issue but that the code expects the webservices.jar to be under /WEB-INF/lib

Alan added an additional libpath attribute to the bluedragon.xml to get around this and other issues but this isn't set by the installer

So given an install path of c:\openbd the following node

<libpath>C:\openbd\lib\</libpath>

Should be in the System portion of the XML

Thought id share in case it caught someone on the list out and also to let @jordan know.

Per Mark Drew:

Default files in c:\railo\tomcat\config\web.xml are kind of in the wrong order, this leads to the main page when you hit the server to display the tomcat page rather than railo, the order should (or rather, could) be:

<welcome-file-list>
   <welcome-file>index.cfm</welcome-file>
   <welcome-file>index.cfml</welcome-file>
   <welcome-file>index.html</welcome-file>
   <welcome-file>index.htm</welcome-file>
   <welcome-file>index.jsp</welcome-file>
</welcome-file-list>

OpenBD Administrator Passowrd []:

Needs to say "password"

Per Mark Drew:

The files are served from the tomcat\ROOT context by default. I traced this down to the c:\railo\tomcat\config\server.xml file, and it had the following:

<Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false">
   @@iisrootref@@ 
</Host>

instead of

<Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true"
            xmlValidation="false" xmlNamespaceAware="false">
   <Context path="" docBase="C:\inetpub\wwwroot" />
</Host>

The Railo Control script has a type in it's help. Just type "railo_ctl" to get the help text and you can see that the text and help is wrong.

Need to verify that *.cfchart and *.cfres are properly mapped in openbd installers.

As suggested by Alan Cole so that OpenBD doesn't attempt to deploy every subfolder.

< Host name="www.domain.com" appBase="/path/to/folder/domain.com" deployOnStartup="true" autoDeploy="false" deployIgnore=".*">
< Alias>domain.com< /Alias>
< Context path="" docBase="/path/to/folder/domain.com/" useHttpOnly="true" allowLinking="true" />
< /Host>

The Jetty servlet engine contains some advantages (and disadvantages) over Tomcat. For example, Jetty will support wildcard domain mappings within the servlet engine. Tomcat does not.

It would be great If, during the install process, a user could select either the Jetty or Tomcat servlet engines.

Currently, there is no way to easily upgrade an existing installation. Railo is unique in that it will allow you to perform a Railo upgrade by using the Railo Administrator, but other software, such as the JRE, Tomcat, the connectors, are not easy to update.

We need to create a process that will upgrade previous installation easily.

The installer currently installs a previous version of FusionReactor 3.5.1. Integral has now released 3.5.5 with increased Railo integration - so it would probably be better for Railo users to use 3.5.5. FusionReactor 3.5.5 is available from the download page at http://www.fusion-reactor.com/fr/downloads.cfm