Exception handling in EJB

[KennedII]

Hi all,

I am build a project in JAVA. With J2EE a Enterprise Development Platform of choice, more and more applications based on J2EE will be put into production. J2EE platform, is one of the important components of enterprise Java Bean (EJB) API. Together with J2EE and EJB technology offer many advantages, but also comes with some new challenges. The issue with EJB exception handling. Please suggest some trick. Thanks in advance.

[Zecho]

In the hello-world situations, the exception handling is very simple. Every time when you encounter an unusual approach, we catch the exception and print a stack trace or a statement that this method throws an exception. Unfortunately, this method is not sufficient to cope with reality in the various types of exceptions occur. In the production system, when there is an exception thrown, it will probably be the end-user can not handle his or her request. When this exception occurs when the end-users typically expected to be like this:
#There is a clear message that an error has occurred
#There is a unique error number, he could then access can easily access customer support system
#The problem is resolved quickly, and can be confident that his request has been processed, or will be dealt with at a set time period.

[Reegan]

Enterprise class system will not only provide these basic services, will be ready for the necessary back-end system. For example, the customer service team should receive immediate error notification to the customer service representative to call for help before the problem can be realized. In addition, the service representative should be able to cross-reference the user's unique error number and product logs to quickly identify problems the problem is best able to locate the exact line number or the exact method. In order to end-users and support teams they need the tools and services, to build a system, you will need to be deployed on the system could possibly go wrong after all parts of an idea. All the best.

[opaper]

To resolve system errors is to establish a production system constructed with the same test system, and then track all of the code lead to an exception thrown, as well as all the different branches of the code. In a distributed application, is likely to be the debugger does not work, so, you may use System.out.println () method of tracking an exception. System.out.println Although very convenient, but a huge overhead. In the disk I / O period, System.out.println pairs of I / O processing of synchronization, which significantly reduces the throughput. Check and reply.

[MindSpace]

when the product J2EE application server is restarted, this file may also be rewritten.The principle of exception handling is here are some generally accepted principles of exception handling:
# If you can not handle an exception, then do not catch it.
# If you catch an exception, please do not casually deal with it.
# An exception was thrown as far as possible in close proximity to the local catch the exception.
# Catch exceptions in places where it recorded in the log, unless you intend to throw it back.
Best of luck.

[Modifier]

In EJB there are many type of exception. I will discuss some exception below:
JVM Exception: This type of exception thrown by the JVM. Out Of MemoryError exception is the JVM a common example. Exceptions to the JVM you are powerless. They showed that a deadly situation. The only decent way out is to stop the application Servers, and then restart the system.
Application Exception: Application exception is a custom exception, by the application programs or third-party libraries throw. These are essentially unchecked exception ; which indicate the business logic in a condition that remain unmet. In such circumstances, EJB method call can gracefully handle this situation and adopt another one alternate route.