Facing the below error while running data-server in 18.1 version even after placing permanent license?

[main] INFO com.appian.data.TopologyFactory - Loading topology /appian/data-server/conf/appian-topology.xml
281 [main] INFO com.appian.data.server.config.CustomPropertiesConfiguration - Configuration file custom.properties was loaded successfully. (Reload check = 30000 ms)
291 [main] INFO com.appian.data.server.Watchdog - Initializing log4j (processName=wd-5400, logsDir=/appian/data-server/../logs/data-server) from /appian/data-server/conf/log4j.properties
2018-04-15 23:45:23,408 wd-5400 [main] INFO com.appian.data.server.JvmStarter - Starting JVM: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.161-3.b14.el6_9.x86_64/jre/bin/java -server -Duser.timezone=GMT -Xms64m -Xmx128m -Dds.home=/appian/data-server -cp /appian/data-server/lib/appian-data-server-classpath-0.72.2.jar com.appian.data.server.Watchdog -f
2018-04-15 23:45:25,385 wd-5400 [main] ERROR com.appian.data.server.Watchdog - Shutting down with exit code 1...
com.appian.data.server.UnrecoverableError: Could not establish WebSocket connection with localhost:5400. The target JVM process exited abnormally. Check for earlier errors (e.g. JVM startup errors).
at com.appian.data.server.HeartbeatListener$SyncHeartbeatListenerBuilder.create(HeartbeatListener.java:157)
at com.appian.data.server.JvmStarter.startSync(JvmStarter.java:45)
at com.appian.data.server.Watchdog.main(Watchdog.java:697)
Caused by: io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: /0.0.0.0:5400
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:347)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:340)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:627)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:551)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:465)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:437)
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873)
at java.lang.Thread.run(Thread.java:748)

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer
    Hi Veera ,

    I believe you have placed your permanent license ( k3.lic ) in ..../linux64 or .../windows64 folders but here The issue was from 18.1 V which expects one more licence for starting data -server that is k4.lic for running data-server this concept is included newly in 18.1 Version.

    For your reference ( docs.appian.com/.../Requesting_and_Installing_a_license.html ).

    Thanks
Reply
  • 0
    Certified Senior Developer
    Hi Veera ,

    I believe you have placed your permanent license ( k3.lic ) in ..../linux64 or .../windows64 folders but here The issue was from 18.1 V which expects one more licence for starting data -server that is k4.lic for running data-server this concept is included newly in 18.1 Version.

    For your reference ( docs.appian.com/.../Requesting_and_Installing_a_license.html ).

    Thanks
Children
  • Thanks Prakash..
    I had permanent license for k4.lic but not for k3.lic. Will this cause the below error?
    The error says "The target JVM process exited abnormally. Check for earlier errors (e.g. JVM startup errors)."
    Is there any other reason to show the above error message?
  • 0
    Certified Senior Developer
    in reply to veerag6659
    Can you share the Complete Log File from <JBOSS_HOME>\standalone\log?
  • Please find the below errors which are suite.ear.failed log.

    "{
    \"JBAS014671: Failed services\" => {\"jboss.web.deployment.default-host./suite\" => \"org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./suite: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context
    Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context\"},
    \"JBAS014771: Services with missing/unavailable dependencies\" => [
    \"jboss.deployment.subunit.\\\"suite.ear\\\".\\\"email-handler.jar\\\".INSTALL is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".deploymentCompleteService]\",
    \"jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]\",
    \"jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".INSTALL is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"unattended-request-handler.jar\\\".deploymentCompleteService]\",
    \"jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]\",
    \"jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]\",
    \"jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean.ValidatorFactory is missing [jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean]\",
    \"jboss.deployment.unit.\\\"suite.ear\\\".deploymentCompleteService is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"email-handler.jar\\\".deploymentCompleteService, jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".deploymentCompleteService, jboss.deployment.subunit.\\\"suite.ear\\\".\\\"unattended-request-handler.jar\\\".deploymentCompleteService]\",
    \"jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean]\",
    \"jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]\"
    ]
    }"
  • 0
    Certified Senior Developer
    in reply to veerag6659
    Hi Veera ,

    As per my understanding It was missing .jar files in your suite.ear\lib directory. Do you have a previous installation or is this your
    first? Also, if you followed convention, you made a backup. Check in the backup directory weather all jars are existing or not?
    If you found any missing jars add those jars and do the below steps

    1. Stop JBoss
    2. Delete JBOSS_HOME\standalone\log\*
    3. Rename JBOSS_HOME\standalone\deployment\*.undeployed to *.dodeploy
    4. Rename JBOSS_HOME\standalone\deployment\*.failed to *.dodeploy
    5. Rename APPIAN_HOME\ear\suite.ear.failed to suite.ear.dodeploy
    6. Start JBoss

    Thanks
  • Actually this is related to jboss start up. But iam facing problem with data-server startup. Don't know why the below error is coming up:
    ERROR com.appian.data.server.Watchdog - Shutting down with exit code 1...
    com.appian.data.server.UnrecoverableError: Could not establish WebSocket connection with localhost:5400. The target JVM process exited abnormally. Check for earlier errors (e.g. JVM startup errors).

    Thanks for your continuous reply and helping me out.
  • 0
    Certified Senior Developer
    in reply to veerag6659
    Can you copy the k4.lic file to the correct path (<APPIAN_HOME>/data-server/engine/bin/q/l64/) and start the data-server.
  • the issue iam facing is :

    ERROR com.appian.data.server.Watchdog - Shutting down with exit code 1...
    java.lang.RuntimeException: Unable to determine the version of the data in '/appian/data-server/data'. The 'ds_txEffects' kafka topic exists, however, the '/appian/data-server/data/version.info' file is missing.
    at com.appian.data.server.migration.MigrationEngine.loadDataVersion(MigrationEngine.java:193)
    at com.appian.data.server.migration.MigrationEngine.isMigrationRequired(MigrationEngine.java:65)
    at com.appian.data.server.Watchdog.startup(Watchdog.java:130)
    at com.appian.data.server.Watchdog.main(Watchdog.java:691)


    If anyone went through this kind of issue. Please let me know the solution to resolve.
  • 0
    A Score Level 1
    in reply to veerag6659
    Have you updated it recently? or installed a new hotfix?
  • Thanks for responding Benhail. The issue is with JDK path and it got corrected.