0 Replies Latest reply on Mar 9, 2004 7:20 AM by jj730105

    JBoss hangs at startup at boss:service=XidFactory

    jj730105

      I am having a problem starting JBoss. It works well on my Windows and OSX installations. However, I am attempting to start it in the following environment:

      RedHat Linux 7.2
      JAVA_HOME: /usr/java/j2sdk1.4.2_03
      JBoss: 3.2.3
      User: NOT root, but the user is the owner of the JBoss install directories

      Server seems to hang when I run the run.sh. I am only copying the tail end of the log file because it is very, very large:

      13:27:15,533 DEBUG [ServiceCreator] About to create bean: jboss:service=WebService with code: org.jboss.web.WebService
      13:27:15,566 DEBUG [ServiceCreator] Created bean: jboss:service=WebService
      13:27:15,566 DEBUG [ServiceConfigurator] Port set to 8083 in jboss:service=WebService
      13:27:15,566 DEBUG [ServiceConfigurator] DownloadServerClasses set to true in jboss:service=WebService
      13:27:15,567 DEBUG [ServiceConfigurator] Host set to 0.0.0.0 in jboss:service=WebService
      13:27:15,568 DEBUG [ServiceConfigurator] BindAddress set to 0.0.0.0 in jboss:service=WebService
      13:27:15,568 DEBUG [ServiceCreator] About to create bean: jboss:service=Naming with code: org.jboss.naming.NamingService
      13:27:15,592 DEBUG [ServiceCreator] Created bean: jboss:service=Naming
      13:27:15,592 DEBUG [ServiceConfigurator] Port set to 1099 in jboss:service=Naming
      13:27:15,593 DEBUG [ServiceConfigurator] BindAddress set to 0.0.0.0 in jboss:service=Naming
      13:27:15,593 DEBUG [ServiceConfigurator] RmiPort set to 1098 in jboss:service=Naming
      13:27:15,595 DEBUG [ServiceConfigurator] RmiBindAddress set to 0.0.0.0 in jboss:service=Naming
      13:27:15,596 DEBUG [ServiceCreator] About to create xmbean object: jboss:service=JNDIView with code: org.jboss.naming.JNDIView with descriptor: resource:xmdesc/JNDIView-xmbean.xml
      13:27:15,890 DEBUG [ModelMBeanInvoker] No persistence-manager descriptor found, null persistence will be used
      13:27:15,891 DEBUG [ServiceCreator] Created bean: jboss:service=JNDIView
      13:27:15,891 DEBUG [ServiceCreator] About to create bean: jboss.security:service=SecurityConfig with code: org.jboss.security.plugins.SecurityConfig
      13:27:15,899 DEBUG [ServiceCreator] Created bean: jboss.security:service=SecurityConfig
      13:27:15,900 DEBUG [ServiceConfigurator] LoginConfig set to jboss.security:service=XMLLoginConfig in jboss.security:service=SecurityConfig
      13:27:15,901 DEBUG [ServiceCreator] About to create bean: jboss.security:service=XMLLoginConfig with code: org.jboss.security.auth.login.XMLLoginConfig
      13:27:15,920 DEBUG [ServiceCreator] Created bean: jboss.security:service=XMLLoginConfig
      13:27:15,920 DEBUG [ServiceConfigurator] ConfigResource set to login-config.xml in jboss.security:service=XMLLoginConfig
      13:27:15,922 DEBUG [ServiceCreator] About to create bean: jboss.security:service=JaasSecurityManager with code: org.jboss.security.plugins.JaasSecurityManagerService
      13:27:15,962 DEBUG [ServiceCreator] Created bean: jboss.security:service=JaasSecurityManager
      13:27:15,962 DEBUG [ServiceConfigurator] SecurityManagerClassName set to org.jboss.security.plugins.JaasSecurityManager in jboss.security:service=JaasSecurityManager
      13:27:15,968 DEBUG [ServiceCreator] About to create bean: jboss:service=XidFactory with code: org.jboss.tm.XidFactor

      ***** This is the point at which the server stops starting up.

      I have noticed a script that is in the bin directory that seems specific to RedHat (and, that you need to run it as root, and JBoss needs to be in a specific directory, etc.), but I'm hoping that I don't have to run that to make everything work on my RedHat installation.

      Can anyone help with any ideas as to why this hangup might be occurring? I am hoping it is not the case that I have to run JBoss as root (and, from what I have read you do not have to). If there is any more information that I can provide that would be useful, please let me know.

      Thanks, in advance.