On 14 okt 2013, at 10:56, Christopher Brown
wrote:
> Hello,
>
> Thanks, the -XX:+StartAttachListener option did the trick.
>
> I'm assuming that this is a cross-platform switch, with nothing OSX-specific,
> and so is safe and portable for a common development environment (Ant
> script...) t
Hello,
Thanks, the -XX:+StartAttachListener option did the trick.
I'm assuming that this is a cross-platform switch, with nothing
OSX-specific, and so is safe and portable for a common development
environment (Ant script...) that runs on OS X, Windows, and Linux?
(obviously, we wouldn't use an in
Another workaround (thanks Alan Bateman) is to run the application with
-XX:+StartAttachListener since this avoids the need for signals.
/Staffan
On 14 okt 2013, at 10:19, Staffan Larsen wrote:
> Taking another look, I think this is the same problem as reported in:
> http://mail.openjdk.java.
Taking another look, I think this is the same problem as reported in:
http://mail.openjdk.java.net/pipermail/serviceability-dev/2013-August/011318.html
The bug report is at: https://bugs.openjdk.java.net/browse/JDK-8023786
A workaround may be to run the application with -Xverify:none until an up
The ConnectionFailedSSL1 and ConnectionFailedSSL2 messages should read:
Secure connection failed. Retry insecurely?
The connection to {0} could not be made using SSL.
Would you like to try without SSL?
(Username and password will be sent in plain text.)
Pressing 'Insecure' will then connect with
