Java report tool FineReport Common Errors and solutions (1), javafinereport

Java report tool FineReport Common Errors and solutions (1), javafinereport
Common Errors encountered during use of FineReport and solutions (1)

I hope that you can solve your own problems and solve them. Mark them to benefit yourself.

 

If any problem occurs, first search for the document, and then check whether du Niang is there, and then check whether there is a forum. If an error is reported, the log must be viewed. Below is a simple list of common problems that are mentioned in most documents.

 

1. address pool is full:

Meaning: The address pool is full and the number of connections exceeds the maximum number of concurrent connections.

Solution:

If the maximum number of connections has been set too large in the connection pool attribute setting of FineReport, the above error is reported, which is usually caused by the database process (processes) reaching the upper limit, this problem can be solved by increasing the number of connections in the database. Modify the maximum number of connections in the database as follows:

Select count (*) from v $ process to view the current number of connections

Select valuefrom v $ parameter where name = 'processs' view the maximum number of connections allowed by the database

Alter system setprocesses = 300 scope = spfile; modify the maximum number of connections

Restart the database and query the maximum number of connections. If the number is changed, the modification is successful.

Note: When a customer releases a database connection, the customer first determines whether the reference times of the connection have exceeded the specified value. If the connection times exceed the specified value, the user deletes the connection, determine whether the total number of connections in the current connection pool is smaller than minConn (minimum number of connections). If the number is smaller than minConn, the connection pool is full. If the number does not exceed, the connection is marked as open for reuse. It can be seen that this policy ensures the effective reuse of database connections and avoids system resource overhead caused by frequent connection establishment and release.

 

2. Unregistered features are used:

Meaning:

You can try all functions of an unregistered version. The registered lic check box is selected. This error is returned if the created template uses the unregistered function. It is generally easy to tell. Some customers may disable the Error Reporting interface. This is a good test. The interface will be unavailable as soon as it is put on the server, and it will not be easy to find it if there is no error reporting interface.

Solution: if you have not purchased some features in the formal environment where you have registered and purchased them, the feature is unavailable.

If you want to know what functions are available in the purchased version, open the Web server and enter: http: // localhost: 8075/WebReport/ReportServer in the browser? Op = fs To Go To The FR system interface, click Management System> Registration Information> function list to see which functions are supported by this version, such:

 

 

3. Registration prompt:

Meaning: an unregistered version is used.

Solution: register common problem solution: http://www.finereporthelp.com/help/9/4.html

 

4. session timed out:

Meaning: The session times out.

Solution: Set session stickiness. Through the configuration of the configuration file, a connection is established between the server in the cluster. When the server receives a request, it finds that the session of this request is not generated by itself, based on the information in the request, the system determines which server generates the session. Then it forwards the request to the corresponding server through the Intranet for processing. This is equivalent to implementing the session sticking function of the J2EE cluster. Detailed operation parameter documentation: server cluster configuration steps.