Java Reporting Tools Finereport Common errors encountered in use and solutions (i)

Common errors encountered in Finereport use and solutions (i)

Here to write a point, I hope we can put their own problems and solutions to dry out, mark, the benefit of self-interest.

There is a problem first search the document there is no, then look at the degree Niang have no, then see the forum there is no. Have an error to read the log. The following is a brief list of common problems, most of which are mentioned in the document.

1. Address pool is full:

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

Workaround:

If the connection pool properties in the Finereport settings, the maximum number of connections has been set too large, and also appear as an error, this is usually the database process (processes) reached the upper limit, you can increase the number of connections in the database to resolve this problem. Modify the maximum number of connections in the database as follows:

Select Count (*) from v$process view current number of connections

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

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

Restart the database and then query the maximum number of connections, and the number changes to indicate that the modification was successful.

Note: When the customer releases the database connection, first determine whether the number of references to the connection has exceeded the specified value, if the connection is deleted more than the current connection pool, and determine whether the total number of connections is less than minconn (minimum number of connections), if less than the connection pool is full, if not over the connection is marked as open state, Available for re-use. It can be seen that this strategy ensures the effective reuse of database connections, and avoids the overhead of establishing and releasing the system resources of the connection frequently.

2, the use of unregistered features:

Meaning:

Unregistered versions are available to try out all the features. The registered LIC is checked by the function point, if the template used the unregistered function will be reported this error. Generally easy to distinguish, some customers may be forbidden error interface, so the test is good, one put on the server will not come out, no error interface is not easy to find.

Workaround: In a formal environment where a purchase has been registered, the feature is not available if some features are not purchased.

If you want to know what features you have purchased, you can open the Web server and enter it in the browser: Http://localhost:8075/WebReport/ReportServer?op=fs Enter the FR system interface, click Manage System > The registration Information > features list allows you to see which features are supported by this release, such as:

3, Prompt registration:

Meaning: The unregistered version is used.

Workaround: Registration FAQ Processing Method: http://www.finereporthelp.com/help/9/4.html

4. Session timed out:

Meaning: Session timed out.

WORKAROUND: Set the session sticky, through configuration file configuration, will establish a connection between the server in the cluster, when the server receives the request, found that the session of the request is not generated by itself, then it will be based on the information in the request to determine which server the session is generated. It then forwards the request over the intranet to the appropriate server for processing. This is equivalent to the implementation of the Java EE cluster session sticky function. Specific operational Parameters Document: server cluster configuration steps.

Java Reporting Tools Finereport Common errors encountered in use and solutions (i)