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

gmontgomery3-Newcomer
3-Newcomer
February 9, 2011
Bill,
I have seen that. The workaround that I found was to dumb down my Windows7
display mode from True Color 32 bit down to 256 colors. It's not a great
solution but it will at allow you to work with the Workflow Admin page. And
it should also give PTC the clue they need to resolve it. It seems like the
Java 2D graphics API and Windows 7 display drivers are not happy together.

On Windows 7 to change the display mode it's : RMB on wallpaper > Screen
Resolution > List all modes

Greg Montgomery


On Wed, Feb 9, 2011 at 11:05 AM, Bill O'Rourke
<->wrote:

> 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! *
Translate
jessh12-Amethyst
12-Amethyst
February 9, 2011
If there's a Java API vs. graphics driver issue on Windows, then the
solution is to add one or more properties to the JVM options to disable
some of Java's use of Direct* APIs. This is done via the Java Control
Panel.

The primary option to try is

-Dsun.java2d.noddraw=false

This turns off Java's use of DirectDraw and Direct3D completely. See
Translate
cscharbert1-Visitor
1-Visitor
February 10, 2011
Hi Bill,

just try to set

-Dsun.java2d.d3d=false

As startup parameter in your Java Runtime Settings

[cid:image001.png@01CBC91B.5D8F1830]

Cheers,

Christian
Translate
jv83421-Visitor
1-Visitor
February 10, 2011
Good Day All!

I wanted to ask the panel of experts (that's you) what is your order of
start up of Apache, Tomcat and Method Servers? I've always first started
Apache, then Tomcat and lastly PDMLink, but I would always get an error in
my Tomcat catalina.out (see below). For fun this morning I modified my
order to be Apache, PDMLink and then Tomcat and my error went away.

So what is your order of start up?
Option A:
- Apache
- Tomcat
- PDMLink

Option B:
- Apache
- PDMLink
- Tomcat


Error:
Info*Engine servlet: resource URI =
/pdm_data/ptc/Windchill/codebase/WEB-INF/ie.properties
2011-02-10 07:50:48,753 ERROR [main] wt.adapter.LoadBalancer -
wt.util.WTException: wt.util.WTRemoteException: Unable to invoke remote
method; nested exception is:
wt.util.WTRemoteException: Unable to locate method server; nested
exception is:
wt.util.WTRemoteException: Unable to locate method server; nested
exception is:
wt.util.WTRemoteException: Unable to get server; nested exception
Translate
ddemay1-Visitor
1-Visitor
February 10, 2011
Jim,



Appears you have a clustered or load balanced environment. Not everyone has
that, so your process will always be different depending on the
configuration.



Provided Windchill Directory Server is up and running or any other JNDI
connected directory server, MethodServers can run without Tomcat or Apache,
you just can't do much. From a development perspective, there are times
where I know if all I'm doing is writing code that executes on Tomcat JVM or
MethodServer JVM, I'll restart only the desired one.



You will get errors in the log files if users or yourself leave open
browsers with PDMLink in it and apache is still running because it will do
Ajax based session keep alives. I know this because if you leave pdmlink
open in a browser, but clear the HTTP Authentication, it will randomly
prompt you for a userid and password.



The order I choose is:



LDAP/ Directory Server

Apache

Tomcat (many if clustered)

MethodServer(s)



Like I said though, I have tomcat and apache running when editing a workflow
with externally reference code and only the MethodServer needs a bounce.
The answer to this question really just has to keep in mind the JVM process
you are working with and which one uses that code. Because of RMI, this is
possible also. Tomcat being embedded into MethodServer in 10.0, well maybe
Steve Dertien could speak to this more, as I have not seen it, but my guess
is you'll just restart MethodServer(s) and Apache. Would be good for Steve
to give a presentation on this improvement at PTC User.







Dave






Translate
RandyJones20-Turquoise
20-Turquoise
February 10, 2011
On 02/10/11 07:00, Jim VanDragt wrote:
> Good Day All!
>
> I wanted to ask the panel of experts (that's you) what is your order of start
> up of Apache, Tomcat and Method Servers? I've always first started Apache,
> then Tomcat and lastly PDMLink, but I would always get an error in my Tomcat
> catalina.out (see below). For fun this morning I modified my order to be
> Apache, PDMLink and then Tomcat and my error went away.
>
> So what is your order of start up?

1. Oracle (including the listener)
su - oracle -c "dbstart wind"
2. WindchillDS (ldap)
/opt/ptc/Windchill/WindchillDS/server/bin/start-ds --quiet
3. Apache
/opt/ptc/Windchill/Apache/bin/apachectl start
4. Tomcat
/opt/ptc/Windchill/Tomcat/bin/wttomcat_start
5. Windchill server manager and method servers
/opt/ptc/Windchill/Windchill/bin/windchill start

> Option A:
> - Apache
> - Tomcat
> - PDMLink
>
> Option B:
> - Apache
> - PDMLink
> - Tomcat
>
>
> Error:
> Info*Engine servlet: resource URI =
> /pdm_data/ptc/Windchill/codebase/WEB-INF/ie.properties
> 2011-02-10 07:50:48,753 ERROR [main] wt.adapter.LoadBalancer -
> wt.util.WTException: wt.util.WTRemoteException: Unable to invoke remote
> method; nested exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to get server; nested exception is:
> wt.util.WTRemoteException: Unable to locate server manager; nested
> exception is:
> java.rmi.ConnectException: Connection refused to host:
> pdm.hermanmiller.com; nested exception is:
> java.net.ConnectException: Connection refused (errno:239)
> Nested exception is: wt.util.WTRemoteException: Unable to invoke remote
> method; nested exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to get server; nested exception is:
> wt.util.WTRemoteException: Unable to locate server manager; nested
> exception is:
> java.rmi.ConnectException: Connection refused to host:
> pdm.hermanmiller.com; nested exception is:
> java.net.ConnectException: Connection refused (errno:239)
> 2011-02-10 07:50:48,756 ERROR [main] com.infoengine.object.ObjectServiceCache
> - load balancing failed for 'com.hermanmiller.pdm.Windchill', selecting a
> service at random.
> 2011-02-10 07:50:48,770 ERROR [main] wt.adapter.LoadBalancer -
> wt.util.WTException: wt.util.WTRemoteException: Unable to invoke remote
> method; nested exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to get server; nested exception is:
> wt.util.WTRemoteException: Unable to locate server manager; nested
> exception is:
> java.rmi.ConnectException: Connection refused to host:
> pdm.hermanmiller.com; nested exception is:
> java.net.ConnectException: Connection refused (errno:239)
> Nested exception is: wt.util.WTRemoteException: Unable to invoke remote
> method; nested exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to locate method server; nested
> exception is:
> wt.util.WTRemoteException: Unable to get server; nested exception is:
> wt.util.WTRemoteException: Unable to locate server manager; nested
> exception is:
> java.rmi.ConnectException: Connection refused to host:
> pdm.hermanmiller.com; nested exception is:
> java.net.ConnectException: Connection refused (errno:239)
> 2011-02-10 07:50:48,771 ERROR [main] com.infoengine.object.ObjectServiceCache
> - load balancing failed for 'com.hermanmiller.pdm.Windchill', selecting a
> service at random.
>
> *Jim Van Dragt*
> Product Development Systems Analyst/Developer - Lead
> Information Technology
>
> _hermanmiller.com_ <www.hermanmiller.com>
> 616 654 5285 OFFICE
> 616 836 8394 MOBILE
>
> *HermanMiller*
>
>
> -----End Original Message-----


--
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
1525 E North St
PO Box 5060
Salina, KS USA 67401
email: -
Phone: 785-823-3276
Fax: 785-667-2695
------------------------------------------------------------------------

Translate
ArturPonurski1-Visitor
1-Visitor
February 10, 2011
Option A.



Kind Regards,

Artur


Translate
jessh12-Amethyst
12-Amethyst
February 10, 2011
Embedding Tomcat into the method servers in 10.0 means that the method
servers are the Tomcats in the picture as well. Thus to [re]start a
Tomcat, you [re]start a method server and when you [re]start a method
server you [re]start the Tomcat therein. In 10.0 you should still have
Oracle and LDAP running first, but beyond that you only have to start
Apache and Windchill. These can be started in either order, but
Windchill will eventually try to ping itself through Apache, so overall
I'd tend to start Apache then Windchill. You can certainly restart
Apache without restarting Windchill or vice versa.

Translate
RudySeidl1-Visitor
1-Visitor
February 10, 2011

Hello Bill,

What browser are you using? Google Chrome operates horribly with PDMLink. Also if you're using 64-Bit with 64-Bit IE, this will cause issues as well.

Also after Java 6 Update 19, when launching certain functions in PDMLink, you will get a Yes / No prompt. Intuitively you want to select "Yes (recommended)", however, you need to select "No"

_Rudy



Translate
jessh12-Amethyst
12-Amethyst
February 10, 2011
On 2/10/2011 9:19 AM, Rudy Seidl wrote:
>
> Hello Bill,
>
> What browser are you using? Google Chrome operates horribly with
> PDMLink. Also if you're using 64-Bit with 64-Bit IE, this will cause
> issues as well.
>
A 64-bit OS with a 64-bit browser will work fine -- except initially
obtaining a 64-bit Java Plug-In in MSIE. The classid used by the
out-of-the-box configuration specifies the 32-bit Java Plug-In even
under a 64-bit MSIE -- in large part because there is no classid for the
64-bit Java Plug-In.

The end-user workaround is to manually install the 64-bit plug-in prior
to attempting to use it from the 64-bit MSIE browser.

The server-side solution (found in R10) is to have

wt.taglib.util.plugin.clientmods=MSIE HPUX AIX Win64
wt.taglib.util.plugin.clientmoddef.Win64.agentContains.1=Win64
wt.taglib.util.plugin.attr.type=browserapplet
wt.taglib.util.plugin.clientmod.MSIE.attr.type=applet
wt.taglib.util.plugin.clientmod.Win64.attr.type=browserapplet

in your wt.properties. This will use the <applet> rather than <object>
tag for the applet in 64-bit MSIE, which resolves the issue. The
installation of a 64-bit Java Plug-In won't be quite as seamless as that
of the 32-bit Java Plug-In (this is an intrinsic limitation of the
current Java Plug-In), but it works and is certainly better than having
to know to install the Java Plug-In manually prior to attempting to use it.
>
> Also after Java 6 Update 19, when launching certain functions in
> PDMLink, you will get a Yes / No prompt. Intuitively you want to
> select "Yes (recommended)", however, you need to select "No"
>
There are temp patches for this -- or better yet make sure you're using
R9.1 M060 (which has lots of other good fixes therein, anyway).

There is a separate issue specific to the document management applets
and Update 22 and higher as well -- though this only impacts certain
(network) configurations.

--
Jess Holle

Translate
Show more replies
Terms & ConditionsAccessibility statement