Liferay Initiating Java -cp Process

[Sai Mohan Gadamsetty, geändert vor 6 Jahren.]

Hi All,

We are facing one issue during tomcat restart time, but this is not happening all the time. Java -cp process is initiating and its not stopping the process. Please find below on process details

java -cp /usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/annotations-api.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/catalina-ant.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/catalina-ha.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/catalina-tribes.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/catalina.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ecj-4.2.2.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/el-api.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/jasper-el.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/jasper.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/jsp-api.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/servlet-api.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-api.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-coyote.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-dbcp.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-i18n-es.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-i18n-fr.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-i18n-ja.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-jdbc.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/tomcat-util.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/activation.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/ccpp.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/hsql.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/jms.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/jta.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/jtds.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/junit.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/jutf7.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/mail.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/mysql.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/persistence.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/portal-service.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/portlet.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/postgresql.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/lib/ext/support-tomcat.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/MessageBox.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/abdera.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/activemq-all-5.5.1.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/alloy-taglib.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/ant.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/antlr2.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/antlr3-runtime.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/antlr3.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/aopalliance.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/asm-analysis.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/asm-commons.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/asm-tree.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/asm-util.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/asm-xml.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/asm.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/lib/aspectj-rt.jar:/usr/local/liferay-portal-6.1.2-ce-ga3/tomcat-7.0.40/webapps/ROOT/WEB-INF/l

I'm not understanding why this process has been initiated and not killing. Some one please help me on this issue.

[Juan Gonzalez, geändert vor 6 Jahren.]

Hi Sai.

The only place new processes are being created that I am aware of is Documents & Media preview feature.

Do you have some PDF or video files in documents & media (and Xuggler feature enabled)?

[Sai Mohan Gadamsetty, geändert vor 6 Jahren.]

Hi Juan,

Thanks for your reply.

We're having 2 environments connected through same lportal, one for Content Management and other for different business requirement.

One environment configured to use Image Magic, Open Office and Xuggler to generate previews and playing videos. But these are enabled via portal-ext properties rather from Control Panel setup.

In other environment all mentioned plugins are not installed and not enabled properties as well. From this environment we had the mentioned issue. Does this environment will get impacted with other environment used properties or third party plugins?

Please advise your thoughts/feedback.

[Olaf Kock, geändert vor 6 Jahren.]

Sai Mohan Gadamsetty:

We're having 2 environments connected through same lportal, one for Content Management and other for different business requirement

....

In other environment all mentioned plugins are not installed and not enabled properties as well. From this environment we had the mentioned issue. Does this environment will get impacted with other environment used properties or third party plugins?

Do I read this correctly as: You have two portals sharing the same database? This would need to be set up a cluster, otherwise weird things might (and will) happen. If you're doing different things on the other portal, you should have a different database. Period.

If you need to share content, consider staging (e.g. "authoring on one, publishing on the other") or just linking - after all, it's all just HTML/HTTP and a click away from each other.