• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 11 subscribers
  • Views 1873 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

Timeout when Starting JBoss

Priya

Hi, we are upgrading from Appian 16.1 to 16.2. While starting the jboss server we are getting the below error
com.appiancorp.ix.ProducerException: type=content, srcId=1943, dstId=f79b4797-b677-4670-83b9-d147a8a569d4, cause=com.appiancorp.core.expr.exceptions.ParseException: com.appiancorp.process.expression.ExpressionRuntimeException$AppianExceptionProvider: Expression evaluation error at function 'load' parameter 3 [line 5]: Invalid list operator 'hash' (expecting comma) (APNX-1-4198-000), level=ERROR. Please find the attached full log as attached

console.log

OriginalPostID-212830

OriginalPostID-212830

  Discussion posts and replies are publicly visible

  • +1
    Appian Employee
    The relevant error is:

    JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
    ("core-service" => "management"),
    ("management-interface" => "native-interface")

    Are you using the Configure script to configure JBoss? This 300 seconds timeout was increased a long time ago in the product. This makes me think you're re-using your JBoss files and that they were never updated with the larger timeout value.
  • 0
    Hi Eduardo,
    we are not using configure scripts for Jboss. This Jboss was configured when we migrated to 7.10 version. From the log we could see that its failing when its trying to parse an object with the id as following
    srcId=1943, dstId=f79b4797-b677-4670-83b9-d147a8a569d4, .
    We were able to solve this issue as below.
    1. we reverted the DB, and started the old instance.
    2. With the UUId and SRC ID we found the object.
    3. Deleted the application to which this object belonged.
    4. Shutdown the jboss server and Appian instance
    5. Repeated the installation of 16.2 version and repeated the migration activity.

    Now we are able to start the servers without any issues.
    The point we noted here is that we were able to bring up the old instance (16.1) with the application that caused the issue. So we are not sure if that application had any object that is incompatible with 16.2

© 2024 Appian. All rights reserved.