iPortal FAQ

A: There are the following possible reasons: (1) Check whether you have installed Kingsoft anti-virus software. Running the Kingsoft may cause the iPortal service to crash. (2)The Tomcat 7.0.29 will cause memory leaks, please change to other Tomcat versions, such as Tomcat 7.0.26.

A: When creating thread in the pool, a physical thread will be created in the operating system. For certain machines with inadequate memory, the memory needed for operating system to create physical thread will compete with Java virtual machine heap memory when the amount of registered data and visits are large, and the system needs to deal with high concurrent requests, resulting in creating threads failed (The maximum memory of Java virtual machine of iPortal 32-bit package is assigned 512M by default, the maximum thread number is 300). To solve the problem, you can: (1) Reduce the memory assigned to Java virtual machine by changing Java virtual machine parameter. For example, changing JAVA_OPTS " in %SuperMap iPortal_HOME%/bin/catalina.bat to a smaller value like -Xmx512. (2) Reduce the active threads of Tomcat connection pool by changing maxThreads in %SuperMap iPortal_HOME%/conf/server.xml to a smaller value.

A: SuperMap iPortal package are deployed in Tomcat by default, Tomcat uses the 8090, 8015 ports by default, if any of the ports are occupied, you can not start the normal service. You can this problem in two ways below: (1) Quit the program that takes the port and restart SuperMap iPortal. Currently known procedures that may occupy 8090 port are: The automatic upgrade program of 360 anti-virus software. (2) Modify the Tomcat port number in SuperMap iPortal package and restart SuperMap iPortal. Go to % SuperMap iPortal_HOME% / conf / server.xml, modify the related ports in it, such as:

A: SuperMap iPortal needs configuring JRE 1.8 or higher, and the license. In the catalog of %SuperMap iPortal_HOME%\bin, you can check the version and configuration information of SuperMap iPortal by using “iportal.bat -v” ("./iportal.sh -v" for Linux/Unix). The possible reasons and solutions are: (1) Use the right license and make sure the license is properly configured. Please refer to Configuring the License. (2) The JRE/JDK version is too low or incompatible. Please download JRE/JDK1.8 or higher and set the environment variables.