6 Replies Latest reply on Mar 2, 2019 1:10 AM by Mohit Kumar

    siperian-mrm.ear deployment failed (MDM 10.3 installation)

    Mohit Kumar Seasoned Veteran

      Post installation failed to deploy siperian-mrm.ear. I am using Microsoft sql server 2012 database and jboss 7.2. However informatica-mdm-platform-ear is successfully deployed.

        • 1. Re: siperian-mrm.ear deployment failed (MDM 10.3 installation)
          Mohit Kumar Seasoned Veteran

          There are the error logs -

           

          15:51:56,385 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "siperian-mrm.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.siperian-mrm.ear\".main" => "WFLYSRV0179: Failed to load module: deployment.siperian-mrm.ear

              Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.common-core"}}

          15:51:56,385 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "siperian-mrm.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.siperian-mrm.ear\".main" => "WFLYSRV0179: Failed to load module: deployment.siperian-mrm.ear

              Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.common-core"}}

          15:51:56,425 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "siperian-mrm.ear" (runtime-name : "siperian-mrm.ear")

          15:51:56,425 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "siperian-mrm.ear" (runtime-name : "siperian-mrm.ear")

          15:51:56,432 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "informatica-mdm-platform-ear.ear" (runtime-name : "informatica-mdm-platform-ear.ear")

          15:51:56,432 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 45) WFLYSRV0010: Deployed "informatica-mdm-platform-ear.ear" (runtime-name : "informatica-mdm-platform-ear.ear")

          15:51:56,434 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

          WFLYCTL0186:   Services which failed to start:      service jboss.module.service."deployment.siperian-mrm.ear".main: WFLYSRV0179: Failed to load module: deployment.siperian-mrm.ear

          WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed

          15:51:56,434 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

          WFLYCTL0186:   Services which failed to start:      service jboss.module.service."deployment.siperian-mrm.ear".main: WFLYSRV0179: Failed to load module: deployment.siperian-mrm.ear

          WFLYCTL0448: 1 additional services are down due to their dependencies being missing or failed

          15:51:56,784 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server

          15:51:56,784 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server

          15:51:56,789 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

          15:51:56,789 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

          15:51:56,789 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

          15:51:56,790 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001) started (with errors) in 294976ms - Started 623 of 811 services (6 services failed or missing dependencies, 355 services are lazy, passive or on-demand)

          15:51:56,789 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

          15:51:56,790 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.2.0.GA (WildFly Core 6.0.11.Final-redhat-00001) started (with errors) in 294976ms - Started 623 of 811 services (6 services failed or missing dependencies, 355 services are lazy, passive or on-demand)

          15:51:57,055 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-113) [2019-02-11 15:51:57,041] [EJB default - 1] [INFO ] com.informatica.mdm.platform.impl.Log4jManagerBean: Log configuration updated from: E:\MDM_INSTALL\mrmserver\conf\log4j-informatica-mdm-platform.xml

          15:51:57,055 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-113) [2019-02-11 15:51:57,041] [EJB default - 1] [INFO ] com.informatica.mdm.platform.impl.Log4jManagerBean: Log configuration updated from: E:\MDM_INSTALL\mrmserver\conf\log4j-informatica-mdm-platform.xml

          15:51:57,056 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-113) [2019-02-11 15:51:57,042] [EJB default - 1] [INFO ] com.informatica.mdm.platform.impl.Log4jManagerBean: Root log level after update: DEBUG

          15:51:57,056 INFO  [stdout] (AsyncAppender-Dispatcher-Thread-113) [2019-02-11 15:51:57,042] [EJB default - 1] [INFO ] com.informatica.mdm.platform.impl.Log4jManagerBean: Root log level after update: DEBUG

          15:53:46,484 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: The function RECOVER: failed. The status is: -3. Error: "*** SQLJDBC_XA DTC_ERROR Context: xa_recover, state=1, StatusCode:-3 (0xFFFFFFFD) ***"

                  at com.microsoft.sqlserver.jdbc.SQLServerXAResource.DTC_XA_Interface(SQLServerXAResource.java:550)

                  at com.microsoft.sqlserver.jdbc.SQLServerXAResource.recover(SQLServerXAResource.java:728)

                  at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.recover(XAManagedConnection.java:373)

                  at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.recover(XAResourceWrapperImpl.java:185)

                  at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:609)

                  at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:201)

                  at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:146)

                  at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:765)

                  at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:377)

          • 2. Re: siperian-mrm.ear deployment failed (MDM 10.3 installation)
            Patrick Piper Seasoned Veteran

            Could be a compatibility issue, 6.4 is the only JBoss version listed in the 10.3 Product Availability Matrix.

            • 3. Re: siperian-mrm.ear deployment failed (MDM 10.3 installation)
              Mohit Kumar Seasoned Veteran

              One more thing. Can it be installed on Windows 10 ?

              • 4. Re: siperian-mrm.ear deployment failed (MDM 10.3 installation)
                Patrick Piper Seasoned Veteran

                Can't say for sure because it's not listed in the PAM. I've installed MDM in environments with an OS not listed in the PAM before, but there won't be any official documentation or support if you do.

                • 5. Re: siperian-mrm.ear deployment failed (MDM 10.3 installation)
                  AKSHAYA RAVICHANDRAN Active Member

                  If you are using sql server, did you follow all the steps from the installation guide, especially on the topic "Install and Configure Microsoft SQL Server for Distributed Transactions"? SQL Server must be enabled for XA transactions.

                   

                  Also, if it is not listed in PAM, I would strongly advise you not to use it in your environment. The potential risk of unsupported platform would be that you might be asked to re-install the MDM in a supported platform later, if you encounter any issues in the future.

                  • 6. Re: siperian-mrm.ear deployment failed (MDM 10.3 installation)
                    Mohit Kumar Seasoned Veteran

                    Yes I have followed all steps and it got installed successfully. Application is working without any issue. The only trick is to use JDK 1.7 to install hub server.