Can not start JBOSS with appian 17.2

RE: Can not start JBOSS with appian 17.2

rogeliog — Tue, 11 Jul 2017 13:07:59 GMT

The conection problem is solved!! yei !!, the issue was that MySQL server configuration on /etc/mysql/mysql.conf.d/mysql.cnf file it only allowed localhost conections, and in appian-mysql-ds.xml.dev it has the conection string by domain name "jdbc:mysql://my.serverdomain.com:3306/appian_dev_data?useOldAliasMetadataBehavior=true</xa-datasource-property>" Even though appian an db server are in the same machine it thought like there was an external conection. Weird :S.

Also a warning message in console that said

"21:10:55,513 WARN [org.jboss.as.messaging] (MSC service thread 1-4) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal"

So I installed it too libaio package.

Now it's running as it is suposed to be.

Thank you all, everything you told me helped a lot.

RE: Can not start JBOSS with appian 17.2

rogeliog — Mon, 10 Jul 2017 15:38:37 GMT

It's the same datasource conection problem.

Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for jdbc/AppianDS

Error creating bean with name 'primaryDataSourceConfig' defined in com.appiancorp.common.spring.BootstrapSpringConfig: Bean instantiation via factory method failed; nested exception is

... 30 more

Caused by: DataSourceConnectionException[jdbc/AppianDS]: FATAL: The Appian data source cannot be reached. Access to the Appian data source is required. The Appian application will fail to deploy. Details: Unable to build EntityManagerFactory (APNX-1-4179-002)

Caused by: org.hibernate.HibernateException: Cannot connect to the database.

JBAS014775: New missing/unsatisfied dependencies:

service jboss.deployment.subunit."suite.ear"."email-poller.rar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."suite.ear".deploymentCompleteService]

service jboss.deployment.subunit."suite.ear"."jms-process-integration-handler.jar".INSTALL (missing) dependents: [service jboss.deployment.subunit."suite.ear"."email-handler.jar".INSTALL]

RE: Can not start JBOSS with appian 17.2

Nagashankar Nallavalli — Mon, 10 Jul 2017 15:15:22 GMT

Hi rogeliog

You can find the server.log file in jboss/standalone/log/server.log location

RE: Can not start JBOSS with appian 17.2

catalinp — Mon, 10 Jul 2017 14:10:59 GMT

Sorry I dont have the time to parse scramble text. Can you please highlight what is the problem now?

RE: Can not start JBOSS with appian 17.2

rogeliog — Mon, 10 Jul 2017 13:42:07 GMT

Prem
Where do I find that server.log file?

RE: Can not start JBOSS with appian 17.2

rogeliog — Mon, 10 Jul 2017 13:39:54 GMT

Hi catalinp

[quote]Only 1 database, the other one you configure via Appian Management.[/quote]. Thanks, I erased the second datasource and only leaving the appian datasource

[quote]

1. From you machine you can connect with that user to MySql server?
2. Inside MySql is do you have both DBs made : appian_dev and appian_dev_data? And you granted to my_appian_db_server full access?[/quote]

Yes and yes (for the full access granting I don't know if you refer to this:.

[quote]3. You need the connector to be in REPO and JBoss folders (repo/modules.... and /jboss/modules...)[/quote]

Checked.

[quote] 4. Check inside module.xml if you have an extra space or w/e[/quote]

Checked. I did it with sublime becase it's easier to spot spaces.

[quote] 5. delete all file that are used in deploy process (i mean .deployed, .failed...) and re-run configure script to deploy to both[/quote]

Deleted and redeployed, still no succes :(

Here it is the console log of the redeployed

community.appian.com/.../console_5F00_log_5F00_server.txt

RE: Can not start JBOSS with appian 17.2

rogeliog — Fri, 07 Jul 2017 13:36:03 GMT

Thanks
I just change it for not posting the real domain for kinda security reasons :)

RE: Can not start JBOSS with appian 17.2

Rama Thummala — Fri, 07 Jul 2017 08:58:29 GMT

Hi rogeliog ,

The below might cause the issue.

In the standalone.xml (JBOSS), is the Database password is encrypted? Here the database password should be encrypted with Appian configure script tools.

In -ds.xml, is the connection string correct? Please verify the connection string once. Here for url we should give either ip address or domain name.

Please keep this updated if it get resolved.

RE: Can not start JBOSS with appian 17.2

catalinp — Fri, 07 Jul 2017 07:00:26 GMT

Only 1 database, the other one you configure via Appian Management.
I didn't spot anything that might be wrong in your conf files. So, take some small steps(I will use your data from xml to be easy for you to follow):
1. From you machine you can connect with that user to MySql server?
2. Inside MySql is do you have both DBs made : appian_dev and appian_dev_data? And you granted to my_appian_db_server full access?
3. You need the connector to be in REPO and JBoss folders (repo/modules.... and /jboss/modules...)
4. Check inside module.xml if you have an extra space or w/e
5. delete all file that are used in deploy process (i mean .deployed, .failed...) and re-run configure script to deploy to both

RE: Can not start JBOSS with appian 17.2

rogeliog — Thu, 06 Jul 2017 18:21:52 GMT

Thanks @catalinp , thanks @Prem , thanks @ramanjaneyulut

I checked everything you tolde me with no succes, i'll post those configuration files maye you can spot something i didnt´

About the "Do you need that connector to be java? ( I'm referring to java:/jdbc/AppianDS)" I did it like that because i saw it in the installation instruccions like that, maybe i got confused. But change it with same result.

Another question, when installing for the first timeappian server, there has to be only the appian datasources for the appian configuration or should be two datasources one ofr appian server an another for bussines data? or the busssines datasource can be later be configure via web admin management?

<REPO_HOME>/bin/jboss/jboss-eap-6.4/modules/com/mysql/jdbc/main/module.xml

<resource-root path="mysql-connector-java-5.1.41-bin.jar"/>

</resources>

</dependencies>

</module>

<REPO_HOME>/bin/jboss/jboss-eap-6.4/standalone/configuration/standalone.xml.dev

<?xml version='1.0' encoding='UTF-8'?>

</extensions>

<system-properties>

</system-properties>

<security-realms>

<security-realm name="ManagementRealm">

</authentication>

</authorization>

</security-realm>

<security-realm name="ApplicationRealm">

</authentication>

</authorization>

</security-realm>

</security-realms>

<audit-log>

<json-formatter name="json-formatter"/>

</formatters>

<file-handler name="file" formatter="json-formatter" relative-to="jboss.server.data.dir" path="audit-log.log"/>

</handlers>

</handlers>

</logger>

</audit-log>

<management-interfaces>

<native-interface security-realm="ManagementRealm">

<socket-binding native="management-native"/>

</native-interface>

<http-interface security-realm="ManagementRealm">

<socket-binding http="management-http"/>

</http-interface>

</management-interfaces>

<access-control provider="simple">

<role-mapping>

</include>

</role>

</role-mapping>

</access-control>

</management>

<hornetq-server>

<persistence-enabled>true</persistence-enabled>

<security-domain>messaging</security-domain>

<journal-file-size>102400</journal-file-size>

<journal-min-files>2</journal-min-files>

<netty-connector name="netty" socket-binding="messaging"/>

<netty-connector name="netty-throughput" socket-binding="messaging-throughput">

</netty-connector>

<in-vm-connector name="in-vm" server-id="0"/>

</connectors>

<netty-acceptor name="netty" socket-binding="messaging"/>

<netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">

</netty-acceptor>

<in-vm-acceptor name="in-vm" server-id="0"/>

</acceptors>

<broadcast-groups>

<broadcast-group name="appian-broadcast-group">

<socket-binding>messaging-group</socket-binding>

<broadcast-period>5000</broadcast-period>

<connector-ref>

netty

</connector-ref>

</broadcast-group>

</broadcast-groups>

<discovery-groups>

<discovery-group name="appian-discovery-group">

<socket-binding>messaging-group</socket-binding>

<refresh-timeout>10000</refresh-timeout>

</discovery-group>

</discovery-groups>

<security-settings>

<security-setting match="#">

</security-setting>

</security-settings>

<address-settings>

<address-setting match="#">

<dead-letter-address>jms.queue.DLQ</dead-letter-address>

<expiry-address>jms.queue.ExpiryQueue</expiry-address>

<redelivery-delay>0</redelivery-delay>

<max-size-bytes>10485760</max-size-bytes>

<address-full-policy>BLOCK</address-full-policy>

<message-counter-history-day-limit>10</message-counter-history-day-limit>

</address-setting>

</address-settings>

<jms-connection-factories>

<connection-factory name="ProcessIntegrationConnectionFactory">

<connector-ref connector-name="netty"/>

</connectors>

</entries>

</connection-factory>

<pooled-connection-factory name="hornetq-ra">

<connector-ref connector-name="in-vm"/>

</connectors>

</entries>

</pooled-connection-factory>

</jms-connection-factories>

<jms-destinations>

<jms-queue name="jms/ProcessQueue">

</jms-queue>

</jms-destinations>

</hornetq-server>

</subsystem>

<console-handler name="CONSOLE">

<named-formatter name="COLOR-PATTERN"/>

</formatter>

</console-handler>

<periodic-rotating-file-handler name="FILE" autoflush="true">

<named-formatter name="PATTERN"/>

</formatter>

</periodic-rotating-file-handler>

</logger>

</logger>

</logger>

</logger>

</logger>

</logger>

</logger>

<root-logger>

</handlers>

</root-logger>

<pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>

</formatter>

<pattern-formatter pattern="%K{level}%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>

</formatter>

</subsystem>

<driver-class>com.mysql.jdbc.Driver</driver-class>

<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>

</driver>

</drivers>

</datasources>

</subsystem>

<deployment-scanner name="appian" path="${appian.home.ear}" auto-deploy-exploded="false" auto-deploy-zipped="false" auto-deploy-xml="false" deployment-timeout="3600" scan-interval="5000"/>

<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000"/>

</subsystem>

<spec-descriptor-property-replacement>false</spec-descriptor-property-replacement>

<jboss-descriptor-property-replacement>true</jboss-descriptor-property-replacement>

<annotation-property-replacement>false</annotation-property-replacement>

</subsystem>

<mdb>

<resource-adapter-ref resource-adapter-name="hornetq-ra"/>

<bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>

</mdb>

<session-bean>

<bean-instance-pool-ref pool-name="slsb-strict-max-pool"/>

</stateless>

</session-bean>

<pools>

<bean-instance-pools>

<strict-max-pool name="slsb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>

<strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" instance-acquisition-timeout="5" instance-acquisition-timeout-unit="MINUTES"/>

<strict-max-pool name="UnattendedRequestPool" max-pool-size="30" instance-acquisition-timeout="15" instance-acquisition-timeout-unit="MINUTES"/>

</bean-instance-pools>

</pools>

</caches>

<passivation-stores>

<file-passivation-store name="file"/>

</passivation-stores>

<timer-service thread-pool-name="default" default-data-store="default-file-store">

<data-stores>

<file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>

</data-stores>

</timer-service>

<thread-pools>

<thread-pool name="default">

<max-threads count="10"/>

<keepalive-time time="100" unit="milliseconds"/>

</thread-pool>

</thread-pools>

<default-security-domain value="other"/>

<default-missing-method-permissions-deny-access value="true"/>

</subsystem>

<cache-container name="web" aliases="standard-session-cache" default-cache="local-web" module="org.jboss.as.clustering.web.infinispan">

<local-cache name="local-web" batching="true">

<file-store passivation="false" purge="false"/>

</local-cache>

</cache-container>

<cache-container name="hibernate" default-cache="local-query" module="org.jboss.as.jpa.hibernate:4">

<local-cache name="entity">

</local-cache>

<local-cache name="local-query">

</local-cache>

<local-cache name="timestamps">

</local-cache>

</cache-container>

</subsystem>

<archive-validation enabled="true" fail-on-error="true" fail-on-warn="false"/>

<bean-validation enabled="true"/>

<default-workmanager>

<short-running-threads>

<core-threads count="50"/>

<queue-length count="50"/>

<max-threads count="50"/>

<keepalive-time time="10" unit="seconds"/>

</short-running-threads>

<long-running-threads>

<core-threads count="50"/>

<queue-length count="50"/>

<max-threads count="50"/>

<keepalive-time time="10" unit="seconds"/>

</long-running-threads>

</default-workmanager>

<cached-connection-manager/>

</subsystem>

<expose-resolved-model/>

<expose-expression-model/>

<remoting-connector/>

</subsystem>

</subsystem>

<mail-session name="default" jndi-name="java:jboss/mail/Default">

<smtp-server outbound-socket-binding-ref="mail-smtp"/>

</mail-session>

</subsystem>

<remote-naming/>

</subsystem>

</subsystem>

<security-domains>

<security-domain name="other" cache-type="default">

<login-module code="Remoting" flag="optional">

<module-option name="password-stacking" value="useFirstPass"/>

</login-module>

<login-module code="RealmDirect" flag="required">

<module-option name="password-stacking" value="useFirstPass"/>

</login-module>

</authentication>

</security-domain>

<security-domain name="jboss-web-policy" cache-type="default">

<policy-module code="Delegating" flag="required"/>

</authorization>

</security-domain>

<security-domain name="jboss-ejb-policy" cache-type="default">

<policy-module code="Delegating" flag="required"/>

</authorization>

</security-domain>

<security-domain name="messaging" cache-type="default">

<login-module code="RealmUsersRoles" flag="required">

<module-option name="unauthenticatedIdentity" value="guest"/>

<module-option name="usersProperties" value="${jboss.server.config.dir}/application-users.properties"/>

<module-option name="rolesProperties" value="${jboss.server.config.dir}/application-roles.properties"/>

</login-module>

</authentication>

</security-domain>

<security-domain name="ds-name-security-primary" cache-type="default">

<login-module code="org.picketbox.datasource.security.SecureIdentityLoginModule" flag="required">

<module-option name="username" value="my_appian_db_user" />

<module-option name="password" value="ScrambledPass784190f554ca0" />

</login-module>

</authentication>

</security-domain>

<security-domain name="ds-name-security-appian" cache-type="default">

<login-module code="org.picketbox.datasource.security.SecureIdentityLoginModule" flag="required">

<module-option name="username" value="my_appian_db_server" />

<module-option name="password" value="ScrambledPAss7850be22f7d1" />

</login-module>

</authentication>

</security-domain>

</security-domains>

</subsystem>

<core-environment>

<process-id>

<uuid/>

</process-id>

</core-environment>

<recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>

<coordinator-environment default-timeout="300"/>

</subsystem>

<virtual-server name="default-host" enable-welcome-root="true">

</virtual-server>

</subsystem>

<modify-wsdl-address>true</modify-wsdl-address>

<wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>

<endpoint-config name="Standard-Endpoint-Config"/>

<endpoint-config name="Recording-Endpoint-Config">

<pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">

</pre-handler-chain>

</endpoint-config>

<client-config name="Standard-Client-Config"/>

</subsystem>

</profile>

<inet-address value="${jboss.bind.address.management:127.0.0.1}"/>

</interface>

<inet-address value="${jboss.bind.address:0.0.0.0}"/>

</interface>

<!--

~ Used for IIOP sockets in the standard configuration.

~ To secure JacORB you need to setup SSL

-->

<inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>

</interface>

</interfaces>

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

<socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/>

<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>

<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/>

<socket-binding name="ajp" port="8009"/>

<socket-binding name="http" port="8080"/>

<socket-binding name="https" port="8443"/>

<socket-binding name="remoting" port="4447"/>

<socket-binding name="txn-recovery-environment" port="4712"/>

<socket-binding name="txn-status-manager" port="4713"/>

<socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:233.252.134.134}" multicast-port="${jboss.messaging.group.port:9876}"/>

<socket-binding name="messaging" port="5445"/>

<socket-binding name="messaging-throughput" port="5455"/>

<outbound-socket-binding name="mail-smtp">

<remote-destination host="localhost" port="25"/>

</outbound-socket-binding>

</socket-binding-group>

</server>

<REPO_HOME>/bin/jboss/jboss-eap-6.4/standalone/deployments/appian-mysql-ds.xml.dev

<?xml version="1.0" encoding="UTF-8"?>

<xa-datasource

jndi-name="jdbc/AppianDS"

pool-name="MySqlDS"

enabled="true"

use-java-context="false">

<xa-datasource-property name="URL">jdbc:mysql://my.serverdomain.com:3306/appian_dev_data?useOldAliasMetadataBehavior=true</xa-datasource-property>

<xa-datasource-property name="useUnicode">true</xa-datasource-property>

<xa-datasource-property name="characterEncoding">UTF-8</xa-datasource-property>

<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>

<driver>com.mysql.jdbc</driver>

<security-domain>ds-name-security-appian</security-domain>

</security>

<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>

<xa-pool>

<min-pool-size>5</min-pool-size>

<max-pool-size>100</max-pool-size>

</xa-pool>

<blocking-timeout-millis>5000</blocking-timeout-millis>

<idle-timeout-minutes>5</idle-timeout-minutes>

</timeout>

</xa-datasource>

<xa-datasource

jndi-name="jdbc/AppianDevDS"

pool-name="MySqlDS"

enabled="true"

use-java-context="false">

<xa-datasource-property name="URL">jdbc:mysql://my.serverdomain.com:3306/appian_dev?useOldAliasMetadataBehavior=true</xa-datasource-property>

<xa-datasource-property name="useUnicode">true</xa-datasource-property>

<xa-datasource-property name="characterEncoding">UTF-8</xa-datasource-property>

<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>

<driver>com.mysql.jdbc</driver>

<security-domain>ds-name-security-primary</security-domain>

</security>

<transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>

<xa-pool>

<min-pool-size>5</min-pool-size>

<max-pool-size>100</max-pool-size>

</xa-pool>

<blocking-timeout-millis>5000</blocking-timeout-millis>

<idle-timeout-minutes>5</idle-timeout-minutes>

</timeout>

</xa-datasource>

</datasources>

<REPO_HOME>/ear/suite.ear/conf/custom.properties.dev

######################

#### Data Sources ####

######################

## Appian must have a dedicated data source. Set the value to the JNDI name of

## the data source that will be used as the Appian data source.

## Note: This data source must point to a separate tablespace than any listed

## in the conf.data.datasources configuration.

conf.data.APPIAN_DATA_SOURCE=jdbc/AppianDS

## Comma-separated list of JNDI names of data sources on the application server

## that will be used to store business data. This list is used by the Query

## Database smart service and Data Stores.

conf.data.datasources=jdbc/AppianDevDS

Firewall

Thanks

RE: Can not start JBOSS with appian 17.2

catalinp — Wed, 05 Jul 2017 08:48:13 GMT

This is the starting point: Caused by: org.hibernate.HibernateException: Cannot connect to the database.

Did you create the DB in your database? Did you made the right connection to that DB in appian...ds.xml? Do you need that connector to be java? ( I'm referring to java:/jdbc/AppianDS)

Do you use a secure domain with a scramble password? It's the same secure domain in JBoss standalone.xml and Appian DB connection - appian...ds.xml?

Do you have a firewall that is blocking the connection to the DB? or other stuff like SeLinux?

After you check those and you made sure that are right, re-run configure script to deploy to both the SUITE context.

RE: Can not start JBOSS with appian 17.2

Prem — Wed, 05 Jul 2017 07:38:38 GMT

Hello Rogeliog,

Could you please check ds.xml is correctly configured. JNDI name should be same in custom.properties file & ds.xml file..Pls see below error logs & looks like DB connection issue. Pls upload server.log file for more analysis.

Caused by: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/jdbc/AppianDS
Caused by: javax.resource.ResourceException: Could not create connection

RE: Can not start JBOSS with appian 17.2

Rama Thummala — Wed, 05 Jul 2017 07:20:17 GMT

Hi rogeliog ,

Please check your -ds.xml and standalone.xml(in JBOSS) and verify the configurations..
If the issue still persists. ..Please do restart the DB ...

Hope it will help you..