CFM Pages Not Working After Server IP Change

BlueOnyx JSP and Servlets, including ColdFusion, CFM, CFML, Railo templates do not run after changing the IP address of the site and server. CFM displays as text.

Datacenter adjustments forced a change in IP addresses for my BlueOnyx server. The IP address of the server, and subsquently, the IP addresses of each of the sites within, had to be changed. Not a big issue, but then all of the CFM pages displayed as text. Not cool.

When the IP address was changed through the BlueOnyx Admin GUI, all of the vhosts were changed, inadvertantly dropping the JSP and Servlet switches. This can be added back either manually entering or through the GUI.

Option 1
Manually entering: find your SiteID for the site.

view plain print about
1basename $(ls -l /home/sites/| grep www.example.tld | awk '{ print $11}')

Then edit the vhosts file, using the correct SiteID

view plain print about
1vi /etc/httpd/conf/vhost/site1

adding back the JSP code:

view plain print about
1# BEGIN JSP SECTION. DO NOT EDIT MARKS OR IN BETWEEN.
2JkMount /* ajp13
3JkMount /*.jsp ajp13
4JkMount /servlet/* ajp13
5# END JSP SECTION. DO NOT EDIT MARKS OR IN BETWEEN.

Then restart httpd:

view plain print about
1/etc/init.d/httpd restart

Now you should be serving up those fancy CFM pages.

Option 2
Through the GUI, in the Web settings for the site, uncheck Enable JSP and Servlets and save. When it finishes saving and resetting, recheck or enable Enable JSP and Servlets and save. This will add 2 lines of the above code block, but you still need to add this to run CFML.

view plain print about
1JkMount /* ajp13

So you still have to edit vhosts (SiteID!)

view plain print about
1vi /etc/httpd/conf/vhost/site1

Change the JSP section from this:

view plain print about
1# BEGIN JSP SECTION. DO NOT EDIT MARKS OR IN BETWEEN.
2JkMount /*.jsp ajp13
3JkMount /servlet/* ajp13
4# END JSP SECTION. DO NOT EDIT MARKS OR IN BETWEEN.
to this:
view plain print about
1# BEGIN JSP SECTION. DO NOT EDIT MARKS OR IN BETWEEN.
2JkMount /* ajp13
3JkMount /*.jsp ajp13
4JkMount /servlet/* ajp13
5# END JSP SECTION. DO NOT EDIT MARKS OR IN BETWEEN.

Then restart httpd:

view plain print about
1/etc/init.d/httpd restart

Back in business, running your fantastice CFML site!

BlueOnyx Recursion Error

We moved a site off of the BlueOnyx box to a wordpress site, but wanted to continue using the BlueOnyx server for mail and mailing list management. I went into my domain registrar and reset the DNS servers to the new ones outside of my hosting provider's.

When sending an email to one of the mailing lists on this domain, I received the following error:

An error occurred while sending mail. The mail server responded:
5.0.0 rewrite: excessive recursion (max 50), ruleset canonify. Please check the message recipient
touchplayers@dallastouch.org and try again.

In the BlueOnyx GUI, I changed the Host Name for the domain from "www" to "mail". I ensured that the site was not managing any domains. Under DNS, the Selected domains box was empty. I restarted sendmail

view plain print about
1/sbin/service sendmail restart

Testing the email list produced this error on a returned email:

----- The following addresses had permanent fatal errors -----

(reason: 553 5.3.5 system config error)
----- Transcript of session follows -----
553 5.3.5 mail.mydomain.org. config error: mail loops back to me
(MX problem?)
554 5.3.5 Local configuration error

I made sure we had a 2 A records in the new DNS server. An A record that generated mail.mydomain.org and an MX record that pointed to that A record.

Testing the email server after that produced the same loop back error.

Changed the the Host name back to "www" from "mail" and restarted sendmail. Definition of insanity - same result. Recursion error. Changed the Host name, once again, to "mail".

Back to BlueOnyx GUI. Under "Services" on the left menu, clicked Web, checked to make sure the domain was a web server alias - mydomain.org. Checking just below on the menu, Email, and made sure that the Email Server Aliases were there - mydomain.org & mail.mydomain.org. Saved.

Went to /etc/mail/local-host-names and made sure that mydomain.org & mail.mydomain.org were present and www.mydomain.org was NOT present.

Restarted sendmail.

view plain print about
1cat /etc/mail/local-host-names
2/sbin/service sendmail restart

Here's the checklist:

  1. Change the Host name from "www" to "mail".
  2. Add A record for mail.mydomain.org and an MX record to point to it.
  3. In BO, make sure the domain, mydomain.org, is a Web Server Alias, under Web Settings
  4. In BO, make sure that mydomain.org & mail.mydomain.org are Email Server Aliases under Email Settings
  5. Check /etc/mail/local-host-names - mydomain.org & mail.mydomain.org present, www.mydomain.org absent
  6. Restart sendmail

Mura on Railo and BlueOnyx

Once Railo is installed and configured on BlueOnyx, make sure you have a MySQL database created and have all the connection info, like username, database name, user password. Create the datasource in Railo Admin.

Download Mura Standard from www.getmura.com/download/mura-downloads/ to your local machine. Unzip or extract the .ZIP file. FTP all files up to your sites /web/ directory. I deleted everything in the /web/ folder EXCEPT /WEB-INF/. These files were created with the Railo install and left from the BO initial site creation.

In your browser, go to http:///index.cfm

I received this error:

Railo 3.3.1.000 Error (application) Message can't copy file [/home/.sites/33/site22/web/config/templates/settings.template.cfm] to [/home/.sites/33/site22/web/config/settings.ini.cfm] Detail Permission denied Stacktrace The Error Occurred in /home/.sites/33/site22/web/config/applicationSettings.cfm: line 88 86: 87: 88: 89: 90: called from/home/.sites/33/site22/web/Application.cfc: line 48 46: ---> 47: 48: 49: 50: We need to add Tomcat to the site's group and change permissions to write for the group on the /web/config/ directory and contents.

We need to adjust permissions

view plain print about
1vi /etc/group
find your site's group, e.g., site22 add tomcat to the group, similar to:
view plain print about
1site22:x:599:johnny,admin,billy,tomcat

Then recursively add write permissions for the /web/config/ directory. Once you are in the /web/ directory.

view plain print about
1chmod -R g+w config

This will allow site members to FTP files.

This will fix the permission denied for the config stuff

view plain print about
1chmod o+w config
But we probably didn't have to do that if we do this....

Navigate up a level and change ownership of /web/ to tomcat.

view plain print about
1cd ../
2chown tomcat.site22 web

Next to run the SEO URL query strings for Mura, you'll have to modify the /web/WEB-INF/web.xml file to allow the wildcards:

view plain print about
1vi /web/WEB-INF/web.xml

add the following lines:

view plain print about
1��<servlet-mapping>
2� ��<servlet-name>CFMLServlet</servlet-name>
3� ��<url-pattern>/index.cfm/*</url-pattern>
4��</servlet-mapping>
in with the rest of the servlet-mappings.

Restart tomcat.

view plain print about
1/sbin/service tomcat5 restart

You should be able to run your Mura site without issue. If you do, please comment here and I'll look into it.

BlueOnyx 5108R 64-bit Version Released

So far BlueOnyx had only been available as 32-bit version (5106R on CentOS 5.7, or 5107R on Scientific Linux 6.1).

While this isn't much of a limitation for a general purpose internet server, there sure are times and purpose where 64-bit may offer some extra advantages. One is the ability to run larger MySQL databases.

Software wise 5107R and 5108R are very, very close. Only three modules ("cce", "i18n" and "base-java.mod") needed some special provisions that Michael Stauber could build on a 64-bit system. The rest of the GUI code is actually unchanged. And even where changes had to be made, it was just architectural stuff. Such as that the system libraries on a 64-bit reside under /lib64/ instead of /lib/.

For typical day to day usage there is nothing special or really different from 5107R.

The only difference is that you don't need a PAE kernel to use more than 8GB of RAM, as the standard 64-bit kernel is already handling that.

Performance wise 64-bit should be a bit faster here and there, as CPU, RAM and the pipelining to the I/O devices ought to be a bit faster. Apache and MySQL on a 64-bit system also benefit slightly from better memory management.

The only thing where you have to be careful is when you install extra software. There you of course need to pick 64-bit RPMs, 64-bit 5108R PKGs or code that was compiled for "X86_64" instead of "i386" or "i686"

In terms of features, functionality and ease of install it is identical to BlueOnyx 5107R and from now on both 5107R and 5108R will be very close cousins code wise and update wise.

For more info and downloads go to http://www.blueonyx.it

Windows Explorer for FTP on BlueOnyx is a No Go

With clients that use Windows Explorer for FTP on their BlueOnyx site, well they are just out of luck. It won't work. It puts them into their user directory on the server.

You'll need to get to the root web folder.
It looks like this: /web

When using Windows Explorer, login will place you in /.users/{Site #}/{username} folder and will not allow you to navigate up and out.

Solution = FileZilla

FileZilla is a free FTP solution. FileZilla is open source software distributed free of charge under the terms of the GNU General Public License.

Download FileZilla.
http://filezilla-project.org/download.php?type=client
There is plenty of documentation on how everything works on their site.

Here are easy instructions on getting started accessing your web files. Remember this BlueOnyx user has to be Site Admin for their site.

  1. Install and open FileZilla
  2. Click on the upper left hand box for Site Manager
  3. Click New Site and name your site
  4. On the right under General Tab, in the Host field enter in your site, ftp.mysitename.com or www.mysitename.com (it won't matter) Select Normal for Logon Type.
  5. Type in your assigned email credentials for User and Password. You should be the Site Admin.
  6. Click Connect.

Once connected you will have to navigate up from your user folder to the root /web folder Here you will see your site files.

BlogCFC Pod Error on Railo

When attempting to edit a Pod in the BlogCFC pod manager on Railo, the resulting error pops up:

attribute validateAt is not supportrd for tag input

shouldn't that be:

attribute validateAt is not supported for tag input

Apparently Railo does not support the validatAt attribute, or maybe it is just not "supportrd", no matter the OS.

The fix is to go into /admin/podform.cfm and around line 54 remove

view plain print about
1validateat="onBlur" validate="regular_expression" pattern="[A-Za-z]" message="Please enter only Alpha characters for the Pod Title"

Transforming:

view plain print about
1<cfform action="pod.cfm" method="post">
2                Pod Name: <cfinput value="#url.pod#" validateat="onBlur" validate="regular_expression" pattern="[A-Za-z]" message="Please enter only Alpha characters for the Pod Title" type="text" name="NewPod" size="25"><br>
3.....

To:

view plain print about
1<cfform action="pod.cfm" method="post">
2                Pod Name: <cfinput value="#url.pod#" type="text" name="NewPod" size="25"><br>
3.....

You will then have to do your own personal validation when editing your Pod Title, which means letters only with no spaces, special characters or numbers.

BlueOnyx Note:
On BlueOnyx, after making the above changes, attempting to save your pod edits produces this error:

no write access to source file [/home/.sites/85/site9/web/includes/pods/tagcloud.cfm]

no write access to source file [/home/.sites/85/site9/web/includes/pods/tagcloud.cfm] at railo.runtime.tag.FileTag.checkFile(FileTag.java:915):915 at railo.runtime.tag.FileTag.actionWrite(FileTag.java:513):513 at railo.runtime.tag.FileTag.doStartTag(FileTag.java:297):297 at blogcfcadmin.pod_cfm$cf.call(/home/.sites/75/site8/web/blogcfcadmin/pod.cfm:26):26 at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:764):764 at railo.runtime.listener.ClassicAppListener._onRequest(ClassicAppListener.java:35):35 at railo.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:24):24 at railo.runtime.PageContextImpl.execute(PageContextImpl.java:1973):1973 at railo.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:280):280 at railo.loader.servlet.CFMLServlet.service(CFMLServlet.java:32):32 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803):803 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269):269 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188):188 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210):210 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172):172 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127):127 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117):117 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108):108 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151):151 at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:200):200 at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291):291 at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:775):775 at org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:704):704 at org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:897):897 at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685):685 at java.lang.Thread.run(Thread.java:619):619

No write permissions. Also BlogCFC is running as user, tomcat, which is not in this site's group (site9 group in this example). Add tomcat to group site9 and change group write permissions so that tomcat can modify the file.

See if tomcat is in group site9:

view plain print about
1cat /etc/group

Add tomcat to site9 group:

view plain print about
1/usr/sbin/usermod -a -G site9 tomcat

Next, change group permissions for site9 on the pods directory. Navigate the site's web directory first.

view plain print about
1chmod -R g+w includes/pods

Check your work. Is tomcat in site9? Do permissions show group write?

view plain print about
1cat /etc/group
2ls -la includes/pods

Restart Tomcat

view plain print about
1/sbin/service tomcat5 restart

Wait for the site to come back up and make your pod edits within BlogCFC's Pod Manager. You should have a successful edit!


Installing BlogCFC on Railo and BlueOnyx

If you are reading this, you probably already know about BlogCFC. It's great. This blog is using it. The link is at the bottom of the page and here as well. BlogCFC.

To install BlogCFC on Railo running on BlueOnyx....

Open the client folder and place the contents under /web/ Delete Application.cfc from /web/ which was created when Railo was deployed. BlobCFC uses Application.cfm.

The Application.cfc error was: key [ISCOLDFUSIONMX7] doesn't exist in struct (keys:applicationname)

BlogCFC on Railo / BlueOnyx Error - key [ISCOLDFUSIONMX7] doesn't exist in struct (keys:applicationname)

The next was: Table 'scrumhalfdb.tblBlogEntries' doesn't exist

BlogCFC on Railo / BlueOnyx Error - Table 'scrumhalfdb.tblBlogEntries' doesn't exist

This is because Linux & MySQL is case sensitive. The file blog.cfc around line 1000, function get Archives has tblBlogEntries camel cased when it should be all lowercase. Edit /web/org/Camden/blog/blog.cfc to correct this, convert tblBlogEntries to tblblogentries as the /install/mysql.sql creates the tables.

The blog now works and shows no blog entries.

BlogCFC on Railo / BlueOnyx Works! - screen shot of empty blog

We have to change the BlogCFC Admin directory because it conflicts with the BlueOnyx Admin. I decided to change my folder name to blogadmin.

Change the admin directory to something else, like blogadmin A command find and replace /admin/ to /blogadmin/ of just the files in the newly named /blogadmin/ folder, formerly named /admin/.

But when we go to the blogadmin/folder, we get no login, just the body of the initial admin page:

BlogCFC on Railo / BlueOnyx not quite done - incomplete admin screen

This was because on line 42 of /web/blogadmin/Application.cfm:

view plain print about
1<cfif findNoCase("/admin", cgi.script_name) and not isLoggedIn() and not findNoCase("/blogadmin/notify.cfm", cgi.script_name)>

The

view plain print about
1<cfif findNoCase("/admin"...

needs to be

view plain print about
1<cfif findNoCase("/blogadmin"...

This was missed on the command find and replace because we had a trailing slash (/).

But wait, there's more...

Next you'll find that you cannot edit settings in BlogCFC admin settings. When changing settings in admin/settings.cfm you get an error with Script Name: /blogadmin/settings.cfm?

view plain print about
1Message: /home/.sites/<site #>/site<ID>/web/org/camden/blog/blog.ini.cfm (Permission denied)
2Java.io.FileNotFoundException

BlogCFC on Railo / BlueOnyx Error - Message: /home/.sites/../siteID/web/org/camden/blog/blog.ini.cfm (Permission denied)
Java.io.FileNotFoundException

This is because of Linux permissions. /home/.sites/siteNumber/siteID/web/org/ is owned by the site admin and needs to be owned by Tomcat. Change ownership to tomcat:

view plain print about
1chown -R tomcat.site<ID> /home/.sites/<site #>/site<ID>/web/org/

Now you will be able to save settings for BlogCFC.

Next issue to deal with is SES URLs in Tomcat. Because BlogCFC takes advantage of SES URLs adjustments need to be made within Tomcat's web.xml.

Another way around is to disable the SES coding in the BlogCFC code. In this link, http://www.coldfusionjedi.com/forums/messages.cfm?threadid=BB778077-E1D7-BD85-E2A147C3B0F4ECBA , Ray tells us to edit makeCategoryLink which is for categories. makeLink for entries. Those are both in blogcfc. You would also need to edit the categories pod.

Otherwise we can edit Tomcat's web.xml by adding the following:

view plain print about
1<servlet-mapping>
2 <servlet-name>CFMLServlet</servlet-name>
3 <url-pattern>/index.cfm/*</url-pattern>
4 </servlet-mapping>
5
6 <servlet-mapping>
7 <servlet-name>CFMLServlet</servlet-name>
8 <url-pattern>/page.cfm/*</url-pattern>
9 </servlet-mapping>

We have to add the wildcards for both page.cfm and index.cfm. If you add pages to your blog site they are referenced by page.cfm and will fail otherwise.

If you make a mistake here or over experiment with the servlet mappings and url patterns, your site's Tomcat instance will fail to start correctly or even at all.

You will have to restart Tomcat in order for the changes to take effect.

Stopping and starting Tomcat through the BlueOnyx Server Management Tomcat Host Manager Interface results in an error.

HTTP Status 503 - This application is not currently available type Status report message This application is not currently available description The requested service (This application is not currently available) is not currently available. Apache Tomcat/5.5.23

BlogCFC on Railo / BlueOnyx Error - Tomcat Error -HTTP Status 503 - This application is not currently available

Therefore, we must Restart Tomcat from the command line for the whole server:

view plain print about
1/sbin/service tomcat5 restart

Don't be too anxious, the shell command line will report Tomcat has started but Railo and everything else has to load too. Wait a couple of more seconds and then test the site.

BlueOnyx MySQL Admin phpMyAdmin

If you are running MySQL on BlueOnyx, you can manage your databases through phpMyAdmin without having to go through the BlueOnyx GUI.

https://<yourdomain>:81/phpMyAdmin/ and login. You can manage your BlueOnyx MySQL database for your site. Even with PHP turned off for your site.

BlogCFC pod updates on Railo BlueOnyx error

The Problem:
Permission denied when updating pods on BlogCFC on Railo on BlueOnyx. Permission denied invalid file [/home/.sites//web/includes/pods/pods.xml]

The Solution:
This is because the pods.xml file is not in in the /web/includes/pods/ directory. Assuming, without looking at the code that BlogCFC pods creates pod.xml when the pods are initially updated. We can create the file as shown.

Login as root and cd into the pods directory.

view plain print about
1[root@www pods]# ls
2archives.cfm monthlyarchives.cfm recentcomments.cfm subscribe.cfm
3calendar.cfm pages.cfm rss.cfm tagcloud.cfm
4feed.cfm recent.cfm search.cfm

Create the pods.xml and change ownership to tomcat.
view plain print about
1[root@www pods]# touch pods.xml
2[root@www pods]# chown tomcat.site8 pods.xml
3[root@www pods]# ls -l
4total 48
5-rw-r--r-- 1 siteuser site8 1049 Dec 28 21:20 archives.cfm
6-rw-r--r-- 1 siteuser site8 4809 Dec 28 21:20 calendar.cfm
7-rw-r--r-- 1 siteuser site8 1267 Dec 28 21:20 feed.cfm
8-rw-r--r-- 1 siteuser site8 1181 Dec 28 21:20 monthlyarchives.cfm
9-rw-r--r-- 1 siteuser site8 779 Dec 28 21:20 pages.cfm
10-rw-r--r-- 1 tomcat site8 0 Jan 7 11:41 pods.xml
11-rw-r--r-- 1 siteuser site8 1132 Dec 28 21:20 recent.cfm
12-rw-r--r-- 1 siteuser site8 1720 Dec 28 21:20 recentcomments.cfm
13-rw-r--r-- 1 siteuser site8 665 Dec 28 21:20 rss.cfm
14-rw-r--r-- 1 siteuser site8 940 Dec 28 21:20 search.cfm
15-rw-r--r-- 1 siteuser site8 3723 Dec 28 21:20 subscribe.cfm
16-rw-r--r-- 1 siteuser site8 2188 Dec 28 21:20 tagcloud.cfm

Change write permissions so the site8 group can write. This is so that siteuser can write to the files as well. If one of the files owned by siteuser is executing the write to pod.xml then it will complete. As it turns out, after testing, this step is completely unnecessary. User tomcat does all the writing. This note is left for reference only.
view plain print about
1[root@www pods]# chmod g+w pods.xml
2[root@www pods]# ls -l
3total 48
4-rw-r--r-- 1 siteuser site8 1049 Dec 28 21:20 archives.cfm
5-rw-r--r-- 1 siteuser site8 4809 Dec 28 21:20 calendar.cfm
6-rw-r--r-- 1 siteuser site8 1267 Dec 28 21:20 feed.cfm
7-rw-r--r-- 1 siteuser site8 1181 Dec 28 21:20 monthlyarchives.cfm
8-rw-r--r-- 1 siteuser site8 779 Dec 28 21:20 pages.cfm
9-rw-rw-r-- 1 tomcat site8 0 Jan 7 11:41 pods.xml
10-rw-r--r-- 1 siteuser site8 1132 Dec 28 21:20 recent.cfm
11-rw-r--r-- 1 siteuser site8 1720 Dec 28 21:20 recentcomments.cfm
12-rw-r--r-- 1 siteuser site8 665 Dec 28 21:20 rss.cfm
13-rw-r--r-- 1 siteuser site8 940 Dec 28 21:20 search.cfm
14-rw-r--r-- 1 siteuser site8 3723 Dec 28 21:20 subscribe.cfm
15-rw-r--r-- 1 siteuser site8 2188 Dec 28 21:20 tagcloud.cfm

Now we can update the pods, their order and display.

But going to the blog itself we see that nothing has changed. Why is that? Because we did not refresh our blog cache. Go back to the admin and click on "refresh blog cache" from the menu.

Tomcat consistently crashes on BlueOnyx

Could not find any default settings for memory and heap sizes. Out of memory error PermGen message similar to:
Exception in thread "TP-Processor209" java.lang.OutOfMemoryError: PermGen space

view plain print about
1[root@www /]# cat /usr/share/tomcat5/logs/catalina.out
2<snip>
3java.lang.OutOfMemoryError: PermGen space
4Exception in thread "TP-Processor210" java.lang.OutOfMemoryError: PermGen space
5Exception in thread "TP-Processor209" java.lang.OutOfMemoryError: PermGen space
6Exception in thread "TP-Processor216" java.lang.OutOfMemoryError: PermGen space
7Exception in thread "TP-Processor215" java.lang.OutOfMemoryError: PermGen space
8Exception in thread "TP-Processor214" java.lang.OutOfMemoryError: PermGen space
9Exception in thread "TP-Processor213" java.lang.OutOfMemoryError: PermGen space
10Exception in thread "TP-Processor217" java.lang.OutOfMemoryError: PermGen space
11Exception in thread "TP-Processor4" java.lang.OutOfMemoryError: PermGen space
12Using CATALINA_BASE: /usr/share/tomcat5
13Using CATALINA_HOME: /usr/share/tomcat5
14Using CATALINA_TMPDIR: /usr/share/tomcat5/temp
15Using JRE_HOME:
16java.lang.reflect.InvocationTargetException
17Exception in thread "main" java.lang.OutOfMemoryError: PermGen space
18Using CATALINA_BASE: /usr/share/tomcat5
19Using CATALINA_HOME: /usr/share/tomcat5
20Using CATALINA_TMPDIR: /usr/share/tomcat5/temp
21</snip>

Following recommendations memory was set as follows:

Initial Java heap size 512m = "-Xms512m"
Maximum Java heap size 512m = "-Xmx512m"
PermGen space initial permsize 256m = "-XX:PermSize=256m"
PermGen space maximum permsize 256m = "-XX:MaxPermSize=256m"
Memory Pool Newsize 128m = "-XX:NewSize=128m"

Edit:
/etc/tomcat5/tomcat5.conf
and
/usr/share/tomcat5/conf/tomcat5.conf
and add:

view plain print about
1JAVA_OPTS="-Xms512m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:NewSize=128m"

Restart Tomcat

view plain print about
1/sbin/service tomcat5 restart

This seemed to eliminate the Out Of Memory Error: PermGen space exception and the sites are running rock solid (so far!).

More Entries

BlogCFC was created by Raymond Camden. This blog is running version 5.9.7. Contact Blog Owner