Its not just old, its EOL (End of Life)
Java 6, and Java 7, are also EOL (by Oracle)
All SSL on Java (through Java 7) is also EOL (again, by Oracle).
You don't even have the current support level of TLS/SSL as built into today's browsers.
There have been literally well over 600 CVE's fixed in Java specifically with regards to TLS/SSL since Java 6.
At this point your environment is vulnerable to a countless number of attack vectors.
That being said, the most common reasons for what you are encountering ...
- minimum cipher suites in use by the general web, are much more aggressive on memory now, you need to allocate more to your process.
- don't run a 32-bit JVM in production, esp with SSL enabled, you'll hit the memory limit of 32-bit processes quicker than you expect.
- many of these sorts of errors are from people exploring your vulnerabilities and tripping up the ancient SSL implementation you are running, you cannot mitigate these sorts of errors in code or configuration, only by updating the JVM itself.