Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 234 Big Data Appliance
- 1.9K Data Science
- 449.7K Databases
- 221.5K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 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
- 24 JavaScript - Nashorn
- Programs
- 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
Oracle Apex - HTTP ERROR 200 Service Unavailable behavior
Hi,
In Oracle Apex 20.2, I have a dynamic PLSQL process I am testing in SQL Workshop > SQL Commands. It's about reading JSON data and executing multiple insert statements within a loop, so basically the code takes long to process. It takes so long to process that I had to click Page Unresponsive > Wait multiple times just to find out that I would get an error result. Please refer to below screenshots.
Page Unresponsive notice:
Error Result:
I also had this similar error in the past. There was an upload feature that was taking around 1.5hrs to process a file but after that the page just stopped and gave the error below:
The only difference between this error and the latter is the URI part. The former has a URI that ends with accept while the latter URI ends with show. But I think these errors are of the same essence.
Would anyone know what causes this type of behavior?
Any ideas or suggestions are appreciated!
-Jazz