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 666705, 1 year ago
via Oracle Community by User9954330-Oracle, 1 year ago
via Oracle Community by 666705, 1 year ago
via Oracle Community by Salaam, 1 year ago
via Oracle Community by 673897, 1 year ago
via Oracle Community by Pete Town - Everest, 1 year ago
java.lang.Exception: New alert stack	at com.certicom.tls.record.alert.Alert.(Unknown Source)	at com.certicom.tls.interfaceimpl.TLSConnectionImpl.closeWriteHandler(Unknown Source)	at com.certicom.tls.interfaceimpl.TLSConnectionImpl.close(Unknown Source)	at javax.net.ssl.impl.SSLSocketImpl.close(Unknown Source)	at weblogic.socket.SocketMuxer.closeSocket(SocketMuxer.java:287)	at weblogic.socket.SocketMuxer.cancelIo(SocketMuxer.java:603)	at weblogic.socket.SocketMuxer.access$100(SocketMuxer.java:31)	at weblogic.socket.SocketMuxer$TimeoutTrigger.trigger(SocketMuxer.java:806)	at weblogic.time.common.internal.ScheduledTrigger.run(ScheduledTrigger.java:243)	at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)	at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)	at weblogic.time.common.internal.ScheduledTrigger.executeLocally(ScheduledTrigger.java:229)	at weblogic.time.common.internal.ScheduledTrigger.execute(ScheduledTrigger.java:223)	at weblogic.time.server.ScheduledTrigger.execute(ScheduledTrigger.java:50)	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)