Open Microscopy Environment

Hi all,

In matlab, against omero 4.4.9 on a windows server, I encounter the following error randomly (i.e it would run correctly for a few hours and then crash). The omero logs show no error or warnings, and neither do the server logs... If anybody have any idea...

Code: Select all

Java exception occurred:
Ice.SecurityException
    reason = "IceSSL: handshake error"
   at IceInternal.ConnectRequestHandler.getConnection(ConnectRequestHandler.java:244)
   at IceInternal.ConnectRequestHandler.sendRequest(ConnectRequestHandler.java:141)
   at IceInternal.Outgoing.invoke(Outgoing.java:77)
   at Ice._ObjectDelM.ice_isA(_ObjectDelM.java:33)
   at Ice.ObjectPrxHelperBase.ice_isA(ObjectPrxHelperBase.java:98)
   at Ice.ObjectPrxHelperBase.ice_isA(ObjectPrxHelperBase.java:61)
   at Glacier2.RouterPrxHelper.checkedCast(RouterPrxHelper.java:2262)
   at omero.client.getRouter(client.java:748)
   at omero.client.createSession(client.java:671)
Caused by: javax.net.ssl.SSLException: Received fatal alert: bad_record_mac
   at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
   at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1639)
   at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1607)
   at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1776)
   at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1080)
   at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:884)
   at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:758)
   at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
   at IceSSL.TransceiverI.handshakeNonBlocking(TransceiverI.java:466)
   at IceSSL.TransceiverI.initialize(TransceiverI.java:43)
   at Ice.ConnectionI.initialize(ConnectionI.java:1933)
   at Ice.ConnectionI.message(ConnectionI.java:1084)
   at IceInternal.ThreadPool.run(ThreadPool.java:321)
   at IceInternal.ThreadPool.access$300(ThreadPool.java:12)
   at IceInternal.ThreadPool$EventHandlerThread.run(ThreadPool.java:693)
   at java.lang.Thread.run(Thread.java:722)


the diagnostics, in case it helps:

Code: Select all

================================================================================
OMERO Diagnostics 4.4.9-ice33-b98
================================================================================

WARNING:omero.util.UpgradeCheck:UPGRADE AVAILABLE:Please upgrade to 5.0.3 See http://trac.openmicroscopy.org.uk/omero fo
r the latest version

Commands:   java -version                  1.7.0     (C:\Program Files (x86)\Java\jre7\bin\java.EXE -- 2 others)
Commands:   python -V                      2.5.5     (C:\Python25\python.EXE)
Commands:   icegridnode --version          3.3.1     (C:\Ice-3.3.1\bin\icegridnode.EXE)
Commands:   icegridadmin --version         3.3.1     (C:\Ice-3.3.1\bin\icegridadmin.EXE)
Commands:   psql --version                 not found

Server:     icegridnode                    running
Server:     Blitz-0                        active (pid = 8968, enabled)
Server:     DropBox                        inactive (disabled)
Server:     FileServer                     active (pid = 8236, enabled)
Server:     Indexer-0                      active (pid = 5272, enabled)
Server:     MonitorServer                  active (pid = 5784, enabled)
Server:     OMERO.Glacier2                 active (pid = 5448, enabled)
Server:     OMERO.IceStorm                 active (pid = 2316, enabled)
Server:     PixelData-0                    active (pid = 5888, enabled)
Server:     Processor-0                    active (pid = 4944, enabled)
Server:     Tables-0                       inactive (disabled)
Server:     TestDropBox                    inactive (enabled)
Server:     OMERO.master                   active (running as LocalSystem)

OMERO:      SSL port                       4064
OMERO:      TCP port                       4063

Log dir:    C:\Users\omero\Desktop\OMERO.server-4.4.9-ice33-b98\var\log exists

Log files:  Blitz-0.log                    243.0 MB      errors=1    warnings=1

(...)

Environment:OMERO_HOME=(unset)
Environment:OMERO_NODE=(unset)
Environment:OMERO_MASTER=(unset)
Environment:OMERO_TEMPDIR=(unset)
Environment:PATH=C:\Windows\system32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin\;C:\Python25\;C:\Windo
ws\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Ice-3.3.1\bin;C:\Program
Files\MySQL\MySQL Server 5.1\bin
Environment:ICE_HOME=(unset)
Environment:LD_LIBRARY_PATH=(unset)
Environment:DYLD_LIBRARY_PATH=(unset)

OMERO data dir: 'E:\\OMERO'     Exists? True    Is writable? True
OMERO temp dir: 'C:\Users\omero\AppData\Roaming\omero\tmp'      Exists? True    Is writable? True   (Size: 0)
OMERO.web status... [NOT STARTED]


Hi

What's the full version of Java that you're using on the server and client (output of java -version)? In the past we've seen similar errors which were fixed by either a Java or an OpenSSL update.

Simon

Thanks, that could be it as I thinks java was updated recently...

Code: Select all

PS C:\Users\omero\Desktop\OMERO.server-4.4.9-ice33-b98> java -version
java version "1.7.0_45"
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) Client VM (build 24.45-b08, mixed mode, sharing)

How can I get the openssl version? Would it be shiped with ice? In which case I would have to update omero to use a newer ice, or downgrade/use an older java?

Thanks
A.

OpenSSL is bundled with Ice on Windows. I'd start by upgrading Java to the latest in the 1.7 series, and see if that fixes things.

Simon

HI all,

I still have the issue, although quite intermittently (like a few times per 96 well plate). I have java 1.7.0_67, omero 5.0.4-ice34 and ice 3.4.2 under windows server 2008, all latest workable version as of last month... Any ideas?

Many thanks
A.

Hi Anatole

The short answer we still have no idea what causes these issues. You could try updating to Java 1.8, though there's no guarantee this will improve things.

Simon

Thanks for the honesty
As I can't be bothered to fight another half week with windows, ice and IIS I'll pass on the upgrade for now. I'll just continue on errors and log them, it happens rarely enough.

A.