URL Process Extension (URL PX) Deployed in Wildfly Server Fails with Error 'Session Has Been Closed' When Account Is Switched, to Connect to Agile (Doc ID 2791066.1)

Last updated on AUGUST 15, 2024

Applies to:

Symptoms

When deployed in Wiildfly server, URL PX gets connection error when PX tries to connect to Agile using another account

ERROR

2020-06-03 10:59:54,510 ERROR [stderr] (default task-6) Error code : 60099
2020-06-03 10:59:54,510 ERROR [stderr] (default task-6) Error message :Session has been closed.
2020-06-03 10:59:54,510 ERROR [stderr] (default task-6)
2020-06-03 10:59:54,510 ERROR [stderr] (default task-6)  at com.agile.api.common.Security.doAs(Security.java:111)
2020-06-03 10:59:54,510 ERROR [stderr] (default task-6)  at com.agile.api.pc.Session.getCurrentUserInfo(Session.java:1346)

STEPS

The issue can be reproduced at will with the following steps:

1. URL PX is configured with Web Proxy (80 port)
2. User triggers the PX,
3. PX gets connection to Agile system
4. User do couple of operations and save the modified data.
5. PX connects to Agile server by using another high privilege account, eg:-admin
6. PX fails with error.
7. PX configuration with port 7001 works well when steps 2-5 are performed.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.