Re: [JBoss-user] 3.0.1 and PostgresDS

2002-08-10 Thread David Jencks 

I can't figure out which part you want me to look at.  I'm saying, remove
all *-ds.xml files from a jboss Branch_3_0 version, they cannot be
deployed. *-ds.xml files work only in 3.2 and 4 (head)

david jencks

On 2002.08.10 01:52:59 -0400 G.L. Grobe wrote:
 Not sure I understood this reply. What's happening is that 3.0.1 is
 hanging
 at this point. I've placed the last lines of the output at the end of
 this
 reply where it hangs.
 
 - Original Message -
 From: David Jencks [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Saturday, August 10, 2002 12:09 AM
 Subject: Re: [JBoss-user] 3.0.1 and PostgresDS
 
 
  Believe the deployer: null part.  *-ds.xml files are only for 3.2 and
  later.
 
  david jencks
 
  On 2002.08.09 23:47:10 -0400 G.L. Grobe wrote:
   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-namePostgresDS/jndi-name
  
 connection-urljdbc:postgresql://localhost:5432/acais/connection-url
 driver-classorg.postgresql.Driver/driver-class
 user-nameuser/user-name
 passwordpass/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 = principaluser/module-option
module-option name = userNameuser/module-option
module-option name = passwordpass/module-option
module-option name =
 managedConnectionFactoryNamejboss.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

Re: [JBoss-user] 3.0.1 and PostgresDS hangs

2002-08-10 Thread G.L. Grobe 

 I can't figure out which part you want me to look at.  I'm saying, remove
 all *-ds.xml files from a jboss Branch_3_0 version, they cannot be
 deployed. *-ds.xml files work only in 3.2 and 4 (head)


Well, I removed *-ds.xml files and jboss still hangs on startup  (though not
as many error messages). Here's about the last page of output before it
hangs ...

--- 3.0.1 output ---

15:29:24,643 INFO  [jbossweb] successfully deployed
file:/u/public/jboss/jboss-3.0.1/server/default/tmp/deploy/server/default/de
ploy/acais_mgr-0.30b.ear/62.acais_mgr-0.30b.ear-contents/acais-web.war to
/acais
15:29:24,647 INFO  [MainDeployer] Deployed package:
file:/u/public/jboss/jboss-3.0.1/server/default/deploy/acais_mgr-0.30b.ear
15:29:24,665 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean
operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
  none
Incompletely deployed packages:
  none
MBeans waiting for classes:
  none
MBeans waiting for other MBeans:
[ObjectName: jboss.system:type=Log4jService,service=Logging
 state: FAILED
 I Depend On:
 Depends On Me: org.jboss.deployment.DeploymentException: No property editor
for attribute: ConfigurationURL; type=class java.net.URL]
15:29:24,701 INFO  [URLDeploymentScanner] Started
15:29:24,703 INFO  [MainDeployer] Deployed package:
file:/u/public/jboss/jboss-3.0.1/server/default/conf/jboss-service.xml
15:29:24,708 ERROR [Server] start failed
Incomplete Deployment listing:
Packages waiting for a deployer:
  none
Incompletely deployed packages:
  none
MBeans waiting for classes:
  none
MBeans waiting for other MBeans:
[ObjectName: jboss.system:type=Log4jService,service=Logging
 state: FAILED

 I Depend On:
 Depends On Me: org.jboss.deployment.DeploymentException: No property editor
for attribute: ConfigurationURL; type=class java.net.URL]
at
org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.ja
va:1095)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:484)
Incomplete Deployment listing:
Packages waiting for a deployer:
  none
Incompletely deployed packages:
  none
MBeans waiting for classes:
  none
MBeans waiting for other MBeans:
[ObjectName: jboss.system:type=Log4jService,service=Logging
 state: FAILED
 I Depend On:
 Depends On Me: org.jboss.deployment.DeploymentException: No property editor
for attribute: ConfigurationURL; type=class java.net.URL]
at
org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.ja
va:1095)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
at java.lang.reflect.Method.invoke(Native Method)
at
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
cher.java:284)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:142)
at org.jboss.Main$1.run(Main.java:375)
at java.lang.Thread.run(Thread.java:484)




---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Re: [JBoss-user] 3.0.1 and PostgresDS hangs

2002-08-10 Thread G.L. Grobe 

I was running 1.3.0 and going to 1.3.1-04 fixed it. Big thanks.

- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, August 10, 2002 4:14 PM
Subject: Re: [JBoss-user] 3.0.1 and PostgresDS hangs


 Slowly... one problem at a time...

 I haven't experienced this myself but several forum posts indicate this is
 due to using jdk 1.3.0 rather than 1.3.1.  I think there was one post that
 explained what to do to get 1.3.0 to work but I can't find it right now
 :-((

 david jencks

 On 2002.08.10 14:57:25 -0400 G.L. Grobe wrote:
   I can't figure out which part you want me to look at.  I'm saying,
  remove
   all *-ds.xml files from a jboss Branch_3_0 version, they cannot be
   deployed. *-ds.xml files work only in 3.2 and 4 (head)
  
 
  Well, I removed *-ds.xml files and jboss still hangs on startup  (though
  not
  as many error messages). Here's about the last page of output before it
  hangs ...
 
  --- 3.0.1 output ---
 
  15:29:24,643 INFO  [jbossweb] successfully deployed
 
file:/u/public/jboss/jboss-3.0.1/server/default/tmp/deploy/server/default/de
  ploy/acais_mgr-0.30b.ear/62.acais_mgr-0.30b.ear-contents/acais-web.war
to
  /acais
  15:29:24,647 INFO  [MainDeployer] Deployed package:
 
file:/u/public/jboss/jboss-3.0.1/server/default/deploy/acais_mgr-0.30b.ear
  15:29:24,665 ERROR [URLDeploymentScanner] MBeanException: Exception in
  MBean
  operation 'checkIncompleteDeployments()'
  Cause: Incomplete Deployment listing:
  Packages waiting for a deployer:
none
  Incompletely deployed packages:
none
  MBeans waiting for classes:
none
  MBeans waiting for other MBeans:
  [ObjectName: jboss.system:type=Log4jService,service=Logging
   state: FAILED
   I Depend On:
   Depends On Me: org.jboss.deployment.DeploymentException: No property
  editor
  for attribute: ConfigurationURL; type=class java.net.URL]
  15:29:24,701 INFO  [URLDeploymentScanner] Started
  15:29:24,703 INFO  [MainDeployer] Deployed package:
  file:/u/public/jboss/jboss-3.0.1/server/default/conf/jboss-service.xml
  15:29:24,708 ERROR [Server] start failed
  Incomplete Deployment listing:
  Packages waiting for a deployer:
none
  Incompletely deployed packages:
none
  MBeans waiting for classes:
none
  MBeans waiting for other MBeans:
  [ObjectName: jboss.system:type=Log4jService,service=Logging
   state: FAILED
 
   I Depend On:
   Depends On Me: org.jboss.deployment.DeploymentException: No property
  editor
  for attribute: ConfigurationURL; type=class java.net.URL]
  at
 
org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.ja
  va:1095)
  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
  at java.lang.reflect.Method.invoke(Native Method)
  at
 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
  cher.java:284)
  at
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
  at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
  at org.jboss.Main.boot(Main.java:142)
  at org.jboss.Main$1.run(Main.java:375)
  at java.lang.Thread.run(Thread.java:484)
  Incomplete Deployment listing:
  Packages waiting for a deployer:
none
  Incompletely deployed packages:
none
  MBeans waiting for classes:
none
  MBeans waiting for other MBeans:
  [ObjectName: jboss.system:type=Log4jService,service=Logging
   state: FAILED
   I Depend On:
   Depends On Me: org.jboss.deployment.DeploymentException: No property
  editor
  for attribute: ConfigurationURL; type=class java.net.URL]
  at
 
org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.ja
  va:1095)
  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:583)
  at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
  at java.lang.reflect.Method.invoke(Native Method)
  at
 
org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispat
  cher.java:284)
  at
  org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
  at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
  at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
  at org.jboss.Main.boot(Main.java:142)
  at org.jboss.Main$1.run(Main.java:375)
  at java.lang.Thread.run(Thread.java:484)
 
 
 
 
  ---
  This sf.net email is sponsored by:ThinkGeek
  Welcome to geek heaven.
  http://thinkgeek.com/sf
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  https://lists.sourceforge.net/lists/listinfo/jboss-user
 
 


 ---
 This sf.net

[JBoss-user] 3.0.1 and PostgresDS

2002-08-09 Thread G.L. Grobe 



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-namePostgresDS/jndi-name 
connection-urljdbc:postgresql://localhost:5432/acais/connection-url 
driver-classorg.postgresql.Driver/driver-class 
user-nameuser/user-name 
passwordpass/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"

Re: [JBoss-user] 3.0.1 and PostgresDS

2002-08-09 Thread David Jencks 

Believe the deployer: null part.  *-ds.xml files are only for 3.2 and
later.

david jencks

On 2002.08.09 23:47:10 -0400 G.L. Grobe wrote:
 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-namePostgresDS/jndi-name
   connection-urljdbc:postgresql://localhost:5432/acais/connection-url
   driver-classorg.postgresql.Driver/driver-class
   user-nameuser/user-name
   passwordpass/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 = principaluser/module-option
  module-option name = userNameuser/module-option
  module-option name = passwordpass/module-option
  module-option name = 
managedConnectionFactoryNamejboss.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=SecurityDomainJndiNamePostgresDbRealm/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=JndiNamePostgresDS/attribute
 attribute name=ManagedConnectionFactoryProperties
   properties
 config-property

Re: [JBoss-user] 3.0.1 and PostgresDS

2002-08-09 Thread G.L. Grobe 

Not sure I understood this reply. What's happening is that 3.0.1 is hanging
at this point. I've placed the last lines of the output at the end of this
reply where it hangs.

- Original Message -
From: David Jencks [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, August 10, 2002 12:09 AM
Subject: Re: [JBoss-user] 3.0.1 and PostgresDS


 Believe the deployer: null part.  *-ds.xml files are only for 3.2 and
 later.

 david jencks

 On 2002.08.09 23:47:10 -0400 G.L. Grobe wrote:
  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-namePostgresDS/jndi-name
 
connection-urljdbc:postgresql://localhost:5432/acais/connection-url
driver-classorg.postgresql.Driver/driver-class
user-nameuser/user-name
passwordpass/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 = principaluser/module-option
   module-option name = userNameuser/module-option
   module-option name = passwordpass/module-option
   module-option name =
managedConnectionFactoryNamejboss.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=SecurityDomainJndiNamePostgresDbRealm/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=JndiNamePostgresDS/attribute
  attribute name