Getting Datasource object configured in JBOSS

[Krishna D. Bhat]

Hi,

I wanted to use DataSource to connect to Oracle database. I am able to configure DataSource in JBoss server (See This). I can see following message on startup of JBoss (I am using jboss-4.0.4.GA) running in my PC:

20:49:49,014 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=OracleDS' to JNDI name 'java:OracleDS'

But I am not able to connect to this DataSource. I used following code to connect to data source:

import java.sql.Connection;
import java.sql.ResultSet;
import java.util.Properties;
 
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.sql.DataSource;
 
public class DataSourceEx {
    public static void main(String args[]) throws Exception {
        Properties prop = new Properties( );
        prop.setProperty(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
        prop.setProperty(Context.PROVIDER_URL,"jndi://localhost:1099");
        Context ctx = new InitialContext(prop);
        DataSource ds = (DataSource) ctx.lookup("OracleDS");
        Connection conn = ds.getConnection();
        ResultSet rs = conn.createStatement().executeQuery("SELECT 'Hello World' FROM Dual");
        if (rs.next()) {
            System.out.println("I got " + rs.getString(1));
        }
        rs.close();
        conn.close();
    }
}

I am getting following exception:

Exception in thread "main" javax.naming.NameNotFoundException: OracleDS
at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:242)
at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:155)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.ha.framework.server.HARMIServerImpl.invoke(HARMIServerImpl.java:209)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:595)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
at org.jboss.ha.framework.server.HARMIServerImpl_Stub.invoke(Unknown Source)
at org.jboss.ha.framework.interfaces.HARMIClient.invokeRemote(HARMIClient.java:172)
at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:267)
at $Proxy0.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at DataSourceEx.main(DataSourceEx.java:16)

Is there anything wrong? How can I connect to Oracle Datasource configured on JBoss Server?

Cheers,
Krishna

[Scott Selikoff]

Try viewing/adding the data source in the JBoss admin console. Oh, and moving to JBoss forum...

[Jaikiran Pai]

Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=OracleDS' to JNDI name 'java :OracleDS'

As you can see, the datasource is bound to the java: namespace (by default). This means that the datasource is not accessible remotely. You can look it up only from the same JVM as the server. In your case, you are looking it up from a standalone client and hence running into this issue. See this for a probable workaround.
[ March 27, 2008: Message edited by: Jaikiran Pai ]