4 Replies Latest reply on Feb 13, 2017 1:17 AM by shpsgm

    jboss 4.2.3 GA to wildfly 10 migration

    shpsgm

      Hi,

      The project's configuration is as follows that i am currently working on , server jboss 4.2.3 GA, seam 2.2 and java 1.6 ,ejb 3.0.

      We want to migrate to newer version so that we go big as jboss 4 to wildfly 10 as you see:)

      So did a little bit at jdbc conf and working ok on that but at last we are getting this errors:

       

      any recommendations would be appreciated.

       

      2017-02-10 11:20:28,942 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "xxxSeam-ear.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [

          "jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.xxxxActionBean.InAppClientContainer is missing [jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.xxxActionBean]",

          "jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.yyyiActionBean.Validator is missing [jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.yyyActionBean]",

          "jboss.naming.context.java.comp.xxxSeam-earxxxSeam-ejb.zzzActionBean.InstanceName is missing [jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.zzzActionBean]",

          "jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.wwwAction.HandleDelegate is missing [jboss.naming.context.java.comp.xxxSeam-ear.xxxSeam-ejb.wwwwiAction]",

       

       

      application.xml

       

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

      <application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

      xmlns="http://java.sun.com/xml/ns/javaee"

      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_6.xsd"

            version="6">

        <display-name>xxxSeam-ear</display-name>

        <initialize-in-order>true</initialize-in-order>

        <module>

          <ejb>jboss-seam.jar</ejb>

        </module>

        <module>

          <web>

            <web-uri>xxxSeam.war</web-uri>

            <context-root>xxxSeam</context-root>

          </web>

        </module>

        <module>

          <ejb>xxxSeam-ejb.jar</ejb>

        </module>

      </application>

        • 1. Re: jboss 4.2.3 GA to wildfly 10 migration
          ctomc

          what does your server log say?

          • 2. Re: jboss 4.2.3 GA to wildfly 10 migration
            shpsgm

            here is snippet from server log.

             

            Thanks in advance!

             

            2017-02-10 11:53:48,257 INFO  [org.jboss.as.ejb3.deployment] (MSC service thread 1-1) WFLYEJB0473: JNDI bindings for session bean named 'FormActionBean' in deployment unit 'subdeployment "xxxxSeam-ejb.jar" of deployment "xxxxSeam-ear.ear"' are as follows:

             

             

              java:global/xxxxSeam-ear/xxxxSeam-ejb/FormActionBean!tr.com.bilim.xxxx.session.FormAction

              java:app/xxxxSeam-ejb/FormActionBean!tr.com.bilim.xxxx.session.FormAction

              java:module/FormActionBean!tr.com.bilm.xxxx.session.FormAction

              java:global/xxxxSeam-ear/xxxxSeam-ejb/FormActionBean

              java:app/xxxxSeam-ejb/FormActionBean

              java:module/FormActionBean

             

             

            2017-02-10 11:53:48,309 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 2.0)

            2017-02-10 11:53:48,318 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = xxxxSeam-ear.ear_com.microsoft.sqlserver.jdbc.SQLServerDriver_2_0

            2017-02-10 11:53:48,399 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "xxxxSeam-ear.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => [

                "jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.MotorsActionBean.ValidatorFactory is missing [jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.MotorsActionBean]",

                "jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.UcusActionBean.InstanceName is missing [jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.UcusActionBean]",

                "jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.UcusOpActionBean.ValidatorFactory is missing [jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.UcusOpActionBean]",

                "jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.kazaActionBean.InstanceName is missing [jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.kazaActionBean]",

                "jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.HvxActionBean.Validator is missing [jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.HvxActionBean]",

                "jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.HtSetActionBean.ValidatorFactory is missing [jboss.naming.context.java.comp.xxxxSeam-ear.xxxxSeam-ejb.HtSetActionBean]",

            *

            *

            *

            *

            *

            *

            *

            *

            *

            2017-02-10 11:53:48,945 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

            2017-02-10 11:53:48,946 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

            2017-02-10 11:53:48,946 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 21655ms - Started 881 of 2589 services (1425 services failed or missing dependencies, 420 services are lazy, passive or on-demand)

            2017-02-10 11:53:49,021 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = xxxxSeam-ear.ear_com.microsoft.sqlserver.jdbc.SQLServerDriver_2_0

            2017-02-10 11:53:49,072 INFO  [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.3.Final

            2017-02-10 11:53:49,147 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 17) WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service 'xxxxSeam-ear.ear/xxxxSeam-ejb.jar#xxxxSeam'

            2017-02-10 11:53:49,170 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: jboss-seam.jar) in 173ms

            2017-02-10 11:53:49,170 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: xxxxSeam-ejb.jar) in 174ms

            2017-02-10 11:53:49,231 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0208: Stopped subdeployment (runtime-name: xxxxSeam.war) in 235ms

            2017-02-10 11:53:49,485 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment xxxxSeam-ear.ear (runtime-name: xxxxSeam-ear.ear) in 488ms

            2017-02-10 11:53:49,616 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "xxxxSeam-ear.ear" (runtime-name: "xxxxSeam-ear.ear")

            2017-02-10 11:53:49,620 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report

            WFLYCTL0184:    New missing/unsatisfied dependencies:

                  service jboss.deployment.subunit."xxxxSeam-ear.ear"."jboss-seam.jar".INSTALL (missing) dependents: [service jboss.deployment.subunit."xxxxSeam-ear.ear"."xxxxSeam.war".INSTALL]

            • 3. Re: jboss 4.2.3 GA to wildfly 10 migration
              mayerw01

              I'd suggest using the most recent JDBC driver?

              • 4. Re: jboss 4.2.3 GA to wildfly 10 migration
                shpsgm

                mysql jdbc driver 5.1.40 , last version that i know. Still got problem though.