Exploded EAR file queries

Solution Unverified - Updated -

Environment

  • JBoss-Enterprise Application Platform (EAP)
    • 4.x
    • 5.0.x
    • 5.1.x

Issue

  • How can I configure JBoss to not explode the archived ear file if it is already there in /tmp/deploy dir.
  • I assume the runtime application files are in /tmp/deploy/ dir. Can I change this tmp directory through some configuration ?
  • Is it possible to configure the name pattern of the expanded ear/war in the "tmp" directory ?

Resolution

  • It is not possible to stop JBoss from not exploding and archived ear or war. If you don't want this behaviour, deploy the archive as exploded in the first place.

  • The naming convention adopted for the sub-folder containing the exploded archive cannot be customised.

  • The system parameter jboss.server.temp.dir determines the location of the exploded archive. If unspecified, it defaults to directory  $JBOSS_HOME/server/$PROFILE/tmp  .  To override the default directory, set the system parameter -Djboss.server.temp.dir to directory of your choice. This can be done by modifying the JAVA_OPTS in the  $JBOSS_HOME/server/$PROFILE/conf/run.conf file for example


`JAVA_OPTS="-Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djboss.server.temp.dir=/home/jbossuser/jboss/jboss-eap-4.3/tmp"`

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.