function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
ReverendReverend 

ssl_error_rx_record_too_long running sample application

I am attempting to work with the oAuth example at:
https://github.com/jamesward/hello-java-spring-force_dot_com/

The application builds and launches just fine.  However, when I click the provided "Contact List from Salesforce.com" link I wind up getting the following error:

Secure Connection Failed

An error occurred during a connection to localhost:8080.
SSL received a record that exceeded the maximum permissible length.
(Error code: ssl_error_rx_record_too_long)


I would like to run the demo locally on my Linux and OSX boxes to test the configuration.

The basic launch command being used is:
java -jar target/dependency/webapp-runner.jar targe*.war


Does anyone have any suggestions on how to resolve this?
 
Aakaash NairAakaash Nair
Hi,

Not quite sure but I found these links that could help.

> http://support.hostgator.com/articles/ssl-certificates/error-ssl-received-a-record-that-exceeded-the-maximum-permissible-length

> http://stackoverflow.com/questions/8706741/ssl-received-a-record-that-exceeded-the-maximum-permissible-length-ff-django-st

Do let me know if this helps!

Thanks,
Aakaash
ReverendReverend
Unfortunately those don't solve the issue.  I tried those along with my first findings from some Google searchs to no avail.  I'm wondering if I need to add something to the Spring configuration for that project in order to get that to stop happening (validated certificate, etc.).  I installed JCE and BouncyCastle in the JVM as I am using them for other things within my development environment and I tried removing them to see if that was the issue without any luck.

I am probably just going to try it on Heroku to see what happens.
ReverendReverend
Everything works fine on Heroku.
It is definitely a local setup error.

I will have to look into the configuration options within my Java environment to set it up properly.
Aakaash NairAakaash Nair
Hi,

Please do let us know the set up chnages once resolved!

Thanks!
ReverendReverend
I finally got this working.
I reset my Jetty setup and instead of using
java -jar target/dependency/webapp-runner.jar targe*.war

I used a full Jetty launch.

I ensured that I was using the */etc/jetty-ssl.xml configuration.
In the configuration I updated the port to 8443 due to other errors and everything worked.