0
I have tested my Desktop application, and noticed that when I leave running for a long time I notice changes in the behavior of the actions that should be performed.
My application runs using Hibernate, and I notice these changes after a few hours it is running.
What should I do to perform more thorough tests and verify what may be causing such problems?
One of the problems that has occurred is when filling out a sales registration and recording the common is after recorded in the bank clear the screen fields as Jtable, Jtextfield, among others but not clear time and keep the data still on the screen if I close the application and open again everything works perfectly.
Another problem is the realization of the whole process and time in the records the data in the database.
What are these behaviors? Detail the problem better to help you.
– adelmo00
Give more details, like this, only with crystal ball.
– Maniero
What’s the matter?
– DiegoAugusto
A doubt, you make
commitof bank operations? Closes connections also?– DiegoAugusto
@Techies Yes I commit and close the connections after any interaction with the bank.
– DevAgil
Is the system in production right? You have its logs?
– DiegoAugusto
@Techies So in case if it generated some Exception everything well would be easy to discover the source of the problems, but it does not happen.
– DevAgil
I am having a problem a little like, the cause is that the system after some time without use loses the connection with the bank, everything I do works however the fields are not updated either.
– DiegoAugusto
@Techies as reached consensus that the system loses connection to the database?
– DevAgil
Let’s go continue this discussion in chat.
– DevAgil
You are using JPA as spec?
– dougg0k
@Douglasgaldino what would be spec?
– DevAgil
It is specification, referring to Java EE, Hibernate although it also works by itself, also works as implementation for the JPA specification.
– dougg0k
But in case I use for a Java SE application
– DevAgil