Ok, I did that, and the result is the same. but now, I can provide actual
details...
1. Here's where it stops...
ty.SubjectSecurityProxyFactory@4695a6
[JAAS Security Manager] Started
[JDBC provider] Starting
[JDBC provider] Started
[postgres] Starting
[postgres] XA Connection pool postgres bound to java:/postgres
2. Here's my jboss.jcml.
<?xml version="1.0" encoding="UTF-8"?>
<!-- This is where you can add and configure your MBeans
ATTENTION: The order of the listing here is the same order as
the MBeans are loaded. Therefore if a MBean depends on another
MBean to be loaded and started it has to be listed after all
the MBeans it depends on.
-->
<server>
<!-- Classloading -->
<mbean code="org.jboss.web.WebService"
name="DefaultDomain:service=Webserver">
<attribute name="Port">8083</attribute>
</mbean>
<!-- JNDI -->
<mbean code="org.jboss.naming.NamingService"
name="DefaultDomain:service=Naming">
<attribute name="Port">1099</attribute>
</mbean>
<mbean code="org.jboss.naming.JNDIView"
name="DefaultDomain:service=JNDIView" />
<!-- Transactions -->
<mbean code="org.jboss.tm.TransactionManagerService"
name="DefaultDomain:service=TransactionManager">
<attribute name="TransactionTimeout">300</attribute>
</mbean>
<!-- Security -->
<!-- Uncomment to enable the sample SRPVerifierStore service
<mbean code="org.jboss.security.plugins.SRPVerifierStoreService"
name="Security:name=SRPVerifierStoreService">
<attribute name="JndiName">SRPDefaultVerifierSource</attribute>
<attribute name="StoreFile">SRPVerifierStore.ser</attribute>
</mbean>
-->
<!-- Uncomment to enable the SRP login service
<mbean code="org.jboss.security.plugins.SRPService"
name="service:name=SRPService">
<attribute name="JndiName">SRPServerInterface</attribute>
<attribute
name="VerifierSourceJndiName">SRPDefaultVerifierSource</attribute>
<attribute
name="AuthenticationCacheJndiName">SRPAuthenticationCache</attribute>
<attribute name="ServerPort">10099</attribute>
</mbean>
-->
<!-- JAAS security manager and realm mapping -->
<mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
name="Security:name=JaasSecurityManager">
<attribute
name="SecurityManagerClassName">org.jboss.security.plugins.JaasSecurityManag
er</attribute>
</mbean>
<!-- Uncomment to enable the XML implementation of the JAAS policy
<mbean code="org.jboss.security.plugins.SecurityPolicyService"
name="Security:name=SecurityPolicyService">
<attribute name="JndiName">DefaultSecurityPolicy</attribute>
<attribute name="PolicyFile">sample_policy.xml</attribute>
</mbean>
-->
<!-- JDBC -->
<mbean code="org.jboss.jdbc.JdbcProvider"
name="DefaultDomain:service=JdbcProvider">
<attribute name="Drivers">org.postgresql.Driver</attribute>
</mbean>
<mbean code="org.jboss.jdbc.XADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=postgres">
<attribute name="PoolName">postgres</attribute>
<attribute
name="DataSourceClass">org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImp
l</attribute>
<attribute name="Properties"></attribute>
<attribute
name="URL">jdbc:postgresql://virtualofficeamerica.com/ejbTest</attribute>
<attribute name="GCMinIdleTime">1200000</attribute>
<attribute name="JDBCUser">carey</attribute>
<attribute name="MaxSize">10</attribute>
<attribute name="Password">$piper</attribute>
<attribute name="GCEnabled">false</attribute>
<attribute name="InvalidateOnError">false</attribute>
<attribute name="TimestampUsed">false</attribute>
<attribute name="Blocking">true</attribute>
<attribute name="GCInterval">120000</attribute>
<attribute name="IdleTimeout">1800000</attribute>
<attribute name="IdleTimeoutEnabled">false</attribute>
<attribute name="LoggingEnabled">false</attribute>
<attribute name="MaxIdleTimeoutPercent">1.0</attribute>
<attribute name="MinSize">0</attribute>
</mbean>
<!-- J2EE deployment -->
<mbean code="org.jboss.ejb.ContainerFactory"
name=":service=ContainerFactory">
<attribute name="VerifyDeployments">true</attribute>
<attribute name="MetricsEnabled">false</attribute>
<attribute name="VerifierVerbose">true</attribute>
<attribute name="BeanCacheJMSMonitoringEnabled">false</attribute>
</mbean>
<!-- Uncomment to add embedded tomcat service
<mbean code="org.jboss.tomcat.EmbeddedTomcatService"
name="DefaultDomain:service=EmbeddedTomcat" />
-->
<!-- Uncomment and set file URL to add Jetty service (you can set config
more than once)
<mbean code="org.jboss.jetty.JettyService"
name="DefaultDomain:service=Jetty">
<attribute name="Configuration">file URL to jetty.xml e.g.
file:/usr/local/jboss/dist/conf/default/jetty.xml</attribute>
</mbean>
-->
<!-- For Message Driven Beans -->
<mbean code="org.jbossmq.server.JBossMQService"
name="DefaultDomain:service=JBossMQ" />
<mbean code="org.jboss.jms.jndi.JMSProviderLoader"
name=":service=JMSProviderLoader,name=JBossMQProvider">
<attribute name="ProviderName">DefaultJMSProvider</attribute>
<attribute
name="ProviderAdapterClass">org.jboss.jms.jndi.JBossMQProvider</attribute>
</mbean>
<mbean code="org.jboss.jms.asf.ServerSessionPoolLoader"
name=":service=ServerSessionPoolMBean,name=StdJMSPool">
<attribute name="PoolName">StdJMSPool</attribute>
<attribute
name="PoolFactoryClass">org.jboss.jms.asf.StdServerSessionPoolFactory</attri
bute>
</mbean>
<!-- Make sure you change EmbeddedTomcat to Jetty if you are using
etty -->
<mbean code="org.jboss.deployment.J2eeDeployer"
name="J2EE:service=J2eeDeployer">
<attribute name="DeployerName">Default</attribute>
<attribute name="JarDeployerName">:service=ContainerFactory</attribute>
<attribute name="WarDeployerName">:service=EmbeddedTomcat</attribute>
</mbean>
<mbean code="org.jboss.ejb.AutoDeployer" name="EJB:service=AutoDeployer">
<attribute name="Deployer">J2EE:service=J2eeDeployer</attribute>
<attribute name="URLs">../deploy</attribute>
</mbean>
<!-- J2EE connector architecture -->
<mbean code="org.jboss.resource.RARDeployer"
name="JCA:service=RARDeployer">
</mbean>
<!-- Minerva no transaction connection manager factory.
Use this for resource adapters that don't support
transactions. -->
<mbean code="org.jboss.resource.ConnectionManagerFactoryLoader"
name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaNoTransCMFactor
y">
<attribute name="FactoryName">MinervaNoTransCMFactory</attribute>
<attribute
name="FactoryClass">org.opentools.minerva.connector.jboss.MinervaNoTransCMFa
ctory</attribute>
<attribute name="Properties"></attribute>
</mbean>
<!-- Minerva local transaction connection manager factory.
Use this for resource adapters that support "local"
transactions. -->
<mbean code="org.jboss.resource.ConnectionManagerFactoryLoader"
name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaSharedLocalCMFa
ctory">
<attribute name="FactoryName">MinervaSharedLocalCMFactory</attribute>
<attribute
name="FactoryClass">org.opentools.minerva.connector.jboss.MinervaSharedLocal
CMFactory</attribute>
<attribute name="Properties"></attribute>
</mbean>
<!-- Minerva XA transaction connection manager factory
Use this for resource adapters that support "xa"
transactions. -->
<mbean code="org.jboss.resource.ConnectionManagerFactoryLoader"
name="JCA:service=ConnectionManagerFactoryLoader,name=MinervaXACMFactory">
<attribute name="FactoryName">MinervaXACMFactory</attribute>
<attribute
name="FactoryClass">org.opentools.minerva.connector.jboss.MinervaXACMFactory
</attribute>
<attribute name="Properties"></attribute>
</mbean>
<!-- Example connection factory for the example "Black Box" resource
adapter. This points at the same database as DefaultDS. -->
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="JCA:service=ConnectionFactoryLoader,name=BlackBoxDS">
<attribute name="FactoryName">BlackBoxDS</attribute>
<attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
<attribute name="ResourceAdapterName">Black Box LocalTx
Adapter</attribute>
<attribute name="Properties">
ConnectionURL=jdbc:HypersonicSQL:hsql://localhost:1476
</attribute>
<attribute
name="ConnectionManagerFactoryName">MinervaSharedLocalCMFactory</attribute>
<!-- See the documentation for the specific connection manager
implementation you are using for the properties you can set -->
<attribute name="ConnectionManagerProperties">
# Pool type - uncomment to force, otherwise it is the default
#PoolConfiguration=per-factory
# Connection pooling properties - see
# org.opentools.minerva.pool.PoolParameters
MinSize=0
MaxSize=10
Blocking=true
GCEnabled=false
IdleTimeoutEnabled=false
InvalidateOnError=false
TrackLastUsed=false
GCIntervalMillis=120000
GCMinIdleMillis=1200000
IdleTimeoutMillis=1800000
MaxIdleTimeoutPercent=1.0
</attribute>
<!-- Principal mapping configuration -->
<attribute
name="PrincipalMappingClass">org.jboss.resource.security.ManyToOnePrincipalM
apping</attribute>
<attribute name="PrincipalMappingProperties">
userName=sa
password=
</attribute>
</mbean>
<!-- This is an example of using a resource adapter that supports XA
transactions. The Black Box XA resource adapter requires an
XADataSource to be in JNDI somewhere. JBoss doesn't include a
database with an XA-compliant JDBC driver, so this will need to
be configured to use whatever XADataSource implementation you
have.
<mbean code="org.jboss.jdbc.RawXADataSourceLoader"
name="DefaultDomain:service=RawXADataSourceLoader,name=BlackBoxXADS">
<attribute name="PoolName">BlackBoxXADS</attribute>
<attribute name="DataSourceClass">Put your XADataSource implementation
class here</attribute>
<attribute name="Properties"></attribute>
</mbean>
<mbean code="org.jboss.resource.ConnectionFactoryLoader"
name="JCA:service=ConnectionFactoryLoader,name=XABlackBoxDS">
<attribute name="FactoryName">XABlackBoxDS</attribute>
<attribute name="RARDeployerName">JCA:service=RARDeployer</attribute>
<attribute name="ResourceAdapterName">Black Box XA Adapter</attribute>
<attribute name="Properties">
XADataSourceName=java:/BlackBoxXADS
</attribute>
<attribute
name="ConnectionManagerFactoryName">MinervaXACMFactory</attribute>
<attribute name="ConnectionManagerProperties">
# Pool type - uncomment to force, otherwise it is the default
#PoolConfiguration=per-factory
# Connection pooling properties - see
# org.opentools.minerva.pool.PoolParameters
MinSize=0
MaxSize=10
Blocking=true
GCEnabled=false
IdleTimeoutEnabled=false
InvalidateOnError=false
TrackLastUsed=false
GCIntervalMillis=120000
GCMinIdleMillis=1200000
IdleTimeoutMillis=1800000
MaxIdleTimeoutPercent=1.0
</attribute>
<attribute
name="PrincipalMappingClass">org.jboss.resource.security.ManyToOnePrincipalM
apping</attribute>
<attribute name="PrincipalMappingProperties">
userName=sa
password=
</attribute>
</mbean>
-->
<!-- JMX adaptors -->
<mbean code="org.jboss.jmx.server.JMXAdaptorService"
name="Adaptor:name=RMI" />
<mbean code="org.jboss.jmx.server.RMIConnectorService"
name="Connector:name=RMI" />
<mbean code="com.sun.jdmk.comm.HtmlAdaptorServer"
name="Adaptor:name=html">
<attribute name="MaxActiveClientCount">10</attribute>
<attribute name="Parser" />
<attribute name="Port">8082</attribute>
</mbean>
<!-- Mail Connection Factory -->
<mbean code="org.jboss.mail.MailService" name=":service=Mail">
<attribute name="JNDIName">Mail</attribute>
<attribute name="ConfigurationFile">mail.properties</attribute>
<attribute name="User">user_id</attribute>
<attribute name="Password">password</attribute>
</mbean>
<!-- Uncomment to enable JMX monitoring of the bean cache
<mbean code="org.jboss.monitor.BeanCacheMonitor"
name="Monitor:name=BeanCacheMonitor"/>
-->
<!-- Add your custom MBeans here -->
</server>
Sorry for the bandwidth, but I didn't want to send a fragment and miss the
important bits...
Thanks again,
Carey
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Dan
Christopherson
Sent: Thursday, March 29, 2001 12:56 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Postgres datasource causes JBoss init to
stop...
Make sure that PostgreSQL's pg_hba.conf is set up to allow and
authenticate accesses from the JBoss machine's IP address.
On Thu, 29 Mar 2001, Carey Nation wrote:
> Hi,
> I'm trying to get jboss going with postgres. I have the latest version
> of both. I've configured the stuff in the config files as shown in the
> docs. The jdbc driver loads, but when it gets to the bit about starting
> up the datasource, jboss freezes. It looks almost as if it's trying to
> time out, but I haven't managed to wait long enough yet. ^c causes jboss
> to shutdown as it should. Postgres is up and running (on another
> machine), and I'm pretty sure the url is right in the config file. I
> don't really think it's getting that far, watching the other datasources
> the come preconfigured start up. I copied the DefaultDS section and
> modified it, as suggested in the docs.
>
> Any ideas? I know this is pretty vague, but I'm away from the machine
> with the stuff on it. I looked in the archive and didn't see anything
> that looked right...
>
> Thanks,
> Carey
>
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
--
Dan Christopherson (danch)
nVisia Technical Architect (www.nvisia.com)
Opinions expressed are mine and do not neccessarily reflect any
position or opinion of nVISIA.
---------------------------------------------------------------------------
If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
-Eben Moglen
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
