About this task
consumes CPU when there is no conversion request to the Document Format Conversion server, the consumption might be caused by a port conflict. Some ports that are needed by soffice.bin
might be in use by other applications. Currently the converter application does not return any response when the ports are occupied, so, it is difficult for the user to identify the issue. The server administrator can use special tools, such as cports
, to identify whether the ports are occupied. If the ports are occupied, the administrator can change conversion configurations to avoid the port conflict.
Parent topic: Troubleshooting and support
- Get conversion_install_root from the response file of your running Document Format Conversion server. See this page for details.
- Assume conversion_install_root is set to c:/IBM/IBMConversion.
- Modify instance.cfg:
- Find instance.cfg from C:\IBMConversion\symphony\sym_monitor\instance.cfg.
- Change the port number that has the conflict to a new port number.
- Modify conversion-config.json::
- Find the JSON file in C:\IBMConversion\config\conversion-config.json
- In the symphony.host-config, specify a new port.
- So that changes take effect, in a stand-alone environment, restart the Document Format Conversion server. In a cluster environment, restart the Document Format Conversion cluster.