• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 5 replies
  • Subscribers 11 subscribers
  • Views 4831 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

19.3 Upgrade - Tomcat Can't Connect to Data Server

Justin Watts
Certified Lead Developer

I'm working on upgrading a 19.2 instance to 19.3 and am having issues getting Tomcat to connect to the Data Server. It seems that Data Server is not listening on the port that Tomcat wants to connect with.

2019-08-31 13:59:09,396 [localhost-startStop-1] ERROR com.appiancorp.ads.designobjects.schema.DesignObjectSchemaManager - APNX-1-4408-001 - Failed to create DesignObjectSchema.
com.appian.data.client.AdsException: APNX-3-0300-000: Unable to process the request: org.apache.http.conn.HttpHostConnectException: Connect to localhost:5450 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

Strangely, at the start of Tomcat startup, it does report that Data Server is healthy, so it seems a specific aspect of data-server is malfunctioning.

2019-08-31 13:56:09,486 [wait-for-component] INFO com.appiancorp.common.startup.WaitForStatefulComponents - Appian component Data Server is healthy

Data Server itself is up and running, which has been verified with health.sh.

I ran nmap and netstat and confirm that my 19.2 instances all listen on port 5450 but my 19.3 does not. The only thing different I notice is that in 19.2 health.sh reports a "leader" status of true, while 19.3 doesn't. This attribute is not documented for either version, so I'm not sure if it is related.

I am using default appian-toplogy.xml and everything else is working as expected (can log in to the migrated instance)

Has any one else seen this issue?

  Discussion posts and replies are publicly visible

Parents
  • 0
    Appian Employee

    Hi Justin, what steps do you perform to reproduce this issue? I'd like to test this on my end to see if I am able to reproduce this as well.

  • 0
    Certified Lead Developer
     in reply to Tejas Kargutkar

    Hi Tejas-

    Sure thing. Let me know if you are looking for any other specifics.

    • Run 19.3 Linux installer
    • Copy data from previous 19.3 installation (K data, content, kafka logs, etc) - I will note I use a script I took from the docker tools to do this to avoid manual updates, though I can't see why this would matter.
    • Run configure script (I created a new repo from 19.3 for this and merged in my custom.properties to make sure appian-topology is still default
    • Start services, search, data-server, tomcat. Tomcat throws the error a few minutes into start up but will eventually start up correctly.

    I reinstalled a few times just to re-trace my steps and had this same experience 3 times or so.

Reply
  • 0
    Certified Lead Developer
     in reply to Tejas Kargutkar

    Hi Tejas-

    Sure thing. Let me know if you are looking for any other specifics.

    • Run 19.3 Linux installer
    • Copy data from previous 19.3 installation (K data, content, kafka logs, etc) - I will note I use a script I took from the docker tools to do this to avoid manual updates, though I can't see why this would matter.
    • Run configure script (I created a new repo from 19.3 for this and merged in my custom.properties to make sure appian-topology is still default
    • Start services, search, data-server, tomcat. Tomcat throws the error a few minutes into start up but will eventually start up correctly.

    I reinstalled a few times just to re-trace my steps and had this same experience 3 times or so.

Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.