Configuration Troubleshooting
Troubleshooting Prerequisites
This section assumes you have installed and configured all of the components as instructed.
Windchill Side
SYMPTOM
The job has started and the first collection step has been in progress for a long time. You see the following error message:
WARNING: Subscribing Windchill Skipped
CAUSE
Windchill failed to subscribe to Message Oriented Middleware. Configuration information was incorrectly entered during installation. You need to update the Windchill Gateway Adapter Property Editor in Info*Engine Administration, and manually subscribe to Message Oriented Middleware.
SOLUTION
1. Access the following properties and see if they have been entered correctly:
◦ JMS Base URI in Core JMS Properties
◦ Queue Connection Factory in Core JMS Properties
If they are not correct, update the properties.
2. Update the properties in the Property Editor as follows:
3. In the wt.properties file check the queue name com.ptc.windchill.dpimpl.distproc.impl.queuename.
If you need to modify this name, use xconfmanager. The queue name must match the queue name defined in the configuration.properties file in the FPLM Server/dpat directory.
4. Restart the method server, or subscribe manually to Message Oriented Middleware as follows:
• Run the following task in a web browser
(For a queue name having direction)
(For an inqueue name having no direction)
For example:
http://fgw-2.ptcnet.ptc.com/Windchill/servlet/IE
/tasks/com/ptc/dpimpl/subscribe.xml?
QUEUE=WCLISTEN&EXECUTE_TASK=
/com/ptc/dpimpl/delegateAction.xml&JMS-SERVICE=SunMQ
FORAN Gateway Adapter Side
SYMPTOM
Windchill Gateway for FORAN is installed. All gateway adapters are configured and running. You start a job for a particular process, but the gateway adapter does not receive any message in the adapter console.
The job shows that the step for that adapter (collect, export or import) is complete or failed. The diagnostic page shows that it is proceeding correctly.
CAUSE
Adapter names could be in conflict. Your adapter name registered with Windchill might be conflicting with an adapter already running on another client. Messages might be being received on that other adapter.
SOLUTION
1. Cross-check all the adapter names that are registered (open Windchill DS and navigate to > .
2. See if any of the adapters share the same name.
3. Stop all but one of the adapters with a duplicate name.
4. Run the configuration utility again on each of those adapters to provide a unique adapter name.
Adapter Throws Exception
SYMPTOM
An adapter throws an exception while starting.
CAUSE
Change the localhost to the actual hostname in the Queue Connection Factory that is used by this adapter (see
Create LDAP Entries For Connection Factory Administered Objects).
SOLUTION
Restart the Windchill server.
SYMPTOM
An adapter throws the following exception:
(com.infoengine.util.IEResource/115)
com.infoengine.exception.fatal.IEFatalServiceException:
Lookup of Administered object with
uri <your_queue_name> returned null.at
com.infoengine.messaging.MsgService.lookupAdminObject
(MsgService.java:1273)at com.infoengine.messaging.MsgService
.lookupQueue(MsgService.java:1289)at com.infoengine.
messaging.MsgService.getQueueListener(MsgService.java:
CAUSE
The queue name is wrongly configured with the adapter.
SOLUTION
Manually edit the config.properties file or configuration.properties file in the FPLM Server/dpat directory to correct the queue name.
SYMPTOM
An adapter throws the following exception:
(com.infoengine.util.IEResource/115) com.infoengine.exception.
fatal.IEFatalServiceException: Lookup of Administered object
with uri <your_connection_factory> returned null. at
com.infoengine.messaging.MsgService.lookupAdminObject
(MsgService.java:1273)at com.infoengine.messaging.MsgService.
lookupConnectionFactory(MsgService.java:1327)at com.infoengine.
messaging.MsgService.getConnectionFactory(MsgService.j
CAUSE
The JMS Base URI or the queue connection factory was incorrectly entered during configuration.
SOLUTION
Manually edit the config.properties file or configuration.properties file in the FPLM Server/dpat directory to correct the JMS Base URI or queue connection factory.
SYMPTOM
An adapter throws the following exception:
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at com.infoengine.au.DefaultServerSocketFactory.
createServerSocket(DefaultServerSocketFactory.java:42)
at com.infoengine.au.SocketAccess.createServerSocket
(SocketAccess.java:707)at com.infoengine.au.
SocketAccess.initialize(SocketAccess.java:318)
at com.infoengine.au.SocketAccess.<init>(SocketAccess.java:237)
at com.ptc.dpa.toolkit.adapter.core.DPAdapterMain.main
(DPAdapterMain.jav
CAUSE
The adapter port is already taken or busy. You must change the configuration of the adapter to an unused port.
SOLUTION
Manually edit the config.properties file or configuration.properties file in the FPLM Server/dpat directory to change the port number.
SYMPTOM
An adapter gets a job message, completes the first step (collect), and sends back a message to the gateway process controller in Windchill. But Windchill never receives the message, and the job does not proceed further. The message queue shows the message from the adapters.
CAUSE
The adapter could be wrongly configured with the Windchill instance name.
SOLUTION
Manually edit the configuration.properties file in the FPLM Server/dpat directory to change the Windchill instance name.
SYMPTOM
An adapter throws an exception with any of the following messages:
• The path specified does not contain the public key
• Unable to read the public key
CAUSE
Either the public key is not copied in the gateway adapter home directory, or the copied public key is not correct.
SOLUTION
1. Contact the gateway administrator and ask for the public key for your adapter.
2. Copy the public key in the gateway adapter home directory.
