9 Replies Latest reply on Jul 16, 2015 3:00 AM by Wolf-Dieter Fink

    Unable to see the JMS message in JBoss AS 6.1.0 Final

    jamespun seb Newbie

      I have deployed EAR file into JBoss AS 6.1.0 Final and server started without any errors/warnings. But when I send a soap request from cleint side the MDB is not getting/publishing the message. The JBoss server is idle and remains in the same started state. I have attached the Boot.log and JBoss console files . Please go through the same.We are using an external JMS Provider to connect to MDB.

      The JMS Provider is an independent directory( SAR ) and deployed successfully. We can see the JMS provider connected to Ldap URL using JNDI.

       

      Could you please help me to resolve this issue ?. Thanks.

        • 1. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
          Scott Marlow Master

          James,

           

          You have a few choices.  Either recreate on the latest community release of WildFly and post on https://community.jboss.org/en/wildfly?view=discussions.  Or, look into getting a subscription to the EAP product (e.g. EAP 6) and use the paid support that you get with that.  I'm not familiar with the cause of the problem that you are hitting but someone else probably will when you recreate on either EAP or latest WildFly.

           

          Best,

          Scott

          • 2. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
            Justin Bertram Master

            Please attach the MDB's configuration (either the MDB itself if configured via annotation or ejb-jar.xml and jboss.xml if configured via deployment descriptor).

             

            Also, please attach the configuration for the external JMS provider (i.e. the SAR that you referenced).

            • 3. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
              jamespun seb Newbie

              Hi Justin,

               

              I have attached the MDB configuration files like ejb-jar.xml, jboss.xml . Please see the same. Also, I have deployed the same EAR file into JBoss 4 and it is working fine. The request message is coming. But in JBoss AS 6.1.0 the messsages not coming although there is no deployment issues.

              The SAR directory successfully deployed.

              In the Jboss.xml file the external JMS Provider is mentioned under <invoker-proxy-binding>at <JMSProviderAdapterJNDI>MbusJMSProvider</JMSProviderAdapterJNDI>.

               

              Please help me to fix this issue

              • 4. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
                Wolf-Dieter Fink Master

                I would recommend to stay with AS4 or AS5 if that work and you have an old application.

                If the application is still maintained I recommend to migrate to wildfly as the latest community version.

                Or if you need reliable support use EAP6 and buy a subscription.

                 

                In any case I would not use AS6 as this version is quite old and you will not find a lot of people in the community for help.

                • 5. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
                  Justin Bertram Master

                  After looking at your jboss.xml and ejb-jar.xml I agree with Wolf - you should stay on JBoss AS 4.x (especially considering that your application actually works there).  You've got a lot of non-standard, non-portable configuration in jboss.xml which is almost certainly why your application isn't working in JBoss AS 6.  I recommend you discard all that and port your MDB to EJB3 on either Wildfly or EAP 6.

                  • 6. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
                    jamespun seb Newbie

                    Thanks for the reply. The application is currently running on JBoss 4. I need to migrate it to JBoss 6.From the server console (console.txt) I can see EJB's are deploying and server started .

                    I have a request. I'm trying to enable logging using log4j in JBoss AS 6. But no proper documentation available about how to activate logging. If logging is enabled I can trace any error in application ear since I have added log.info messages in java classes. Could you please help me to enable logging ?. I tried differnt config changes but no luck

                     

                    Thanks,

                    James

                    • 7. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
                      jamespun seb Newbie

                      Thanks for the reply. The application is currently running on JBoss 4. I need to migrate it to JBoss 6.From the server console (console.txt) I can see EJB's are deploying and server started .

                      I have a request. I'm trying to enable logging using log4j in JBoss AS 6. But no proper documentation available about how to activate logging. If logging is enabled I can trace any error in application ear since I have added log.info messages in java classes. Could you please help me to enable logging ?. I tried differnt config changes but no luck

                       

                      Thanks,

                      James

                      • 8. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
                        jamespun seb Newbie

                        I have added modified jboss.xml and ejb-jar.xml and log file. In the log file, I can see the Message Listener EJB not bound due to local home interfaces.see below

                         

                        :29:34,426 DEBUG [EjbModule] startService, starting container: MessageListenerEJB

                        11:29:34,426 DEBUG [ServiceController] starting service jboss.j2ee:jndiName=local/MessageListenerEJB@22853794,service=EJB

                        11:29:34,426 DEBUG [MessageDrivenContainer] Starting jboss.j2ee:jndiName=local/MessageListenerEJB@22853794,service=EJB

                        11:29:34,427 DEBUG [MessageDrivenContainer] Begin java:comp/env for EJB: MessageListenerEJB

                        11:29:34,427 DEBUG [MessageDrivenContainer] TCL: org.jboss.util.loading.DelegatingClassLoader@1e7e602

                        11:29:34,427 DEBUG [MessageDrivenContainer] Unable to retrieve orbjavax.management.InstanceNotFoundException: jboss:service=CorbaORB is not registered.

                        11:29:34,429 DEBUG [MessageDrivenContainer] Using java:comp using id=jboss.j2ee:jndiName=local/MessageListenerEJB@22853794,service=EJB

                        11:29:34,429 DEBUG [MessageDrivenContainer] Linked java:comp/TransactionSynchronizationRegistry to JNDI name: java:TransactionSynchronizationRegistry

                        11:29:34,432 DEBUG [MessageDrivenContainer] Binding an EJBReference ejb/ProcessorHomeRemote

                        11:29:34,433 DEBUG [MessageDrivenContainer] adding mbus-message-driven-bean:ProcessorHomeRemote to Reference

                        11:29:34,440 DEBUG [MessageDrivenContainer] End java:comp/env for EJB: MessageListenerEJB

                        11:29:34,440 DEBUG [BaseLocalProxyFactory] MessageListenerEJB cannot be Bound, doesn't have local and local home interfaces

                        11:29:34,440 DEBUG [ServiceController] starting service jboss.j2ee:service=EJB,plugin=pool,jndiName=local/MessageListenerEJB@22853794

                        11:29:34,440 DEBUG [MessageDrivenInstancePool] Starting jboss.j2ee:service=EJB,plugin=pool,jndiName=local/MessageListenerEJB@22853794

                        11:29:34,441 DEBUG [MessageDrivenInstancePool] Started jboss.j2ee:service=EJB,plugin=pool,jndiName=local/MessageListenerEJB@22853794

                         

                        Please see the attachments of jboss.xml and ejb-jar.xml

                        • 9. Re: Unable to see the JMS message in JBoss AS 6.1.0 Final
                          Wolf-Dieter Fink Master

                          I did not recommend to use JBoss AS6 as this is an outdated version.

                          If you try to migrate you should use WildFly instead which is the successor.