Skip to main content
J
jessh12-Amethyst
12-Amethyst
January 7, 2011
Question

ProE embedded browser performance issue.

  • January 7, 2011
  • 16 replies
  • 2036 views
First off, the temp patches are to run Windchill *clients* with Java 6
Update 19 and higher.

Secondly, I believe the correct temp patch is 9.1-M050_TP23 -- but I'm
no expert on our temp patches.

Finally, the best solution overall is to move to R9.1 M060 as it
contains lots of other fixes (as all MORs do). I've seen numerous cases
where the customer and PTC technical support and R&D spent weeks working
together to troubleshoot and diagnose an issue -- only to find that it
was an issue that was already fixed in an MOR that was readily available
when the customer encountered the issue. Yes, it would be nice if we
could automatically say "that's issue ___" that we already fixed, but it
is often far from this obvious. Selectively applying temp patches
rather than moving to the latest available MOR is asking to fall into
this situation.

--
Jess Holle

16 replies

Show previous replies
D
davehaigh13-Aquamarine
13-Aquamarine
January 10, 2011
One more thing you ought to look at is the Windchill Client Inspector. You can download it from PTC and then run it on the client machine.

There's also a Windhill Configuration Assistant to test your server

David Haigh
S
SteveVinyard1-Visitor
1-Visitor
January 11, 2011
If you use un supported software versions in conjunction with PTC’s software you will traditionally see a lot of anomalies like this. I’m not saying that is 100% of your issue but certainly getting on a supported version of Java is extremely important, especially if you are seeing problems.

Latest Supported Java - 1_6_18
Windows 7 32bit 64bit Not fully supported on M030 of PDMLink 9.1 (I think it starts with M040) with the Pro/E WGM

I think your testing verifies a lot of this as well. You are only seeing problems when using the more complex WGM functions within Pro/E (i.e. Checkin -out).

It’s very important to always consult the reference documentation (software matrixes) for PDMLink as there are so many working pieces that go together when using a web based tool.

J
jessh12-AmethystAuthor
12-Amethyst
January 11, 2011
On 1/11/2011 8:41 AM, Steve Vinyard wrote:
>
> If you use un supported software versions in conjunction with PTC’s
> software you will traditionally see a lot of anomalies like this. I’m
> not saying that is 100% of your issue but certainly getting on a
> supported version of Java is extremely important, especially if you
> are seeing problems.
>
> Latest Supported Java - 1_6_18
>
This is inaccurate. Wherever (i.e. in whichever product versions and
client vs. server) Windchill supports Java 6 we support all updates of
Java 6 from the minimum version stated in the platform support matrix to
the very latest update. Currently the latest Java 6 release is Java 6
Update 23, which is thus supported wherever we support Java 6.

As already noted, Oracle caused some client regressions with changes
they made in Java 6 Update 19 and 20. These have been addressed by
readily available temp patches.

It should also be clear that when Java is not being used by the client
whichever version of the Java Plug-In you have installed won't impact
the client. Rather, the Java Plug-In version will only impact pages
containing applets and/or Java Web Start applications (PSE).

--
Jess Holle

S
SteveVinyard1-Visitor
1-Visitor
January 11, 2011
Good to know, for sure. Unfortunately none of that is on the reference documentation and temp patches, as a PTC best practice, should be run through on your development env. - tested and validated which can be quite a bit of effort and not everyone has a dev environment. I think for the most part sticking with the documentation is certainly the easiest\safest route to stay with.

At a core, an uncontrolled client environment can lead to poor client experience with Windchill as it depends on several third party applications. Too many Java versions are left to automatically update, web browsers are updated without thought to Windchill’s compatibility and finally operating systems can move beyond Windchill’s support without upgrades. These are things that in the end need to be controlled, tested and considered when moving forward with the other critical components to ensure a more worry free environment.


[cid:image001.gif@01CBB169.E8EBEFD0]

Steve Vinyard
Application Engineer
J
jessh12-AmethystAuthor
12-Amethyst
January 11, 2011
The documentation is rather explicit about the "or higher" policy when
it comes to Java version support -- unless this changed recently.

But, in general, yes, uncontrolled updates on the client may push one
past what PTC has managed to test and/or support at that point.

S
SteveVinyard1-Visitor
1-Visitor
January 11, 2011
It’s only ever said that higher versions are “expected” to work to the best of my knowledge. All just trivial details, but I certainly encourage my users to avoid staying with anything other than what the documentation supports as it avoids the headaches like we’ve seen Java cause this year. Yeah it can be trivial for some but in a larger environment it can certainly create a lot of headaches.

[cid:image001.gif@01CBB17A.FF8EDBB0]

Steve Vinyard
Application Engineer
Terms & ConditionsAccessibility statement