Dee Brown

If you read this thread you will see that a signature of the indicated issue is that hibernate will issue two update() calls even though a single record is being persisted. To confirm the above use the following to enable tracing:

log4j.logger.org.hibernate.SQL=DEBUG, A1
log4j.additivity.org.hibernate.SQL=false

The 'fix':

<property name = "hibernate.jdbc.batch_size" value="0" />

Thanks for the tip.

As an FYI, I had originally tried the 11g driver and switched to the 10g driver when "a hang" was first encountered. Since I did not view the SQL log at that time (I am new to Hibernate), I will likely try the 11g driver again.

Thanks

db

I have what appears to be the exact same problem that you have documented here. I have the 'double update' condition when the failure is present. Would it be possible for you to tell me what the fix for the problem was? I would be very grateful if you are able to.

Thanks in advance..db

I believe multiple files in the associated folder needed the setting, so I navigated to the folder and executed: chmod 755 *.sh

You should be able to display the tiff file using an image display app and select copy, and then paste it into your resume editing tool. If you are using Microsoft Word to edit your resume it should not be a problem, but it might even work in wordpad (which is free). I am on a Mac so I cannot see if paint handles a tiff, but there is freeware available on the net if your system does not have an appropriate image app.

I realize it is too late, but I believe I have seen that many people get 10 to 20 percent better than their hsfj scores. But everyone is different.

Private message sent since (I assume) they do not want links posted here.

I have only used Eclipse and IDEA (by IntelliJ). I have heard good things about MyEclipse, but its users still have to deal with issues related to Eclipse. Once such issue is the highlighting of code with (pseudo) errors like:

- ServletContext cannot be resolved to a type
- FacesContext cannot be resolved

After experiencing such problems I find it is a known issue that all the documented fixes never completely resolve. When I experienced highlighted code in IDEA, it was always resolved to a bad jar (i.e. a real error) or improperly configured project (a psuedo error). If it is also due to an improperly configured Eclipse project, it is very difficult to isolate as colleagues with years of Eclipse experience eventually give up on it. In my opinion, Eclipse/MyEclipse is ideal for a business on a shoestring budget, and any university that teaches computer science / software engineering.

So it was a trick question.

Your failure to provide that information up front is likely the reason why your question went unanswered for as long as it did. Your failure to provide information on where the question came from leaves little else to go on. The idea here is to make it as easy as possible for others to answer your question. If you also include where the question is from maybe someone else has come across it and has the answer, or knows that the provided answer is in fact wrong (because they reviewed the errata).

However, in this case (assuming they are listed in A-D alphabetical order), I have not identified why A and D would be wrong. Extensive analysis was not performed because it does not appear to be necessary.

This can occur as a result of a non-standard "web.xml" file.

According to google:
1) For a JSP 2.0 container, you should be using JSTL 1.1, and you should have your web application declared as a Servlets 2.4 web app by using the Servlets 2.4 XML Schema.
2) For a JSP 1.x container, you should be using JSTL 1.0, and you should have your web application declared as a Servlets 2.3 web app by using the Servlers 2.3 DOCTYPE.

I believe the following is correct for my 2.4 installation:

<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">

...

</web-app>

Seems like a trick question but I would have to say they all do. This is because all are passed an EventObject (subclass) that has reference to the associated HttpSession object. Through HttpSession.getContext(), the above listeners can call the associated parameter methods to retrieve the names and values of the context parameters.

I believe refactoring is associated with bringing existing code up to spec, and providing the best implementation of a given construct (e.g. a table). Writing code to spec is for the most part straightforward, but to take an existing implementation and determine how to economically reconstruct it takes a slightly different thought process.

According to the api for the cookie class, "The browser returns cookies to the servlet by adding fields to HTTP request headers."

An associated rfc (2109) states:

4.3.4 Sending Cookies to the Origin Server

When it sends a request to an origin server, the user agent sends a
Cookie request header to the origin server...

The syntax for the header is:

cookie = "Cookie:" cookie-version
1*((";" | ",") cookie-value)
cookie-value = NAME "=" VALUE [";" path] [";" domain]
cookie-version = "$Version" "=" value
NAME = attr
VALUE = value
path = "$Path" "=" value
domain = "$Domain" "=" value

It would therefore appear the maxAge value you are retrieving is one the container supplies when it instantiates a cookie it receives from the client. Since the setting of maxAge is the setting of a value that is used by the client, the fact that the "-1" is retrieved is not all that important.

You can verify that the maxAge is not in the request header using the Live HttpHeaders plugin/addon in the Firefox browser.

In your code you state, "Cookie [] cookies = request.getKookies();", so the code cannot compile. Can you supply the actual code that is being used?

Since both HttpSessionBindingListener and HttpSessionListener are possible answers, for your answer to be correct would be to say that the callback to the HttpSessionBindingListener is more closely associated with a session timeout than the callback to the HttpSessionListener, which is not true. The callback to the HttpSessionBindingListener occurs when an attribute is unbound, which can occur as a result of a session timeout.