Sign in to Cloud. Access your cloud dashboard, manage orders, and more. Sign up for a free trial. Download Minecraft for your PC or Mac. Create, explore and survive! REALMS Own an always-online Minecraft world. Invite nice people to join! Creating a shortcut, etc.). You will need Java, and some dependencies, most of which should already be present on common linux desktops. This is definitely the 'some assembly required' option though. Instagram for mac desktop. Java manual download page. Get the latest version of the Java Runtime Environment (JRE) for Windows, Mac, Solaris, and Linux. Download Help. Java Downloads for All Operating Systems. Oracle Java (Version 7 and later versions) requires an Intel-based Mac running Mac OS X 10.7.3 (Lion) or later and administrator privileges for.
- Download Java 7 For Mac Os
- Java 7 Mac Os X 10.6.8
- Get Java 7 For Mac
- Java 7 Mac Os
- Java 7 For Mac Os X
- Java
Contents
Introduction
This document describes how to troubleshoot issues with Java 7 on Cisco AnyConnect Secure Mobility Client, Cisco Secure Desktop (CSD)/Cisco Hostscan, and clientless SSL VPN (WebVPN).
Note: Cisco bug IDs marked as investigative are not restricted to the symptoms described. If you face issues with Java 7, ensure that you upgrade the AnyConnect client version to the latest client version or to at least the 3.1 maintenance release 3 version available on Cisco Connection Online (CCO).
General Troubleshooting
Run the Java Verifier in order to check if Java is supported on the browsers in use. If Java is enabled properly, review the Java console logs in order to analyze the problem.
Windows
This procedure describes how to enable the console logs in Windows:
- Open the Windows Control Panel, and search for Java.
- Double-click Java (the coffee cup icon). The Java Control Panel appears.
- Click the Advanced tab.
- Expand Debugging, and select Enable tracing and Enable logging.
- Expand Java console, and click Show console.
Mac
This procedure describes how to enable the console logs on a Mac:
- Open System Preferences, and double-click the Java icon (coffee cup). The Java Control Panel appears.
- Click the Advanced tab.
- Under Java console, click Show console.
- Under Debugging, click Enable tracing and Enable logging.
Specific Troubleshooting
AnyConnect
For AnyConnect-related issues, collect the Diagnostic AnyConnect Reporting (DART) logs as well as the Java console logs.
Windows
Cisco bug ID CSCuc55720, 'IE crashes with Java 7 when 3.1.1 package is enabled on the ASA,' was a known issue, where Internet Explorer crashed when a WebLaunch was performed and AnyConnect 3.1 was enabled on the headend. This bug has been fixed.
You might encounter issues when you use some versions of AnyConnect and Java 7 with Java apps. For further information, see Cisco bug ID CSCue48916, 'Java App(s) Break when using AnyConnect 3.1.00495 or 3.1.02026 & Java v7.'
Issues with Java 7 and IPv6 Socket Calls
If AnyConnect does not connect even after you upgrade the Java Runtime Environment (JRE) to Java 7, or if a Java application is unable to connect over the VPN tunnel, review the Java console logs and look for these messages:
These log entries indicate that the client/application makes IPv6 calls.
One solution for this issue is to disable IPv6 (if it is not in use) on the Ethernet adapter and the AnyConnect Virtual Adapter (VA):
A second solution is to configure Java to prefer IPv4 over IPv6. Set the system property 'java.net.preferIPv4Stack' to 'true' as shown in these examples:
- Add code for the system property to the Java code (for Java applications written by the customer):
- Add code for the system property from the command line:
- Set the environment variables _JPI_VM_OPTIONS and _JAVA_OPTIONS in order to include the system property:
For additional information, refer to:
A third solution is to disable IPv6 completely on Windows machines; edit this registry entry:
For additional information, see How to disable IP version 6 or its specific components in Windows.
Issues with AnyConnect WebLaunch After Java 7 Upgrade
Cisco JavaScript code previously looked for Sun as the value for the Java vendor. However, Oracle changed that value as described in JDK7: Java vendor property changes. This issue was fixed by Cisco bug ID CSCub46241, 'AnyConnect weblaunch fails from Internet Explorer with Java 7.'
Mac
No issues have been reported. Tests with AnyConnect 3.1 (with the WebLaunch / Safari / Mac 10.7.4 / Java 7.10 configuration) show no errors. Star war the old republic for mac.
Miscellaneous
Issues with Java 7 Apps on Cisco AnyConnect
Cisco bug ID CSCue48916, 'Java App(s) Break when using AnyConnect 3.1.00495 or 3.1.02026 & Java v7,' has been filed. Initial investigation indicates that the issues are not a bug on the client side, but might be related to the Java virtual machine (VM) configuration instead.
Previously, in order to use Java 7 apps on the AnyConnect 3.1(2026) client, you unchecked the IPv6 virtual adapter settings. However, it is now necessary to complete all of the steps in this procedure:
- Install AnyConnect Version 3.1(2026).
- Uninstall Java 7.
- Reboot.
- Install Java SE 6, update 38, available on the Oracle web site.
- Navigate to the Java 6 control panel settings, then click the Update tab to upgrade to the latest version of Java 7.
- Open a command prompt and enter:
- Log in with AnyConnect, and the Java apps should work.
Note: This procedure has been tested with Java 7 updates 9, 10, and 11.
CSD/Hostscan
For CSD/Hostscan-related issues, collect the DART logs as well as the Java console logs.
In order to obtain the DART logs, the CSD logging level must be turned to debugging on the ASA:
- Navigate to ASDM > Configuration > Remote Access VPN > Secure Desktop Manager > Global Settings.
- Turn up CSD logging to debugging on the Cisco Adaptive Security Device Manager (ASDM).
- Use DART in order to collect the CSD/Hostscan logs.
Windows
Hostscan is susceptible to crashes similar to those described previously for AnyConnect in Windows (Cisco bug ID CSCuc55720). The hostscan issue has been resolved by Cisco bug ID CSCuc48299, 'IE with Java 7 crashes on HostScan Weblaunch.'
Mac
Issues with CSD Versions 3.5.x and Java 7
In CSD 3.5.x, all WebVPN connections fail; this includes AnyConnect web launches. The Java console logs do not reveal any problems:
If you downgrade to JRE 6 or upgrade CSD to 3.6.6020 or later, the Java console logs do reveal the problems:
The resolution is to upgrade CSD or downgrade Java. Because Cisco recommends that you run the latest version of CSD, you should upgrade CSD, rather than downgrade Java, especially since a Java downgrade can be difficult on a Mac.
Issues with Chrome and Safari with WebLaunch on Mac 10.8
Issues with Chrome and Safari are expected behavior:
- Chrome is a 32-bit browser and does not support Java 7.
- Chrome has never been an officially supported browser for WebLaunch.
- Mac 10.8 disabled the use of Java 7 on Safari, and older versions of Java are not enabled by default.
If you already have Java 7 installed, the resolutions are:
- Use Firefox.
- Enable Java 7 on Safari:
- Verify that Java 7 is installed on the Mac and that the Mac has been restarted. Open Firefox, and go to the Java Verifier.
- Open Safari, and go the Java Verifier again. You should now see this screen:
- Disable Java 7, and enable Java SE 6 provided by Apple.
Tip: If you do not have Java installed or you have an older version of Java, you are likely to see the error message 'Java blocked for this web site' on java.com . See Java updates available for OS X on August 28, 2013 on the Apple support forum for information on installation of Java updates.
Issues with Safari with WebLaunch on Mac 10.9
If you you are on Mac 10.9 and already have the Java plugin enabled (as described in the Issues with Chrome and Safari with WebLaunch on Mac 10.8 section), the WebLaunch might continue to fail. All Java applets are initiated, but the browser simply continues to spin. If Java logs are enabled as described in the General Troubleshooting section, the logs quickly fill up as shown here:
Look for this type of entry earlier in the log:
This indicates that you are encountering Cisco bug ID CSCuj02425, 'WebLaunch on OSX 10.9 fails if java unsafe mode is disabled.' In order to workaround this issue, modify the Java preferences so Java can run in unsafe mode for Safari:
- Click Preferences.
- Click Manage Website Settings.
- In the Security tab, select Java, and note that Allow is selected by default.
- Change Allow to Run in Unsafe Mode.
WebVPN
For WebVPN issues related to Java, collect this data for troubleshooting purposes:
- Output from the show tech-support command.
- Java console logs with and without Adaptive Security Appliance (ASA) as explained in the General Troubleshooting section.
- WebVPN captures.
- HTTP watch captures on local machine with and without the ASA.
- Standard packets captures on the ASA and on the local machine.
- On the local machine, these captures can be done with Wireshark.
- For information on how to capture traffic on the ASA, see Configuring Packet Captures.
- All jar files downloaded to the Java cache when going through the ASA. This is an example from the Java console:
In this example, 6a0665e9-1f510559.idx is the cached version of mffta.jar 7. If you do not have access to these files, you can collect them from the Java cache when using direct connection.
A test setup can expedite the resolution.
Security Features in Java 7 U51 and How That Affects WebVPN Users
Recently announced changes scheduled for Java 7 update 51 (January 2014) have established that the default security slider requires code signatures and the Permissions Manifest attribute. In summary, all Java applets require:
- to be signed (Applets and Web Start applications).
- to set the 'Permissions' attribute within the Manifest.
The applications are affected if it uses Java started through a web browser. Applications run from any where outside a web browser are fine. What this means for WevVPN is all the client plugins that are distributed by Cisco could be impacted. Since these plugins are not maintained or supported by Cisco, Cisco cannot make changes to the code signing certificate or to the applet in order to ensure it complies with these restrictions. The proper solution for this is to use the temporary code signing certificate on the ASA. ASAs provide a temporary code signing certificate to sign Java applets (for Java rewriter and plugins). The temporary certificate lets Java applets perform their intended functions without a warning message. ASA administrators should replace the temporary certificate before it expires with their own code signing certificate issued by a trusted certificate authority (CA). If this is not a viable option, the workaround is to complete these steps:
- You can use the Exception Site list feature on the end client machine's Java settings in order to run the applications blocked by security settings. The steps to do this are described in Issues with Safari with WebLaunch on Mac 10.9.
- You can also lower the Java Security settings. This setting is also set in the client machine's Java settings as shown here:
Warning: The use of the these workarounds still gives you some errors, but Java does not block the application as it would have done without the workarounds in place.
Windows
Applications that launch Java applets have been reported to fail over WebVPN after an upgrade to Java 7. This problem is caused by the lack of Secure Hash Algorithm (SHA)-256 support for the Java rewriter. Cisco bug ID CSCud54080, 'SHA-256 support for webvpn Java rewriter,' has been filed for this issue.
Applications that start Java applets through the portal with Smart Tunnel might fail when JRE7 is used; this is most common with 64-bit systems. In the captures, note that the Java VM sends the packets in clear text, not through the Smart Tunnel connection to the ASA. This has been addressed by Cisco bug ID CSCue17876, 'Some java applets won't connect via smart tunnel on windows with jre1.7.'
Greenhorn
posted 5 years agoI have been programming in java for a bit now and can generally figure out things. But this one has me stumped. I have a mac and I have recently updated from java 6 to java 7. I had quite a bit of code that was running fine with java 6, but is having problems in java 7. The precise problem is that only the first JFileChooser dialog window in the program will actually show up (the window to select the files). I include a snippet of code below:
Only the open dialog window of chooser1 will show up. The dialog window for chooser2 never shows up. The program acts like the chooser2.show OpenDialog statement is executing and is waiting for me to select a file, but nothing shows up.
As I said code like this (several JOptionChooser dialogs or JOptionPane dialog in a row) ran with no problem before the upgrade to java 7. Now only the first one show up. ??? help!
Only the open dialog window of chooser1 will show up. The dialog window for chooser2 never shows up. The program acts like the chooser2.show OpenDialog statement is executing and is waiting for me to select a file, but nothing shows up.
As I said code like this (several JOptionChooser dialogs or JOptionPane dialog in a row) ran with no problem before the upgrade to java 7. Now only the first one show up. ??? help!
Sheriff
posted 5 years agoWelcome to the Ranch!
I can't reproduce the issue on my Windows / Java 7 box. Are you sure you're running this code on the Event Dispatch thread?
I can't reproduce the issue on my Windows / Java 7 box. Are you sure you're running this code on the Event Dispatch thread?
Greenhorn
posted 5 years agoMartin,
Thank you for your time to reply, but as I said, I am working on a MAC which has 'special' issues.
As far as an event dispatch thread,.. well let me put it this way. If you cut and paste the above code into the
main method of a new class and then compile and run, you should get two file chooser dialog window in a row.
Nothing exotic, nothing more than a novice program would do.
I believe this is a Mac issue and I hope there are others out there (mac users) that might have had the same problem.
Java 7 is the first non-apple version of java available from oracle. As such, there are bugs!! This is the reason that
questions to uninstall java 7 on macs are such popular topics!!
I teach java and and a few of my students that were mac users and upgraded also had this problem. Their solution was to
go back to java 6. I hope to solve this and move on.
Thank you for your time to reply, but as I said, I am working on a MAC which has 'special' issues.
As far as an event dispatch thread,.. well let me put it this way. If you cut and paste the above code into the
main method of a new class and then compile and run, you should get two file chooser dialog window in a row.
Nothing exotic, nothing more than a novice program would do.
I believe this is a Mac issue and I hope there are others out there (mac users) that might have had the same problem.
Java 7 is the first non-apple version of java available from oracle. As such, there are bugs!! This is the reason that
questions to uninstall java 7 on macs are such popular topics!!
I teach java and and a few of my students that were mac users and upgraded also had this problem. Their solution was to
go back to java 6. I hope to solve this and move on.
Sheriff
![Java Java](/uploads/1/3/3/9/133903649/954382933.png)
cate anderson wrote:As far as an event dispatch thread,.. well let me put it this way. If you cut and paste the above code into the
main method of a new class and then compile and run, you should get two file chooser dialog window in a row.
Nothing exotic, nothing more than a novice program would do.
main method of a new class and then compile and run, you should get two file chooser dialog window in a row.
Nothing exotic, nothing more than a novice program would do.
Yes, I can put that code into my main method and it works in my environment. Nevertheless, I wouldn't be so benevolent about it. Swing has a clearly documented requirement that all Swing code must be run on the Event Dispatch thread, and teaching students otherwise is very, very bad, in my opinion. It might work somewhere, but it isn't guaranteed to work. Such code is faulty.
If you take your example, run it on the EDT and it doesn't behave as you expect, then yes, that would mean Java on your platform has problems. I'd suggest to try it (I can't do it myself, not having a Mac) and if it doesn't work, to file a bug with Oracle.
author and jackaroo
posted 5 years agoMartin Vajsar wrote:If you take your example, run it on the EDT and it doesn't behave as you expect, then yes, that would mean Java on your platform has problems. I'd suggest to try it (I can't do it myself, not having a Mac) and if it doesn't work, to file a bug with Oracle.
Emphasis on running it within the Event Dispatch thread - don't file a bug report otherwise.
For what it's worth, running it within Eclipse Kepler (20130919-0819) on my Mac Mountain Lion 10.8.5 (Kernel Version 12.5.0) resulted in the same results you saw.
Download Java 7 For Mac Os
Running it from the command line Java (build 1.6.0_65-b14-462-11M4609) resulted in both dialogs being displayed and both selected files being output:FileName 1:BeerSong.javaFileName 2:AudioHijack.mp3h105:bin andrew$
FileName 1:checkConnectTime.shFileName 2:BeerSong.javah105:bin andrew$
(the h105 is my machine name, bin is the directory I was in, andrew is my login name).
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7Personal blog
author and jackaroo
Java 7 Mac Os X 10.6.8
posted 5 years agoGet Java 7 For Mac
Just went back and checked - I have configured Eclipse to use Java 1.7.0_11.
Bumping it back to 1.6 made it work correctly in Eclipse.
Bumping it back to 1.6 made it work correctly in Eclipse.
The Sun Certified Java Developer Exam with J2SE 5: paper version from Amazon, PDF from Apress, Online reference: Books 24x7Personal blog
Sheriff
posted 5 years agoJava 7 Mac Os
- 1
Andrew, have you run the example as is, or on the Event Dispatch thread? The code using EDT might be:
I'm trying to understand whether this is a Swing bug or not.
I'm trying to understand whether this is a Swing bug or not.
Greenhorn
Java 7 For Mac Os X
posted 5 years agoMartin
I tried your posted code. And it seems to clear up the problem. The code runs as it should.
I use the event dispatcher with my own research programs, but it is a bit overwhelming for novice programers so I don't introduce it until the advanced course. It has never been an issue before which is what floored me.
Andrew, just knowing someone else had seen the issue made me feel less alone!
Thank you both for your effort. I am glad I stopped spinning my wheels and asked for advice. Also very glad to know there are knowledgeable javites out there I can ask question to.
Picture me happy!!!
I tried your posted code. And it seems to clear up the problem. The code runs as it should.
I use the event dispatcher with my own research programs, but it is a bit overwhelming for novice programers so I don't introduce it until the advanced course. It has never been an issue before which is what floored me.
Andrew, just knowing someone else had seen the issue made me feel less alone!
Thank you both for your effort. I am glad I stopped spinning my wheels and asked for advice. Also very glad to know there are knowledgeable javites out there I can ask question to.
Picture me happy!!!
Java
Sheriff
posted 5 years agoGlad to hear the issue is cleared up!
Though I'm not a teacher, I can quite understand that teaching Swing to novice programmers is difficult. I'd suggest just to tell them that they need to put a few lines of code (the SwingUtilities.invokeLater stuff) into their projects as a necessary precondition which will be explained later.
I also think it is better this way. Unlearning bad habits is more difficult than learning the good practices right from the start, in my opinion (an opinion fostered by all that SQL-injection prone code seen in our JDBC forum). But then, perhaps this is why I'm not a teacher..
Though I'm not a teacher, I can quite understand that teaching Swing to novice programmers is difficult. I'd suggest just to tell them that they need to put a few lines of code (the SwingUtilities.invokeLater stuff) into their projects as a necessary precondition which will be explained later.
I also think it is better this way. Unlearning bad habits is more difficult than learning the good practices right from the start, in my opinion (an opinion fostered by all that SQL-injection prone code seen in our JDBC forum). But then, perhaps this is why I'm not a teacher..