hibernate - web application hangs in tomcat 6.0.21/7.0.11 without clue -


I only have a web application that hangs after a few minutes. Basically, this is an application to create and preview a very customized format, and after a few minutes of intense user interaction, the application simply stops working. This means that a request is made and never gives a response.

I have been "lost" because I have not had a clue about the hanging in the TomTrot log and the application log, the application server is running because I am using Lambda / PSI-Check And I can check any more troublesome application with any problem (the investigation itself is another web application).

The application uses Hibernate, which was working fine for a long time, and, lately, to improve performance (Hybridlet injures many questions if you have special ) I started native SQL through Java SQLL standard API. I am not careful to mix both of them and they are used only in JSP, the first few (some) objects are hibernate and then using some logic with JDBC. Hibernation session is closed before using Jdbc.

I have read something about the database connection problems (I have several times and the database server is running fine), the deadlock or runway thread, using the vidyum in the visual dimensions. / P>

So, can anyone give a clue about hanging or trapping? Can you give some clues to use visual visualization to capture or trap the fictional runaway thread or deadlock? The latter will highlight me because I'm just waiting and running threads.

I am using 6.0.06 Tomcat (I always tried 7.0.11 with the same result) Java 1.6 (development and presentation on Mac OSX and Linux

>

Try running jconsole (if you are able to do this on a machine If you are not, you will need to enable remote JMX, restart the JVM and reproduce the hang), and then click on the Thread tab and click on Demand Click here to find out. This can be some help.

There are other things to use, as you say, vidyuum, or.

Edit < / Strong>

Looking at your comment, try the following:

  1. Start Jessensole and join your VM with your hanging
  2. MBINs → Go to ComSune Administration → Hotspot Diagnostic → Operations
  3. There will be a button called DumpHap Next to the two text boxes will be with. In the first text box, enter a unique name - I use something like my initial letter - rt20110317 . Place another text box on the right. Press the dumphead button

    This will write the stack in a larger file. Find and load this file This tool provides all useful bits and pieces to look at VM's position. There are also some magicians to find the memory leak, which can also tell why your VM is hanging if it is due to the same type of symptoms.

Comments

Post a Comment