11 Replies Latest reply on Nov 15, 2007 2:53 AM by sridharkumarch

    Deploying error with JBoss 4.x

    sridharkumarch
    sridharkumarch Nov 12, 2007 1:04 AM

      Hello,

      I'm trying to configure and deploy a project with JBoss (Jboss connection with Oracle datasource)


      so I get the following error.

      10:55:18,032 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
      State: CONFIGURED
      I Depend On:
      jboss.jca:service=DataSourceBinding,name=DefaultDS

      ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=Invoker
      jboss.web:service=WebServer

      ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
      State: CONFIGURED
      I Depend On:
      jboss:service=TransactionManager
      jboss.jca:service=DataSourceBinding,name=DefaultDS

      ObjectName: jboss.mq:service=StateManager
      State: CONFIGURED
      I Depend On:
      jboss.jca:service=DataSourceBinding,name=DefaultDS
      Depends On Me:
      jboss.mq:service=DestinationManager

      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=DefaultDS
      Depends On Me:
      jboss.mq:service=DestinationManager

      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
      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.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=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=DefaultDS
      State: NOTYETINSTALLED
      Depends On Me:
      jboss.ejb:service=EJBTimerService,persistencePolicy=database
      jboss:service=KeyGeneratorFactory,type=HiLo
      jboss.mq:service=StateManager
      jboss.mq:service=PersistenceManager




      Can any one help me...

      Regards
      Sridhar Kumar Chinchili

      • 2257 Views
      • Tags:
        • 1. Re: Deploying error with JBoss 4.x
          jaikiran
          jaikiran Nov 12, 2007 1:08 AM (in response to sridharkumarch)

           

          --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
          ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
          State: NOTYETINSTALLED


          How are you deploying your datasource? Did you do any changes to the hsqldb-ds.xml file which comes in JBoss distribution?


            • Actions
          • 2. Re: Deploying error with JBoss 4.x
            sridharkumarch
            sridharkumarch Nov 13, 2007 12:55 AM (in response to sridharkumarch)

            HI JaiKiran,

            I didnt modify hsqldb-ds.xml file. But still I m getting same problem.

              • Actions
            • 3. Re: Deploying error with JBoss 4.x
              jaikiran
              jaikiran Nov 13, 2007 1:29 AM (in response to sridharkumarch)

               

              I'm trying to configure and deploy a project with JBoss (Jboss connection with Oracle datasource)


              How are you doing that? Using a *-ds.xml file? Please provide more details as to what you have done so that we might be able to tell what's causing these exceptions.



                • Actions
              • 4. Re: Deploying error with JBoss 4.x
                sridharkumarch
                sridharkumarch Nov 13, 2007 6:47 AM (in response to sridharkumarch)

                Hi JaiKiran,


                I m using *.-ds.xml file. But I dont know why I m getting error.


                  • Actions
                • 5. Re: Deploying error with JBoss 4.x
                  jaikiran
                  jaikiran Nov 13, 2007 6:52 AM (in response to sridharkumarch)

                   

                  "sridharkumarch" wrote:

                  I m using *.-ds.xml file. But I dont know why I m getting error.


                  Post the contents of your ds.xml file here.

                  While posting, remember to wrap the contents of file in a code block, by using the Code button in the message editor window.

                    • Actions
                  • 6. Re: Deploying error with JBoss 4.x
                    jaikiran
                    jaikiran Nov 13, 2007 6:54 AM (in response to sridharkumarch)

                    Also, post the logs from server console, from the point when JBoss starts till the point where you see these exceptions

                      • Actions
                    • 7. Re: Deploying error with JBoss 4.x
                      sridharkumarch
                      sridharkumarch Nov 14, 2007 1:48 AM (in response to sridharkumarch)

                      HI JaiKiran,

                      These are the logs:

                      12:07:13,234 INFO [Server] Starting JBoss (MX MicroKernel)...
                      12:07:13,234 INFO [Server] Release ID: JBoss [Zion] 4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)
                      12:07:13,234 INFO [Server] Home Dir: C:\softwaredump\eclipse\jboss-4.0.2
                      12:07:13,234 INFO [Server] Home URL: file:/C:/softwaredump/eclipse/jboss-4.0.2/
                      12:07:13,234 INFO [Server] Library URL: file:/C:/softwaredump/eclipse/jboss-4.0.2/lib/
                      12:07:13,234 INFO [Server] Patch URL: null
                      12:07:13,234 INFO [Server] Server Name: default
                      12:07:13,234 INFO [Server] Server Home Dir: C:\softwaredump\eclipse\jboss-4.0.2\server\default
                      12:07:13,234 INFO [Server] Server Home URL: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/
                      12:07:13,250 INFO [Server] Server Data Dir: C:\softwaredump\eclipse\jboss-4.0.2\server\default\data
                      12:07:13,250 INFO [Server] Server Temp Dir: C:\softwaredump\eclipse\jboss-4.0.2\server\default\tmp
                      12:07:13,250 INFO [Server] Server Config URL: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/conf/
                      12:07:13,250 INFO [Server] Server Library URL: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/lib/
                      12:07:13,250 INFO [Server] Root Deployment Filename: jboss-service.xml
                      12:07:13,250 INFO [Server] Starting General Purpose Architecture (GPA)...
                      12:07:14,500 INFO [ServerInfo] Java version: 1.5.0_02,Sun Microsystems Inc.
                      12:07:14,500 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_02-b09,Sun Microsystems Inc.
                      12:07:14,500 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
                      12:07:17,359 INFO [Server] Core system initialized
                      12:07:20,750 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
                      12:07:20,859 INFO [WebService] Using RMI server codebase: http://GGN-01-F1-063:8083/
                      12:07:21,797 INFO [NamingService] Started jndi bootstrap jnpPort=1099, rmiPort=1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
                      12:07:26,437 INFO [Embedded] Catalina naming disabled
                      12:07:26,781 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
                      12:07:26,781 INFO [Catalina] Initialization processed in 297 ms
                      12:07:26,797 INFO [StandardService] Starting service jboss.web
                      12:07:26,797 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.9
                      12:07:26,828 INFO [StandardHost] XML validation disabled
                      12:07:26,859 INFO [Catalina] Server startup in 78 ms
                      12:07:27,109 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/http-invoker.sar/invoker.war/
                      12:07:27,375 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
                      12:07:27,875 INFO [TomcatDeployer] deploy, ctxPath=/ws4ee, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/tmp/deploy/tmp54221jboss-ws4ee-exp.war/
                      12:07:28,031 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jbossweb-tomcat55.sar/ROOT.war/
                      12:07:28,281 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
                      12:07:30,375 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/management/console-mgr.sar/web-console.war/
                      12:07:31,000 INFO [MailService] Mail Service bound to java:/Mail
                      12:07:31,719 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jboss-ha-local-jdbc.rar
                      12:07:31,844 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jboss-ha-xa-jdbc.rar
                      12:07:31,953 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jboss-local-jdbc.rar
                      12:07:32,078 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jboss-xa-jdbc.rar
                      12:07:32,234 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jms/jms-ra.rar
                      12:07:32,344 INFO [RARDeployment] Required license terms exist view the META-INF/ra.xml: file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/mail-ra.rar
                      12:07:32,640 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jdbc/ to JNDI name 'java:jdbc/'
                      12:07:33,578 INFO [WrapperDataSourceService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS to JNDI name 'java:DefaultDS'
                      12:07:34,000 INFO [ConnectionFactoryBindingService] Bound connection factory for resource adapter for ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA to JNDI name 'java:JmsXA'
                      12:09:17,812 INFO [TomcatDeployer] deploy, ctxPath=/art, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/tmp/deploy/tmp54268art-exp.war/
                      12:10:45,172 INFO [TomcatDeployer] deploy, ctxPath=/art, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/tmp/deploy/tmp54269arts-exp.war/
                      12:10:45,937 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C:/softwaredump/eclipse/jboss-4.0.2/server/default/deploy/jmx-console.war/
                      12:10:46,125 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: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.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
                      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.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=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


                      12:10:46,297 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
                      12:10:46,390 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
                      12:10:46,406 INFO [JkMain] Jk running ID=0 time=0/62 config=null
                      12:10:46,453 INFO [Server] JBoss (MX MicroKernel) [4.0.2 (build: CVSTag=JBoss_4_0_2 date=200505022023)] Started in 3m:33s:203ms

                        • Actions
                      • 8. Re: Deploying error with JBoss 4.x
                        jaikiran
                        jaikiran Nov 14, 2007 8:39 AM (in response to sridharkumarch)

                         

                        --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
                        ObjectName: jboss.jca:service=DataSourceBinding,name=OracleDS
                        State: NOTYETINSTALLED


                        Sridhar,

                        This error is different from what was posted in your first post. The earlier post contained exception which indicated that the DefaultDS datasource was not deployed yet. This new error shows that the OracleDS datasource is not deployed.

                        Can you tell us what changes you have done (or added any files) to the JBoss installation that you downloaded. That will help us in pointing you in right direction.


                          • Actions
                        • 9. Re: Deploying error with JBoss 4.x
                          sridharkumarch
                          sridharkumarch Nov 15, 2007 12:32 AM (in response to sridharkumarch)

                          JaiKiran,

                          I have just modified hsqldb-ds.xml file in deploy/ folder. After that

                          --- MBeans waiting for other MBeans ---
                          ObjectName: jboss.ejb:service=EJBTimerService,persistencePolicy=database
                          State: CONFIGURED
                          I Depend On:
                          jboss.jca:service=DataSourceBinding,name=DefaultDS


                          Error not showing.... Only its showing reamaning errors....

                            • Actions
                          • 10. Re: Deploying error with JBoss 4.x
                            jaikiran
                            jaikiran Nov 15, 2007 12:51 AM (in response to sridharkumarch)

                             

                            I have just modified hsqldb-ds.xml file in deploy/ folder


                            And what did you change in that file? Can you post the contents of that changed file(remember to wrap the contents in a code block by using the Code button in the message editor window, while posting)? By the way, why did you change that file? Are you trying to deploy your oracle datasource? If yes, then all you have to do is create a file name *-ds.xml (ex: oracle-ds.xml) with appropriate contents as mentioned at http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAOracleDatasource and place that file in the deploy folder.

                            Also, you might want to have a look at http://wiki.jboss.org/wiki/Wiki.jsp?page=ConfigDataSources

                              • Actions
                            • 11. Re: Deploying error with JBoss 4.x
                              sridharkumarch
                              sridharkumarch Nov 15, 2007 2:53 AM (in response to sridharkumarch)

                              Hi JaiKiran,


                              I am trying to deploy my Oracle datasource. I have just modified <jndi-name> attribute in that file. The content of my datasource file is:

                              <?xml version="1.0" encoding="UTF-8"?>


                              <local-tx-datasource>
                              <jndi-name>jdbc/</jndi-name>
                              <connection-url>jdbc:oracle:thin:@203.199.164.114:1521:VSNLDB</connection-url>
                              <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
                              <user-name>test</user-name>
                              test

                              <!-- The minimum connections in a pool/sub-pool.
                              Pools are lazily constructed on first use -->
                              <min-pool-size>1</min-pool-size>

                              <!-- The maximum connections in a pool/sub-pool -->
                              <max-pool-size>5</max-pool-size>
                              <idle-timeout-minutes>0</idle-timeout-minutes>

                              <!-- <track-statements/> -->
                              <!-- Checks the Oracle error codes and messages for fatal errors -->
                              <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
                              <!-- sql to call when connection is created
                              <new-connection-sql>some arbitrary sql</new-connection-sql>
                              -->

                              <!-- sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered
                              <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                              -->

                              <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->

                              <type-mapping>Oracle9i</type-mapping>


                              </local-tx-datasource>






                              and content of hsqldb-ds.xml is:::









                              <?xml version="1.0" encoding="UTF-8"?>

                              <!-- The Hypersonic embedded database JCA connection factory config
                              $Id: hsqldb-ds.xml,v 1.15 2004/09/15 14:37:40 loubyansky Exp $ -->



                              <local-tx-datasource>

                              <!-- The jndi name of the DataSource, it is prefixed with java:/ -->
                              <!-- Datasources are not available outside the virtual machine -->
                              <jndi-name>DefaultDS</jndi-name>

                              <!-- for tcp connection, allowing other processes to use the hsqldb
                              database. This requires the org.jboss.jdbc.HypersonicDatabase mbean.
                              <connection-url>jdbc:hsqldb:hsql://localhost:1701</connection-url>
                              -->
                              <!-- for totally in-memory db, not saved when jboss stops.
                              The org.jboss.jdbc.HypersonicDatabase mbean necessary
                              <connection-url>jdbc:hsqldb:.</connection-url>
                              -->
                              <!-- for in-process persistent db, saved when jboss stops. The
                              org.jboss.jdbc.HypersonicDatabase mbean is necessary for properly db shutdown
                              -->
                              <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}hypersonic${/}localDB</connection-url>

                              <!-- The driver class -->
                              <driver-class>org.hsqldb.jdbcDriver</driver-class>

                              <!-- The login and password -->
                              <user-name>sa</user-name>


                              <!--example of how to specify class that determines if exception means connection should be destroyed-->
                              <!--exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyExceptionSorter</exception-sorter-class-name-->

                              <!-- this will be run before a managed connection is removed from the pool for use by a client-->
                              <!--<check-valid-connection-sql>select * from something</check-valid-connection-sql> -->

                              <!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
                              <min-pool-size>5</min-pool-size>

                              <!-- The maximum connections in a pool/sub-pool -->
                              <max-pool-size>20</max-pool-size>

                              <!-- The time before an unused connection is destroyed -->
                              <!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
                              <!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
                              <idle-timeout-minutes>0</idle-timeout-minutes>

                              <!-- sql to call when connection is created
                              <new-connection-sql>some arbitrary sql</new-connection-sql>
                              -->

                              <!-- sql to call on an existing pooled connection when it is obtained from pool
                              <check-valid-connection-sql>some arbitrary sql</check-valid-connection-sql>
                              -->

                              <!-- example of how to specify a class that determines a connection is valid before it is handed out from the pool
                              <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.DummyValidConnectionChecker</valid-connection-checker-class-name>
                              -->

                              <!-- Whether to check all statements are closed when the connection is returned to the pool,
                              this is a debugging feature that should be turned off in production -->
                              <track-statements/>

                              <!-- Use the getConnection(user, pw) for logins
                              <application-managed-security/>
                              -->

                              <!-- Use the security domain defined in conf/login-config.xml -->
                              <security-domain>HsqlDbRealm</security-domain>

                              <!-- Use the security domain defined in conf/login-config.xml or the
                              getConnection(user, pw) for logins. The security domain takes precedence.
                              <security-domain-and-application>HsqlDbRealm</security-domain-and-application>
                              -->

                              <!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->

                              <type-mapping>Hypersonic SQL</type-mapping>


                              <!-- This mbean can be used when using in process persistent hypersonic -->
                              jboss:service=Hypersonic,database=localDB
                              </local-tx-datasource>

                              <!-- This mbean should be used only when using tcp connections. Uncomment
                              when the tcp based connection-url is used.

                              1701
                              true
                              default
                              false
                              true

                              -->

                              <!-- This mbean can be used when using in process persistent db -->

                              localDB
                              true






                              Please tell where I have did mistake??

                              Thanks and Regards,
                              Sridhar

                                • Actions