8 Replies Latest reply on Jul 13, 2015 2:43 PM by manzar.chaudhary
      • 1. Re: what are the steps in Migrating JCA related config from 5 to as7
        alesj

        AS7 still supports -jboss-beans.xml.

        We didn't port all features, but mostly all generic ones.

        • 2. Re: what are the steps in Migrating JCA related config from 5 to as7
          aminjava

          I was actually looking for some guide document or something that could help me migrate existing workmanager configurations from 5 to As7

           

          first i got this

          4771: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.myApp.myApp.env.wm.WorkManagerjboss.naming.context.java.module.myApp.

          myApp.env.WorkManagerMissing[jboss.naming.context.java.module.myApp.myApp.env.wm.WorkManagerjboss.naming.context.java.module.myApp.myApp.env.WorkManager]","jbo

          ss.naming.context.java.module.myApp.myApp.env.jdbc.dsjboss.naming.context.java.jboss.java:ds.myAppDSMissing[jboss.naming.context.java.module.myApp.myApp.env.jd

          bc.dsjboss.naming.context.java.jboss.java:ds.myAppDS]"]}

           

          which was ok as i did not yet migrate or do any config changes for WorkManager

           

          my jboss-web.xml  refers to this

          <resource-ref>

                <res-ref-name>wm/WorkManager</res-ref-name>

                <jndi-name>WorkManager</jndi-name>

              </resource-ref>

           

           

          but i got stuck here to find out how and what to do for that

           

          you are right all features are not ported as just placing the same file does not help .. 

           

          and how do we know what is ported . or what to modify

          this is what is currently contains

           

          <deployment xmlns="urn:jboss:bean-deployer:2.0">

           

           

            <!-- ==================================================================== -->

            <!-- JBossCX setup, for J2EE connector architecture support               -->

            <!-- ==================================================================== -->

           

           

            <!-- THREAD POOL -->

            <bean name="WorkManagerThreadPool" class="org.jboss.util.threadpool.BasicThreadPool">

           

           

               <!-- Expose via JMX --> 

               <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.jca:service=WorkManagerThreadPool", exposedInterface=org.jboss.util.threadpool.BasicThreadPoolMBean.class)</annotation>

           

               <!-- The name that appears in thread names -->

               <property name="name">WorkManager</property>

           

           

               <!-- The maximum amount of work in the queue -->

               <property name="maximumQueueSize">1024</property>

           

           

               <!-- The maximum number of active threads -->

               <property name="maximumPoolSize">100</property>

           

           

               <!-- How long to keep threads alive after their last work (default one minute) -->

               <property name="keepAliveTime">60000</property>

           

           

            </bean>

           

           

            <!-- WORK MANAGER -->

            <bean name="WorkManager" class="org.jboss.resource.work.JBossWorkManager">

           

           

               <!-- Expose via JMX --> 

               <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.jca:service=WorkManager", exposedInterface=org.jboss.resource.work.JBossWorkManagerMBean.class)</annotation>

           

           

               <!-- The thread pool -->

               <property name="threadPool"><inject bean="WorkManagerThreadPool"/></property>

              

               <!-- The xa terminator -->

               <property name="XATerminator"><inject bean="TransactionManager" property="XATerminator"/></property>

           

            </bean>

           

           

            <!-- CACHED CONNECTION MANAGER -->

            <bean name="CachedConnectionManager" class="org.jboss.resource.connectionmanager.CachedConnectionManager">

           

           

               <!-- Expose via JMX --> 

               <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.jca:service=CachedConnectionManager", exposedInterface=org.jboss.resource.connectionmanager.CachedConnectionManagerMBean.class)</annotation>

           

           

               <!-- Whether to track unclosed connections and close them -->

               <property name="debug">true</property>

           

           

               <!-- Whether to throw an error for unclosed connections (true) or just log a warning (false) -->

               <property name="error">false</property>

             

               <!-- The transaction manager -->

               <property name="transactionManager"><inject bean="TransactionManager" property="transactionManager"/></property>

           

           

            </bean>

           

           

          </deployment>

          • 3. Re: what are the steps in Migrating JCA related config from 5 to as7
            aminjava

            this is what i get with the file above

            7:24:57,784 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" =>

            {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jca-jboss-beans.xml\".PARSE" => "org.jboss.msc.service.StartExceptio in service jboss.deployment.unit.\"jca-jboss-beans.xml\".

            PARSE: Failed to process phase PARSE of deployment \"jca-jboss-beans.xml\""}}}}

            • 4. Re: what are the steps in Migrating JCA related config from 5 to as7
              alesj

              <annotation> is not supported anymore.

              Other xml elements should work.

              And you need to check what's the exact service name of TransactionManager in AS7.

               

              But the most important - I highly doubt the same service classes exist in AS7. ;-)

              So the real problem here is not -jboss-beans.xml, but determining what exactly are you trying to do with that WorkManager.

              1 of 1 people found this helpful
              • 5. Re: what are the steps in Migrating JCA related config from 5 to as7
                aminjava

                is there and reference document or guide(Admin,dev ) for this to find out equivelent tags and what all we can configure etc

                • 6. Re: what are the steps in Migrating JCA related config from 5 to as7
                  aminjava

                  had been using WAS for long time .. this is all new exp to jboss ... so some questions might sound stupid

                  where do we find the classes to use for configuration , from what i read is that we should be using org.jboss.threads module and it does not have the said class i.e BasicThreadPool

                  • 7. Re: what are the steps in Migrating JCA related config from 5 to as7
                    nimmi

                    Hello Amin,

                     

                    Did you make any progress in migrating your Jboss5 jca-jboss-beans.xml to Jboss7 ?

                    Please let me know as I am facing similar issue.

                    • 8. Re: what are the steps in Migrating JCA related config from 5 to as7
                      manzar.chaudhary

                      Hi Amin,

                      Are you able to resolve jca-jboss-bean.xml issue..

                      I am also facing the same annotation parsing issue