12 Replies Latest reply on May 4, 2011 8:09 AM by wolfgangknauf

    Jboss 5.1 AS taking unsually long time to boot

    raghuseeta
    raghuseeta Apr 25, 2011 9:35 AM

      I am trying to start the JBOSS 5.1 AS on RHEL Linux box. It is taking unusually long time to boot. Ultimately it dosn't start and comes out throwing some errors and killing the process. I have set JAVA_OPTS as follows:

      JAVA_OPTS:  -Xms256m -Xmx720m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true

       

      I am running the the zip file what i got from distribution with default components. I have not put any of my war and jars

      As shown in the attached logs I started the jboss at 1:50:17 . By the time it came out it was  08:42:24 !!!!

       

      It paused after the following line for 1 hr !!

      01:50:54,924 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@6257828d[ defaultDomain='jboss' ]

      02:50:58,097 WARN  [config] jacorb.home unset! Will use '.'

       

       

      Can anybody please suggest me what could be going wrong by looking to the logs. Whether this has got something to do with the network issues. My linux machine has got 4 GB of RAM. I am a new to without much prior experience in JBOSS. Can anybody please help me in this. Pls let me know if any body need any details. Please find the logs below

        JBoss Bootstrap Environment

       

        JBOSS_HOME: /root/jbossraw/whp-jboss-cluster-5

       

        JAVA: /usr/java/jdk1.6.0_17/bin/java

       

        JAVA_OPTS: -Dprogram.name=jboss_run.sh -server -Xms128m -Xmx720m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true

       

        CLASSPATH: /root/jbossraw/whp-jboss-cluster-5/bin/run.jar:/usr/java/jdk1.6.0_17/lib/tools.jar

       

      =========================================================================

                                                                                     01:50:17,454 INFO  [ServerImpl] Starting JBoss (Microcontainer)...

      01:50:17,476 INFO  [ServerImpl] Release ID: JBoss [EAP] 5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)

      01:50:17,477 INFO  [ServerImpl] Bootstrap URL: null

      01:50:17,477 INFO  [ServerImpl] Home Dir: /root/jbossraw/whp-jboss-cluster-5

      01:50:17,477 INFO  [ServerImpl] Home URL: file:/root/jbossraw/whp-jboss-cluster-5/

      01:50:17,477 INFO  [ServerImpl] Library URL: file:/root/jbossraw/whp-jboss-cluster-5/lib/

      01:50:17,508 INFO  [ServerImpl] Patch URL: null

      01:50:17,508 INFO  [ServerImpl] Common Base URL: file:/root/jbossraw/whp-jboss-cluster-5/common/

      01:50:17,508 INFO  [ServerImpl] Common Library URL: file:/root/jbossraw/whp-jboss-cluster-5/common/lib/

      01:50:17,508 INFO  [ServerImpl] Server Name: default

      01:50:17,508 INFO  [ServerImpl] Server Base Dir: /root/jbossraw/whp-jboss-cluster-5/server

      01:50:17,508 INFO  [ServerImpl] Server Base URL: file:/root/jbossraw/whp-jboss-cluster-5/server/

      01:50:17,508 INFO  [ServerImpl] Server Config URL: file:/root/jbossraw/whp-jboss-cluster-5/server/default/conf/

      01:50:17,509 INFO  [ServerImpl] Server Home Dir: /root/jbossraw/whp-jboss-cluster-5/server/default

      01:50:17,509 INFO  [ServerImpl] Server Home URL: file:/root/jbossraw/whp-jboss-cluster-5/server/default/

      01:50:17,509 INFO  [ServerImpl] Server Data Dir: /root/jbossraw/whp-jboss-cluster-5/server/default/data

      01:50:17,509 INFO  [ServerImpl] Server Library URL: file:/root/jbossraw/whp-jboss-cluster-5/server/default/lib/

      01:50:17,509 INFO  [ServerImpl] Server Log Dir: /root/jbossraw/whp-jboss-cluster-5/server/default/log

      01:50:17,509 INFO  [ServerImpl] Server Native Dir: /root/jbossraw/whp-jboss-cluster-5/server/default/tmp/native

      01:50:17,509 INFO  [ServerImpl] Server Temp Dir: /root/jbossraw/whp-jboss-cluster-5/server/default/tmp

      01:50:17,509 INFO  [ServerImpl] Server Temp Deploy Dir: /root/jbossraw/whp-jboss-cluster-5/server/default/tmp/deploy

      01:50:20,497 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/root/jbossraw/whp-jboss-cluster-5/server/default/conf/bootstrap.xml

      01:50:21,822 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]

      01:50:21,826 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]

      01:50:22,563 INFO  [CopyMechanism] VFS temp dir: /root/jbossraw/whp-jboss-cluster-5/server/default/tmp

      01:50:22,571 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.

      01:50:26,284 INFO  [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.

      01:50:26,284 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_17-b04)

      01:50:26,284 INFO  [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 14.3-b01,Sun Microsystems Inc.

      01:50:26,285 INFO  [ServerInfo] OS-System: Linux 2.6.18-92.el5,amd64

      01:50:26,295 INFO  [ServerInfo] VM arguments: -Dprogram.name=jboss_run.sh -Xms128m -Xmx720m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/root/jbossraw/whp-jboss-cluster-5/lib/endorsed

      01:50:26,351 INFO  [JMXKernel] Legacy JMX core initialized

      01:50:38,082 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/

      01:50:51,604 INFO  [CXFServerConfig] JBoss Web Services - Stack CXF Runtime Server

      01:50:51,610 INFO  [CXFServerConfig] 3.1.2.SP7

      01:50:54,924 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@6257828d[ defaultDomain='jboss' ]

      02:50:58,097 WARN  [config] jacorb.home unset! Will use '.'

      02:50:58,344 WARN  [config] File ./jacorb.properties for configuration jacorb not found

      02:56:52,863 WARN  [config] jacorb.home unset! Will use '.'

      02:56:53,654 WARN  [config] File ./jacorb.properties for configuration jacorb not found

      03:06:46,961 INFO  [CorbaNamingService] CORBA Naming Started

      03:12:43,100 INFO  [MailService] Mail Service bound to java:/Mail

      03:46:45,488 INFO  [SnmpAgentService] SNMP agent going active

      04:35:05,874 INFO  [DefaultPartition] Initializing partition DefaultPartition

      04:37:05,615 INFO  [STDOUT]

      ---------------------------------------------------------

      GMS: address is 127.0.0.1:55200 (cluster=DefaultPartition)

      ---------------------------------------------------------

      04:38:24,207 INFO  [DefaultPartition] Number of cluster members: 1

      04:38:24,233 INFO  [DefaultPartition] Other members: 0

      04:38:34,593 INFO  [PlatformMBeanServerRegistration] JBossCache MBeans were successfully registered to the platform mbean server.

      04:38:55,065 INFO  [STDOUT]

      ---------------------------------------------------------

      GMS: address is 127.0.0.1:55200 (cluster=DefaultPartition-HAPartitionCache)

      ---------------------------------------------------------

      04:38:58,634 INFO  [RPCManagerImpl] Received new cluster view: [127.0.0.1:55200|0] [127.0.0.1:55200]

      04:38:58,667 INFO  [RPCManagerImpl] Cache local address is 127.0.0.1:55200

      04:38:59,914 INFO  [RPCManagerImpl] state was retrieved successfully (in 4.07 seconds)

      04:39:07,780 INFO  [ComponentRegistry] JBoss Cache version: JBossCache 'Malagueta' 3.2.5.GA

      04:39:07,800 INFO  [DefaultPartition] Fetching serviceState (will wait for 30000 milliseconds):

      04:39:13,645 INFO  [DefaultPartition] State could not be retrieved (we are the first member in group)

      04:40:28,441 INFO  [HANamingService] Started HAJNDI bootstrap; jnpPort=1100, backlog=50, bindAddress=/127.0.0.1

      04:40:29,334 INFO  [DetachedHANamingService$AutomaticDiscovery] Listening on /127.0.0.1:1102, group=230.0.0.4, HA-JNDI address=127.0.0.1:1100

      04:44:56,667 WARN  [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.

      04:51:30,315 INFO  [UnifiedInvokerHA] Service name is jboss:service=invoker,type=unifiedha

      04:55:33,276 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP07) - JBoss Inc.

      04:55:33,455 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer

      04:59:22,168 INFO  [TransactionManagerService] Initializing recovery manager

      05:00:09,031 INFO  [TransactionManagerService] Recovery manager configured

      05:00:10,308 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference

      05:00:36,718 INFO  [TransactionManagerService] Starting transaction recovery manager

      05:49:10,828 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.ActionStatusService_7] - Connection Lost to Recovery Manager

      05:49:47,225 WARN  [loggerI18N] [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

      05:51:59,174 WARN  [loggerI18N] [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

      05:52:43,541 INFO  [AprLifecycleListener] 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_17/jre/lib/amd64/server:/usr/java/jdk1.6.0_17/jre/lib/amd64:/usr/java/jdk1.6.0_17/jre/../lib/amd64:/usr/java/packages/lib/amd64:/lib:/usr/lib

      05:53:09,267 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080

      05:53:09,840 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009

      05:53:27,056 INFO  [StandardService] Starting service jboss.web

      05:53:27,776 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.10

      05:54:10,900 WARN  [loggerI18N] [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

      05:54:26,260 INFO  [Catalina] Server startup in 75864 ms

      05:55:25,228 INFO  [TomcatDeployment] deploy, ctxPath=/juddi

      05:56:21,484 WARN  [loggerI18N] [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

      06:01:10,591 WARN  [loggerI18N] [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

      06:03:24,700 WARN  [loggerI18N] [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

      06:03:51,924 INFO  [RegistryServlet] Loading jUDDI configuration.

      06:03:52,016 INFO  [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties

      06:03:52,016 INFO  [RegistryServlet] Initializing jUDDI components.

      06:04:51,071 INFO  [TomcatDeployment] deploy, ctxPath=/web-console

      06:10:08,586 WARN  [loggerI18N] [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

      06:53:42,799 WARN  [loggerI18N] [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

      06:54:12,397 INFO  [TomcatDeployment] deploy, ctxPath=/invoker

      06:54:40,660 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws

      06:55:53,279 WARN  [loggerI18N] [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

      06:58:05,218 WARN  [loggerI18N] [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

      06:58:29,748 INFO  [RARDeployment] Required license terms exist, view vfsfile:/root/jbossraw/whp-jboss-cluster-5/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml

      06:59:00,943 INFO  [RARDeployment] Required license terms exist, view vfsfile:/root/jbossraw/whp-jboss-cluster-5/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml

      06:59:10,477 INFO  [RARDeployment] Required license terms exist, view vfsfile:/root/jbossraw/whp-jboss-cluster-5/server/default/deploy/jms-ra.rar/META-INF/ra.xml

      06:59:35,808 INFO  [RARDeployment] Required license terms exist, view vfsfile:/root/jbossraw/whp-jboss-cluster-5/server/default/deploy/mail-ra.rar/META-INF/ra.xml

      07:00:20,131 WARN  [loggerI18N] [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

      07:00:38,727 INFO  [RARDeployment] Required license terms exist, view vfsfile:/root/jbossraw/whp-jboss-cluster-5/server/default/deploy/quartz-ra.rar/META-INF/ra.xml

      07:01:19,682 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main

      07:01:25,884 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.

      07:01:26,422 INFO  [RAMJobStore] RAMJobStore initialized.

      07:01:26,439 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'

      07:01:26,451 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2

      07:01:27,210 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.

      07:02:30,470 WARN  [loggerI18N] [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

      07:04:19,530 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'

      07:04:40,979 WARN  [loggerI18N] [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

      07:08:59,833 WARN  [loggerI18N] [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

      07:09:57,013 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX 7f000001:b054:4dae1acb:3c in state  RUN

      07:10:00,064 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX 7f000001:b054:4dae1acb:3c in state  CANCEL

      07:10:03,521 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_18] - TransactionReaper::check timeout for TX 7f000001:b054:4dae1acb:3c in state  CANCEL_INTERRUPTED

      07:10:03,536 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id 7f000001:b054:4dae1acb:3c invoked while multiple threads active within it.

      07:10:05,414 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_6] - TransactionReaper::check worker Thread[Thread-25,5,jboss] not responding to interrupt when cancelling TX 7f000001:b054:4dae1acb:3c -- worker marked as zombie and TX scheduled for mark-as-rollback

      07:10:05,424 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action 7f000001:b054:4dae1acb:3c aborting with 1 threads active!

      07:10:05,491 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_10] - TransactionReaper::check successfuly marked TX 7f000001:b054:4dae1acb:3c as rollback only

      07:10:18,378 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TransactionReaper_13] - TransactionReaper::doCancellations worker Thread[Thread-25,5,jboss] missed interrupt when cancelling TX 7f000001:b054:4dae1acb:3c -- exiting as zombie (zombie count decremented to 0)

      07:10:18,462 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_40] - Abort called on already aborted atomic action 7f000001:b054:4dae1acb:3c

      07:10:22,330 ERROR [ExceptionUtil] org.jboss.jms.server.plugin.JDBCJMSUserManagerService@757d6bea startService

      javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!

              at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1422)

              at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)

              at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)

              at org.jboss.messaging.core.impl.JDBCSupport$TransactionWrapper.end(JDBCSupport.java:354)

              at org.jboss.messaging.core.impl.JDBCSupport.createSchema(JDBCSupport.java:321)

              at org.jboss.messaging.core.impl.JDBCSupport.start(JDBCSupport.java:167)

              at org.jboss.jms.server.plugin.JDBCJMSUserManager.start(JDBCJMSUserManager.java:98)

              at org.jboss.jms.server.plugin.JDBCJMSUserManagerService.startService(JDBCJMSUserManagerService.java:78)

              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)

              at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:269)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

              at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)

              at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

              at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)

              at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

              at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)

              at $Proxy38.start(Unknown Source)

              at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)

              at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)

              at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)

              at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)

              at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)

              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

              at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

              at org.jboss.system.ServiceController.doChange(ServiceController.java:688)

              at org.jboss.system.ServiceController.start(ServiceController.java:460)

              at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)

              at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)

              at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)

              at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

              at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)

              at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)

              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)

              at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)

              at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

              at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

              at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

              at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)

              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

              at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)

              at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)

              at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

              at org.jboss.Main.boot(Main.java:221)

              at org.jboss.Main$1.run(Main.java:556)

              at java.lang.Thread.run(Thread.java:619)

      07:10:23,045 ERROR [AbstractKernelController] Error installing to Start: name=jboss.messaging:service=JMSUserManager state=Create mode=Manual requiredState=Installed

      javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active!

              at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1422)

              at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:137)

              at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)

              at org.jboss.messaging.core.impl.JDBCSupport$TransactionWrapper.end(JDBCSupport.java:354)

              at org.jboss.messaging.core.impl.JDBCSupport.createSchema(JDBCSupport.java:321)

              at org.jboss.messaging.core.impl.JDBCSupport.start(JDBCSupport.java:167)

              at org.jboss.jms.server.plugin.JDBCJMSUserManager.start(JDBCJMSUserManager.java:98)

              at org.jboss.jms.server.plugin.JDBCJMSUserManagerService.startService(JDBCJMSUserManagerService.java:78)

              at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)

              at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:269)

              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

              at java.lang.reflect.Method.invoke(Method.java:597)

              at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)

              at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

              at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)

              at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

              at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)

              at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)

              at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)

              at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)

              at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)

              at $Proxy38.start(Unknown Source)

              at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)

              at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)

              at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)

              at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)

              at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)

              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

              at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:297)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

              at org.jboss.system.ServiceController.doChange(ServiceController.java:688)

              at org.jboss.system.ServiceController.start(ServiceController.java:460)

              at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:163)

              at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:99)

              at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)

              at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)

              at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55)

              at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1193)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)

              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)

              at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)

              at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)

              at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)

              at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)

              at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)

              at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)

              at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)

              at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)

              at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)

              at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778)

              at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543)

              at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)

              at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)

              at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)

              at org.jboss.Main.boot(Main.java:221)

              at org.jboss.Main$1.run(Main.java:556)

              at java.lang.Thread.run(Thread.java:619)

      07:11:11,455 WARN  [loggerI18N] [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

      07:13:38,041 WARN  [loggerI18N] [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

      08:08:19,280 WARN  [loggerI18N] [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

      08:09:23,613 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console

      08:10:30,425 WARN  [loggerI18N] [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

      08:10:39,322 INFO  [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/admin-console'

      08:12:42,521 WARN  [loggerI18N] [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

      08:14:54,643 WARN  [loggerI18N] [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

      08:17:10,709 WARN  [loggerI18N] [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

      08:22:05,771 WARN  [loggerI18N] [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

      08:24:17,953 WARN  [loggerI18N] [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

      08:26:36,633 WARN  [loggerI18N] [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

      08:33:22,142 WARN  [loggerI18N] [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

      08:35:36,319 WARN  [loggerI18N] [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

      08:37:48,768 WARN  [loggerI18N] [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

      08:42:24,552 WARN  [loggerI18N] [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

      jboss_run.sh: line 286:  3398 Killed                  "/usr/java/jdk1.6.0_17/bin/java" -Dprogram.name=jboss_run.sh -server -Xms128m -Xmx720m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs="/root/jbossraw/whp-jboss-cluster-5/lib/endorsed" -classpath "/root/jbossraw/whp-jboss-cluster-5/bin/run.jar:/usr/java/jdk1.6.0_17/lib/tools.jar" org.jboss.Main -c default

      • 13796 Views
      • Categories: JBoss AS 5.1
      • Tags:
        • 1. Jboss 5.1 AS taking unsually long time to boot
          peterj
          peterj Apr 25, 2011 10:55 AM (in response to raghuseeta)

          >>Whether this has got something to do with the network issues.

          That is what I would guess, because the pauses sound like network timeouts to me.

           

          First, the server.log proably shows a little more detail on what is happening during that one hour. You could look there for more info.

           

          Second, when you see a pause like this, take a JVM thread dump and look for the thread that is waiting on a reply form the network. Knowing what that thread is waiting on might provide some clue as to what part of the network is giving problems.

           

          Third, search the forums. This problem comes up occasionally (though i have to admit you 8 hours is by far the longest tsartup time I have seen, usually the startup time is around 15 minutes or so)

            • Actions
          • 2. Jboss 5.1 AS taking unsually long time to boot
            raghuseeta
            raghuseeta Apr 26, 2011 9:03 AM (in response to peterj)

            Thanks Peter for the quick reply

             

            I tried getting the ThreadDump of the jvm by using jstack <pid> of jboss and kill -3 <pid> while jboss is starting . (I obtained pid by ps -ef | grep jboss). But i am not getting any logs . I am redirecting the logs to file like  jstack<pid> > threaddump.txt. While I do this, nothing is getting written to the txt file. Can you pls let me know whether these are the ways to obtain thread dump or  we should do something else

              • Actions
            • 3. Jboss 5.1 AS taking unsually long time to boot
              peterj
              peterj Apr 26, 2011 10:15 AM (in response to raghuseeta)

              http://java.sun.com/developer/technicalArticles/Programming/Stacktrace/

               

              Double-check the pid - it should be for a process named 'java'

               

              You can also use VirtualVM (jvirtualvm) to get a thread dump.

                • Actions
              • 4. Jboss 5.1 AS taking unsually long time to boot
                rhusar
                rhusar Apr 26, 2011 10:51 AM (in response to raghuseeta)

                Looks like you are running into some soft of deadlocks. Really, a jstack output would be very helpful (do something like jps -l | grep jboss to find the pid).

                 

                Regarding the question of  start up time there is a guide how to slim it down thus improve boot time:  http://community.jboss.org/wiki/JBoss5xTuningSlimming

                  • Actions
                • 5. Jboss 5.1 AS taking unsually long time to boot
                  raghuseeta
                  raghuseeta Apr 27, 2011 8:47 AM (in response to rhusar)

                    Thanks Husar and Peter for your timely responses

                   

                   

                  After doing some analysis, what I found is probably problem is not with jboss. But is with the configurations of the machine. I have single core, 64 bit machine with 4 GB RAM. When I start the JBOSS I get very high I/O Waiting time and very high memory usage. A trace of top is as show below:

                   

                  [root@ccdevapp01 ~]# top

                  top - 23:30:57 up 29 days,  1:34,  5 users,  load average: 4.36, 3.92, 5.17

                  Tasks: 116 total,   2 running, 114 sleeping,   0 stopped,   0 zombie

                   

                  Cpu(s):  0.3%us,  0.3%sy,  0.0%ni,  0.0%id, 99.0%wa,  0.0%hi,  0.3%si,  0.0%st

                   

                  Mem:    381508k total,   376448k used,    5060k free,      212k buffers

                   

                  Swap:   786424k total,   437628k used,   348796k free,    10288k cached

                   

                    PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND

                    248 root          10  -5     0    0    0 S  0.3  0.0  20:43.49 kswapd0

                   

                  4737 dbus      15   0 21376  484  252 S  0.3  0.1   1:11.99 dbus-daemon

                   

                  5280 root      19   0 1592m 298m 4212 S  0.3 80.1   0:23.05 java


                  20580 root      16   0  607m 3088 1348 D  0.3  0.8   8:43.56 firefox

                      1 root         15   0 10328   64   40 S  0.0  0.0   0:28.18 init

                      2 root         RT  -5     0    0    0 S  0.0  0.0   0:00.00 migration/0

                      3 root         34  19     0    0    0 S  0.0  0.0   0:00.00 ksoftirqd/0

                      4 root         RT  -5     0    0    0 S  0.0  0.0   0:00.00 watchdog/0

                      5 root        10  -5     0    0    0 S  0.0  0.0   0:06.66 events/0

                      6 root        10  -5     0    0    0 S  0.0  0.0   0:00.00 khelper

                     10 root        11  -5     0    0    0 S  0.0  0.0   0:29.51 kthread

                     14 root        10  -5     0    0    0 S  0.0  0.0   0:09.73 kblockd/0

                     15 root        20  -5     0    0    0 S  0.0  0.0   0:00.00 kacpid

                    174 root        20  -5     0    0    0 S  0.0  0.0   0:00.00 cqueue/0

                    177 root        20  -5     0    0    0 S  0.0  0.0   0:00.00 khubd

                    179 root        10  -5     0    0    0 S  0.0  0.0   0:00.00 kseriod

                    249 root        20  -5     0    0    0 S  0.0  0.0   0:00.00 aio/0

                   

                  If we notice in the highlighted parts above, the  I/O Wait time is 99%, the java process is taking 80.1%. Free memory is 5060k. With these statistics, can we conclude that this is an issue with hardware configuration and work towards solving them. I am a new for all these kinds of performance statistics on linux. Mine is a superficial conclusion based on what I saw on few links in the google. Are these parameters with the hardware are OK and nothing to do with slow start of the jboss?. If you guys have any background on the hardware statistics, Can you please let me know  whether I should again looking into the jboss or look into the harware part. Any help in this regard will be truly make my life easier

                    • Actions
                  • 6. Re: Jboss 5.1 AS taking unsually long time to boot
                    rhusar
                    rhusar Apr 27, 2011 8:58 AM (in response to raghuseeta)

                    So now its obvious what is happening. The swapping I/O wait is a problem. Look at your swap

                     

                    437628k used

                     

                    and swapping deamon:

                     

                      248 root          10  -5     0    0    0 S  0.3  0.0  20:43.49 kswapd0

                     

                    Looks like a lot of your heap is swapped in the swap. That is a blocker for reasonable operation.

                     

                    You should probably look at understanding the actual memory usage of JVM, I cant find the Sun article but there is something here, http://www.yourkit.com/docs/kb/sizes.jsp - note that the heap size -Xmx is only a part of it.

                      • Actions
                    • 7. Jboss 5.1 AS taking unsually long time to boot
                      peterj
                      peterj Apr 27, 2011 2:06 PM (in response to rhusar)

                      You wrote "with 4 GB RAM." yet I see:

                       

                      Mem:    381508k total,   376448k used,    5060k free

                       

                      This says you have only 380MB RAM, of which only 5MB is free. No wonder you are having issues! That amount of RAM is barely enough for the OS (unless you did a lot of trimming and tuning).

                       

                      Is JBoss AS running within a virtual machine? That would explain the memory discrepancy.

                        • Actions
                      • 8. Jboss 5.1 AS taking unsually long time to boot
                        raghuseeta
                        raghuseeta Apr 28, 2011 10:37 AM (in response to peterj)

                        Thanks Peter  and Husar

                         

                        @Peter , Its a silly thing. I ought to have checked that first. Since the machine was given to me my by admin. I took that for granted and even when I checked  since I did not look closely, I was not able to make out. Anyway thanks to have pointed out that and now JBOSS is staring properly with in 50 seconds !!!

                         

                        Now I am running into one more problem. I am able to access jboss from my localhost like wget http://localhost:8080 , But not able to do with IP from browser or locally . Like if try to acccess  http://<my ip> :8080 , I am not able to do either with browser or locally by wget http://<my ip>:8080. Any idea.

                         

                        I accept it is trivial and am asking more than what I should and i am also trying  by looking it in the net. I am the only one in my project who is into this right nw and no access to help. Please let me know if you have any idea on this

                         

                        @Huser, Thank you for your response an also let me know if you have any idea on the afore said problem

                          • Actions
                        • 9. Jboss 5.1 AS taking unsually long time to boot
                          peterj
                          peterj Apr 28, 2011 10:51 AM (in response to raghuseeta)

                          I am able to access jboss from my localhost like wget http://localhost:8080 , But not able to do with IP from browser or locally

                           

                          This should help: https://community.jboss.org/wiki/JBoss42FAQ

                            • Actions
                          • 10. Jboss 5.1 AS taking unsually long time to boot
                            raghuseeta
                            raghuseeta May 2, 2011 2:14 AM (in response to peterj)

                            Hi Peter

                             

                            Your inputs really got me out of the fix. Thanks a lot for your valuable inputs

                              • Actions
                            • 11. Jboss 5.1 AS taking unsually long time to boot
                              raghuseeta
                              raghuseeta May 3, 2011 10:26 AM (in response to raghuseeta)

                              Hi

                               

                              Continuting the same I have clustered two jboss appservers . I am getting following error when starting the second node at the end of startup  and first node is already running.

                               

                              Deployment "<UNKNOWN jboss.j2ee:ear=ear-BeyondBP-239732.ear,jar=abd-beyondbp.jar,name=SearchManagerImpl,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **, ** UNRESOLVED Demands 'jndi:ear-BeyondBP-239732/StatusManagerImpl/local-com.ness.search.StatusManager' **, ** UNRESOLVED Demands 'jndi:ear-BeyondBP-239732/ThrottlerImpl/remote-com.ness.throttle.Throttler' **

                                Deployment "<UNKNOWN jboss.j2ee:ear=ear-BeyondBP-239732.ear,jar=dean-beyondbp.jar,name=ThrottlerImpl,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **

                                Deployment "<UNKNOWN jboss.j2ee:ear=ear-BeyondBP-239732.ear,jar=scheduler-beyondbp.jar,name=SchedulerImpl,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ha:service=HASingletonDeployer,type=Barrier' **

                               

                              However when only one node is running , or when i stop the first node  and if i run in single server every thing seems to be work fine. I am not understanding why HASingletonDeployer  service is not getting deployed  in a clustered environment and only while starting the second node.

                              I have not coded the part using HASingletonDeployer  service and I have very little idea on the working of HASingletonDeployer  . I am just deploying the .ear. Please let me know if you have any idea on this

                                • Actions
                              • 12. Jboss 5.1 AS taking unsually long time to boot
                                wolfgangknauf
                                wolfgangknauf May 4, 2011 8:09 AM (in response to raghuseeta)

                                Hi,

                                 

                                here is another thread about the same error - hope that you find some useful information: http://community.jboss.org/thread/68768?tstart=0

                                 

                                Best regards

                                 

                                Wolfgang

                                  • Actions