[JBoss-user] postgres driver failure ... could not create connection

[G.L. Grobe]

18:54:13,716 ERROR [DBaseFetchBean] getTasks: Could not create connection; - nested throwable: (Something unusual has occured to cause the driver to fail. Please report this exception: java.sql.SQLException: No Postgres username specified in startup packet.); - nested throwable: (org.jboss.resource.ResourceException: Could not create connection; - nested throwable: (Something unusual has occured to cause the driver to fail. Please report this exception: java.sql.SQLException: No Postgres username specified in startup packet.)) I'm moving my app from 2.4 into 3.0.1 and I see that the default postgres-service.xml file (below) has username and password commented out and says I must include a login module named PostgresDbRealm ... and from the errors above ... am I following that right? Anyone done this or know how this is supposed to go? btw - I did comment the application-policy section out, but same results.   --- 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">myuser</module-option>              <module-option name = "userName">myuser</module-option>              <module-option name = "password">mypass</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>