Bookmark Topic Watch Topic
  • New Topic

Null pointer exception

 
elli dian
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Report post to moderator
I want to call stored procedure using callablestatement, but i get error:null pinter exception.
please give a solution to solve it.

My program:

package absen_dexa;

import java.sql.Connection;
import java.sql.SQLException;

import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;

public class Connection_Database {
private Connection koneksi;
public Connection_Database()
{
}
public Connection getConnection()
{
try
{
InitialContext cont = new InitialContext();
DataSource ds = (DataSource) cont.lookup("jdbc/ds2");
return ds.getConnection("ess_adm", "adm_ess");
}catch (NamingException e)
{
e.printStackTrace();
} catch (SQLException e) {
e.printStackTrace();
}
return null;
}
}

Connection conn=koneksi.getConnection();

try
{
CallableStatement cs=conn.prepareCall("{call submitClockingData(?,?,?,?)}");
cs.setString(1,"DX");
cs.setString(2,"DX005010001");
cs.setString(3,date1);
cs.setInt(4,1);
cs.execute();
}catch(SQLException err)
{
System.out.println("Error "+err.getClass());
}finally
{
conn.close();
}
 
marc weber
Sheriff
Posts: 11343
Java Mac Safari
  • Mark post as helpful
  • send pies
  • Report post to moderator
As suggested in your last null pointer topic, it would be much easier for others to help if you posted the trace.

(Code Tags would also help.)
 
Ernest Friedman-Hill
author and iconoclast
Marshal
Pie
Posts: 24212
35
Chrome Eclipse IDE Mac OS X
  • Mark post as helpful
  • send pies
  • Report post to moderator
Well, you don't say where the NPE happens -- the stack trace has a lot of useful information in it. But one thing I see here is that if the getConnection() method fails, it prints an exception message and returns null. Then the code that calls getConnection() fails to test the return value for null; so if getConnection() fails, you'll get an NPE in its client code.

If getConnection() fails, the routine that calls it should fail, too, so actually, getConnection() should not catch those exceptions; it should just let them go up and abort the caller.
 
marc weber
Sheriff
Posts: 11343
Java Mac Safari
  • Mark post as helpful
  • send pies
  • Report post to moderator
Now that I've looked closer at your previous post, I see that this is a continuation of that topic. Please continue this discussion in that original thread, rather than starting a new thread. Thanks!
 
    Bookmark Topic Watch Topic
  • New Topic