3 Replies Latest reply on Feb 17, 2011 3:34 PM by Nicklas Karlsson

    Datasource loading in jbossweb-standalone

    mmaley Newbie

      I apologize in advance if there is a totally obvious answer, but I've reached my limit on googling for a solution and I'm turning to the community for help.

       

      I'm trying to deploy a war under JBoss AS 6.0.  When I deploy it under default, it (finally) starts up and binds in all the environment variables from jboss-web.xml and mysite-service.xml, including all of the custom *-ds.xml datasource configuration files I've put into the deploy directory.

       

      Now, I'm trying to migrate this into the jbossweb-standalone (or minimal for that matter) configurations and I'm having trouble getting the datasources to be recognized.  I'm not sure if I've included all the necessary beans and configs, but it seems as though none of my *-ds.xml files are loading. My application fails to deploy stating that the java:jdbc/mydataDB should be installed, but is actually in state "NOT FOUND".

       

      I can paste all of my configs, etc. here if needed, but I'm primarily interested in what is responsible for processing and making available the *-ds.xml files and what beans are required to make this happen.  I started pursuing deploying jca, etc. but then I was well beyond a 'minimal' installation.  Maybe that was the right path and I got scared.

       

      Any suggestions before I post copious amounts of config files and text here?

        • 1. Datasource loading in jbossweb-standalone
          Nicklas Karlsson Master

          Attach the server log and the *-ds.xml file you threw in your deploy directory.

          • 2. Re: Datasource loading in jbossweb-standalone
            mmaley Newbie

            Thanks for responding Nicklas.  Here's is my server.log:

             

            {code}

            2011-02-17 14:35:18,672 ERROR [ProfileServiceBootstrap] (Thread-2) Failed to load profile:: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SE

            E PREVIOUS ERRORS FOR DETAILS):

             

             

            DEPLOYMENTS MISSING DEPENDENCIES:

              Deployment "jboss-switchboard:appName=starter,module=starter" is missing the following dependencies:

                Dependency "java:jdbc/starterRepository" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:jdbc/starterRepository' **")

                Dependency "java:jdbc/starterContentDB" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:jdbc/starterContentDB' **")

                Dependency "java:jdbc/starterControlDB" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:jdbc/starterControlDB' **")

                Dependency "java:jdbc/starterEventDB" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:jdbc/starterEventDB' **")

                Dependency "java:/Mail" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'java:/Mail' **")

              Deployment "jboss.web.deployment:war=/starter" is missing the following dependencies:

                Dependency "jboss-switchboard:appName=starter,module=starter" (should be in state "Installed", but is actually in state "Create")

             

             

            DEPLOYMENTS IN ERROR:

              Deployment "java:jdbc/starterControlDB" is in error due to the following reason(s): ** NOT FOUND Depends on 'java:jdbc/starterControlDB' **

              Deployment "java:jdbc/starterContentDB" is in error due to the following reason(s): ** NOT FOUND Depends on 'java:jdbc/starterContentDB' **

              Deployment "java:jdbc/starterEventDB" is in error due to the following reason(s): ** NOT FOUND Depends on 'java:jdbc/starterEventDB' **

              Deployment "java:jdbc/starterRepository" is in error due to the following reason(s): ** NOT FOUND Depends on 'java:jdbc/starterRepository' **

              Deployment "java:/Mail" is in error due to the following reason(s): ** NOT FOUND Depends on 'java:/Mail' **

             

             

                    at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]

                    at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]

                    at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]

                    at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]

                    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]

                    at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]

                    at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

                    at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

                    at java.lang.Thread.run(Thread.java:636) [:1.6.0_20]

             

             

            2011-02-17 14:35:18,692 INFO  [org.apache.coyote.http11.Http11Protocol] (Thread-2) Starting Coyote HTTP/1.1 on http-0.0.0.0-8080

            2011-02-17 14:35:18,698 INFO  [org.apache.coyote.ajp.AjpProtocol] (Thread-2) Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009

            2011-02-17 14:35:18,698 INFO  [org.jboss.bootstrap.impl.base.server.AbstractServer] (Thread-2) JBossAS [6.0.0.Final "Neo"] Started in 1m:6s:832ms

            {code}

             

             

            I have removed my other *-ds.xml files except for this one (called  mssql-contentDB-ds.xml).  I understand that all the other datasource bindings will fail, but I'd expect the Content mapping to be found.

             

             

            {code:xml}

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

             

            <datasources>

              <local-tx-datasource>

                <jndi-name>jdbc/starterContentDB</jndi-name>

                <connection-url>jdbc:jtds:sqlserver://10.1.1.10:1433/starter_content;sendStringParametersAsUnicode=false</connection-url>

                <driver-class>net.sourceforge.jtds.jdbc.Driver</driver-class>

                <user-name>myuser</user-name>

                <password>secretpassword</password>

             

             

                <!-- optional parameters -->

                <transaction-isolation>TRANSACTION_READ_UNCOMMITTED</transaction-isolation>

                <min-pool-size>4</min-pool-size>

                <max-pool-size>200</max-pool-size>

                <idle-timeout-minutes>15</idle-timeout-minutes>

                <blocking-timeout-millis>5000</blocking-timeout-millis>

                <new-connection-sql>select 1 from test</new-connection-sql>

                <check-valid-connection-sql>select 2 from test</check-valid-connection-sql>

                <set-tx-query-timeout></set-tx-query-timeout>

                <metadata>

                  <type-mapping>MS SQLSERVER2000</type-mapping>

                </metadata>

              </local-tx-datasource>

            </datasources>

             

            {code}

            • 3. Re: Datasource loading in jbossweb-standalone
              Nicklas Karlsson Master

              Attach the entire log, it speaks of "previous errors"