버전 비교

이전 버전 24

changes.mady.by.user admin

에 저장

비교대상

새 버전 현재

changes.mady.by.user admin

에 저장

키

  • 이 줄이 추가되었습니다.
  • 이 줄이 삭제되었습니다.
  • 서식이 변경되었습니다.

...

Sv translation
languageen

This document describes how to register, edit or delete the MagicINFO Server service.

Register / Delete the service

You can add new or edit default options when running the service of MagicINFO Server.

For applying, you need to delete and register the related Windows service.

For example, in case the JVM is out of memory, you can change the size of heap memory or perm memory.

How to change the options

First, go to the path mentioned below and find "service.bat" file.

File path : {The path installed the MagicINFO Server}\tomcat\bin\service.bat


After opening the file with a text editor, move the page down and check the command under :installed. (Refer the below image)

You can specify or change the options that will be executed when the service is registed and started.

For the related options, refer the configuration of daemon execution.

The list of options : https://commons.apache.org/proper/commons-daemon/procrun.html

After modifying(adding/editing/deleting) the options related to daemon configuration, stop, delete and restart the registered service.

Execute in order : Stop the service → Delete the service → Install the service → Restart the service


TypeCommand
Delete serviceservice uninstall 
Install serviceservice install




Tomcat Configurations (modify server.xml)

You can modify the required settings for executing the web service when running Tomcat.

After opening below file with a text editor, modify the options that you need and save, and restart MagicInfoPremium service to take effect.

File path : {The path installed the MagicINFO Server}\tomcat\conf\server.xml


The descriptions of existing options

optiondescription
port

Specify a port number that the connector operates on. If the port is already in use, then you can change the port number to use.

maxHttpHeaderSize

If there is a lot of information in the HTTP Header, it needs to be modified according to the characteristics of the service. (The default value is 4KB)

maxThreads

It is a very important option. This option determines the number of threads in Tomcat. The number of threads means the number of active users. In other words, it means the number of transactions that can be processed at the same time.

Generally, the most appropriate value is around 100, and it is common to set around 50 to 500 depending on the weight of the transaction. It is better to adjust this value while tuning through a performance test.

acceptCount

This option defines the length of the request queue. When an HTTP request comes in, if there is no idle thread, this is the length of the queue waiting for the request until an idle thread is created in the queue. Normally, messages that piled up in the queue means that there is no thread available to process the request through the Tomcat instance, and it is likely that it is already in a disabled state and that requests cannot be processed even if all threads are used.

So, it is better to make the length of queue short rather than long. Because if requests cannot be processed any more, it's better to send an error code to clients as soon as possible to handle the error.

 If the length of the queue is long, the waiting time becomes longer. Then, there can be a case that the response is continuously waiting even in a failure situation and then propagated to another failure.

maxPostSize 

When using Tomcat, if too much data is sent in the post method, request data can be initialized(be null). So, when transmitting form data in the post method, if the size of form data exceeds 2M(default value), it must be set separately.

secure

SSLEnabled

sslProtocol

sslEnabledProtocols

The option is regarding SSL settings.

For more information, refer to the link below.

1.7 SSL/TLS 설정 가이드

정보

For more information, refer to the official Tomcat site.

Official site : https://tomcat.apache.org/tomcat-8.0-doc/config/http.html


Delete Tomcat cache

Basically, when a web-application is deployed by Tomcat, the cache is left.

Because of cache, when changes are made to the web-application file ({The path installed the MagicINFO Server}\server), it may not be applied properly.

In this case, delete all folders and files under the folders that cache is stored and restart the MagicINFO Server service.

경고

When you delete the cache, Tomcat may not run properly, so you must back up the folders before deleting just in case.


Folder path : tomcat\temp, tomcat\webapps, tomcat\work

Image Modified

Image Modified


How to check Tomcat log

To check the log about Tomcat operation, refer to the files under the folder "tomcat\logs".

You can figure out the problem of Tomcat operation and tune the settings based on the logs.

Image Modified


The types of log files

File nameDescription
catalina.YYYY-MM-DD.log

Server start, stop, service start, stop information (for Tomcat)

host-manager.logTomcat Host Manager Web app log (virtual host manager)
manager.logTomcat Manager Web App log (web console)
localhost.logHost (same to VirtualHost) limited log
commons-daemon.log

Daemon(background service) execution log

magicinfo*.log

Log for each products in MagicINFO


Tomcat Monitoring and how to tune

When you encounter problems such as slow operation of Magicinfo server, you can grasp the execution status of threads used by Tomcat and tune it according to the server execution status.


  1. Monitoring using Tomcat manager

      2. Tuning