2 Replies Latest reply on Feb 13, 2018 12:00 AM by n_nagraj321

    Migration from Jboss 4.2.3 to WildFly

    n_nagraj321
    n_nagraj321 Feb 12, 2018 9:20 AM

      Hi,

       

      we have  Very legacy application which currently running on Jboss 4.2.3 GA. We have decided to upgrade to the latest WildFly server.

       

      qestion here is we have invoker-bindings element in Jbos.xml and couldn find the qualent element in Jboss-ejb3.xml.

       

      Any help on this highly appreciated.

      Thanks in advance.

       

      Thanks

      Nagarju

      • 617 Views
      • Tags:
        • 1. Re: Migration from Jboss 4.2.3 to WildFly
          jaikiran
          jaikiran Feb 12, 2018 11:43 PM (in response to n_nagraj321)

          WildFly is completely different in terms of the underlying architecture when compared to JBoss AS 4.x. The invoker bindings play no role in WildFly. Most likely whatever was configured in there won't be applicable in WildFly. However, if there's any specific config that you are interested in, in that section, paste that section in your post and we can see if there's an equivalent in WildFly for that.

            • Actions
          • 2. Re: Migration from Jboss 4.2.3 to WildFly
            n_nagraj321
            n_nagraj321 Feb 13, 2018 12:00 AM (in response to n_nagraj321)

            Thanks jaikiran for your reply. Below is the context of jboss.xml

             

             

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

            <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_2.dtd">

            <jboss>

               <invoker-proxy-bindings>

                  <invoker-proxy-binding>

                     <name>tibmessage-driven-bean</name>

                     <invoker-mbean>default</invoker-mbean>

                     <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>

                     <proxy-factory-config>

                        <JMSProviderAdapterJNDI>ActiveMQJMSProvider</JMSProviderAdapterJNDI>

                        <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>

                        <MinimumSize>5</MinimumSize>

                        <MaximumSize>10</MaximumSize>

                        <KeepAliveMillis>30000</KeepAliveMillis>

                        <MaxMessages>1</MaxMessages>

                        <MDBConfig>

                           <ReconnectIntervalSec>10</ReconnectIntervalSec>

                           <DLQConfig>

                              <DestinationQueue>queue/DLQ</DestinationQueue>

                              <DLQUser>username</DLQUser>

                              <DLQPassword>password</DLQPassword>

                              <MaxTimesRedelivered>5</MaxTimesRedelivered>

                              <TimeToLive>0</TimeToLive>

                           </DLQConfig>

                        </MDBConfig>

                     </proxy-factory-config>

                  </invoker-proxy-binding>

               </invoker-proxy-bindings>

               <enterprise-beans>

                  <message-driven>

                     <ejb-name>MessageEJB</ejb-name>

                     <destination-jndi-name>com.test.queue</destination-jndi-name>

                     <resource-ref>

                        <res-ref-name>jms/QCF</res-ref-name>

                        <jndi-name>java:/JNDINAME</jndi-name>

                     </resource-ref>

                     <invoker-bindings>

                        <invoker>

                           <invoker-proxy-binding-name>tibmessage-driven-bean</invoker-proxy-binding-name>

                        </invoker>

                     </invoker-bindings>

                     <mdb-user>username</mdb-user>

                     <mdb-passwd>password</mdb-passwd>

                  </message-driven>

               </enterprise-beans>

            </jboss>

              • Actions