3 Replies Latest reply on Nov 15, 2011 5:16 AM by gaanbd

    Problems to start JBoss 5.1.0 GA

    gaanbd

      Hi All,

       

      Our team had decided to Migrate from Jboss 3.X(which used JDK 1.3) to Higher Version, so we have decided to Go with Jboss 5.1.0 GA(JDK 1.6).

       

      Using Ant we could build the .ear file but when i started the server i get Exception as below:

       

      My ejb.jar.xml Header was changed as given below :

       

      <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejbjar_2_0.dtd">

       

      Please suggest your valuable findings 

       

      Exception :

       

       

      15:39:44,642 INFO [ServerImpl] Starting JBoss (Microcontainer)...

      15:39:44,642 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)

      15:39:44,642 INFO [ServerImpl] Bootstrap URL: null

      15:39:44,642 INFO [ServerImpl] Home Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA

      15:39:44,642 INFO [ServerImpl] Home URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/

      15:39:44,642 INFO [ServerImpl] Library URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/lib/

      15:39:44,642 INFO [ServerImpl] Patch URL: null

      15:39:44,642 INFO [ServerImpl] Common Base URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/common/

      15:39:44,642 INFO [ServerImpl] Common Library URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/common/lib/

      15:39:44,642 INFO [ServerImpl] Server Name: default

      15:39:44,642 INFO [ServerImpl] Server Base Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server

      15:39:44,642 INFO [ServerImpl] Server Base URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/server/

      15:39:44,642 INFO [ServerImpl] Server Config URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/server/default/conf/

      15:39:44,642 INFO [ServerImpl] Server Home Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default

      15:39:44,642 INFO [ServerImpl] Server Home URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/server/default/

      15:39:44,642 INFO [ServerImpl] Server Data Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default\data

      15:39:44,642 INFO [ServerImpl] Server Library URL: file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/server/default/lib/

      15:39:44,642 INFO [ServerImpl] Server Log Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default\log

      15:39:44,642 INFO [ServerImpl] Server Native Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default\tmp\native

      15:39:44,642 INFO [ServerImpl] Server Temp Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default\tmp

      15:39:44,642 INFO [ServerImpl] Server Temp Deploy Dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default\tmp\deploy

      15:39:44,986 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/server/default/conf/bootstrap.xml

      15:39:45,267 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]

      15:39:45,267 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]

      15:39:45,423 INFO [CopyMechanism] VFS temp dir: C:\Documents and Settings\E3003319\Desktop\JBoss\jboss-5.1.0.GA\server\default\tmp

      15:39:45,423 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.

      15:39:45,923 INFO [ServerInfo] Java version: 1.6.0_04,Sun Microsystems Inc.

      15:39:45,923 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_04-b12)

      15:39:45,923 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b19,Sun Microsystems Inc.

      15:39:45,923 INFO [ServerInfo] OS-System: Windows XP 5.1,x86

      15:39:45,923 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dfile.encoding=Cp1252

      15:39:45,939 INFO [JMXKernel] Legacy JMX core initialized

      15:39:46,798 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@1afe460[domain=default, server=default, name=default]

      15:39:47,689 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/

      15:39:50,861 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core

      15:39:50,861 INFO [NativeServerConfig] 3.1.2.GA

      15:39:51,204 INFO [AttributeCallbackItem] Owner callback not implemented.

      15:39:52,017 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@51e67c[ defaultDomain='jboss' ]

      15:39:57,517 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/C:/Documents%20and%20Settings/E3003319/Desktop/JBoss/jboss-5.1.0.GA/server/default/deploy/WebCSR.ear/ state=Not Installed mode=Manual requiredState=Parse

       

      org.jboss.deployers.spi.DeploymentException

       

       

       

        • 1. Re: Problems to start JBoss 5.1.0 GA
          muzzajboss

          Hi,

          Please check ur bootstrap.xml files and jboss-sevice.xml files whether the url and codebase mentioned properly in that.

          • 2. Re: Problems to start JBoss 5.1.0 GA
            wdfink

            I would recommend that you start a the JBoss as is without your application to see it works correct and than hot-deploy your app.

            If you use datasources and additional configuration you should also deploy this step by step to show clear what is the (next) problem.

             

            Remember that JBoss5 support EJB1.x but is more restrictive regarding XML validation.

            • 3. Re: Problems to start JBoss 5.1.0 GA
              gaanbd

              Mohammed,

               

              I have not changed any of these files, if you encounter any thing has to be changed please suggest.

               

              bootstrap.xml

               

              <?xml version="1.0" encoding="UTF-8"?>
              <!--
                 The list of URLs for mc beans to load during bootstrap.
                 $Id: bootstrap.xml 88109 2009-05-01 20:10:48Z bstansberry@jboss.com $
              -->
              <bootstrap xmlns="urn:jboss:bootstrap:1.0">

                 <url>bootstrap/logging.xml</url>
                 <url>bootstrap/vfs.xml</url>
                 <url>bootstrap/classloader.xml</url>
                 <url>bootstrap/aop.xml</url>
                 <url>bootstrap/jmx.xml</url>
                 <url>bootstrap/deployers.xml</url>
                 <url>bootstrap/profile.xml</url>

              </bootstrap>

               

               

              jboss-sevice.xml


              <?xml version="1.0" encoding="UTF-8"?>
              <!DOCTYPE server>
              <!-- $Id: jboss-service.xml 76997 2008-08-12 22:29:19Z bstansberry@jboss.com $ -->

              <server>

                <!-- The HTTP invoker service configration
                -->
                <mbean code="org.jboss.invocation.http.server.HttpInvoker"
                  name="jboss:service=invoker,type=http">
                   <!-- Use a URL of the form http://<hostname>:8080/invoker/EJBInvokerServlet
                    where <hostname> is InetAddress.getHostname value on which the server
                    is running.
                    -->
                   <attribute name="InvokerURLPrefix">http://</attribute>
                   <attribute name="InvokerURLSuffix">
                      <!-- To get value, ask the ServiceBindingManager to do a string
                           replacement operation using the HTTP connector port -->
                      <value-factory bean="ServiceBindingManager" method="getStringBinding">
                         <parameter>jboss.web:service=WebServer</parameter>
                         <parameter>:${port}/invoker/EJBInvokerServlet</parameter>
                      </value-factory>
                   </attribute>
                   <attribute name="UseHostName">true</attribute>
                </mbean>

                 <!-- Expose the Naming service interface via HTTP -->
                 <mbean code="org.jboss.invocation.http.server.HttpProxyFactory"
                    name="jboss:service=invoker,type=http,target=Naming">
                    <!-- The Naming service we are proxying -->
                    <attribute name="InvokerName">jboss:service=Naming</attribute>
                    <!-- Compose the invoker URL from the cluster node address -->
                    <attribute name="InvokerURLPrefix">http://</attribute>
                    <attribute name="InvokerURLSuffix">
                      <!-- To get value, ask the ServiceBindingManager to do a string
                           replacement operation using the HTTP connector port -->
                      <value-factory bean="ServiceBindingManager" method="getStringBinding">
                         <parameter>jboss.web:service=WebServer</parameter>
                         <parameter>:${port}/invoker/JMXInvokerServlet</parameter>
                      </value-factory>
                    </attribute>
                    <attribute name="UseHostName">true</attribute>
                    <attribute name="ExportedInterface">org.jnp.interfaces.Naming</attribute>
                    <attribute name="JndiName"></attribute>
                    <attribute name="ClientInterceptors">
                        <interceptors>
                           <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
                           <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
                           <interceptor>org.jboss.naming.interceptors.ExceptionInterceptor</interceptor>
                           <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
                        </interceptors>
                    </attribute>
                 </mbean>

                 <!-- Expose the Naming service interface via clustered HTTP. This maps
                 to the ReadOnlyJNDIFactory servlet URL
                 -->
                 <mbean code="org.jboss.invocation.http.server.HttpProxyFactory"
                    name="jboss:service=invoker,type=http,target=Naming,readonly=true">
                    <attribute name="InvokerName">jboss:service=Naming</attribute>
                    <attribute name="InvokerURLPrefix">http://</attribute>
                    <attribute name="InvokerURLSuffix">
                      <!-- To get value, ask the ServiceBindingManager to do a string
                           replacement operation using the HTTP connector port -->
                      <value-factory bean="ServiceBindingManager" method="getStringBinding">
                         <parameter>jboss.web:service=WebServer</parameter>
                         <parameter>:${port}/invoker/readonly/JMXInvokerServlet</parameter>
                      </value-factory>
                    </attribute>
                    <attribute name="UseHostName">true</attribute>
                    <attribute name="ExportedInterface">org.jnp.interfaces.Naming</attribute>
                    <attribute name="JndiName"></attribute>
                    <attribute name="ClientInterceptors">
                        <interceptors>
                           <interceptor>org.jboss.proxy.ClientMethodInterceptor</interceptor>
                           <interceptor>org.jboss.proxy.SecurityInterceptor</interceptor>
                           <interceptor>org.jboss.naming.interceptors.ExceptionInterceptor</interceptor>
                           <interceptor>org.jboss.invocation.InvokerInterceptor</interceptor>
                        </interceptors>
                    </attribute>
                 </mbean>
              </server>