How to get Connection through JNDI Datasource.

[Shane Connors]

Hi Guys,

here is my datasource file in JBOSS\deploy folder - (flytours-ds.xml)

   
<datasources>
  <local-tx-datasource>
		<jndi-name>flytours_ora-datasource</jndi-name>
		<use-java-context>false</use-java-context>
	
		<driver-class>oracle.jdbc.OracleDriver</driver-class>

		<connection-url>jdbc:oracle:thin:@10.2.81.21:1521:orcl</connection-url>
		<user-name>flytours</user-name>
		<password>flytours</password>



		<!-- Uses the pingDatabase method to check a connection is still valid before handing it out from the pool -->
    	<valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker</valid-connection-checker-class-name>
		<!-- Checks the Oracle error codes and messages for fatal errors -->
    	<exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
        <!-- sql to call when connection is created
        <new-connection-sql>some arbitrary sql</new-connection-sql>
        -->

        <!--sql to call on an existing pooled connection when it is obtained from pool - the OracleValidConnectionChecker is prefered-->
        <check-valid-connection-sql>SELECT 1 FROM dual</check-valid-connection-sql>

		<!-- The minimum connections in a pool/sub-pool. Pools are lazily constructed on first use -->
		<min-pool-size>10</min-pool-size>

		<!-- The maximum connections in a pool/sub-pool -->
		<max-pool-size>50</max-pool-size>

		<!-- The time before an unused connection is destroyed -->
		<!-- NOTE: This is the check period. It will be destroyed somewhere between 1x and 2x this timeout after last use -->
		<!-- TEMPORARY FIX! - Disable idle connection removal, HSQLDB has a problem with not reaping threads on closed connections -->
		<idle-timeout-minutes>0</idle-timeout-minutes>

		<!-- Whether to check all statements are closed when the connection is returned to the pool,
           this is a debugging feature that should be turned off in production -->
		<track-statements/>

		<!-- corresponding type-mapping in the standardjbosscmp-jdbc.xml (optional) -->
		<metadata>
			<type-mapping>Oracle10g</type-mapping>
		</metadata>
	</local-tx-datasource>

</datasources>
 

####my web.xml file######

    
    <resource-ref>
  		<res-ref-name>jdbc/flytours_ora-datasource</res-ref-name>
  		<res-type>javax.sql.DataSource</res-type>
  		<res-auth>Container</res-auth>
	</resource-ref>

####jboss-web.xml#####

  
<jboss-web>
    <resource-ref>
        <res-ref-name>jdbc/flytours_ora-datasource</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <jndi-name>java:/flytours_ora-datasource</jndi-name>
    </resource-ref>
</jboss-web>

#### Java class####

    
Connection con = null;
DataSource ds = null;

Context init = new InitialContext();
Context ctx = (Context) init.lookup("java:comp/env");
ds = (DataSource) ctx.lookup("jdbc/flytours_ora-datasource");
ctx.close();

When staring the server it throws this exception,

    
 javax.naming.NamingException: Could not dereference object [Root exception is javax.naming.NameNotFoundException: flyfwd_ora-datasource not bound]

can anyone suggest me a way to get this working?

[Shane Connors]

Just to remind im using JBoss4.2 in Windows XP

[Jaikiran Pai]

Is that "Java class" a servlet? You can't use the java:comp/env in any Java class. It has to be an enterprise component (like servlet).

[Shane Connors]

Jaikiran Pai wrote:Is that "Java class" a servlet? You can't use the java:comp/env in any Java class. It has to be an enterprise component (like servlet).

Hi,

Thats a normal java class, servlet calls this class to get DB connection. wht should i do here?

i have tested this with below coding too

   
InitialContext ic;
               
ic = new InitialContext();
ds = (DataSource) ic.lookup("java:/flytours");
 

[Jaikiran Pai]

Please post the entire exception stacktrace and the relevant code from your servlet which calls this class.

[Shane Connors]

Jaikiran Pai wrote:Please post the entire exception stacktrace and the relevant code from your servlet which calls this class.

Complete stack trace is huge, i have copied some part

    
15:03:35,451 ERROR [STDERR] javax.naming.NameNotFoundException: flytours not bound
15:03:35,451 ERROR [STDERR] 	at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
15:03:35,451 ERROR [STDERR] 	at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
15:03:35,451 ERROR [STDERR] 	at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
15:03:35,451 ERROR [STDERR] 	at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
15:03:35,451 ERROR [STDERR] 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:667)
15:03:35,451 ERROR [STDERR] 	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:627)
15:03:35,451 ERROR [STDERR] 	at javax.naming.InitialContext.lookup(InitialContext.java:392)
15:03:35,451 ERROR [STDERR] 	at com.pw.flyforward.user.DbConn.getCon(DbConn.java:102)

Servlet

    
public class GlobalPropertyLoader implements ServletContextListener {
    private ServletContext context = null;
        Connection con = null;
    public void contextInitialized(ServletContextEvent event) {
        try{
        context = event.getServletContext();
        con = PropertyLoader.getConnection( context);
        }catch(SQLException e){
            //e.printStackTrace();
           // System.out.println(e.getMessage());
           int r=0;
        }
        
        try{
            scheduleAutoJoinTimerTask(new AutoJoinTask(), context);
        }catch(SQLException e){
            //e.printStackTrace();
            int r=0;
        }        
        }
        

    }

PropertyLoader

    
public class PropertyLoader {

Connection con = null;
DataSource ds = null;
   
public Connection getConnection(ServletContext context) throws SQLException {

try{
Context init = new InitialContext(); 
Context ctx = (Context) init.lookup("java:comp/env"); 
ds = (DataSource)ctx.lookup("flytours"); 
ctx.close();
} catch (NamingException e) {
e.printStackTrace();
}
con = ds.getConnection();
return con;

}
}

[Jaikiran Pai]

Ah, so you are looking it up in a ServletContextListener when the context is initialized. I'm not sure the JNDI java:comp/env is setup correctly at that time.

By the way, why do you want to hold the DB connection in the ServletContextListener?

[Shane Connors]

Jaikiran Pai wrote:Ah, so you are looking it up in a ServletContextListener when the context is initialized. I'm not sure the JNDI java:comp/env is setup correctly at that time.

By the way, why do you want to hold the DB connection in the ServletContextListener?

Well...

its working fine with tomcat 6, i wanted to shift this to JBoss 4.2, i couldnt do that because of this issue..