5 Replies Latest reply on Feb 21, 2011 12:35 AM by nprasanna

    Admin/Jmx console not showing up

    nprasanna


      Hi,

       

      I'm working on a Service Readiness Script for JBoss Enterprise App Server 5.1. The shell script does some customization like, changes the default port settings, log4j configurations, security settings etc.. to say the least. I've joined this project recently. Previously somebody in the team had worked on the same script for version 5.0 and it works fine. But since I wanted it for version 5.1.0, I updated the template with the files from the new version. I just found that one file in our template had a big variation - And that is bindings-jboss-beans.xml. After replacing this to the new version, the server is starting, but the admin console or jmx console is not available to access. If I search for the corresponding port using netstat also, I'm not able to find it. The server.log is showing no errors.

       

      2011-02-17 10:01:48,429 INFO  [org.jboss.web.WebService] (main) Using RMI server codebase: http://192.168.41.128:8083/ 2011-02-17 10:02:01,932 INFO  [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) JBoss Web Services - Stack Native Core 2011-02-17 10:02:01,933 INFO  [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) 3.1.2.SP7 2011-02-17 10:02:04,192 INFO  [org.jboss.logbridge.LogNotificationListener] (main) Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@156d7c8[ defaultDomain='jboss' ] 2011-02-17 10:02:27,105 WARN  [jacorb.config] (main) jacorb.home unset! Will use '.' 2011-02-17 10:02:27,106 WARN  [jacorb.config] (main) File ./jacorb.properties for configuration jacorb not found 2011-02-17 10:02:27,322 WARN  [jacorb.config] (main) jacorb.home unset! Will use '.' 2011-02-17 10:02:27,329 WARN  [jacorb.config] (main) File ./jacorb.properties for configuration jacorb not found 2011-02-17 10:02:28,160 INFO  [org.jboss.iiop.CorbaNamingService] (main) CORBA Naming Started 2011-02-17 10:02:32,980 INFO  [org.jboss.jmx.adaptor.snmp.agent.SnmpAgentService] (main) SNMP agent going active 2011-02-17 10:02:38,028 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (main) Initializing partition DefaultPartition 2011-02-17 10:02:38,426 INFO  [STDOUT] (JBoss System Threads(1)-3) --------------------------------------------------------- GMS: address is 192.168.41.128:55200 (cluster=DefaultPartition) --------------------------------------------------------- 2011-02-17 10:02:38,596 INFO  [org.jboss.cache.jmx.PlatformMBeanServerRegistration] (main) JBossCache MBeans were successfully registered to the platform mbean server. 2011-02-17 10:02:38,715 INFO  [STDOUT] (main) --------------------------------------------------------- GMS: address is 192.168.41.128:55200 (cluster=DefaultPartition-HAPartitionCache) --------------------------------------------------------- 2011-02-17 10:02:40,657 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (JBoss System Threads(1)-3) Number of cluster members: 1 2011-02-17 10:02:40,658 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (JBoss System Threads(1)-3) Other members: 0 2011-02-17 10:02:40,732 INFO  [org.jboss.cache.RPCManagerImpl] (main) Received new cluster view: [192.168.41.128:55200|0] [192.168.41.128:55200] 2011-02-17 10:02:40,735 INFO  [org.jboss.cache.RPCManagerImpl] (main) Cache local address is 192.168.41.128:55200 2011-02-17 10:02:40,779 INFO  [org.jboss.cache.RPCManagerImpl] (main) state was retrieved successfully (in 2.03 seconds) 2011-02-17 10:02:40,801 INFO  [org.jboss.cache.factories.ComponentRegistry] (main) JBoss Cache version: JBossCache 'Malagueta' 3.2.5.GA 2011-02-17 10:02:40,801 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (main) Fetching serviceState (will wait for 30000 milliseconds): 2011-02-17 10:02:40,803 INFO  [org.jboss.ha.framework.interfaces.HAPartition.DefaultPartition] (main) State could not be retrieved (we are the first member in group) 2011-02-17 10:02:40,973 INFO  [org.jboss.ha.jndi.HANamingService] (main) Started HAJNDI bootstrap; jnpPort=1100, backlog=50, bindAddress=/192.168.41.128 2011-02-17 10:02:40,981 INFO  [org.jboss.ha.jndi.DetachedHANamingService$AutomaticDiscovery] (main) Listening on /192.168.41.128:1102, group=230.0.0.4, HA-JNDI address=192.168.41.128:1100 2011-02-17 10:02:42,786 INFO  [org.jboss.invocation.unified.server.UnifiedInvokerHA] (main) Service name is jboss:service=invoker,type=unifiedha 2011-02-17 10:02:44,214 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP07) - JBoss Inc. 2011-02-17 10:02:44,215 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Setting up property manager MBean and JMX layer 2011-02-17 10:02:44,641 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Initializing recovery manager 2011-02-17 10:02:45,041 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Recovery manager configured 2011-02-17 10:02:45,042 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Binding TransactionManager JNDI Reference 2011-02-17 10:02:45,143 INFO  [com.arjuna.ats.jbossatx.jta.TransactionManagerService] (main) Starting transaction recovery manager 2011-02-17 10:02:47,121 INFO  [org.apache.catalina.core.AprLifecycleListener] (main) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/jdk1.6.0_22/jre/lib/i386/server:/usr/java/jdk1.6.0_22/jre/lib/i386:/usr/java/jdk1.6.0_22/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib 2011-02-17 10:02:47,334 INFO  [org.apache.coyote.http11.Http11Protocol] (main) Initializing Coyote HTTP/1.1 on http-192.168.41.128-8080 2011-02-17 10:02:47,335 INFO  [org.apache.coyote.ajp.AjpProtocol] (main) Initializing Coyote AJP/1.3 on ajp-192.168.41.128-8009 2011-02-17 10:02:47,384 INFO  [org.apache.catalina.core.StandardService] (main) Starting service jboss.web 2011-02-17 10:02:47,388 INFO  [org.apache.catalina.core.StandardEngine] (main) Starting Servlet Engine: JBoss Web/2.1.10 2011-02-17 10:02:47,457 INFO  [org.apache.catalina.startup.Catalina] (main) Server startup in 121 ms 2011-02-17 10:02:47,495 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/web-console 2011-02-17 10:02:49,670 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jbossws 2011-02-17 10:02:49,980 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/juddi 2011-02-17 10:02:50,027 INFO  [org.apache.juddi.registry.RegistryServlet] (main) Loading jUDDI configuration. 2011-02-17 10:02:50,046 INFO  [org.apache.juddi.registry.RegistryServlet] (main) Resources loaded from: /WEB-INF/juddi.properties 2011-02-17 10:02:50,046 INFO  [org.apache.juddi.registry.RegistryServlet] (main) Initializing jUDDI components. 2011-02-17 10:02:50,785 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/var/lib/jbossas/server/cms-jbeap/deploy/jboss-local-jdbc.rar/META-INF/ra.xml 2011-02-17 10:02:50,801 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/var/lib/jbossas/server/cms-jbeap/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml 2011-02-17 10:02:50,808 INFO  [org.jboss.resource.deployers.RARDeployment] (main) Required license terms exist, view vfsfile:/var/lib/jbossas/server/cms-jbeap/deploy/mail-ra.rar/META-INF/ra.xml 2011-02-17 10:02:53,267 INFO  [org.jboss.resource.connectionmanager.ConnectionFactoryBindingService] (main) Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 2011-02-17 10:02:54,328 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/admin-console 2011-02-17 10:02:54,561 INFO  [javax.enterprise.resource.webcontainer.jsf.config] (main) Initializing Mojarra (1.2_13-b01-FCS) for context '/admin-console' 2011-02-17 10:02:56,065 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR 2011-02-17 10:03:03,397 INFO  [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/jmx-console 2011-02-17 10:03:03,649 INFO  [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Loading profile: ProfileKey@1611ed3[domain=default, server=default, name=cms-jbeap] 2011-02-17 10:03:03,662 INFO  [org.apache.coyote.http11.Http11Protocol] (main) Starting Coyote HTTP/1.1 on http-192.168.41.128-8080 2011-02-17 10:03:03,687 INFO  [org.apache.coyote.ajp.AjpProtocol] (main) Starting Coyote AJP/1.3 on ajp-192.168.41.128-8009 2011-02-17 10:03:03,801 INFO  [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)] Started in 1m:41s:5ms 2011-02-17 10:05:06,108 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR 2011-02-17 10:07:16,151 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR 2011-02-17 10:09:26,195 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR 2011-02-17 10:11:36,239 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR 2011-02-17 10:13:46,282 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR 2011-02-17 10:15:56,326 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-18) [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery  got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/DefaultJMSProvider, XAException.XAER_RMERR

       

       

      Sorry for "quoting" the log in improper format. I couldn't find any other way. If it might help, I've also attached the log file. Please go through it.

      It shows no error. And the server started message is also appearing. The second set of WARN messages are because I had removed JMS components as part of security requirements. Can anyone help me identify the problem as to why the admin/jmx consoles are not opening up.

       

      It's an urgent issue. So any help is much appreciated.

        • 1. Admin/Jmx console not showing up
          nprasanna

          I had mentioned that I had removed certain components because of security requirements. They are:

          1) moved deploy/ROOT.war to customprofile/un-deploy folder(we created it)

          2) uuid-key-generator.sar, httphainvoker.sar, quartz-ra.rar, mail-service.xml, scheduler-service.xml, scheduler-manager-service.xml

          3) moved the deploy/messaging folder to un-deploy folder

          4) moved deploy/jms-ra.rar also

          5) moved unwanted jars like autonumber-plugin.jar, mail.jar, mail-plugin.jar, scheduler-plugin-example.jar, scheduler-plugin.jar to JBOSS_HOME/common/un-lib folder(we created it)

           

          We customized the conf/jboss-log4j.xml to our needs.

          We enable virtual host configuration in some of the xmls.

           

          These are the things our script does. Coud anyone help based on this info. If you want, I can provide more info. Please help asap!!

          • 2. Admin/Jmx console not showing up
            nickarls

            Tried running the script in parts (as far as it's possible) to see where it breaks? Does it pick up *any* applications?

            1 of 1 people found this helpful
            • 3. Admin/Jmx console not showing up
              nprasanna

              Hi Nicklas,

              Thanks for replying! I haven't tried to run it in parts so far, but since it's a good idea, I'm going to try it now and post the updates.

              Thanks again.

              • 4. Admin/Jmx console not showing up
                nprasanna

                Hi Nicklas, I did what you said. I tested individually and separately what the service readiness script does. I made the required changes in some xmls and they all worked fine. But when I try to run them all through the script with the template of all the files that I've modified, I get this problem : The admin and jmx consoles are coming up. Fine with them. I deployed some application wars and jars. They are showing as successfully deployed, up and running in the admin console and there are no deployment errors in the server.log. But when I try to access the application url for all the applications only a blank page is coming. No errors. I get the feel that something is blocking the application from showing in the browser. But I don’t know what it is :(
                The following are the changes I made in some of the xml files and the template consists of these files with the changes:
                1) Created a custom profile based on Jboss 5.1 EAP production profile
                2) changed http and messaging port in custom profile/conf/bindings..xml
                3) moved ROOT.war, uuid-key-generator.sar, httpha-invoker.sar, quartz-ra.rar, mail-service.xml, schedule-manager-service.xml, scheduler-service.xml, jms-ra.rar from deploy to customProfile/un-deploy folder created by me
                4) Modified custProfile/deploy/jbossweb.sar/server.xml to include a virtual host tag for virtual host configuration
                5) Modified custProfile/deploy/jmx-console.war/WEB-INF/jboss-web.xml for virtual host  configuration(same as above). Did the same for admin-console.war's jboss-web.xml file
                6) Modified /deploy/jmx-console.war/WEB-INF/web.xml to include GET and POST methods in some html tag
                7) Added a tag for Authorization in custProfile/deploy/jmx-invoker-service.xml
                That's it! Only these changes. When I made these changes one by one, they worked fine. When I tested them all at the same time, even then it worked fine.(Testing means I ran the server, checked the log for any errors, brought up admin and jmx consoles, undeployed and deployed some apps and tried to access them through browser)
                The problem was when I tested them through a readiness shell script, that does all these changes by itself, I'm not able to access the apps. Please help me with this issue asap.
                Thanks in advance.

                • 5. Admin/Jmx console not showing up
                  nprasanna

                  Could it be this? As mentioned above, in the jmx-console.war and admin-console.war, I'm also editing the web.xml to include the followin tags:
                  JBossAdmin
                  and
                  JBossAdmin and in jboss-web.xml, I have,
                  java:/jaas/jmx-console          localhost.localdomain-cms-jbeap-cms-jbeap-cms-jbeap
                  Could it be possible that in my Application war files too, I have to edit the web.xml to include the security role tag so that I may be able to access the Applications?!