MonthMay 2012

JBoss 6.x Tuning/Slimming

Introduction

The following slimming recommendations are for a standard JBoss AS 6.0.0 final (Community) “All” configuration.

Slimming is very application specific, so this is by no means a universal document. If you have documented the process for slimming other services for JBoss 6.x please add to them here.

The slimming document for JBoss5.x http://community.jboss.org/wiki/JBoss5xTuningSlimming will be not complete out of date for JBoss 6.x, so you might look into.

Remove hornetQ JMS (Java Message Service)

In JBOSS_HOME/server/<node>/deploy/ remove:

  • hornetq
  • jms-ra.rar

In JBOSS_HOME/server/<node>/deployers/ remove:

  • hornetq

In JBOSS_HOME/common/lib remove (only if no server configuration use hornetq)

  • hornetq*

In JBOSS_HOME/server/<node>/conf/ remove useless configuration:

  • delete element <application-policy name=”hornetq”> from login-config.xml
  • remove props/hornetq-roles.properties
  • remove props/hornetq-users.properties

Turn off hot deployment

In JBOSS_HOME/server/<node>/deploy/ remove:

  • hdscanner-jboss-beans.xml

Remove Hypersonic DB

In JBOSS_HOME/server/<node>/deploy/ remove:

  • hsqldb-ds.xml

In JBOSS_HOME/common/lib remove (only if no server configuration use hornetq)

  • hsqldb.jar hsqldb-plugin.jar

The following services use the “DefaultDS” datasource for persistence:

  • JUDDI
  • UUID key generator
  • EJB2 timer

One option is to remove or adapt such services, the other option is to provide a datasource “DefaultDS” for another RDBMS.

Datasource examples will be located in docs/examples/jca.

EJB2 Timer service

To deactivate persistence for EJB2 timer replace:

with:

Remove JUDDI

In JBOSS_HOME/server/<node>/deploy/ remove:

  • juddi-service.sar

Remove Key Generator

In JBOSS_HOME/server/<node>/deploy/ remove:

  • uuid-key-generator.sar

Remove Administration console

In JBOSS_HOME/common/deploy/ remove:

  • admin-console.war

In JBOSS_HOME/server/<node>/deploy/ remove:

  • admin-console-activator-jboss-beans.xml

Remove JMX console

https://community.jboss.org/message/734664#734664

In JBOSS_HOME/common/deploy/ remove:

  • jmx-console.war

In JBOSS_HOME/server/<node>/deploy/ remove:

  • jmx-console-activator-jboss-beans.xml

Remove JBoss Web Services console

In JBOSS_HOME/common/deploy/ remove:

  • jbossws-console.war

In JBOSS_HOME/server/<node>/deploy/ remove:

  • jbossws-console.war
  • jbossws-console-activator-jboss-beans.xml

Build Your Checklist

The Weekly Review: How One Hour Can Save You A Week’s Worth of Hassle and Headache

A weekly review checklist is an essential tool to making sure you touch on all three of the pillars mentioned above. Here’s what a basic review checklist looks like, courtesy of GTD TimesPhoto by Karuka (Shutterstock).

Get Clear

  • Collect loose papers and materials
  • Get Inbox to zero
  • Empty your head

Get Current

  • Review Action Lists
  • Review past calendar data
  • Review upcoming calendar
  • Review Waiting For list
  • Review Project (and larger outcome) lists
  • Review any relevant checklists

Get Creative

  • Review Someday/Maybe
  • Be creative and courageous

If you need more detail, David Allen offers a template checklist (free, but requires registration) on his site to get you started, and this one (scroll down to weekly review) is another good example. On the GTD forums, some users have shared their own checklists for inspiration. Whether you use a template or build yours from scratch (and it doesn’t have to be long—just those things you want to make sure you do every week), make sure you populate it with things you want to review and not do. Remember, you’re not supposed to spend time working during your weekly review—just reviewing.

© 2017 Ziben IT Solutions

Theme by Anders NorénUp ↑