Search Engine: Elastic

Article ID: 130830, created on May 17, 2017, last review on May 17, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 6.0


Upon restart of pau service, it fails to start with the following messages in console.log:

JBAS011048: Failed to construct component instance
concurrent access timeout on org.jboss.invocation.InterceptorContext$Invocation@7079c030 - could not obtain lock within 5000MILLISECONDS
Services which failed to start: service jboss.deployment.subunit."pau-ear.ear"."poakernel-ejb.jar"

Howerver, WildFly java process was still alive and further attempts to restart pau fail with different error and create new WildFly instance:

Caused by: Address already in use


Hostname of OA management node was not included in local hosts file. It is required by JBoss/WildFly to start and work properly.


  1. Kill all existing JBoss/Wildfly processes.
  2. Add OA Management node's backnet address and a hostname to /etc/hosts file.
  3. Start pau service.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF