Mani's Blog

August 25, 2011

False Alarm on MEM “InnoDB Tablespace Cannot Automatically Expand”

Filed under: MySQL — mani @ 1:09 am

Issue

MEM is throwing false alerts regarding the InnoDB autoextend capabilities. We got couple of alert from MySQL Enterprise Dashboard saying “InnoDB Tablespace Cannot Automatically Expand”.   When we check the DB my.cnf configured correctly.

Following solution was applied to correct the issue.

Cause

The issue is caused when the connection pool is being exhausted after reading the initial variable values. A connection will be attempted to evaluate the SQL function locate() for the rule, since it does not exist in the JAVA code. The attempt fails since a connection cannot be established, the function defaults to false causing the rule to fail, and so a false alert is sent.

This was repeated in test cases to justify the cause of the false alerts.

Solution

Increased default.maxActive from 70 to 150.

  1. Open the file #INSTALL_DIR/apache-tomcat/webapps/ROOT/WEB-INF/config.properties in your favourite text editor.
  2. Locate the line “default.maxActive=70”.
  3. Change the line to be “default.maxActive=150” (or a larger number if required, but 200+ should not be needed).
  4. Save the changes to the file.
  5. Restart the tomcat service (example is for Linux/Unix installs):
shell>  ./mysqlmonitorctl.sh restart
Advertisements

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: