Cannot insert into sql server using JDBC

[achuthan mukundarajan]

I tried to insert into sql server using the following code:

String connectionURL="jdbc:sqlserver://localhost:1433;databaseName=sampledb;integratedSecurity=true";  
            Connection connection=null;  
            ResultSet rs;  
            response.setContentType("text/html;charset=UTF-8");  
            PrintWriter out = response.getWriter();  
            String name=request.getParameter("txtname");  
            int age=Integer.parseInt(request.getParameter("txtage"));  
            try  
            {  
                Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");  
                Connection conn = DriverManager.getConnection(connectionURL,"","");  
                String query="INSERT into details VALUES(?,?)";  
                PreparedStatement pst=connection.prepareCall(query);  
                pst.setString(1, name);  
                pst.setInt(2, age);  
      
                 }  
            catch(ClassNotFoundException e){  
      out.println("Couldn't load database driver: "  
      + e.getMessage());  
      }  
            catch(SQLException e){  
      out.println("SQLException caught: "   
      + e.getMessage());  
      }  
      catch (Exception e){  
      out.println(e);  
      }  
            finally {  
      // Always close the database connection.  
      try {  
      if (connection != null) connection.close();  
      }  
      catch (SQLException ignored){  
      out.println(ignored);  
      }  
      }  

But i get a null pointer exception. I tried printing the stack trace but i get a blank page.

Why is there a nullpointerexception? Thanks in advance.

[Tim Holloway]

I believe that in JSP there's a "log" object or method that will write to the server log. That will work better than attempting to log the stacktrace to the client. Or, if all else fails, write the stacktrace to System.out.

Actually, attempting to acquire a database connection in the way you described has 2 strikes against it.

1. We do not recommend putting logic in JSPs. Use the JSP for display and let a servlet do the dirty work.

2. Instead of the relatively expensive process of creating a Connection that you're using, well-written enterprise webapps use Connection Pools constructed by the webapp server.

Yes, the "brute force" ASP/PHP way is quicker to code, but J2EE is an expensive technology and the extra work up front should pay off in terms of overall maintainability and performance.

Speaking as a rabid Java fan, when I need something quick and dirty, I do use something like PHP, not J2EE.

[chain singh]

Try

executeUpdate instead of prepareCall
may be it will work

[achuthan mukundarajan]

chain singh wrote:Try

executeUpdate instead of prepareCall
may be it will work

IT WORKED!!! thanks. Also i thank tim for the valuable advice..