E-IB: PeopleTools 8.54 remote node ping fails when using dedicated application server. (Doc ID 1965234.1)

Last updated on JUNE 29, 2015

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.54 and later
Information in this document applies to any platform.

Symptoms

On : PeopleTools 8.54, Integration Broker

When attempting to use an 8.54 gateway to ping a remote node (such as a Peopletools 8.52 system), when using a dedicated IB domain the local node will not ping.

The following error occurs:

ERROR
-----------------------
 Result: Integration Gateway: No response received from Gateway (158,10829)


"PeopleSoftTargetConnector - The appserver may be down.  Check Appserver URL or Domain Password. (158 "

The errorLog.html shows:

"bea.jolt.ServiceException: Invalid Session"

The PIA_stderr logs shows:
"bea.jolt.SessionException: TPEPERM - bad permissions"


PIA_weblogic log file on the 8.54 system contians:
spec-version:3.0]] Servlet failed with an Exception
java.lang.NullPointerException
at java.util.Hashtable.hash(Hashtable.java:262)
at java.util.Hashtable.get(Hashtable.java:459)
...

com.peoplesoft.pt.integrationgateway.framework.SessionPool.getSession(SessionPool.java:60)
at
com.peoplesoft.pt.integrationgateway.framework.SessionPoolManager.getSession(SessionPoolManager.java:78)
at
com.peoplesoft.pt.integrationgateway.framework.IntegrationServiceClient.sendRequestToServer(IntegrationServiceClient.java:122)
...



REPLICATION STEPS
=================
Two systems, 8.52 and 8.54 (Note this can also be reproduced with remoted nodes on other releases than 8.52 when using the 8.54 gateway)
1) On the 8.52 with Two installed application servers, Appserver 1 for users, Appserver 2 dedicated for Integration broker and pubsub services.  No users have yet logged into the dedicated IB application server.
a) Configure the PIA to direct user traffic inly to Appserver 1
b) Login to the 8.52 system, verify that you are logged in using application server Appserver 1
Setup local IB gateway to point to the remote 8.54 gateway url
c) While still logged into the 8.52 system, Add the remote (8.52) nodes to the 8.54 gateway properties using Appserver 2 and SAVE.
d) Ping the remote node

Result: Integration Gateway: No response received from Gateway (158,10829)
etc.


NOTE: Changing to the LOCAL 8.52 gateway and ping the nodes (SUCCESS).


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms