It is widely reported that I log on to the 64-bit server and the server is stuck (I don't know why)
So I decided to say goodbye to 64 for everyone's happiness. Haha.
I set up an environment on other servers, and everything went smoothly, because it has been set up many times,
However, when Tomcat is started at the end, when auto deploy restart started for/LTC/home/liferay/deploy is started, nothing will go down, and it won't be done after a long time,
Later, I asked a hacker in the group and finally got it done with your help. The solution is as follows:
Modify portal/portal-EJB/class/portal. Properties
# Set the following to true if you want to index your entire library of files on startup.
Index. on. startup = true
# Set the following to true if you want the indexing on startup to be
# Executed on a separate thread to speed up execution.
Index. With. Thread = false
Change the values of true and false, and then redeploy.
You can also use RAR open tomcat/webapps/root/WEB-INF/lib inside the portal-ejb.jar, the portal. properties drag out, modify and then drag back
. Or tomcat/webapps/root/WEB-INF/classes/portal-ext.properties, adding index. on. startup = false is also valid
In this way, you do not need to redeploy
However, despite the solution, Tomcat can be started and can be used normally, but there is an error: Error [javaseservlet: 102] Java at startup. io. ioexception: Lock obtain timed out: Lock @ C:/LTC/liferay4.2.2/tomcat/temp/lucene-a752935b5af5ef791728c018b499a4cb-write.lock
Not solved yet.