1Ben Rose  27.01.2015 11:29:16  Notes/Domino 9.0.1 FP3 has shipped

I'm seeing a fault in the IBM Domino Console client since apply FP3 to my 9.0.1 client. It's unable to connect to any servers.

Anybody else seeing this issue?

2Ben Rose  27.01.2015 12:13:43  Notes/Domino 9.0.1 FP3 has shipped

To respond to myself, confirmed bug and an SPR already existed with IBM.

Hold off upgrading those admin clients, useless in its current form.

3Ben Rose  27.01.2015 16:24:23  Notes/Domino 9.0.1 FP3 has shipped

Follow up:

9.0.1 FP2 Domino Console can talk to 9.0.1 FP2 Domino server.

9.0.1 FP2 Domino Console can talk to 9.0.1 FP3 Domino server.

9.0.1 FP3 Domino Console can talk to 9.0.1 FP3 Domino server.

9.0.1 FP3 Domino Console can NOT talk to 9.0.1 FP2 Domino server or any previous version including 8.5.x

IBM suggested solution is to upgrade all Domino server to 9.0.1 FP3 - not an option here right now.

4Rejean Gosselin  27.01.2015 21:04:21  Notes/Domino 9.0.1 FP3 has shipped

I updated my Notes client to 9.0.1 FP3 today and I am able to see the console and sent commands ...

5Ben Rose  27.01.2015 21:15:45  Notes/Domino 9.0.1 FP3 has shipped

Rejean,

We aren't talking about admin client, we are talking about the jconsole.exe application.

6Thomas Höfer  28.01.2015 9:14:57  Notes/Domino 9.0.1 FP3 has shipped

CKEditor is not working anymore after installing FP3. After investigation, we found that the CKEditor oneui3 skin and plugin folders are missing! After reverting back to FP2 CKEditor works.

Does anybody have the same issue?

Thanks

7Ben Rose  28.01.2015 9:18:14  Notes/Domino 9.0.1 FP3 has shipped

Thomas,

IBM tell me that my java console issue is one of many caused by the upgrade of POODLE to close a known security vulnerability. They have apparently been flooded with calls.

As I interpret it, FP3 itself is all good but they included the POODLE upgrade in the bundle which broke lots of stuff. All the FP3 testing was done with the older version of POODLE.

Bad QA really.

8Thomas Höfer  28.01.2015 9:27:16  Notes/Domino 9.0.1 FP3 has shipped

Ben,

thanks for your response.

"Bad QA" - absolutely right!

9Ben Rose  31.01.2015 10:01:00  Notes/Domino 9.0.1 FP3 has shipped

Still being given the runaround by IBM support team, none of their suggestions so far have worked.

Really shocking QA there these days.

10Mike Ipkendanz  04.02.2015 14:32:17  Notes/Domino 9.0.1 FP3 has shipped

Hi, we can not update our windows 64bit server from 9.0.1FP2IF1 (Release901FP2HF384) to FP3. Windows Error:

[Window Title]

domino901FP3_w64.exe

[Main Instruction]

domino901FP3_w64.exe has stopped working

[Content]

A problem caused the program to stop working correctly. Please close the program.

There ar no entries in upgrade.log .-(

11Mike Ipkendanz  09.02.2015 12:09:10  Notes/Domino 9.0.1 FP3 has shipped

Hey, now we installed the fix pack successfully. The downloaded file was damaged

@ Daniel: Thanks for the tip with the downloaded file.

12Ben Rose  12.02.2015 9:15:21  Notes/Domino 9.0.1 FP3 has shipped

Just to follow up, IBM has no plans to fix the java console issue with FP3.

They've offered to make it a feature request for consideration in a future release - but with 9.0.2 already feature complete, we all know what this means.

I fight hard to keep this product within our company but if IBM can't even ship a working admin client then it's testing for even the most dedicated customers.

13Ben Rose  01.04.2015 14:33:55  Notes/Domino 9.0.1 FP3 has shipped

Two months, many escalations and one critsit later, we discover there was a solution available all along.

From support:

Per 9.0.1 FP3 SSL is disabled in the JVM, it is possible to enable this by setting the following the system property:

com.ibm.jsse2.disableSSLv3=false

This is documented in

{ Link }

The jconsole application uses an embedded JVM invoked via JNI so it is not possible to pass the above via the command line when starting jconsole. However, there is a general parameter that can be used to specify additional arguments when invoking embedded JVMs via JNI and one can set this as environment variable. Set the following as system variable on the workstation used to administer the servers:

Variable: JAVA_TOOL_OPTIONS

Value: -Dcom.ibm.jsse2.disableSSLv3=false

Tested and am able to connect from a 9.0.1FP3 jconsole to both 85x , 9.0.1 and 9.0.1FP3 servers.

14Daniel Nashed  02.04.2015 9:25:11  Notes/Domino 9.0.1 FP3 has shipped

@Ben, thanks for the feedback and solution.

From what I had read previously the IBM JVM team did completely remove SSLv3 and Oracle just disabled it by default.

So I wasn't looking for a workaround re-enabling SSLv3. But it sounds like it is just disabled and that Java option does enable it.

I will write up a new blog post to have the community aware. Thank's!!

Did you also test it with the newer JVM SR16 FP3?

15Ben Rose  02.04.2015 16:21:12  Notes/Domino 9.0.1 FP3 has shipped

I think you may have overlooked in my post, the jconsole application used an embedded JVM - the installed version on the client is irrelevant.

16Daniel Nashed  03.04.2015 6:10:20  Notes/Domino 9.0.1 FP3 has shipped

@Ben, oh I see. Interesting... I overread it because I would never have expexted that they use an additional JVM.

Thanks!