I second that. It would be really great if this and some other bugs reported
against Resin 3.1.x could be addressed after the next 4.0.1 release. Many
companies must run a stable and feature-complete application server in their
mission critical environments and therefore can not get into the
On Jul 24, 2009, at 12:52 PM, Steffen Busch wrote:
I second that.
It would be really great if this and some other bugs reported
against Resin 3.1.x could be addressed after the next 4.0.1 release.
Many companies must run a stable and feature-complete application
server in their mission
Thanks for adding the notes to issue 3431. I was hoping that Scott and
Emil could chime in where I think the changes need to happen. We're
wanting to implement 3.1.6 (up to 3.1.9) in our production environments,
and this change is key to that development.
If this is a logical place to start,
Howdy,
Please refer to:
http://bugs.caucho.com/view.php?id=3431 (which is a reopen of)
http://bugs.caucho.com/view.php?id=2360
We're using Resin Pro 3.1.6 and trying to limit the cipher suites for
JSSE. I couldn't find the documentation, but through trial and error was
able to discover that