Per Tomcat in the Grid Infrastructure Home (Doc ID 2655066.1) - it appears
that Tomcat will run out of the GI Home in a specific set of cases - one of
which is the one alluded to by Timur - RHP (now known as FPP)
ACFS does not seem to spring out of the listed use cases for GI to be
running Tomcat...(Qos, FPP / RHP, Memory Guard and TFA are listed)
The workaround suggested in 2570547.1 was around Bug 27768034 - which
should have been fixed in 19.1
Thanks,
--Rajesh
On Thu, May 6, 2021 at 9:20 AM Timur Akhmadeev <timur.akhmadeev@xxxxxxxxx>
wrote:
Hi Nenad,
I've 19.9 at hand and see OraJavaAgentDriver present. According to 2570547.1
it should be gone with
srvctl stop cvu
srvctl disable cvu
srvctl status cvu
I don't see Tomcat running here and the closest hit on MOS is 30386318.8
which mentions RHP, so I'd look around rhpctl.
Plus I'd try killing the process a few times to see what's in GI logs if
it's restarted. And also check the process' file descriptors to see if
there's any clue why the hell Oracle Corp wants it running.
HTH
On Thu, May 6, 2021 at 2:57 PM Noveljic Nenad <nenad.noveljic@xxxxxxxxxxxx>
wrote:
Two Java processes are running under 19c Grid Infrastructure, one of
which is Tomcat:
grid 4605 1 0 Mar26 ? 05:29:07
/u00/oracle/GI/product/19.3.0/jdk/bin/java -Xms128M -Xmx384M -classpath
/u00/oracle/GI/product/19.3.0/jdk/jre/lib/rt.jar:/u00/oracle/GI/product/19.3.0/jdk/jre/lib/i18n.jar:/u00/oracle/GI/product/19.3.0/jlib/jagent.jar:/u00/oracle/GI/product/19.3.0/jlib/srvm.jar:
-Dora.jagent.conf=conf/orajagent.conf oracle.jagent.core.OraJavaAgentDriver
grid 4693 1 0 Mar26 ? 01:55:43
/u00/oracle/GI/product/19.3.0/jdk/bin/java -server -Xms128M -Xmx384M
-Djava.awt.headless=true -Ddisable.checkForUpdate=true
-Djava.util.logging.config.file=/u00/oracle/GI/gridbase/crsdata/lsdbp05i/qos/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-DTRACING.ENABLED=false -Djava.rmi.server.hostname=host
-Doracle.http.port=8888 -Doracle.jmx.port=8895 -Doracle.tls.enabled=false
-Doracle.jwc.tls.http.enabled=false -Djava.security.manager
-Djava.security.policy=/u00/oracle/GI/gridbase/crsdata/host/qos/conf/catalina.policy
-Djav .security.egd=file:/dev/urandom
-Dcatalina.home=/u00/oracle/GI/product/19.3.0/tomcat
-Dcatalina.base=/u00/oracle/GI/gridbase/crsdata/host/qos
-Djava.io.tmpdir=/u00/oracle/GI/gridbase/crsdata/host/qos/temp
-Doracle.home=/u00/oracle/GI/product/19.3.0 -Doracle.jwc.mode=CLUSTERWARE
-classpath
/u00/oracle/GI/product/19.3.0/jlib/cryptoj.jar:/u00/oracle/GI/product/19.3.0/jlib/oraclepki.jar:/u00/oracle/GI/product/19.3.0/jlib/osdt_core.jar:/u00/oracle/GI/product/19.3.0/jlib/osdt_cert.jar:/u00/oracle/GI/product/19.3.0/tomcat/lib/tomcat-juli.jar:/u00/oracle/GI/product/19.3.0/tomcat/lib/bootstrap.jar:/u00/oracle/GI/product/19.3.0/jlib/jwc-logging.jar
org.apache.catalina.startup.Bootstrap start
They presumably belong to the Grid Infrastructure Bundled Agent, which
manages application failovers.
As we don’t need that, is there a way to disable this?
We strive to keep our footprint small. The only reason that we installed
Clusterware is because we’re storing our database file on ACFS, which,
sadly, doesn’t seem to be supported with Oracle Restart (even though it
basically works).
Best regards,
Nenad
____________________________________________________
Please consider the environment before printing this e-mail.
Bitte denken Sie an die Umwelt, bevor Sie dieses E-Mail drucken.
Important Notice
This message is intended only for the individual named. It may contain
confidential or privileged information. If you are not the named addressee
you should in particular not disseminate, distribute, modify or copy this
e-mail. Please notify the sender immediately by e-mail, if you have
received this message by mistake and delete it from your system.
Without prejudice to any contractual agreements between you and us which
shall prevail in any case, we take it as your authorization to correspond
with you by e-mail if you send us messages by e-mail. However, we reserve
the right not to execute orders and instructions transmitted by e-mail at
any time and without further explanation.
E-mail transmission may not be secure or error-free as information could
be intercepted, corrupted, lost, destroyed, arrive late or incomplete. Also
processing of incoming e-mails cannot be guaranteed. All liability of
Vontobel Holding Ltd. and any of its affiliates (hereinafter collectively
referred to as "Vontobel Group") for any damages resulting from e-mail use
is excluded. You are advised that urgent and time sensitive messages should
not be sent by e-mail and if verification is required please request a
printed version.
Please note that all e-mail communications to and from the Vontobel Group
are subject to electronic storage and review by Vontobel Group. Unless
stated to the contrary and without prejudice to any contractual agreements
between you and Vontobel Group which shall prevail in any case,
e-mail-communication is for informational purposes only and is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction.
The legal basis for the processing of your personal data is the
legitimate interest to develop a commercial relationship with you, as well
as your consent to forward you commercial communications. You can exercise,
at any time and under the terms established under current regulation, your
rights. If you prefer not to receive any further communications, please
contact your client relationship manager if you are a client of Vontobel
Group or notify the sender. Please note for an exact reference to the
affected group entity the corporate e-mail signature. For further
information about data privacy at Vontobel Group please consult
www.vontobel.com.
--
Regards
Timur Akhmadeev
