Discussions
Categories
- 196.7K All Categories
- 2.2K Data
- 235 Big Data Appliance
- 1.9K Data Science
- 449.8K Databases
- 221.6K 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.9K SQL & PL/SQL
- 21.3K SQL Developer
- 295.4K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.1K Development Tools
- 104 DevOps
- 3.1K QA/Testing
- 645.9K Java
- 28 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
- 158 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
- 395 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
- 1.1K Español
- 1.9K Japanese
- 230 Portuguese
"Error: error - Service Unavailable" after Dynamic Actions - Execute Server-side Code
How can I avoid the below error when firing off multiple (< 5) Ajax calls using Dynamic Actions - Execute Server-side Code?
Are the requests timing out? Hitting some kind of limit?
I've tried setting "Wait For Result" to 'No' but that didn't seem to help. I'm on Oracle's AutoTP DB.
Answers
-
You may be able to resolve this by debugging your code. This looks like a serious error on the database side, like running out of space.
-
I don't get anything in debug i'm afraid, also this only happens on one page where multiple "Execute Server-side Code" DAs fire, other pages with a single DA or no DA work fine.
The DB in question is at 80% storage utilization, CPU utilization usually peaks at 30% but on average sits around 5%, while testing for the error, session count (interval of 1 min) has been between 25 and 35.
-
The problem is probably your code, but without having access to your code and environment, it is hard to tell.
Keep putting additional debug messages in your code to trace the problem.
-
I only had debug set to app trace, after setting to full trace it's logging:
Cursor leak: difference in "opened cursors current" is 1:
The errors were coming back too fast before but under full trace and mid the DAs firing, refreshing another open APEX page displays:
503 Service Unavailable
ORDS was unable to make a connection to the database.
This can occur if the database is unavailable, the maximum number of sessions has been reached or the pool is not correctly configured.
With all that I think I found the problem, the DAs were firing "Clear" actions against items with "Cascading List of Values" already set, some of these actions were 3 'levels' deep so the number of times the "Execute Server-side Code" actions were getting fired was multiplied between 2 and 4 times depending on the level.
Still, the total number of "Execute Server-side Code" actions fired in quick succession must have been less than 15 which I would of thought be easily handled by the database. I assume APEX or ORDS chokes at some point before any programmed limitations are hit.
-
Still, the total number of "Execute Server-side Code" actions fired in quick succession must have been less than 15 which I would of thought be easily handled by the database.
Do you have any Set Value DA's? Check property Suppress Change Event. If it is set to No, you may get an infinite loop if items are mutually dependent.
-
It's a good call but no items are mutually dependant, DAs cascade 'down' the page and don't refer back 'up'.
