Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by shadowknight, 1 year ago
Received close_notify during handshake [Root exception is javax.net.ssl.SSLException: Received close_notify during handshake]oracle.oc4j.rmi.OracleRemoteException: Unable to failover
javax.naming.CommunicationException: Received close_notify during handshake [Root exception is javax.net.ssl.SSLException: Received close_notify during handshake]oracle.oc4j.rmi.OracleRemoteException: Unable to failover	at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.getReplacementObject(RecoverableRemoteInvocationHandler.java:68)	at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.handleRecovery(RecoverableRemoteInvocationHandler.java:41)	at com.evermind.server.rmi.RecoverableRemoteInvocationHandler.invoke(RecoverableRemoteInvocationHandler.java:30)	at com.evermind.server.ejb.StatefulSessionRemoteInvocationHandler.invoke(StatefulSessionRemoteInvocationHandler.java:31)	at __Proxy8.getEvents(Unknown Source)	at oracle.oc4j.admin.jmx.client.MBeanServerEjbRemoteSynchronizer.getEvents(MBeanServerEjbRemoteSynchronizer.java:530)	at oracle.oc4j.admin.jmx.client.CoreRemoteMBeanServer.getEvents(CoreRemoteMBeanServer.java:319)	at oracle.oc4j.admin.jmx.client.EventManager.run(EventManager.java:217)	at oracle.oc4j.admin.jmx.client.ThreadPool$ConfigurableThreadImpl.run(ThreadPool.java:303)