Are you using a "jboss.xml" file for your EJB-JAR? If not, then
the resource declared in ejb-jar.xml will automatically be linked to the
first connection pool created, not the connection pool with the same name.
So it is likely your pool is pointing to Hypersonic when you think it's
pointing to Oracle. One easy way to test this would be to remove all DB
pools except the one you want, and see if it starts working then (because
your pool is now the "first" one). If you create a jboss.xml file with a
resource manager and then references for each data source for each bean
that link the resource in ejb-jar.xml to the resource manager, it'll fix
this problem (if that is indeed the problem).
Aaron
On Tue, 24 Oct 2000 [EMAIL PROTECTED] wrote:
> InitialContext ic = new InitialContext();
> DataSource ds = (DataSource)ic.lookup("java:comp/env/myDB");
> Connection con = ds.getConnection();
> Statement stmt = con.createStatement();
> ResultSet rs = stmt.executeQuery( "select myfield from mytable"); <--
> TransactionRollbackException Here
>
> ... Table not found: MYTABLE in statement [select myfield from mytable]
>
> Table is there (I can manually query) and...
>
> My DBA assures me that thin Oracle JDBC connections are established with proper
> privledges.
>
> I am using following config:
>
> classes12.zip
> org.jboss.minerva.xa.XADataSourceImpl
>
> ( I also tried this with prepared statements with the same results. )
>
> Sorry for going on...
> Does anyone hava an idea?
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
