RE: jdk16 to jdk17 frustration

From: Courtney Llamas <>
Date: Thu, 11 Feb 2016 11:35:35 -0800 (PST)
Message-ID: <529955a3-b23a-4790-92f8-bf3ae793a67b_at_default>

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…

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



From: Timur Akhmadeev [] Sent: Thursday, February 11, 2016 2:00 AM To: Herring, David
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:

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 <HYPERLINK "" \> 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.






From: Timur Akhmadeev [mailto:HYPERLINK "" \] Sent: Wednesday, February 10, 2016 1:47 AM To: Herring, David
Cc: HYPERLINK "" \ Subject: Re: jdk16 to jdk17 frustration




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 <HYPERLINK "" \> 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

o   WebLogic

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> 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.







Timur Akhmadeev



Timur Akhmadeev

Received on Thu Feb 11 2016 - 20:35:35 CET

Original text of this message