Hi All, I have installed 7.9 version and updated other configurations

...jboss.as] (MSC service thread 1-14) JBAS015950: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) stopped in 9ms
D:\\jboss-eap-6.4\\bin>

Please find attached text file for complete details.

Also there is problem with deploying Oracle Datasources. Appreciate your help in resolving this error.

Thanks,
Madhu

The following message indicates that there is an issue with the deployment scanner within the standalone configuration.

"JBAS014784: Failed executing subsystem deployment-scanner
boot operations"

Please note that if you are migrating from an existing version of Appian that as of 7.9 the deployment scanner does not contain deployment properties for ss.ear

Just to complement what Tim has mentioned above, the specific error around that message is

failure description: "JBAS014803: Duplicate resource [(\\"deployment\\" => \\"suite.ear\\")]"

this means that:

1. You have two "suite.ear" directories (different name but the same EAR) under <APPIAN_HOME>\\ear. Make sure you don't have anything else but two things under <APPIAN_HOME>\\ear:

---> The suite.ear directory
---> The suite.ear.dodeploy file

2. Also review your standalone.xml and make sure that urn:jboss:domain:deployment-scanner subsystem only has one entry for appian.home.ear and one for the deployments directory of JBoss, for instance:

<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
<deployment-scanner name="appian" path="${appian.home.ear}" scan-interval="5000" auto-deploy-zipped="false" auto-deploy-exploded="false" auto-deploy-xml="false" deployment-timeout="1800"/>
</subsystem>

@Tim its a new Setup and not a migration from existing version.
@ Eduardo, under \\ear I have only suite.ear file and suite.ear.failed file.
I have verified standalone.xml and we have only entry for urn:jboss:domain:deployment-scanner subsystem

1. How many deployment-scanner elements do you have under the urn:jboss:domain:deployment-scanner subsystem?

2. Can you stop JBoss and rename suite.ear.failed to suite.ear.dodeploy and test?

Its two elements:
<subsystem xmlns="urn:jboss:domain:deployment-scanner:1.1">
<deployment-scanner name="appian" path="${appian.home.ear}" auto-deploy-exploded="false" auto-deploy-zipped="false" auto-deploy-xml="false" deployment-timeout="1800" scan-interval="5000"/>
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>
</subsystem>

Also as said I have renamed suite.ear.failed to suite.ear.dodeploy and started the JBoss again, it failed again. Please find attached details from file suite.ear.failed

Thanks,
Madhu

suite.ear.failed

Can you attach the new server.log, appian-ds.xml and standalone.xml? (please remove any passwords and server names from these files for security reasons)

Hi Eduardo,
Attaching the files with passwords renamed.

appian-ds.xml

Hi Eduardo,

Please find attached zip file containing server.log, appian-ds.xml and standalone.xml files.
Also below is what we found in the logs:


06:55:33,168 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 29) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("jdbc-driver" => "oracle.jdbc")
]) - failure description: "JBAS010441: Failed to load module for driver [oracle.jdbc]"
Regards,
Madhu

files.zip

Excellent it seems we are making progress this error makes more sense. In standalone.xml you have

<drivers>
<driver name="oracle.jdbc" module="oracle.jdbc">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>

which means you need a file called module.xml inside <JBOSS_HOME>\\modules\\oracle\\jdbc\\main\\ as well as the driver you specified inside that module.xml. Please attach screenshots showing the content of this file and that it's in the right location.