Microsoft has got to be kidding

Question

I have never been so frustrated in my whole life. Microsoft has really crossed the line with both Skype, and Internet Explorer. They should be ashamed of themselves. How can Microsoft's own software be so bloated and crappy? They are the ones who made very good Operating Systems after all (excluding Vista and Windows 8 ). I haven't used a single software created by microsoft which isn't a big piece of crap, expect for the OS. Internet explorer is always crashing for apparently, no bloody reason at all. Skype was also ruined by the piece of crap company, crashing all the time, delay in calls, bloated, and crappy. I sometimes wonder why the programmers at Microsoft aren't cleaning toilet full of their own software, yes, crap. And you know what? I don't give two craps if I posted this in the wrong section, Microsoft has been doing wrong things for a long time, one mistake on my end shouldn't affect anything.Microsoft has got the reverse of the midas touch, just like EA Games, they touch something and turn it right into crap. I bet the thing they're going to be ruining next will be Minecraft. I really hope they'll do a good job with windows 10 this time...

Answer 1

Ann,
As the above responder stated, servlets, and therefore instance variables declared in servlets, are not inherently thread safe in nature. It is up to you to program all of the update logic for instance variables in your servlet, which usually means some sort of synchronized blocks in your code. Another way which you may solve your problem of DataSource synchrnization is to use sessions. For instance you could have the following code:
public class LoginClass extends HttpServlet{
  public void init() throws ServletException {
    //verify user and password here
   HttpSession session = request.getSession(true); // create a new session if one does not exist
    //form a connection to your database here
    session.setAttribute("connection", connection); // add the connection to your database to the session of the user
}Then in another servlet that uses the connection simply use:
HttpSession session = request.getSession(); //notice no parameter
Connection conn = (Connection)request.getAttribute("connection");You must cast the getAttribute() results to a Connection because it returns an Object. I have used this method in a web app with 10 simultaneous users without problem and without synchronization blocks of code. Hope this helps.
-Matt