• State Not Answered
  • +2 person also asked this people also asked this
  • Replies 5 replies
  • Subscribers 12 subscribers
  • Views 5675 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Administration

Upgrade 17.4 from 17.2 errors issues

rogeliog

Hi, I made an upgrade from 17.2 to 17.4, i followed the instructions to upgrade but i'm having issues when starting JBOSS.

 

Its a long log but in summary the main errors are:

17:48:55,382 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.opensaml.core.config.InitializationService - Initializing OpenSAML using the Java Services API
17:48:55,409 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.opensaml.xmlsec.algorithm.AlgorithmRegistry - Cipher algorithm 'www.w3.org/.../xmlenc is not supported, its key length 192 exceeds Cipher max key length 128
17:48:55,410 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.opensaml.xmlsec.algorithm.AlgorithmRegistry - Algorithm failed runtime support check, will not be usable: www.w3.org/.../xmlenc

17:49:02,939 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.impl.SessionFactoryObjectFactory - Not binding factory to JNDI, no JNDI name configured
17:49:03,019 INFO [stdout] (ServerService Thread Pool -- 91) 2018-01-17 17:49:03,017 [ServerService Thread Pool -- 91] INFO com.appiancorp.rdbms.hb.DataSourceManagerHbImpl - [jdbc/AppianDS] Checking schema and migrating if necessary (appian/db/changelog/db-changelog-master.xml)...
17:49:03,026 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.connection.ConnectionProviderFactory - Initializing connection provider: com.appiancorp.rdbms.hb.LoggingDatasourceConnectionProvider
17:49:03,026 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.util.NamingHelper - JNDI InitialContext properties:{}
17:49:03,027 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.connection.DatasourceConnectionProvider - Using datasource: jdbc/AppianDS
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.cfg.SettingsFactory - Database ->
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) name : MySQL
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) version : 5.7.20-0ubuntu0.16.04.1
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) major : 5
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) minor : 7
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.cfg.SettingsFactory - Driver ->
17:49:03,029 ERROR [stderr] (ServerService Thread Pool -- 91) name : MySQL Connector Java
17:49:03,030 ERROR [stderr] (ServerService Thread Pool -- 91) version : mysql-connector-java-5.1.41 ( Revision: 83c6dc41b96809df81444362933043b20a1d49d5 )
17:49:03,030 ERROR [stderr] (ServerService Thread Pool -- 91) major : 5
17:49:03,030 ERROR [stderr] (ServerService Thread Pool -- 91) minor : 1
17:49:03,030 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.transaction.TransactionFactoryFactory - Using default transaction strategy (direct JDBC transactions)
17:49:03,031 ERROR [stderr] (ServerService Thread Pool -- 91) [ServerService Thread Pool -- 91] INFO org.hibernate.transaction.TransactionManagerLookupFactory - No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)

ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 91) JBWEB000284: Exception starting filter listingsFilter: java.lang.ClassNotFoundException: com.appiancorp.ap2.ListingsServletFilter from [Module "deployment.suite.ear.web.war:main" from Service Module Loader]

17:49:33,732 INFO [stdout] (ServerService Thread Pool -- 91) 2018-01-17 17:49:33,731 [ServerService Thread Pool -- 91] INFO com.appiancorp.rdbms.datasource.BusinessDataSourceValidator - Validating data sources.
17:49:33,913 ERROR [stderr] (ServerService Thread Pool -- 91) Wed Jan 17 17:49:33 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
17:49:33,965 ERROR [stderr] (ServerService Thread Pool -- 91) Wed Jan 17 17:49:33 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.
17:49:33,983 INFO [stdout] (ServerService Thread Pool -- 91) 2018-01-17 17:49:33,983 [ServerService Thread Pool -- 91] INFO com.appiancorp.rdbms.datasource.BusinessDataSourceValidator - Data source: jdbc/AppianDevDs validated successfully.

17:50:04,270 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "suite.ear")]) - failure description: {
"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.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.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\".\"jms-process-integration-handler.jar\".deploymentCompleteService, jboss.deployment.subunit.\"suite.ear\".\"email-handler.jar\".deploymentCompleteService, jboss.deployment.subunit.\"suite.ear\".\"unattended-request-handler.jar\".deploymentCompleteService]",
"jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]",
"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.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.Validator is missing [jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean]",
"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]"
]
}
17:50:04,342 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "appian-mysql-ds.xml" (runtime-name : "appian-mysql-ds.xml")
17:50:04,343 INFO [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear")
17:50:04,348 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.deployment.subunit."suite.ear"."email-handler.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."suite.ear".deploymentCompleteService]
service jboss.deployment.subunit."suite.ear"."jms-process-integration-handler.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."suite.ear".deploymentCompleteService, service jboss.deployment.subunit."suite.ear"."email-handler.jar".INSTALL]
service jboss.deployment.subunit."suite.ear"."unattended-request-handler.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."suite.ear".deploymentCompleteService, service jboss.deployment.subunit."suite.ear"."jms-process-integration-handler.jar".INSTALL]
service jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean (missing) dependents: [service jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.Validator, service jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean.ValidatorFactory]
service jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean (missing) dependents: [service jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean.ValidatorFactory, service jboss.naming.context.java.comp.suite.jms-process-integration-handler.JmsProcessIntegrationHandlerBean.Validator]
service jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean (missing) dependents: [service jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.ValidatorFactory, service jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean.Validator]
JBAS014777: Services which failed to start: service 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

17:50:03,430 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 91) JBWEB000284: Exception starting filter listingsFilter: java.lang.ClassNotFoundException: com.appiancorp.ap2.ListingsServletFilter from [Module "deployment.suite.ear.web.war:main" from Service Module Loader]

 

weel, there are a lot of messages and i'm totally lost.

My previous 17.2 installation was working fine 

I attach the full log in case is needed18418.server.log

 

Thanks in advance.

  Discussion posts and replies are publicly visible

  • 0
    Certified Lead Developer

    My guess is some JARs are missing or corrupted. The listingservletfiter (BWEB000284: Exception starting filter listingsFilter: java.lang.ClassNotFoundException: com.appiancorp.ap2.ListingsServletFilter from [Module "deployment.suite.ear.web.war:main" from Service Module Loader]) was added in 17.x (not sure when exactly), but that would make sense that if something didn't go right with the 17.4 migration, then the classes related to that might be missing.

    Offhand, I don't know which JAR you want to check to see if the class exists. I suggest bringing this to Appian Support's attention regardless since this may be caused by problem or gap with migration documentation.

  • 0

    I don't know if helps but the contents of the suite.ear.fail archive says:

    {
    \"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.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.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.deployment.unit.\\\"suite.ear\\\".deploymentCompleteService is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".deploymentCompleteService, jboss.deployment.subunit.\\\"suite.ear\\\".\\\"unattended-request-handler.jar\\\".deploymentCompleteService, jboss.deployment.subunit.\\\"suite.ear\\\".\\\"email-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.email-handler.EmailHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.email-handler.EmailHandlerBean]\",
        \"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.unattended-request-handler.UnattendedRequestHandlerBean.Validator is missing [jboss.naming.context.java.comp.suite.unattended-request-handler.UnattendedRequestHandlerBean]\",
        \"jboss.deployment.subunit.\\\"suite.ear\\\".\\\"jms-process-integration-handler.jar\\\".INSTALL is missing [jboss.deployment.subunit.\\\"suite.ear\\\".\\\"unattended-request-handler.jar\\\".deploymentCompleteService]\"
    ]
}

     I attached a recen log iven by the terminal of jboss.

     

    Again, any help would be great.

     

    Error jboss despues de upgrade.log

  • 0
    Certified Lead Developer
     in reply to rogeliog
    This is the next thing to look at: 18:59:16,522 ERROR [stderr] (ServerService Thread Pool -- 82) [ServerService Thread Pool -- 82] ERROR org.hibernate.connection.DatasourceConnectionProvider - Could not find datasource: jdbc/AppianDS
    18:59:16,523 ERROR [stderr] (ServerService Thread Pool -- 82) javax.naming.NameNotFoundException: jdbc/AppianDS -- service jboss.naming.context.java.jdbc.AppianDS

    Something with the JDBC connection looks like its not set properly, and when that happens, you'll get all sorts of errors. I would double check that you've set this correctly in:
    1) custom.properties
    2) any appian-ds.xml files in JBoss
    3) standalone.conf has the drivers set correctly
    4) JBOSS_HOME/modules has the drivers and the xml configs created correctly
  • 0
    Certified Senior Developer
     in reply to rogeliog
    have you solved it, i am also facing same issue.
  • 0 in reply to Pankaj Kabdal
    No :'(

    Even though i did everything Justin Watts ecommended it didn't help.

    I think it's better to do a fresh installation of 17.4 (latest now 18.1) instead of an upgrade.

    OR if you ever find a solution please post it in here.

    Good luck
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.