Apart from things like that in my code (bmp entities and stateless sessions)
:
Context ctx = new InitialContext();
DataSource ds = (DataSource)ctx.lookup("java:comp/env/jdbc/OracleDB");
conn = ds.getConnection();
...
jdbc bla bla bla
...
conn.close();
I have all my cmp beans using (jboss.xml) :
<resource-ref>
<res-ref-name>jdbc/OracleDB</res-ref-name>
<resource-name>OralceDB</resource-name>
</resource-ref>
<resource-manager>
<res-name>OracleDB</res-name>
<res-jndi-name>java:/OraclePool</res-jndi-name>
</resource-manager>
while (jboss.jcml):
<mbean code="org.jboss.jdbc.RawXADataSourceLoader"
name="DefaultDomain:service=XADataSource,name=OraclePool">
<attribute name="PoolName">OraclePool</attribute>
<attribute
name="DataSourceClass">oracle.jdbc.xa.client.OracleXADataSource</attribute>
<attribute
name="Properties">URL=jdbc:oracle:oci8:scott/tiger@orcl</attribute>
</mbean>
Shahar.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Toby Allsopp
Sent: Monday, April 09, 2001 10:33 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Solving Oracle Connection Pool Hanging
On Mon, Apr 09, 2001 at 10:05:43PM +0200, Shahar Solomianik wrote:
> Im pretty sure I do get my transactions managed by jboss. are you 100%
sure
> about that ?
I think we should make sure that we're talking about the same thing. Can
you post the code that uses the XADataSource, please?
Toby.
> Shahar.
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Toby Allsopp
>
> On Mon, Apr 09, 2001 at 09:08:31PM +0200, Shahar Solomianik wrote:
> > Well, RawXADataSourceLoader works and XADataSourceLoader doesnt...
>
> I think you'll find that "works" is very limited in this case. You won't
> get your transactions managed by the container for one thing.
>
> > doesnt RawXADataSourceLoader pool connections ??? it should be
implemented
> > in the driver.
>
> Why should it be? Connection pooling is a service provided by the app
> server,
> not the JDBC driver. It may well be the case that Oracle's XADataSource
> implementation does do pooling, but this doesn't change the fact that your
> application component code shouldn't be dealing directly with XADataSource
> and XAConnection.
>
> Toby.
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Toby Allsopp
> >
> > RawXADataSourceLoader is not a replacement for XADataSourceLoader.
> >
> > The latter binds a DataSource implementation into JNDI which provides
> > connection pooling. The latter binds an XADataSource in JNDI, which
> provides
> > pretty much nothing that application components should be messing with.
> >
> > How are you using the XADataSource in your code?
> >
> > Toby.
> >
> > On Mon, Apr 09, 2001 at 04:48:00PM +0200, Shahar Solomianik wrote:
> > > yes.
> > > and use properties attribute instead the standard params, and Oracle
XA
> > > instead of minerva...
> > > this is from my jboss.jcml :
> > > <mbean code="org.jboss.jdbc.RawXADataSourceLoader"
> > > name="DefaultDomain:service=XADataSource,name=OraclePool">
> > > <attribute name="PoolName">OraclePool</attribute>
> > > <attribute
>
name="DataSourceClass">oracle.jdbc.xa.client.OracleXADataSource</attribute>
> > > <attribute
> > > name="Properties">URL=jdbc:oracle:oci8:scott/tiger@orcl</attribute>
> > > </mbean>
_______________________________________________
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
