Tag: availability
Unspecified defaults can cause your application to crash.
Do not use API that requests system permission directly. Please onboard mShop Permission Service first.
Missing check on the value returned by moveToFirst API can cause your application to crash.
Deserializing objects from relational databases should allocate a 64-bit, not 32-bit, type for the auto-incremented identifier.
Custom manual retries of calls to AWS SDK APIs are inefficient.
Accessing the cache response metadata without performing a null
check might cause a null dereference error.
This code uses deprecated methods, which suggests that it has not been recently reviewed or maintained.
Reuse AWS clients in Lambda.
Recreating AWS clients in each Lambda function invocation is expensive.
Insecure ways of creating temporary files and directories can lead to race conditions, privilege escalation, and other security vulnerabilities.
Improper use of locks in a multi-threaded program can lead to deadlock and cause the program to be unresponsive.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.
Always call super.finalize
explicitly.
Failure to specify a content length causes the contents of the input stream to buffer locally in memory in order to calculate its length. This can result in performance problems.
Allocated resources are not released properly.
Getting a substring outside the range of a string can cause an index-out-of-bounds exception.
Public method parameters should be validated for nullness, unexpected values, and malicious values.
Improper use of thread-unsafe classes in multi-threaded programs can cause the programs to be unstable.
Provide the full URL for the Amazon SQS queue.
Missing check on the value returned by ResultSet.next can cause your application to crash.
To minimize the risk of error, use an enum instead of a string to specify an AWS Region.
Dereferencing a null pointer can lead to unexpected null pointer exceptions.
Atomicity violations caused by improper usage of ConcurrentHashMap
or ConcurrentLinkedQueue
can result in crashses or incorrect program results.
Your application can crash if the check for an application that can receive the implicit intent is missing from code.
Use loop control flow to ensure that loops are exited, even if exceptional behaviors are encountered.
Unhandled failures of deleting files can exhaust file handles.