Re: EM Java Support was (jdk16 to jdk17 frustration)

From: Chris Taylor <christopherdtaylor1994@xxxxxxxxx>
To: niall.litchfield@xxxxxxxxx
Date: Mon, 7 Mar 2016 11:08:01 -0600

Part of the issue with the JDK stuff was (or is) changes in the SSL
traffic.  I had to create a spreadsheet for the patches and figure where
the dependencies were.  Granted, this was a fresh install of 12.1.0.5 EM
after the browser makers had patched their browsers to prevent certain
types of traffic.

JSSE traffic really messes with the whole 12.1.0.5 stack I think.

Here's a bit from my spreadsheet (not the latest PSUs and Weblogic patches
now)

12.

13079846

Oracle JDK 1.7 u91  - See:

*How to Install and Maintain the Java SE Installed or Used with FMW 11g/12c
Products (Doc ID 1492980.1)
<https://support.oracle.com/epmos/faces/DocumentDisplay?id=1492980.1>*

*What Needs to Change in the Weblogic Server Startup Scripts After a JDK
Upgrade? (Doc ID 2014989.1)
<https://support.oracle.com/epmos/faces/DocumentDisplay?id=2014989.1>*

There’s a few ways to do this.  The best way is to create a centralized JDK
location and change the environment scripts to point to the new JDK home:

$MW_HOME/wlserver_10.3/common/bin/commEnv.sh (change line# 157)

$MW_HOME/gc_inst/user_projects/domains/GCDomain/bin/startEMServer.sh (line
103)

$AGENT_BASE/agent_inst/sysman/config/emd.properties

$AGENT_HOME/../core/12.1.0.5.0/stage/sysman/config/emd.properties

Or you can just replace the delivered JDKs with the new JDK:

$AGENT_BASE/../core/12.1.0.5.0/jdk

$MW_HOME/jdk16/jdk

$MW_HOME/Oracle_WT/jdk

13

12932224

Weblogic Patch for JSSE traffic using t3s?

14.

20124292

Note 1943873.1, Known Issues Document says to apply after JDK update - also
must enable HTTP Listen Port (7001) in Weblogic Admin Console
(EMGC_ADMINSERVER config)

To do this:

1. open the Weblogic Admin Console (https://machine:port/console), login as
weblogic, and goto your Environment->Servers Page

2. Click the EMGC_ADMINSERVER and then click the Configuration->General Tab.

3. Click the “Listen Port Enabled” and give it a port number – I used
7001.  This gives you HTTP port traffic to port 7001 which is necessary for
this patch (screenshot)

3. Reboot Weblogic (emctl stop oms -all)

4. When you deploy the ear file as part of the patch you will run:

$ORACLE_HOME/opmn/bin/opmnctl redeploy -adminHost *machine_name* -adminPort
7001 (as it cannot use the 7101 https port)

On Mon, Mar 7, 2016 at 3:09 AM, Niall Litchfield <niall.litchfield@xxxxxxxxx

wrote:

For various reasons, most of which I'm not entirely happy with, we'll be
applying every current appropriate PSU to our EM software stack (hey,at
least, we have a non-prod EM on which to screw up). I don't know if this
was the root of Dave's frustrations - it looks like some bad advice from
support in his case, but I can understand it if it was.

The "natural" to me approach was to look at Note 2074802.1
<https://support.oracle.com/epmos/faces/DocumentDisplay?id=2074802.1> (Patch
Set Update and Critical Patch Update Availability Document January 2016) .
That has a section for each release of EM.

In the EM section we have a table that includes *Base Platform Fusion
Middleware home *that refers us to the WebLogic part of the same document
that includes *Oracle Java SE home *that in turn contains a link to  Note
1492980.1: How to Maintain the Java SE Installed or Used with FMW 11g
Products
<https://support.oracle.com/epmos/faces/DocumentDisplay?parent=DOCUMENT&sourceId=2074802.1&id=1492980.1>
which
says contrary to the note Courtney references below.

"*It is always supported to update the JDK/JRE to the latest minor

version of an installed release" *

In addition, the FMW note references the procedure Dave describes of
installing in a new home and updating the java path in various files. The
EM specific note suggests backing up the old JDK and replacing with the new
one.

For anyone like me who may have to patch the entire EM stack, it would be
nice if MOS had a note along the lines of 1492980.1 *Note XXXXXX.1 How to
maintain the EM software stack*, rather than a set of links to notes
designed for each component from which one has to reconstruct the whole
picture. That would also likely be useful for cases such as Dave's.

On Thu, Feb 11, 2016 at 7:35 PM, Courtney Llamas <
courtney.llamas@xxxxxxxxxx> wrote:

Have you contacted support?   EM 12.1.0.x does not support JDK 1.7, you
can only go to the latest of JDK 1.6…

[image: https://mosemp.us.oracle.com/epmos/adf/images/t.gif]

*How to Upgrade JDK to 1.6 Update 95 on OMS 12.1.0.4 or 12.1.0.5 (Doc ID
2059426.1)*

*From:* Timur Akhmadeev [mailto:timur.akhmadeev@xxxxxxxxx]
*Sent:* Thursday, February 11, 2016 2:00 AM

*To:* Herring, David
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: jdk16 to jdk17 frustration

In this case I'd try to find something more from emctl logs/trace files
if those are available. Looks like there are ways to configure them:
https://blogs.oracle.com/EMMAA/entry/maintaining_trace_and_log_files

Depending on what/how exactly emctl tries to start and where exactly this
fails you can go further.

Also I'd try to start NM manually directly and see if this works or not,
what's in logs, etc.

On Wed, Feb 10, 2016 at 8:10 PM, Herring, David <HerringD@xxxxxxx> wrote:

I'm actually not starting NM directly but indirectly from the OMS start
-> $OMS_HOME/bin/emctl start oms.  The various components start until it
gets to NM and that's when it fails.  This happens shortly after the
Webtier starts and I've confirmed this by using "strace" to track progress
as best I can.  In the output I can see opmn commands completing but then
not a whole lot of help until NM fails.  The NM process actually gets
created but that's it.

Regards,

Dave

*From:* Timur Akhmadeev [mailto:timur.akhmadeev@xxxxxxxxx]
*Sent:* Wednesday, February 10, 2016 1:47 AM
*To:* Herring, David
*Cc:* oracle-l@xxxxxxxxxxxxx
*Subject:* Re: jdk16 to jdk17 frustration

Hi,

so you try to start NM and it fails with NoClassDefFoundError?

can you show full texts of how you actually start Node Manager and full
content of its out files right from the start.

On Wed, Feb 10, 2016 at 2:01 AM, Herring, David <HerringD@xxxxxxx> wrote:

Folks, I have an SR open w/ Oracle that appears to be going nowhere so
I'm hoping that someone can at least lead me in a direction where I'll make
progress.  Here's the situation (all in the context of EM 12c):

·         We're having issues with our WL Admin console page and I
opened an SR to resolve the problem.

·         I was told to upgrade JDK which should resolve the problem.
Right now our various versions in the EM stack are:

o   OMS 12.1.0.5.160119

o   WebLogic 10.3.6.0.13

o   JDK 1.6.0_43

·         In trying to upgrade to JDK 1.7.0_95 I wanted to avoid a
release-specific path.  Right now JDK1.6 sits under $MW_HOME/jdk16/jdk.  As
part of the move to JDK1.7 I want to start using $MW_HOME/jdk, as I'm
assuming in the future any JDK upgrades would be specific to FMW for EM.

·         I followed MOS docs 1309855.1 and 1616397.1 to make sure I
covered everything necessary.  As far as I can tell all that's involved is
stopping processes, plopping the new release in a directory, updating key
files to point to this new directory and start everything back up.

When I start up the OMS I get the following:

Node Manager Could Not Be Started

Check Node Manager log file for details:
.../NodeManager/emnodemanager/nodemanager.log

Oracle Management Server is Down

Exception in thread "main" java.lang.NoClassDefFoundError:
oracle/jdbc/OraclePreparedStatement

The nodemanager.log file isn't very helpful, giving me the following over
and over:

<Feb 9, 2016 6:58:59 AM> <WARNING> <I/O error while closing socket
connection>

java.net.SocketException: Connection reset

       ...

Has anyone successfully upgraded the JDK and in the process moved
$JAVA_HOME to a new location from the base install of EM?  Does anyone know
a way to get more information out of NM as to why he's failing?

I'm sure someone is going to ask:

·         Why are you upgrading JDK?  The whole EM stack is suppose to
be a black box?  Answer: I'd love to NOT upgrade JDK but it's per a request
of Oracle to resolve a different issue.

·         Why place the new JDK under $MW_HOME?  Why not keep it
completely out of the EM software directories?  Answer: I can see the point
and to tell the truth I didn't think of that initially.  Currently this is
an EM-only host so JDK has no point other than with EM.

Regards,

Dave

--

Regards
Timur Akhmadeev

--

Regards
Timur Akhmadeev

--
Niall Litchfield
Oracle DBA
http://www.orawin.info

References:
- EM Java Support was (jdk16 to jdk17 frustration)
  - From: Niall Litchfield

Re: EM Java Support was (jdk16 to jdk17 frustration)

Other related posts: