How to change the Java heap size for WebSphere Application Server 6.1 profiles

How to change the Java heap size for WebSphere Application Server 6.1 profiles

Open the integrated solutions console
https://:9044/ibm/console/
Default login is
system:manager

Navigate to the JVM for the server profile you want to change

Application servers > server1 > Process Definition > Java Virtual Machine
Change these values
Initial Heap Size=512
Maximum Heap Size=512
These correspond to the Xms and Xmx params of the JVM. So make sure you do not set Max lower than Initial, nor set Max higher than available OS RAM. I am not sure if adding a K,M,or G to the number will work, it seems by default the numbers are considered MB. Be aware that your JVM is 32 bit so there is a mathematical limit (and practical limit) to how much memory it can address. 3800 MB is where you will likely top out for max heap space unless your OS limits you to 2GB, which puts your heap max down to 1600MB.

You will have to restart the WAS server profile instance to have this change take effect on the JVM.

Adding a datasource to the maven jetty plugin

In your pom.xml

           <plugin>
               <groupId>org.mortbay.jetty</groupId>
               <artifactId>maven-jetty-plugin</artifactId>
               <version>6.1.21</version>
               <configuration>
                    <!-- <jettyConfig>src/main/resources/devJetty.xml</jettyConfig>  -->
                    <webXml>${basedir}/src/main/resources/jetty-web.xml</webXml>
                    <jettyEnvXml>${basedir}/src/main/resources/jetty-env.xml</jettyEnvXml>
                   <contextPath>/OCM</contextPath>
                   <scanIntervalSeconds>3</scanIntervalSeconds>
                   <scanTargetPatterns>
                       <scanTargetPattern>
                           <directory>src/main/webapp/WEB-INF</directory>
                           <excludes>
                               <exclude>**/*.jsp</exclude>
                           </excludes>
                           <includes>
                               <include>**/*.properties</include>
                               <include>**/*.xml</include>
                           </includes>
                       </scanTargetPattern>
                   </scanTargetPatterns>
                   <stopKey>foo</stopKey>
                   <stopPort>9966</stopPort>
               </configuration>
           </plugin>
Key lines are
                    <webXml>${basedir}/src/main/resources/jetty-web.xml</webXml>
                    <jettyEnvXml>${basedir}/src/main/resources/jetty-env.xml</jettyEnvXml>

Define your jetty-env.xml like this:

<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC -//Mort Bay Consulting//DTD Configure//EN http://jetty.mortbay.org/configure.dtd>

<Configure class="org.mortbay.jetty.webapp.WebAppContext">

 <!-- an XADataSource                                                -->
 <New id="MAVENJETTYDS" class="org.mortbay.jetty.plus.naming.Resource">
   <Arg></Arg>
   <Arg>jdbc/datasource</Arg>
   <Arg>
         <New class="org.apache.commons.dbcp.BasicDataSource">
                     <Set name="driverClassName">[[jdbc driver class]]</Set> <!-- for example, com.ibm.db2.jcc.DB2Driver -->
                     <Set name="url">[[jdbc url]]</Set> <!-- for example, jdbc:db2://yourdbhostnameorip:[port]/yourdb -->
                     <Set name="username">[[username]]</Set><!-- for example, yourmom -->
                      <Set name="password">[[password]]</Set><!-- for example, correcthorsebatterystaple -->
                     <Set name="defaultCatalog">[[schema, if needed]]</Set>
         </New>
   </Arg>
  </New>
</Configure>

Then add the ref to your web.xml

<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" id="WebApp_1270163143862">
<pre>
   <!-- SNIP -->

<!-- Bug fix for editing locked CSS and JS running in Jetty -->
<servlet>
   <servlet-name>default</servlet-name>
   <servlet-class>org.mortbay.jetty.servlet.DefaultServlet</servlet-class>
   <init-param>
     <param-name>useFileMappedBuffer</param-name>
     <param-value>false</param-value>
   </init-param>
   <load-on-startup>0</load-on-startup>
</servlet>

       <resource-ref>
         <res-ref-name>jdbc/datasource</res-ref-name>
         <res-type>javax.sql.DataSource</res-type>
         <res-auth>Container</res-auth>
    </resource-ref>

</web-app>

JSP debug code

The following can be pasted into a JSP and then used to display (either in HTML source or in the browser window), the JSP Request, Session, Page, and Application settings for the environment and container the JSP is running within.

I have found this to be a quick useful way to get the lay of the land, when joining a project already in development.

<!-- 
 <%@ page import="java.util.*"%>
 <%
  Object eobj = request.getParameter("error");
  if (eobj != null) {
   Exception exception = null;
   Object obj = request.getAttribute("exception");
   if (obj != null && obj instanceof Exception) {
    exception = (Exception) obj;
   }
   if (exception == null) {
    obj = request.getAttribute("javax.servlet.error.exception");
    if (obj != null && obj instanceof Exception) {
     exception = (Exception) obj;
    }
   }
   if (exception != null) {
 %><pre>
  <%
   exception.printStackTrace(new java.io.PrintWriter(out));
  %>
 </pre>
 <%
  }
  }
  out.println("<h3>Request:</h3><ul>");
  Enumeration names = request.getHeaderNames();
  while (names.hasMoreElements()) {
   String name = (String) names.nextElement();
   out.println("<li>HEADER " + name + ": "
     + request.getHeader(name));
  }

  for (Enumeration e = request.getParameterNames(); e
    .hasMoreElements();) {
   String name = (String) e.nextElement();
   out.println("<li>PARAM " + name + "="
     + request.getParameter(name) + "</li>");
  }

  for (Enumeration e = request.getAttributeNames(); e
    .hasMoreElements();) {
   String name = (String) e.nextElement();
   out.println("<li>ATTRIB " + name + "="
     + request.getAttribute(name) + "</li>");
  }
  out.println("</ul><h3>Session:</h3><ul>");
  for (Enumeration e = session.getAttributeNames(); e
    .hasMoreElements();) {
   String name = (String) e.nextElement();
   out.println("<li>ATTRIB " + name + "="
     + session.getAttribute(name) + "</li>");
  }
  out.println("</ul><h3>Page Scope Attributes:</h3><ul>");
  for (Enumeration e = pageContext
    .getAttributeNamesInScope(pageContext.PAGE_SCOPE); e
    .hasMoreElements();) {
   String name = (String) e.nextElement();
   out.println("<li>ATTRIB "
     + name
     + "="
     + pageContext
       .getAttribute(name, pageContext.PAGE_SCOPE)
     + "</li>");
  }
  out.println("</ul><h3>Application Scope Attributes:</h3><ul>");
  for (Enumeration e = pageContext
    .getAttributeNamesInScope(pageContext.APPLICATION_SCOPE); e
    .hasMoreElements();) {
   String name = (String) e.nextElement();
   if (name.equals("com.sun.jsp.taglibraryCache")) {
    out.print("<li>ATTRIB " + name
      + "= <b>NULL POINTER!</b></li>");
    continue;
   }
   out.print("<li>ATTRIB " + name + "=");
   out.println(pageContext.getAttribute(name,
     pageContext.APPLICATION_SCOPE)
     + "</li>");
  }
  out.println("</ul>");
 %>
 -->

JSP for DataSource Connection Pool testing

If you need to test a datasource here is a JSP that will help you do it.

<%@ page language="java" contentType="text/html; charset=ISO-8859-1"
   pageEncoding="ISO-8859-1"%>
<%@ page import="java.sql.*,javax.naming.*,javax.sql.*" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Test Data Source</title>
</head>
<body>
<h1>Test Data Source</h1>
<p>Hello</p>
<%
    DataSource ds = null;
    Connection con = null;
    Statement stmnt = null;
    ResultSet resultSet = null;
   try {
       InitialContext ctx = new InitialContext();
       ds = (DataSource)ctx.lookup("java:comp/env/jdbc/DataSource");
       con = ds.getConnection();
    stmnt = con.createStatement();
    resultSet = stmnt.executeQuery("select * from PERSON");
    if (resultSet != null) {
        %><table><tr><%
       ResultSetMetaData resultSetMetaData = resultSet.getMetaData();
       int nOfColumns = resultSetMetaData.getColumnCount();
       for(int j = 0; j<nOfColumns; j++) {
           String columnLabel = resultSetMetaData.getColumnLabel(j+1);
           %><th><%=columnLabel %></th><%
       }
       %></tr><%
       if (resultSet.getType() != ResultSet.TYPE_FORWARD_ONLY) {
           resultSet.beforeFirst();
       }
       while (resultSet.next()) {
                %><tr><%
               for (int i = 1; i <= nOfColumns; ++i) {
                        %><td><%
                       Object  value = resultSet.getObject(i);
                       if (resultSet.wasNull()) {
                           %><b>null</b><%
                       } else {
                           %><%=value.toString() %><%
                       }
                       %></td><%
               }
               %></tr><%
       }
       %></table><%
    }
   } catch(NamingException e) {
       throw e;
   } catch(SQLException e) {
       throw e;
   } finally {
      try {
        if (resultSet != null) {
          resultSet.close();
        }
      } catch (SQLException e) {
      }
      resultSet = null;
      try {
        if (stmnt != null) {
          stmnt.close();
        }
      } catch (SQLException e) {
      }
      stmnt = null;
      try {
        if (con != null) {
          con.close();
        }
      } catch (SQLException e) {
      }
      con = null;
      ds = null;
   }
%>
</body>
</html>

Just change

java:comp/env/jdbc/DataSource

To what the name of your DataSource connection pool is.

Then change

select * from PERSON

To a test query from this table:

Cloudscape	#SQL SELECT 1
#DB2	#SQL SELECT COUNT(*) FROM SYSIBM.SYSTABLES
#Informix	#SQL SELECT COUNT(*) FROM SYSTABLES
#Microsoft SQL Server	#SQL SELECT COUNT(*) FROM SYSOBJECTS
#MySQL	#SQL SELECT 1
#Oracle	#SQL SELECT 1 FROM DUAL
#PointBase	#SQL SELECT COUNT(*) FROM SYSTABLES
#PostgreSQL	#SQL SELECT 1
#Progress	#SQL SELECT COUNT(*) FROM SYSTABLES
#Sybase	#SQL SELECT COUNT(*) FROM SYSOBJECTS

Do not use this code to interact with a datasource, this should only be used for figuring out what the name of a datasource you created in the J2ee container is and that it is working.

How do I use my web resource bundle within my Spring controller?

Here is how I did it:

In my controller:

import org.springframework.context.ApplicationContext; ...

@Autowired private ApplicationContext context; 

In the resource bundle ApplicationResources.properties

gotocode.error.notfound=Sorry {0} is not recognized as a code. 

Back in the controller

public static final String GOTOCODE_NOTFOUND_KEY = "gotocode.error.notfound"; 

public static final String CODE_NOT_FOUND_MESSAGE = "Sorry the entry {0} is not recognized as a code.";

...

public ModelAndView findNextInSeries(String code,..   

String errorMessage = context.getMessage(

GOTOCODE_NOTFOUND_KEY, new Object[] { code }, CODE_NOT_FOUND_MESSAGE, Locale.getDefault());   

Previously my ApplicationResources.properties was configured in the web.xml

http://java.sun.com/xml/ns/j2ee"     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" id="WebApp_1270163143862"></web-app>

 <display-name>Sample Spring Resource Bundle

 <distributable>

     

 <context-param>

 <param-name>javax.servlet.jsp.jstl.fmt.localizationContext

 <param-value>ApplicationResources

 

As well as in the Spring Application context configuration (dispatcher-servlet.xml):

J2EE App Server startup error in VM

When I am re-starting a proprietary J2EE app server (which requires Java 1.4.x). I periodically get this critical Java VM error:

# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_03-b02 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=2 tid=0x00a59768 nid=0x590 runnable
#

Heap at VM Abort:
Heap
 def new generation   total 36480K, used 31516K [0x10010000, 0x127a0000, 0x14ed0000)
  eden space 32448K,  971244656sed [0x10010000, 0x11ed7240, 0x11fc0000)
  from space 4032K,   01244656sed [0x11fc0000, 0x11fc0000, 0x123b0000)
  to   space 4032K,   01244656sed [0x123b0000, 0x123b0000, 0x127a0000)
 tenured generation   total 483968K, used 43490K [0x14ed0000, 0x32770000, 0x50010000)
   the space 483968K,   81244656sed [0x14ed0000, 0x17948a20, 0x17948c00, 0x32770000)
 compacting perm gen  total 35072K, used 34831K [0x50010000, 0x52250000, 0x56010000)
   the space 35072K,  991244656sed [0x50010000, 0x52213e60, 0x52214000, 0x52250000)
Dynamo exited abnormally.  For troubleshooting information go to the URL:
  http://www.atg.com/support
Press any key to continue . . .

I can get it very consistently when I restart the application multiple times rapidly. This is running under Windows 2003 Enterprise Server SP2. Googling for "Error ID: 43113F32554E54494D45110E435050030" gives me nothing. I read something about array initialization being a place to check. Since this is not 100% consistent, I am sure it will be a nightmare to really determine the actual cause and create a fix for it. Thankfully I don't think there is a problem with the 2007.1 release of the ATG Service platform, because they have moved away from the Dynamo Application Server and just use JBOSS, or WEBLOGIC as the app server. Also I think you can use Java 1.5 rather that 1.4. I suspect this is a problem in the DAS code (or the Java 1.4 VM) that only seems to occur when restarting DAS frequently. Some businesses heavily use the legacy 2006.3 version with the DAS app server, so it will continue to be an issue whenever I need to work in this environment and restart the app server.

I get impatient with these app servers, it takes long enough to start without having to wait a little extra time between restarts, just to ensure the app server does not crash.