Thursday Mar 27, 2014

Tip: Set JVM Heap Size with 32b and 64b JVMs

Hi all,

I wanted to share a tip I learned about the hard way recently.   If you are using AutoVue with large 3D models it is often valuable to increase the maximum heap size available to the AutoVue client. 

However, this can be unexpectedly tricky if you have both 32b and 64b Java virtual machines installed - the traditional way to do it is to select Java from the windows control panel and set the heap size there.   However if you have both 32b and 64b JVMs installed, that control panel will only give access to the 64b JVMs - you won't be able to change the 32b JVM settings there.

If you are running a browser that is 32b - you will need to change the 32b JVM settings - and the way to do this is slightly counter-intuitive. In the 64b java control panel accessed through the windows control panel, go to the Advanced tab, and scroll to the very bottom and turn on "Place Java icon in system tray".  
Screenshot - place java in system tray
Then start AutoVue the way you do normally.   You should see a Java icon appear in the windows sytem tray at the bottom of your screen. 

Screenshot - System Tray

Right click on that icon, and select  'Open Control Panel' - from here if you change the heap size parameters it will do it for the JVM that is actually running AutoVue.

Screenshot - Java Environment Settings

If you want to be completely sure whether you are setting the parameters for the 32b or 64b version - look at the "Path" field of the "Java Runtime Environment" settings - if you see "Program Files (x86)" then it is the 32b version.


Hope this helps!!

Friday Jan 17, 2014

Java 7u51 and AutoVue

Hello all - As you may be aware, Java 7u51 was released earlier this week.  This release includes a lot of important security fixes for java - However these fixes do have some impact on users of the AutoVue client.

The first potential impact is that all applets (including the AutoVue client) must define a 'permissions' attribute in order for them to run.  We released a patch for all supported versions of AutoVue late last year that included this attribute.

The other issue is that 'LiveConnect', which is what allows Javascript to call Java code, is disabled in Java 7u51.  Most AutoVue integrations, including our integrations to Agile PLM, Web Center Content, and Documentum, make use of this mechanism to open files, start comparing files, and various other operations.  

Additionally, some older versions of Java, including Java 7u45, will disable LiveConnect once they 'notice' that Java 7u51 is available, so if a user is prompted to upgrade to Java 7u51 and refuses, LiveConnect will also be disabled.

To renable 'LiveConnect' in Java 7u51, the easiest approach is to make use of the 'Exception Site' configuration.  This configuration allows a user to indicate that a certain set of URLs are trusted - and any Java code provided from those URLs will have LiveConnect enabled.  

The 'Exception Site' list can be configured by an individual user by going into the Java control panel, but it is ultimately controlled by a text file stored inside the local Java deployment - so administrators can update the file centrally, and then push the file out to all members of an organization who need to use AutoVue.

We've published KM note 1615032.1 with more details on how to deal with these issues.

Friday Jan 03, 2014

Patches Available to Assist with Newer Java Releases

First off - best wishes to all of you for a very happy new years!

 To follow up on Graham's post yesterday, some of you may have noticed that after upgrading to Java 7u45 there is an additional warning indicating "This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute".   I wanted to point out that we expect that the next java security update will start to enforcing the blocking of applets without the Permissions attribute - this means that the out of the box version of the AutoVue client will stop running after this java update is applied.   We have created patches for all supported versions - the patches, along with some additional details, are listed in the KM note Graham mentions: - KM 1594439.1

Patches that install the updated client properly on Agile PLM systems are underway and will be available soon.

If you have already moved to Java 7 update 45, or plan to move to future updates or Java when they are available, we highly recommend that you install these patches ASAP.

Thursday Jan 02, 2014

Understanding the Impact of Newer Java Versions on AutoVue Client/Server Deployment

Keeping up with the latest Java Runtime Environment (JRE) updates is both a priority and a challenge for most organizations. Similarly, Oracle’s applications that leverage the JRE by way of client-side applets must also ensure these applications continue to work properly in light of the JRE updates.

For AutoVue – specifically AutoVue Client/Server Deployment in which the most common client implementation is a Java applet – certain JRE updates have notable impact. In these cases, all efforts are made to fully detail the impact through alerts in the My Oracle Support knowledge base. In addition, when necessary product patches will be provided by Oracle to address issues between the AutoVue client and the newer JRE versions.

The two most recent examples are detailed in the following knowledge base articles – recommended reading for all AutoVue Client/Server Deployment administrators:

  • KM Note 1553322.1 – Java SE 7u21 Changes to the Java Browser Plug-in Behavior, Getting Message: "Security Warning - Do you want to run this application?" When Using AutoVue Client/Server Deployment With Java–based Customizations
  • KM Note 1594439.1 – AutoVue Client Usage with Java 7u45

In addition to being posted as ‘Alerts’ in the knowledge base so that they show up directly on your My Oracle Support dashboard (if configured properly), these types of alerts are typically also posted through the Oracle Support team’s quarterly newsletter.

About

The authors of this blog are members of the AutoVue Enterprise Visualization team at Oracle. The views expressed on this blog reflect those of the members and do not necessarily reflect the views of Oracle.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today