- 196.7K All Categories
- 2.2K Data
- 234 Big Data Appliance
- 1.9K Data Science
- 449.7K Databases
- 221.5K General Database Discussions
- 31 Multilingual Engine
- 549 MySQL Community Space
- 477 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 532 SQLcl
- 4K SQL Developer Data Modeler
- 186.8K SQL & PL/SQL
- 21.2K SQL Developer
- 295.3K Development
- 17 Developer Projects
- 138 Programming Languages
- 292K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 27 Java Learning Subscription
- 37K Database Connectivity
- 153 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 157 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 203 Java User Groups
- 387 LiveLabs
- 37 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.6K Other Languages
- 2.3K Chinese
- 170 Deutsche Oracle Community
- 1K Español
- 1.9K Japanese
- 230 Portuguese
The commit causes the application to stop working when the connection lifetime expires
A simple test application was created to seek to improve the management of the connection pool in production ADF applications. For this, the following test was run:
You have the same application running in two different browsers, Browser 1 and Browser 2.
Then, in both applications the submit is performed to store the changes only in memory, in both applications the last name was changed in the same record.
The connection lifetime (two minutes) is expected to expire in both applications.
Then a commit is done in browser app 1, the commit is successful.
In browser 2 the same thing is done, commit is executed and the alert that is expected to come out appears, nothing out of the ordinary.
However, in Browser 2 the application seems to "disconnect" after clicking on the "ok" button, because it no longer shows the information from the employees table and the form is empty, this behavior only happens when execute the commit after the connection lifetime "JDBC DataSource" expires and the connection is released.
The test was originally done on Weblogic with the standard settings and also on payara, the behavior is the same.
Lastly, no useful information was found in the weblogic log that would give me guidelines to solve the problem.
What could this problem be due to?
Java (TM) Platform: 1.8.0_211
Oracle Jdeveloper 12c IDE: 18.104.22.168.42.190911.2248
Scheme used: HR
Test application AppModule configuration:
Tab - Database and Scalability
Idle Instance Timeout (s): 60
Pool Polling Interval (s): 30
Tab - Properties