A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
Arduino in Action
this week in the
A special promo:
Enter your blog post or vote on a blogger to be featured in an upcoming Journal
Joined: Jul 01, 2002
Mar 09, 2006 18:52:00
I am running RMI over SSL using custom Socket Factory.
When I keep my client idle for few seconds, I get the following exception.
How can I keep my rmi connection from not getting expired?
Error: -------- RMI ConnectionExpiration- 10.210.54.74:3698,com.SecureClientSocketFactory@131303f], called close() RMI ConnectionExpiration- [10.210.54.74:3698,com.SecureClientSocketFactory@1313 03f], called closeInternal(true) RMI ConnectionExpiration- [10.210.54.74:3698,com.SecureClientSocketFactory@131303f], SEND TLSv1 ALERT: warning, description = close_notify Plaintext before ENCRYPTION: len = 18 RMI ConnectionExpiration- [10.210.54.74:3698,com.SecureClientSocketFactory@1313 03f], WRITE: TLSv1 Alert, length = 18
I agree. Here's the link:
- if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
subject: RMI ConnectionExpiration
Question about SSL debug test
Activation setup problem
SOAPException= SOAP-ENV:Client, Error opening socket: null
Web Service Client & Certificate
The server sent HTTP status code -1
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2013