Entries for "OutOfMemoryError Java heap space" errors similar to the following are found in the logs for a Smarts application environment:
[September 5, 2012 11:24:43 AM GMT+01:00 +472ms] t@1266xxxxxx
ASAM_MESSAGE-*-INFO-.[Connector] Attempting (re)connection to JMS.
[September 5, 2012 11:24:43 AM GMT+01:00 +473ms] t@1266xxxxxxx
ASAM_MESSAGE-*-FINE-.[Connector] Call InitialContext:{java.naming.provider.url=jnp://10.x.x.x:1099/, java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, jnp.disableDiscovery=true, jnp.timeout=60000, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces}
[September 5, 2012 11:24:43 AM GMT+01:00 +482ms] t@1266xxxxxx
ASAM_MESSAGE-*-SEVERE-.[Connector] Exception Type:java.lang.OutOfMemoryError Java heap space
./sm_server -n ALCATEL-SAM -c alcatel-sam --output --daemon --java=maxheapsize=1024M
If you are starting the domain as a service, you will need to modify the service script accordingly for this change.