Skip to main content
borourke11-Garnet
11-Garnet
February 9, 2011
Question

Windows 7 and PDMLink 9.1 M050 Workflow Administrator

Our NASA center is pushing Windows 7 out to the community and we have found that when you go to the Workflow Administrator to view or edit a workflow, a blank screen appears. There are no errors thrown in the Java console(we are using 1.6.0_23). We have a call in with PTC, but so far they are stumped. Just curious if anyone else has seen this. Thanks and Happy Mardi Gras to everyone!

Send lawyers, guns, and money...the sh!t has hit the fan!

24 replies

Show previous replies
craymond12-Amethyst
12-Amethyst
February 10, 2011
Jesse,
I was wondering if you could provide more details on the Java 22 and up document management applets issues? I personally see such issues with Java 23. We were hoping Java 23 would be more useful due to its 'login' changes, but we are not pushing it because of issue we see with file upload, etc.

Craig Raymond
Windchill / Web Developer

BAE Systems
Intelligence & Security
IT Operations
600 Main St, Johnson City, NY 13790
Translate
jessh12-Amethyst
12-Amethyst
February 10, 2011
If you see "getCacheDescriptor failed" messages emanating from the
upload applet *and* these messages occur when you use the Java 6 Update
22 (or higher) Plug-In and not when you use the Java 6 Update 21
Plug-In, then you're seeing an issue introduced by Java 6 Update 22.

If you see "getCacheDescriptor failed" messages emanating from the
upload applet when using Java 6 Update 21, then you have a different
issue. [The error message is, unfortunately, far too generic and can
have many wildly disparate underlying causes.]

The Update 22 issue is noted by

access restriction" are found in the Java console logs, despite what
Oracle's release notes state.

If you are impacted by this issue, you can try to examine your DNS, etc,
as suggested in Oracle's release notes. Otherwise a workaround in PTC
code is being worked under SPR #2047075.

--
Jess Holle

On 2/10/2011 11:56 AM, Raymond, Craig (US SSA) wrote:
>
> Jesse,
>
> I was wondering if you could provide more details on the Java 22 and
> up document management applets issues? I personally see such issues
> with Java 23. We were hoping Java 23 would be more useful due to its
> 'login' changes, but we are not pushing it because of issue we see
> with file upload, etc.
>
> *Craig Raymond*
>
> Windchill / Web Developer
>
> BAE Systems
>
> Intelligence & Security
>
> IT Operations
>
> 600 Main St, Johnson City, NY 13790
>
> *From:*Jess Holle [
Translate
craymond12-Amethyst
12-Amethyst
February 10, 2011
Thanks Jess, exactly what I was looking for, and very much appreciated.

Craig Raymond
Windchill / Web Developer

BAE Systems
Intelligence & Security
IT Operations
600 Main St, Johnson City, NY 13790
Translate
achukwuka1-Visitor
1-Visitor
February 11, 2011
Jim,

I have always started windchill services in the order

Apache
PDMLink
Tomcat.

I have never encountered the error you listed below.

Thanks

Alexius C. Chukwuka
IT Analyst, PDP Systems
John Deere Power Systems
Product Engineering Center
*Voice: 319-292-8575
*Mobile: 319-429-5336
*Fax:319-292-6282
*E-Mail: -
CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to Deere & Company, or one of its subsidiaries or affiliates, and are intended solely for the use of the individual or entity to whom they are addressed, shall be maintained in confidence and not disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.
Translate
Anonymous
February 11, 2011

I noticed that several people responded similar as below, with Apache first.
PTC's recommendation is to start Apache last, as you would not want people attempting to get into Windchill until all of the other components are already running.

Am I missing something?

Gerry

In Reply:


I have always started windchill services in the order

Apache
PDMLink
Tomcat.

Translate
achukwuka1-Visitor
1-Visitor
February 11, 2011
Jim,

I don't think it matters for Apache, because even if you start Apache last someone can attempt to login to windchill before Apache completely starts, although Apache starts relatively quickly. The only reason why I start Windchill before Tomcat, is because I have seen cases where starting Tomcat first, results in Tomcat running on one of ports designated for the MethodServer, so when you start windchill, it freaks out and dies and spits out "Port already in use" error. I remember way back when Smiley Happy I started working with WIndchill, we had a PTC consultant who advised us to always start Apache first.

Thanks

Alexius C. Chukwuka
IT Analyst, PDP Systems
John Deere Power Systems
Product Engineering Center
*Voice: 319-292-8575
*Mobile: 319-429-5336
*Fax:319-292-6282
*E-Mail: -
CONFIDENTIALITY. This electronic mail and any files transmitted with it may contain information proprietary to Deere & Company, or one of its subsidiaries or affiliates, and are intended solely for the use of the individual or entity to whom they are addressed, shall be maintained in confidence and not disclosed to third parties without the written consent of the sender. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error and that any use, dissemination, forwarding, printing, or copying of this electronic mail is strictly prohibited. If you have received this electronic mail in error, please immediately notify the sender by return mail.
Translate
MikeLockwood22-Sapphire I
22-Sapphire I
February 11, 2011
Restarting after a scheduled cold backup for example should not be too sensitive users attempting to log on and start working. But - If you ever need to restart during working hours and do not have a good way to notify all users, it's night and day different depending on when Apache is started.

Best results when users may be attempting to log on are from bringing up Windchill and Tomcat and allow them to stabililze before bringing up Apache.
Translate
ddemay1-Visitor
1-Visitor
February 12, 2011
No technically you are correct. Some people don't even restart apache, they just throw a different resource up there that is redirected to during downtime. Takes some config but your users know it won't be long.

For those that do restart apache and answer this question, it is highly probable its during downtime window or scheduled maintenance and so the likelyhood someone makes a request to apache is significantly low.


Sent from my Verizon Wireless BlackBerry
Translate
SteveVinyard1-Visitor
1-Visitor
February 14, 2011
All running as a service:

1-oracle (rarely restart this)
2-WindchillDS
3-Apache
4-Tomcat
5-Windchill

A lot of systems will experience errors when booting up after a backup or restart if their backup script simply "stops" the Windchill service. I've found it MUCH more stable to include a "C:\ptc\Windchill\bin\windchill stop" command BEFORE stopping the Windchill service (windows service). When starting backup you should only need to start the service.

The issue around this seems to be that stopping the windows server (Windchill) doesn't kill the server manager or method servers all the time.

[cid:image001.gif@01CBCC3E.F287B610]

Steve Vinyard
Application Engineer
Translate
DanielReid12-Amethyst
12-Amethyst
February 15, 2011
That's really interesting because the recommendation I got from at least
some PTC folks was to start Apache first, then Tomcat, then Windchill.
Some suggested it really doesn't matter.

I have seen that error this thread started with though but had not
experienced a problem with startup.
Translate
Show more replies
Terms & ConditionsAccessibility statement