Hi, I am trying to install Appian 7.8 using jboss 6.3 in linux VM and follo

Hi,
I am trying to install Appian 7.8 using jboss 6.3 in linux VM and followed the configuration steps given in forum.
While deploying suite.ear getting errors in launching the jboss server. These errors are related to failing of deployment of subunits present in suite.ear: (jms-transient-topic-handler, email-handler, jms-process-integration-handler)…

Same issue facing in windows deployment of appian for version 7.10 in jboss 6.4. Used Appian’s automate process of configure.bat file for the deployment.
The errors looks same related to failing of deployment of suite.ear subunits (jms-transient-topic-handler, email-handler, jms-process-integration-handler)…

Attaching log files for linux and windows appian installation.

18:20:51,786 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.subunit."suite.ear"."jms-transient-topic-handler.jar".PARSE: org.jboss.msc.service.StartExc...

logs.zip

OriginalPostID-159417

OriginalPostID-159417

  Discussion posts and replies are publicly visible

  • ...eption in service jboss.deployment.subunit."suite.ear"."jms-transient-topic-handler.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "jms-transient-topic-handler.jar" of deployment "suite.ear"
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]
    at java.lang.Thread.run(Thread.j...
  • ...ava:745) [rt.jar:1.8.0_45]
    Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
    at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:625) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:278)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageDrivenBeanMetaData(MessageDrivenComponentDescriptionFactory.java:244)
    at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processBeanMetaData(MessageDrivenComponentDescriptionFactory.java:89)
    at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processBeanMetaData(AnnotatedEJBComponen...
  • ... tDescriptionDeploymentUnitProcessor.java:65)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.processDeploymentDescriptor(AbstractDeploymentUnitProcessor.java:143)
    at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:84)
    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
    ... 5 more
  • Regarding Appian 7.10 installation - Can you please attach the custom.properties which is there in the repository that is created when you use the 'configure.bat' script? Also you need to check the following: 1. Is the custom.properties in the repository edited correctly 2. Is the standalone.xml edited correctly 3. Is the appian-ds.xml edited correctly? 4. Have you copied the mysql-connector jar in modules directory of JBoss? 5. Have you specified the path to the JBoss 6.4 EAP directory correctly? 6. Is JAVA_HOME env. variable pointing to JDK 1.8 directory?

    It would be helpful to find the cause of the issue if you could attach your custom.properties, standalone.xml and appian-ds.xml.
  • Also note that your compressed file with the logs is corrupted and cannot be opened.
  • I m sorry keeping you guys awaited.. here I am attaching the requested files..
    custom.properties and standalone.xml from appian v7.10 installation repository.

    @Chetan Yewale.. I did and verified all the steps you mentioned except no. 5. Can you tell me how to set JBoss 6.4 EAP directory path...?

    custom.properties

    standalone.xml

    custom.properties.dev

  • Hi Mangesh, In your custom.properties, the value for "conf.data.datasources" is not set. Uncomment it and set it to the data source which will be used as secondary datasource (for example - java:/jdbc/AppianBusinessDS, It must be the same datasource which you have mentioned in appian-ds.xml).

    Regarding JBoss EAP 6.4 path: when you are running the configure script, it will ask you for the JBoss directory path. Specify the path of the parent directory in the JBoss directory which contains "bin". (For example: F:\\jboss-eap-6.4.0_for_710 where F:\\jboss-eap-6.4.0_for_710 contains the "bin" folder.) Note that when you extract the JBoss 6.4 to a directory, the folder hierarchy is something like this: F:\\jboss-eap-6.4.0\\jboss-eap-6.4.0\\*. In that case, you will need to specify the path as F:\\jboss-eap-6.4.0\\jboss-eap-6.4.0\\

    Also if the configure script is not asking you for the JBoss EAP6.4 path, delete the ".configure" file from APPIAN_HOME/_admin/_scripts/configure directory and re-run the configure.bat script.

    In case things go wrong, delete the repository, delete the ".configure" file and then re-run the "configure.bat" script.