8 Replies Latest reply on Feb 20, 2008 12:30 PM by T T

    error when start/run Jboss App Server 4.2.2

    T T Newbie

      Hi, I hope to ask for help. I cannot successfully start the Jboss App Server 4.2.2 without error. Error I have is below. Please help. Thank you.


      
      ...
      ...
      ...
      
      log4j:WARN Continuable parsing error 313 and column 11
      log4j:WARN The content of element type "root" must match "(param*,(priority|level)?,appender-ref*)".
      16:47:23,112 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
      
      
      ...
      ... other objects in between here are of state: CONFIGURED, so no problem in this area...
      ....
      
      ...
      
      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.jca:service=DataSourceBinding,name=OracleDS
       State: NOTYETINSTALLED
       Depends On Me:
       jboss.mq:service=PersistenceManager
      
      
      
      
      
      
      


        • 1. Re: error when start/run Jboss App Server 4.2.2
          Peter Johnson Master

          Please post the complete error message. (The console log usually is not that long, unless there are stack traces, so you could post the whole log)

          Also post the contents of the *-ds.xml file that defines OracleDS.

          • 2. Re: error when start/run Jboss App Server 4.2.2
            T T Newbie

            PeterJ,

            here is the error for starting the Jboss AS. Hopefully error msg not too long to post. Thanks.

            Taicode

            09:09:23,611 INFO [Server] Starting JBoss (MX MicroKernel)...
            09:09:23,611 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
            09:09:23,611 INFO [Server] Home Dir: C:\jboss-4.2.2.GA
            09:09:23,611 INFO [Server] Home URL: file:/C:/jboss-4.2.2.GA/
            09:09:23,627 INFO [Server] Patch URL: null
            09:09:23,627 INFO [Server] Server Name: default
            09:09:23,627 INFO [Server] Server Home Dir: C:\jboss-4.2.2.GA\server\default
            09:09:23,627 INFO [Server] Server Home URL: file:/C:/jboss-4.2.2.GA/server/default/
            09:09:23,627 INFO [Server] Server Log Dir: C:\jboss-4.2.2.GA\server\default\log
            09:09:23,627 INFO [Server] Server Temp Dir: C:\jboss-4.2.2.GA\server\default\tmp
            09:09:23,627 INFO [Server] Root Deployment Filename: jboss-service.xml
            09:09:24,096 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
            09:09:24,096 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_11-b03,Sun Microsystems Inc.
            09:09:24,096 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
            09:09:24,487 INFO [Server] Core system initialized
            09:09:27,240 INFO [ServiceBindingManager] Initializing store
            09:09:27,240 INFO [ServiceBindingManager] Using StoreURL: file:/C:/jboss-4.2.2.GA/docs/examples/binding-manager/sample-bindings.xml
            09:09:28,100 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8183/
            09:09:28,100 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
            log4j:WARN Continuable parsing error 313 and column 11
            log4j:WARN The content of element type "root" must match "(param*,(priority|level)?,appender-ref*)".
            09:09:49,373 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
            
            --- MBeans waiting for other MBeans ---
            ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=Invoker
             jboss.web:service=WebServer
            
            ObjectName: jboss.mq.destination:service=Topic,name=testTopic
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
             jboss.mq:service=SecurityManager
            
            ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
             jboss.mq:service=SecurityManager
            
            ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
             jboss.mq:service=SecurityManager
            
            ObjectName: jboss.mq.destination:service=Queue,name=testQueue
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
             jboss.mq:service=SecurityManager
            
            ObjectName: jboss.mq.destination:service=Queue,name=A
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
            
            ObjectName: jboss.mq.destination:service=Queue,name=B
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
            
            ObjectName: jboss.mq.destination:service=Queue,name=C
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
            
            ObjectName: jboss.mq.destination:service=Queue,name=D
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
            
            ObjectName: jboss.mq.destination:service=Queue,name=ex
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
            
            ObjectName: jboss.mq:service=Invoker
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=TracingInterceptor
             jboss:service=Naming
             Depends On Me:
             jboss.mq:service=InvocationLayer,type=HTTP
             jboss.mq:service=InvocationLayer,type=JVM
             jboss.mq:service=InvocationLayer,type=UIL2
            
            ObjectName: jboss.mq:service=TracingInterceptor
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=SecurityManager
             Depends On Me:
             jboss.mq:service=Invoker
            
            ObjectName: jboss.mq:service=SecurityManager
             State: CONFIGURED
             I Depend On:
             jboss.security:service=JaasSecurityManager
             jboss.mq:service=DestinationManager
             Depends On Me:
             jboss.mq.destination:service=Topic,name=testTopic
             jboss.mq.destination:service=Topic,name=securedTopic
             jboss.mq.destination:service=Topic,name=testDurableTopic
             jboss.mq.destination:service=Queue,name=testQueue
             jboss.mq:service=TracingInterceptor
             jboss.mq.destination:service=Queue,name=DLQ
            
            ObjectName: jboss.mq.destination:service=Queue,name=DLQ
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=DestinationManager
             jboss.mq:service=SecurityManager
            
            ObjectName: jboss.mq:service=InvocationLayer,type=JVM
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=Invoker
            
            ObjectName: jboss.mq:service=DestinationManager
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=MessageCache
             jboss.mq:service=PersistenceManager
             jboss.mq:service=StateManager
             Depends On Me:
             jboss.mq.destination:service=Topic,name=testTopic
             jboss.mq.destination:service=Topic,name=securedTopic
             jboss.mq.destination:service=Topic,name=testDurableTopic
             jboss.mq.destination:service=Queue,name=testQueue
             jboss.mq.destination:service=Queue,name=A
             jboss.mq.destination:service=Queue,name=B
             jboss.mq.destination:service=Queue,name=C
             jboss.mq.destination:service=Queue,name=D
             jboss.mq.destination:service=Queue,name=ex
             jboss.mq:service=SecurityManager
             jboss.mq.destination:service=Queue,name=DLQ
            
            ObjectName: jboss.mq:service=PersistenceManager
             State: CONFIGURED
             I Depend On:
             jboss.jca:service=DataSourceBinding,name=OracleDS
             Depends On Me:
             jboss.mq:service=DestinationManager
            
            ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
             State: CONFIGURED
             I Depend On:
             jboss.mq:service=Invoker
            
            --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
            ObjectName: jboss.jca:service=DataSourceBinding,name=OracleDS
             State: NOTYETINSTALLED
             Depends On Me:
             jboss.mq:service=PersistenceManager
            
            
            




            • 3. Re: error when start/run Jboss App Server 4.2.2
              T T Newbie

              PeterJ,

              and here is the default-ds.xml file content.

              <?xml version="1.0" encoding="UTF-8"?>
              <datasources>
               <local-tx-datasource>
               <jndi-name>DefaultDS</jndi-name>
               <connection-url>jdbc:oracle:thin:@
               (DESCRIPTION =
               (ADDRESS = (PROTOCOL = TCP)(HOST = cdctu002)(PORT = 1521))
               (CONNECT_DATA =
               (SERVER = DEDICATED)
               (SERVICE_NAME = XE)
               )
               )
               </connection-url>
              
               <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
               <user-name>dashboard</user-name>
               <password>dashboard</password>
               <min-pool-size>5</min-pool-size>
               <max-pool-size>200</max-pool-size>
               <idle-timeout-minutes>0</idle-timeout-minutes>
               <track-statements/>
               <check-valid-connection-sql>select 1 from dual</check-valid-connection-sql>
               <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
               <metadata>
               <type-mapping>Oracle9i</type-mapping>
               </metadata>
               </local-tx-datasource>
              </datasources>
              
              
              


              • 4. Re: error when start/run Jboss App Server 4.2.2
                Peter Johnson Master

                 

                log4j:WARN The content of element type "root" must match "(param*,(priority|level)?,appender-ref*)"


                It looks like you made some change in the jboss-log4j.xml file and the change is incorrect. This change is possibly preventing the rest of the console log output from being displayed (or did you change the Threshold setting for the console log?)

                Your default-ds.xml file uses the jndi-name DefaultDS. There is already a DefaultDS declare in the file hsqldb-ds.xml. Two data sources cannot have the same jndi name. Or did you remove hsqldb-ds.xml?

                Let me point out that it is impossible for anyone to help you if you do not say what kind of changes you have made, and apparently you have made several changes yet have not made any statement other than "I cannot successfully start the Jboss App Server 4.2.2 without error".

                • 5. Re: error when start/run Jboss App Server 4.2.2
                  Paradiso Noir Newbie

                  I had such a problem once but mine was when I just upgraded to this versions, and jar files for jboss messaging were not set properly in my CLASSPATH.

                  • 6. Re: error when start/run Jboss App Server 4.2.2
                    T T Newbie

                    PeterJ,

                    Thanks for the suggestion. I will look into those files to get familiar with them.

                    I didn't change anything or delete any file in Jboss. I wouldn't change anything unless I know about it or what it does, and I know nothing about Jboss. I'm very new to Jboss.

                    Should I try to reinstall Jboss to be sure? Other than that, I will continue to study Jboss to get better understand. Thanks.

                    Taicode

                    • 7. Re: error when start/run Jboss App Server 4.2.2
                      Peter Johnson Master

                      Yes, I suggest that you reinstall and run JBossAS before making any changes. Do not put your default-ds.xml file in the deploy directory until you are satisfied that JBossAS starts successfully.

                      • 8. Re: error when start/run Jboss App Server 4.2.2
                        T T Newbie

                        PeterJ,

                        Thanks. I re-install and start the Jboss AS, successfully started without error. I'm still not sure why the previous installation didn't work. Thank you.

                        Taicode