I'm having a few problems w/ my 3.0.1 postgres setup. I've included the error message (which I don't really understand) below along w/ the postgres-service.xml and postgres-ds.xml files below that ... (it just seemed to complain about the postgres-ds.xml) ...
 
Any help much appreciated.
 
----output
 
00:14:16,873 INFO  [MainDeployer] Deployment of package: file:/u/public/jboss/jboss-3.0.1/server/default/deploy/postgres-ds.xml is waiting for an appropriate deployer.
00:14:16,893 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@385a8857 { url=file:/u/public/jboss/jboss-3.0.1/server/default/deploy/postgres-ds.xml }
  deployer: null
  status: null
  state: INIT_WAITING_DEPLOYER
  watch: file:/u/public/jboss/jboss-3.0.1/server/default/deploy/postgres-ds.xml
  lastDeployed: 1028952856872
  lastModified: 1028952856000
  mbeans:
]Incompletely deployed packages:
 
---------------------- postgres-ds.xml -----------------------
<?xml version="1.0" encoding="UTF-8"?>
 
<!-- ====================================================================== -->
<!--                                                                        -->
<!-- JBoss Server Configuration                                             -->
<!--                                                                        -->
<!-- ====================================================================== -->
 
<!-- ====================================================================== -->
<!--                                                                        -->
<!-- Datasource config for Postgres                                         -->
<!--                                                                        -->
<!-- ====================================================================== -->
 
<datasources>
 
<!- acais on the connection-url line is the context name of my web-app, not sure if that goes there -->
 
   <local-tx-datasource>
      <jndi-name>PostgresDS</jndi-name>
      <connection-url>jdbc:postgresql://localhost:5432/acais</connection-url>
      <driver-class>org.postgresql.Driver</driver-class>
      <user-name>user</user-name>
      <password>pass</password>
   </local-tx-datasource>
 
</datasources>
 

---------------------- postgres-service.xml -----------------------
 
<?xml version="1.0" encoding="UTF-8"?>
 
  <!-- ======================================================================================== -->
  <!-- New ConnectionManager setup for default PostgreSQL dbs                                   -->
  <!-- Build jmx-api (build/build.sh all) and view for config documentation                     -->
  <!-- To avoid class not found headaches, copy your postgres driver to the jboss lib directory -->
  <!-- ======================================================================================== -->
 
<server>
 
  <mbean code="org.jboss.resource.connectionmanager.LocalTxConnectionManager" name="jboss.jca:service=LocalTxCM,name=PostgresDS">
    <!-- ======================================================= -->
    <!-- You must include a login module configuration named PostgresDbRealm
         in your login-conf.xml, here is an example for a
         ConfiguredIdentityLoginModule:
 
    <application-policy name = "PostgresDbRealm">
       <authentication>
          <login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" flag = "required">
             <module-option name = "principal">user</module-option>
             <module-option name = "userName">user</module-option>
             <module-option name = "password">pass</module-option>
             <module-option name = "managedConnectionFactoryName">jboss.jca:service=LocalTxCM,name=PostgresDS</module-option>
          </login-module>
       </authentication>
    </application-policy>
 
    NOTE: the application-policy name attribute must match SecurityDomainJndiName, and the
      module-option name = "managedConnectionFactoryName"
    must match the object name of the ConnectionManager you are configuring here.
    -->
    <!-- ===================================================================== -->
    <!--uncomment out this line if you are using the PostgresDbRealm above
    <attribute name="SecurityDomainJndiName">PostgresDbRealm</attribute>
    -->
 
    <depends optional-attribute-name="ManagedConnectionFactoryName">
      <!--embedded mbean-->
      <mbean code="org.jboss.resource.connectionmanager.RARDeployment" name="jboss.jca:service=LocalTxDS,name=PostgresDS">
<!-- ========== Set the JndiName ======================= -->
        <attribute name="JndiName">PostgresDS</attribute>
        <attribute name="ManagedConnectionFactoryProperties">
          <properties>
            <config-property name="ConnectionURL" type="java.lang.String">jdbc:postgresql://localhost:5432/acais</config-property>
            <config-property name="DriverClass" type="java.lang.String">org.postgresql.Driver</config-property>
            <!--set these only if you want only default logins, not through JAAS -->
            <config-property name="UserName" type="java.lang.String"></config-property>
            <config-property name="Password" type="java.lang.String"></config-property>
          </properties>
 
        </attribute>
 
<!--Below here are advanced properties -->
        <!--hack-->
        <depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper</depends>
 
        <!--real attributes-->
      </mbean>
    </depends>
 
    <depends optional-attribute-name="ManagedConnectionPool">
      <!--embedded mbean-->
      <mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" name="jboss.jca:service=LocalTxPool,name=PostgresDS">

        <attribute name="MinSize">0</attribute>
        <attribute name="MaxSize">50</attribute>
        <attribute name="BlockingTimeoutMillis">5000</attribute>
        <attribute name="IdleTimeoutMinutes">15</attribute>
        <!--criteria indicates if Subject (from security domain) or app supplied
            parameters (such as from getConnection(user, pw)) are used to distinguish
            connections in the pool. Choices are
            ByContainerAndApplication (use both),
            ByContainer (use Subject),
            ByApplication (use app supplied params only),
            ByNothing (all connections are equivalent, usually if adapter supports
              reauthentication)-->
        <attribute name="Criteria">ByContainer</attribute>
      </mbean>
 
    </depends>
    <depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager</depends>
 
    <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
 
    <attribute name="TransactionManager">java:/TransactionManager</attribute>
    <!--make the rar deploy! hack till better deployment-->
    <depends>jboss.jca:service=RARDeployer</depends>
  </mbean>
</server>

Reply via email to