Portal and Orient DB services not running

Document ID : KB000071344
Last Modified Date : 19/02/2018
Show Technical Document Details
Issue:
Not able to connect to portal as Portal and Orient DB services not running. I did upgrade (setup_CA Test Data Manager Portal4.4.0.10.exe) from TDM 4.2 and unable to start OrientDB service.

ERROR:
************
INFO  OrientDB auto-config DISKCACHE=3,641MB (heap=3,641MB direct=3,641MB os=16,383MB), assuming maximum direct memory size equals to maximum JVM heap size [OMemoryAndLocalPaginatedEnginesInitializer]
WARNI MaxDirectMemorySize JVM option is not set or has invalid value, that may cause out of memory errors. Please set the -XX:MaxDirectMemorySize=16383m option when you start the JVM. [OMemory]
INFO  Listening http connections on 127.0.0.1:2480 (protocol v.10, socket=default) [OServerNetworkListener]
WARNI Port 127.0.0.1:2480 busy, trying the next available... [OServerNetworkListener]
SEVER Unable to listen for connections using the configured ports '2480' on host '127.0.0.1' [OServerNetworkListener]
Environment:
Upgrade from TDM portal 4.2 to 4.4
Cause:
The new installed when we upgrade results in port change from 2424 to 2480 for binary,
In orientdb-server-config.xml below are the changes and that was the issue for Orient DB. 

<listener protocol="binary" socket="default" port-range="2424" ip-address="127.0.0.1"/> 
<listener protocol="http" socket="default" port-range="2480" ip-address="127.0.0.1"> 
Resolution:
Change the port number from 2424 to 2480 in orientdb-server-config.xml to resolve the issue.