• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 13 replies
  • Subscribers 9 subscribers
  • Views 10627 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

New installation, JBOSS not working, Fatal error

Praveen Nenawa

Hi, 

 

I am a bit new to Appian and trying to setup a local instance for learning purpose.

I have installed 18.1 and relevant hotfix too.

I am using JBOSS EAP 6.4. All the services/data server / Search server are starting as expecetd but not the Jboss server.

below are a part of the error log. Can anybody please help me understand what went wrong here?

PS: 1. I followed Qucik start guide 18.1 with MySQL/Jboss to set it up.
       2. I know one or two things about XML but nothing about JAVA/Jscript.

07:46:38,036 DEBUG [org.jboss.as.config] (MSC service thread 1-7) VM Arguments: -Djava.vendor=New Oracle -Xloggc:C:\appian\bin\jboss\jboss-eap-6.4\standalone\log\gc.log -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -XX:+UseCompressedOops -Dprogram.name=standalone.bat -Xms2048m -Xmx4096m -XX:+HeapDumpOnOutOfMemoryError -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC -Dorg.apache.catalina.connector.URI_ENCODING=UTF-8 -Duser.timezone=GMT -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Dfile.encoding=UTF-8 -Dappian.home.ear=C:\appian\ear -Djboss.as.management.blocking.timeout=3600 -Dorg.jboss.resolver.warning=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=C:\appian\bin\jboss\jboss-eap-6.4\standalone\log\server.log -Dlogging.configuration=file:C:\appian\bin\jboss\jboss-eap-6.4\standalone\configuration/logging.properties


07:46:43,688 WARN [org.jboss.messaging] (ServerService Thread Pool -- 22) JBAS011618: There is no resource matching the expiry-address jms.queue.ExpiryQueue for the address-settings #, expired messages from destinations matching this address-setting will be lost!

07:46:43,703 WARN [org.jboss.messaging] (ServerService Thread Pool -- 22) JBAS011619: There is no resource matching the dead-letter-address jms.queue.DLQ for the address-settings #, undelivered messages from destinations matching this address-setting will be lost!

07:47:24,356 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 11) JBAS014612: Operation ("add") failed - address: ([("deployment" => "suite.ear")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"suite.ear\")]"

07:47:24,356 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem deployment-scanner boot operations"

07:47:24,356 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"JBAS014784: Failed executing subsystem deployment-scanner boot operations\""

07:47:24,372 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

07:47:24,434 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) stopped in 54ms

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer
    Hi Praveen ,

    can you check once in your appian-mysql-ds.xml.
    Jndi-name and xa-datasource-property name should be same..but in your scenario you gave appianPrimary insted.


    jndi-name="jdbc/AppianDS"
    pool-name="MySqlDS"
    enabled="true"
    use-java-context="false">
    <xa-datasource-property name="URL">jdbc:mysql://localhost:3306/AppianDS?useOldAliasMetadataBehavior=true</xa-datasource-property>


    Thanks
Reply
  • 0
    Certified Senior Developer
    Hi Praveen ,

    can you check once in your appian-mysql-ds.xml.
    Jndi-name and xa-datasource-property name should be same..but in your scenario you gave appianPrimary insted.


    jndi-name="jdbc/AppianDS"
    pool-name="MySqlDS"
    enabled="true"
    use-java-context="false">
    <xa-datasource-property name="URL">jdbc:mysql://localhost:3306/AppianDS?useOldAliasMetadataBehavior=true</xa-datasource-property>


    Thanks
Children
  • 0 in reply to prakashb9987

    I have configured Appian similar to Praveen. I am getting the same issue that Praveen was facing.

    Even after changing the xa-datasource-property name , it did not help much .

  • 0 in reply to vinodnaik
    "{
    \"JBAS014771: Services with missing/unavailable dependencies\" => [\"jboss.data-source.jdbc/AppianDS is missing [jboss.jdbc-driver.com_mysql_jdbc]\"],
    \"JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available.\" => {
    \"Services that were unable to start:\" => [
    \"jboss.data-source.reference-factory.jdbc/AppianDS\",
    \"jboss.naming.context.java.jdbc.AppianDS\"
    ],
    \"Services that may be the cause:\" => [
    \"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.jdbc-driver.com_mysql_jdbc\",
    \"jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean\",
    \"jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean\",
    \"jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean\"
    ]
    }
    }"
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.